Visualisation
Can you draw what you're trying to build?
If you can't draw it, you can't build it. When a group can't see the same future, they create turbulence despite best intentions. AI generates images and diagrams on command. Humans generate shared vision — the picture in your head that aligns a team, attracts capital, and survives first contact with reality.
| Without Visualisation | With Visualisation |
|---|---|
| Abstract strategy | Concrete picture |
| Misaligned teams | Shared mental model |
| "I think I understand" | "Now I see it" |
| Build then discover gaps | See gaps before building |
Mental Rehearsal
Visualise the process, not just the outcome:
| Type | What to Picture | What It Trains |
|---|---|---|
| Outcome | The end state — what does success look like? | Motivation, direction |
| Process | Each step of getting there — the moves, the sequence | Preparation, gap detection |
| Failure | What goes wrong — the risks, the obstacles | Contingency planning, resilience |
| Others | How do different stakeholders see this? | Empathy, alignment |
Athletes who visualise the process outperform those who only visualise winning. The same applies to strategy, product, and careers.
Sketch-First Protocol
Before words, before code, before meetings:
| Rule | Why It Works |
|---|---|
| Sketch before writing | Drawing forces spatial thinking — reveals structure that prose hides |
| Rough beats polished | A napkin sketch in 2 minutes communicates faster than a 20-page doc |
| Whiteboard every planning session | Shared visual = shared understanding. Words alone diverge. |
| "Done" as a picture | Describe what it looks like, not just what it does |
You don't need to draw well. You need to draw fast. Quality of thinking matters, not quality of line.
Diagram Types
Different visualisations solve different problems:
| Diagram | Best For | Example |
|---|---|---|
| Flowchart | Sequences and decisions | User journey, process flow |
| Matrix/2x2 | Comparing two dimensions | Priority grid, risk assessment |
| System map | Showing relationships and feedback loops | Architecture, stakeholder map |
| Timeline | Showing sequence over time | Roadmap, project plan |
| Hierarchy | Showing structure | Org chart, category tree |
| Before/After | Showing transformation | Current state vs target state |
Choose the diagram that matches the question. "How does this flow?" = flowchart. "How do these compare?" = matrix. "How do these connect?" = system map.
Shared Vision Protocol
When aligning a team:
- Each person sketches their understanding — Independently, 5 minutes
- Compare sketches — Where do they diverge? That's where misalignment lives
- Build one shared picture — Merge the best elements, resolve conflicts visually
- Reference the picture — In every subsequent meeting, point to it
The gap between two sketches is more honest than any verbal "I agree."
The Shadow
Fantasy. Mistaking the picture for the work. Beautiful diagrams that never ship. Vision without execution. Spending more time on the map than the territory.
By Archetype
| Archetype | Visualisation Style |
|---|---|
| Dreamer | Sees what could be — futures nobody else imagines |
| Engineer | Turns vision into blueprints — architecture diagrams, system maps |
| Coach | Helps others see — makes the invisible visible |
Context
- Creativity — Generating what to visualise
- Presenting — Delivering the vision
- Diagrams — Tools for visual thinking
- Planning — From picture to plan