Client stories
Client stories & reviews
Evidence from documentation audits, knowledge base redesigns, and writing engagements with engineering teams.
“They spent the first week reading our actual pull-request comments before touching the site map. The resulting IA cut our onboarding Slack threads roughly in half — though the API reference still needs a second pass.”
We hired Toolkit Maple for a knowledge base architecture workshop after two wiki migrations left orphaned pages everywhere. The ownership matrix was the useful part; some template suggestions felt too strict for our design system docs, and we adapted those.
The audit report named three conflicting “getting started” guides we had forgotten about. Cleaning those alone saved our solutions engineers hours each week.
Workshop day was dense but practical — we rewrote one runbook live. I would have liked more time on screenshot standards, but the progressive-disclosure exercises stuck with the team.
Extended story: consolidating platform runbooks
A mid-size cloud platform team in Taipei asked for a Documentation System Audit after on-call handovers kept failing on missing context. Over four weeks we inventoried 180+ runbook pages across two wikis, identified twelve topics with three or more conflicting versions, and proposed a single hierarchy with on-call owners.
The team executed the cleanup themselves using our sequence. Three months later they reported fewer escalations during shift changes. We did not rewrite every page; the value was the map and the ownership rules.