Chapter 1
The Invisible Operating System at Work
Describes the informal layer of judgment and coordination that carries work after the documented process runs out.
AI and organizational behavior concept
What Is the Difference Between Documented Work and Actual Work?
Direct answer
Documented work is the company on paper: policies, process maps, job descriptions, and systems. Actual work is what people must do to produce an outcome when those representations are incomplete. It includes informal coordination, judgment, workarounds, trusted relationships, and exceptions that rarely appear in official documentation.
In the book
Where this concept is developed
This page offers a concise orientation. An Inbox Between Us develops the idea in greater depth through the following parts of the book, where it is connected to the wider argument about AI, organizational behavior, and modern work.
Chapter 2
Human Patterns Behind Process Bottlenecks
Looks past the visible workflow to the pressure, uncertainty, and adaptation that often create or sustain a bottleneck.
Chapter 7
The Real Cost of Chaos
Follows the human and operational cost of the gap between the company on paper and the work people must actually perform.
The map is not the terrain
The company on paper is necessary, but it is a model of work rather than the work itself. It simplifies variation so people can communicate, govern, and repeat a process. The simplification becomes dangerous when leaders assume everything omitted from the model is unimportant.
Actual work contains exceptions, history, relationships, resource constraints, and local knowledge. Those elements often determine whether the documented process succeeds.
“Before trying to fix processes or deploy new technology, organizations must understand the behavioral system that governs how work gets done.”
Why AI strategies miss the real organization
When AI is trained only on official policies and process documentation, it learns the organization as described. Employees encounter the organization as lived. The resulting recommendations can sound correct while failing at the exact points where judgment and adaptation carry the process.
Effective discovery therefore starts by comparing official intent with behavioral evidence rather than choosing one as the complete truth.
Actual work contains the steps no one counted
In the Tim Stating the Obvious episode, David describes a familiar pattern: a documented step may look simple from above, while frontline employees know the thirty smaller steps required to make it happen. Someone calls one person, waits for another, assembles a side document, reconciles a spreadsheet, or confirms context before the official step can move.
Those hidden steps are not noise around the process. They are often the process as experienced by the people responsible for producing the outcome.
The unwritten book of work
In The Book Leads conversation, David describes the most important book as the unwritten one: the stories people carry about how work actually happens, why they make the choices they make, and what those choices cost or protect.
Those stories often explain the gap between documented work and actual work. They show why an informal step exists, why a team trusts one route over another, and why a documented process may be accurate without being complete.
The written contract has an other duties clause
Delivering Marketing Joy frames the official organization as a written contract: job descriptions, company values, advertised responsibilities, and official processes. The unwritten contract is the work hidden inside phrases like “other duties apply.” It includes how people handle risk, solve problems, call the right colleague, create a side artifact, or mitigate a situation no process anticipated.
That is why actual work cannot be reduced to the official job description. The business runs because people interpret the gap between what was written and what reality requires.
The behavioral operating system carries the culture
In the Build a Vibrant Culture episode, Nicole Greer names the distinction directly: the documented operating model is what leaders design and formalize, while the behavioral operating system is the less visible layer that actually influences how the organization works.
For culture leaders, this matters because stated values and formal training are only part of the system. Actual work appears when people leave the training room and decide how to behave inside real pressure, relationships, incentives, and constraints.
The undocumented work is where discovery begins
On Lifelong Learners Collective, the official contract includes job descriptions, company values, standard operating procedures, and the stated way a role should function. The undocumented work includes the calls, meetings, personal systems, workarounds, and practiced responses people use when reality does not follow those steps.
David describes this as the work hidden inside “other duties apply.” Documenting those duties helps an organization see what people know, where the process depends on informal adaptation, and whether the right response is automation, training, clearer decision authority, or a conversation.
Operational example
An SOP routes a request directly from one department to another. In practice, employees check with two experienced colleagues first because the receiving team frequently interprets the request differently. Automating the SOP removes the adaptation without resolving the disagreement.
Further conversations and perspectives
These appearances extend the book’s argument through questions, examples, and perspectives raised in conversation.
ProductCamp Conversations →
The conversation contrasts controlled inputs with the raw story of work, showing how forms can omit the upstream experience, downstream effects, and informal behavior that explain an entry.
The Expert Authority Coach Podcast
The conversation connects the formal job description to the “other duties apply” work people are hired to handle: ambiguity, unexpected situations, and the lived experience through which the job actually gets done.
Lifelong Learners Collective →
The conversation contrasts the official contract of work with the undocumented behaviors and “other duties” through which employees actually accomplish the job.
People Business
The discussion examines hidden systems and why official processes cannot fully explain operational reality.
Transform Now
The conversation frames emails, meetings, and workarounds as an unwritten contract alongside official systems.
Book Leads
The episode treats workplace stories as the real evidence people need to hear when they want to understand how work happens.
Tim Stating the Obvious →
The conversation explains how official steps often depend on many smaller informal steps that only frontline employees can describe.
Delivering Marketing Joy
The episode distinguishes the written contract of job descriptions and official process from the unwritten contract of ambiguity, adaptation, and problem-solving.
Build a Vibrant Culture
The episode distinguishes the documented operating model from the behavioral operating system HR and culture leaders encounter in employee experience.
Finding Freedom
The episode distinguishes the official contract of values, org charts, job descriptions, and procedures from the unwritten contract of how the job actually gets done.
Follow The Brand by Grant McGaugh →
David distinguishes the documented system—policies, values, process documents, and presentations—from the undocumented system of steps people use to get the job done. The second system explains how the company actually operates when the formal description is incomplete.
Undiscovered Entrepreneur: Get Across The Start Line →
The written contract contains the organization’s declared roles, values, and documented processes. The unwritten contract contains the decisions, relationships, adaptations, and workarounds through which the business actually operates.
On Brand with Nick Westergaard →
The episode distinguishes the official documented system from the undocumented system, or unwritten contract, through which the business actually runs.
Questions this concept helps answer
- Why do process maps become inaccurate?
- Are workplace workarounds always bad?
- How can leaders discover actual work?
- Why does automating the official process sometimes fail?
Keep exploring
Follow the idea without losing your place
Start with the closest connections. Open the additional links only when you want to go further.
Ideas
Related concepts
Conversations
Related appearances
Reading
Related articles
Take the idea further
Move from the concept into the book, a live conversation, or the experience behind the work.