Strategy management
Strategy Manager: CEO Strategy Layer
Company strategy as reviewable data, not slides: every objective, owner and dependency in one graph.
- status
- In build: the strategy canvas is at 17 of 19 tasks; runs locally, not yet deployed
- Strategy nodes captured as structured data: missions, objectives, initiatives, constraints and the people accountable for them
- Declared relationships between them, 130 approved and 11 rejected on the record, a reviewed graph, not a diagram
- 0New databases. Strategy lives as YAML in git, so a change to the company's direction arrives as a diff someone can approve
Your strategy is out of date the day it is written
Most organisations have a strategy, but very few can tell you what it currently says. It lives in a deck from a planning offsite, and the deck is already out of date.
- Nobody can say what an initiative serves without asking the person who wrote it.
- Objectives and the work delivering them sit in different systems, so drift goes unnoticed.
- Strategy for one business gets quietly applied to another.
- Rejected ideas vanish, so the same argument returns every quarter.
What Strategy Manager does
Strategy Manager holds your company’s strategy as data rather than slides. Every mission, objective, initiative and constraint is written down, linked to what it depends on, and owned by a named person. Today it holds 143 of these items across fifteen types.
- Links are argued, not assumed. Each link between items carries a status: 130 approved and 11 explicitly rejected, so a rejected idea stays on the record as a decision.
- Several businesses, no bleed. Every item records the business it belongs to, so strategy for one is never silently read as strategy for another.
- A canvas for the chains. An interactive board lays out what has to happen before what, connecting events, goals and outcomes into dependency chains.
- It creates the actual work. When something is ready to be real, it creates the project and milestone in the tracker your team already uses, linked back to the strategy that justified it.
- Status is fetched, never copied. Progress on any item is pulled live from the systems doing the work when someone asks, and nothing is written back.
What changes for the business
A change to the company’s direction arrives as a change someone reviews and approves, not a new version of a deck. The reasoning behind a decision is still there a year later. Nothing is hard-deleted, so the history of a decision survives the decision being reversed. An uncertain idea can be captured as a guess without appearing on a rendered map as established fact. The strategy stops being a document somebody owns and becomes a structure the business can question, review and act on.
Security and trust
The safeguards are mostly about not overstating what is known. Strategy content is plain text in a private repository, with no new database, no new service to secure and no copy of the data anywhere else. The canvas can read the strategy but may only make narrow, audited additions or amendments, never deletions.
Where it stands today
Strategy Manager is in build and runs locally today; it is not yet deployed. The canvas is at 17 of 19 tasks. It suits teams comfortable treating strategy the way engineering treats code: reviewed, versioned and open to line-by-line comparison. It fits groups running several businesses where one strategy conversation keeps contaminating another.
See the graph
The fastest way to judge it is to follow one initiative up to the objective it serves and down to the work delivering it.