A messy knowledge base
Structure
Information can be mapped into models, taxonomies, and reading paths.
Collaboration
What needs to become readable?
Information is gathered, shaped, and shared—so teams can think together across time, formats, and attention spans.
A short note is enough: context, audience, and what “done” looks like.
Signals
When a conversation is useful.
If any of these feel familiar, a first call can be scheduled.
Research that stays stuck
Synthesis
Findings can be shaped into decisions, narratives, and reusable artefacts.
Too much noise
Signal
Priority can be clarified and the essential thread can be kept intact.
Readers drop off
Reading
Hierarchy, rhythm, and pacing can be tuned for calmer attention.
Many stakeholders
Alignment
A shared language can be created across teams, roles, and constraints.
Outputs need continuity
System
Templates and components can keep quality consistent across releases.
Start
How collaboration can begin.
A small sequence is used so intent stays clear and scope stays calm.
-
Context note
Audience, constraints, and the current material are shared in a short email.
-
Signal audit
What matters is identified, what distracts is removed, and the structure is outlined.
-
Prototype
A sample chapter, spread, or module is produced to set the tone and rules.
-
System + delivery
Components are finalized and the full body of work is delivered with guidelines.