Information Architecture for Technical Documents
  • Main
  • Time is $
    • How to save money
    • Risks w/o clean info process
    • Meta-tagged navigation FAQs
    • IA solutions
    • Podcast talks
    • Full ROI example
  • Evergreen
  • AI considerations

​Are you ready to future-proof your content?

Explore our solutions
Request a quote
What We Do Best

Kraft Consulting specializes in:
  • Information Architecture for technical content systems.
  • Docs-as-code migrations using GitHub, MkDocs and static site generators.
  • Developer documentation that supports APIs, SDKs and onboarding.
  • Content audits, metadata planning, and taxonomy development.
  • Long-term knowledge management strategies for scaling organizations.
  • Project management with your tool stack.

Whether you’re modernizing a legacy content system or launching a brand-new documentation platform, we design solutions that save time, cut support costs and improve team performance.

Why It Matters
​

Well-architected information systems do more than help people find what they need. They:​
  • Accelerate your business by reducing wasted effort.
  • Enhance your visibility to partners, clients and regulators.
  • Unlock time and cost efficiencies across teams.
  • Improve compliance and reduce risk through clearer governance.
We believe documentation should be a strategic asset, not a last-minute afterthought.

History Notes

The main "enemies" of information architecture are the the failure to adapt to evolving digital environments, meaning recognizing the complexity, inconsistency, and how poorly organized content becomes without a plan. All of this leads to user frustration and failure to find information. 
  • Volume of data is challenging: Without the proper architecture to organize it, data lacks value and becomes difficult to manage, leading to risk and cost without benefit.
  • No structure or governance: A complete lack of planning or consistent maintenance will cause the information system to become disorganized and chaotic over time. Content must be treated as a "living, breathing thing" that evolves, not a static object.
  • Lack of cross-linking and contextual connections: Without intentional and valuable links to related content, users can hit a dead end, unsure of what to do next. This reduces engagement and the time users spend exploring the site
Picture
About Susan Kraft-Yorke
Consultant | Information Architect | Technical Writer

Information architecture consulting, documentation process redesign,
cross-functional writing strategy roles with AI or platform engineering teams.

Kraft Consulting, LLC (c) 2025​
Request a 30-minute calendar appointment

​Privacy policy  ​
  • Main
  • Time is $
    • How to save money
    • Risks w/o clean info process
    • Meta-tagged navigation FAQs
    • IA solutions
    • Podcast talks
    • Full ROI example
  • Evergreen
  • AI considerations