Schematex
mindmap·Buzan (1970s)·saas, management·complexity 2/3

Quarterly OKRs mindmap

Company OKRs organized as a mindmap — three objectives, each with measurable key results — suited for the all-hands kickoff of a new quarter.

For the chief of staff

Open in Playground →
mindmap·§
↘ preview
100%
Q4 Company OKRs map mindmap with 22 nodes 10 new qualified logos Win rate ≥ 25% Expand enterprise pipeline Net revenue retention ≥ 120% Seat adoption +40% Increase expansion Grow ARR 30% 100% API coverage Zero-downtime cutover Core migration Sub-5-min quickstart 95% doc satisfaction Developer experience Ship Platform v2 8 senior engineers 2 staff PMs Hiring Voluntary attrition < 5% eNPS ≥ 40 Retention Strengthen team Q4 Company OKRs
UTF-8 · LF · 27 lines · 465 chars✓ parsed·2.0 ms·12.0 KB SVG

Scenario

The chief of staff projects this during the Q4 all-hands. Three objectives radiate from the centre; every key result is a leaf with a specific number. The mindmap format reads fast — every person in the company can find their team's objective within three seconds — and it tolerates mid-quarter edits without disturbing other branches.

Annotation key

How to read

The root names the quarter. The three ## branches are the objectives — the things that will be judged at the end of the quarter. Each ### groups key results by theme; the bullets are the actual measurable targets. If a KR can't be reduced to a number, it probably belongs in a planning doc rather than on this mindmap.

Mindmap syntax