The explicit, published record of an engineer's or team's current working context — available to anyone who needs it, without requiring the originator to be online.
Declared state includes: what the person is working on, what is blocked, what decisions have been made, and what the next person needs to know before touching the work. It is the difference between a team whose continuity depends on who is available and a team whose continuity is built into the system.
The opposite of declared state is ambient awareness — the informal, unstructured, often-invisible knowledge that exists only in the heads of people who happen to be online at the same time.
Foundation concept for: declared handoff, StandIn's wrap protocol.
Why Declared state Matters for Distributed Teams
Declared state is the foundation concept that makes async governance possible. Without it, teams default to ambient awareness — the informal knowledge that exists in Slack channels, hallway conversations, and the memory of whoever was online at the right time.
Ambient awareness works when everyone is in the same room. It fails catastrophically when a team spans Berlin, San Francisco, and Sydney. Declared state replaces ambient awareness with explicit, structured, queryable records that survive timezone boundaries.
Frequently Asked Questions
What is declared state in engineering?
Declared state is the explicit, published record of an engineer's or team's current working context — available to anyone who needs it without requiring the originator to be online. It includes current work, blockers, decisions, and next actions. It replaces ambient awareness with structured, queryable records.
What is the opposite of declared state?
The opposite of declared state is ambient awareness — the informal, unstructured knowledge that exists only in the heads of people who happen to be online at the same time. Ambient awareness works in co-located teams. It fails in distributed teams because context does not survive timezone boundaries.
Related Terms
Declared handoff
A structured transfer of working state from one engineer — or one shift — to the next, made explicit before the outgoing...
Read definitionEngineering wrap
A structured end-of-shift declaration made by an engineer before going offline. The wrap declares current state, outstan...
Read definitionState transfer
The act of passing the current working state of a piece of work from one person to another — explicitly and completely —...
Read definitionFurther Reading
Get the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See declared state in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.