Communication and engagement solutions
What an organisation puts in front of people keeps describing a season it already left behind, because nothing marks the moment that should have triggered the update.
What an organisation puts in front of people drifts out of step with what the organisation actually is. A stale website is one instance of that, not the whole of it: the same gap opens in a one-pager still naming a partner who moved on, or an exported snapshot still carrying a figure nobody would stand behind today. Nothing marks the moment that should trigger the correction, so each surface keeps stating what used to be true until somebody happens to notice.
The same source of truth drives every surface the organisation puts in front of people, so an update is triggered by the change itself rather than remembered by whoever last touched the page. The website rebuilds because what it describes changed; everything drawn from the same source, the one-pager, the snapshot, the deck, rebuilds with it, and nothing states two different versions of the same organisation.
One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.
- writes current state
- Current state, replacing the prior value. A registry holds what is true now, not how it got there.
A change in what the organisation is triggers the rebuild of the site and of the exports drawn from the same source.
Each step in the order it runs, and where one stops before the next begins.
- 01RECORDNOT MECHANISED YET A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to MASON.
- 02PROPOSE · toolGAUGE proposes through the target’s own gate, never writes.Nothing in this run reaches it. Hands on to REBUILT SITE.
- 03RUN · toolMASON .Reached from NOT MECHANISED YET. Hands on to BUILD RECORD, REBUILT SITE, SHAREABLE EXPORTS: SNAPSHOT, ONE-PAGER, DESIGN FILES.
- 04RECORDBUILD RECORD A record the run reads, writes or hands on.Reached from MASON. The run parks here.
- 05RECORDREBUILT SITE A record the run reads, writes or hands on.Reached from MASON, GAUGE. The run parks here.
- 06RECORDSHAREABLE EXPORTS: SNAPSHOT, ONE-PAGER, DESIGN FILES A record the run reads, writes or hands on.Reached from MASON. The run parks here.
- 01picked upMASON NOT MECHANISED YET.Matter the run starts from. No member of the suite put it there.
- 02parks hereMASON BUILD RECORD.Build record.Nothing later in this run reads it, so this is where that branch of the run stops.
- 03parks hereMASON REBUILT SITE.Nothing later in this run reads it, so this is where that branch of the run stops.
- 04parks hereMASON SHAREABLE EXPORTS: SNAPSHOT, ONE-PAGER, DESIGN FILES.Nothing later in this run reads it, so this is where that branch of the run stops.
- 05nothing crossesGAUGE REBUILT SITE.This hand-off is not mechanised yet. A person notices, or nobody does.
The rebuild/snapshot itself is a state write.