Chapter 5
Data Is Human Before It Is Technical
Places spreadsheets inside the human decisions, competing definitions, and practical adaptations that shape data before it reaches a formal system or AI model.
AI and organizational behavior concept
Why Are Spreadsheets Behavioral Evidence in AI-Enabled Work?
Direct answer
Spreadsheets become behavioral evidence when they reveal where people had to adapt the business so work could keep moving. An extra workbook may point to missing system capability, unclear ownership, delayed reporting, unavailable data, or a decision rule that never made it into the documented process. Counting spreadsheets is therefore not only a technical inventory. It can expose what the official operating model still does not explain.
“If AI really wanted to challenge the world, it would figure out how to eliminate the spreadsheet.”
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.
Spreadsheets show where the official system ends
In the Tim Stating the Obvious conversation, spreadsheets become the most concrete artifact of the unwritten contract. They appear when people need to combine information, create a report, reconcile a decision, or track work before the official system can support the reality in front of them.
That does not make every spreadsheet a failure. It makes the spreadsheet a clue. It marks a place where the organization’s documented process and actual work separated.
Shadow IT can be a survival label
Organizations often call these artifacts shadow IT. That label may be technically accurate, but it can hide the human reason the artifact exists. People usually build unofficial tools because the expectation remains in place while the official process, data, funding, reporting, or technology is insufficient.
Leaders get better signal when they ask what the spreadsheet is compensating for before they ask who created it.
AI can reveal spreadsheet sprawl, but people must interpret it
AI can help identify where spreadsheets cluster around processes, approvals, reports, or teams. It can compare those artifacts with email, chat, meeting transcripts, and process documentation to surface repeated patterns.
The interpretation still belongs to people close to the work. A spreadsheet may represent waste, but it may also represent local expertise, missing context, risk containment, or a workaround that kept customers, employees, or leaders from feeling the gap.
Replacing the spreadsheet is not the first step
The goal is not to rush toward a new system or AI workflow simply because a spreadsheet exists. The first step is to understand the behavior it carries. What decision does it support? What data does it combine? What trust or timing problem does it solve? Who depends on it, and what breaks if it disappears?
Only after that discovery can leaders decide whether the spreadsheet should be retired, formalized, automated, governed, or left alone because it is still the simplest responsible tool for the job.
Spreadsheets can protect psychological safety
In Finding Freedom, the spreadsheet is described as the number one artifact proving how people really get work done. Employees build them because they still need to deliver when official tools, budgets, permissions, reports, or systems are missing.
That makes the spreadsheet more than technical debt. It may be a psychological safety tool: a familiar place where employees can track, reconcile, and control work when the official process does not make them feel supported enough to succeed.
Operational example
A department has hundreds of workbooks tied to monthly reporting. A technical audit sees duplication. A behavioral review asks why the official system cannot produce the needed view, why each team trusts its own version, and what decision pressure forced people to build parallel reporting in the first place.
Further conversations and perspectives
These appearances extend the book’s argument through questions, examples, and perspectives raised in conversation.
ProductCamp Conversations →
David describes spreadsheets as natural survival tools people create when formal systems do not match the work, reinforcing the need to understand why the artifact exists before replacing it.
Tim Stating the Obvious →
The episode frames spreadsheets as artifacts of adaptation and asks whether counting them measures technical debt or what documented processes still fail to explain.
Future Factory
The conversation describes spreadsheets as survival artifacts created when employees still need to get the job done.
People Strategy Forum
The discussion connects shadow tools to the undocumented system through which people adapt to missing resources and incomplete process design.
Finding Freedom
The episode describes spreadsheets as familiar survival tools employees create when they lack the budget, systems, or support needed to do the job another way.
On Brand with Nick Westergaard →
David identifies spreadsheets as a primary artifact of undocumented behavior because employees use them to track, organize, and keep work moving when formal systems do not fit.
Questions this concept helps answer
- Why do spreadsheets keep appearing inside organizations?
- Are spreadsheets always technical debt?
- How can AI help examine spreadsheet sprawl responsibly?
- What should leaders ask before replacing an unofficial workbook?
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.