This chapter offers a framework for seeing your own business more clearly. The framework is simple—four questions—but the questions are designed to reveal where problems actually live. You do not need a consultant or a complex methodology. You need a way to look at your business that makes the underlying structure visible.
The Four Questions
The framework centers on four diagnostic questions:
Where does information get lost?
What depends on one person?
These questions map to the three flows examined earlier: work, information, and decisions. Each moves through the business in patterns that can be observed and understood. The fourth question addresses the dependency problem that runs through the entire book: when too much routes through a single person, usually the owner, the business becomes fragile.
Each question is simple to ask but requires honest observation to answer. The goal is to identify the places where the structure of the business is creating problems.
Where Does Work Get Stuck?
Everyone can be busy while work moves slowly through the system. The question “where does work get stuck?” asks you to identify where this happens in your business.
Work gets stuck at bottlenecks where more arrives than can be processed, in invisible queues that no one is tracking, waiting for inputs that take too long to arrive, and at handoffs between people or stages where expectations are unclear.
To answer this question, pick a type of work that matters to your business—a customer order, a service request, or a project—and trace its path from beginning to end. Where does it wait? Where does it slow down? Where do people report feeling backed up or overwhelmed? The answers point to constraints that limit what the business can accomplish.
Signs that work is stuck:
- Jobs take much longer to complete than the actual working time required
- Certain people or steps are always backed up
- Customers wait longer than they should for responses or deliverables
- The same slowdowns appear repeatedly despite efforts to address them
Where Does Information Get Lost?
Information scatters across inboxes, spreadsheets, and people’s memories. The question “where does information get lost?” asks you to identify where this scattering causes problems.
Information gets lost when it exists only in one person’s inbox or memory, when it is recorded in a place no one else knows to check, when multiple systems hold conflicting versions, or when finding the answer to a simple question requires tracking down a specific person.
To answer this question, pay attention to the questions that arise in daily work. When someone asks “what did we promise this customer?” or “where is that file?” or “what’s the status of this job?”—how is the question answered? If the answer requires finding a specific person rather than looking in a known place, information is getting lost.
Signs that information is getting lost:
- The same questions get asked repeatedly
- People rely on one person’s memory for critical details
- Different people have different understandings of the same situation
- Finding information takes significant time that could be spent on actual work
Where Are Decisions Delayed?
Decisions pile up, especially when they are concentrated around you. The question “where are decisions delayed?” asks you to identify where this delay creates drag on the business.
Decisions get delayed when they require someone who is unavailable, when the information needed to make them is hard to gather, when authority has not been distributed so that routine matters wait for someone already overloaded, or when no one is sure who is supposed to make them.
To answer this question, notice what sits waiting during a typical week. What approvals are pending? What questions are awaiting answers? What could move forward if someone would just decide? The pattern reveals where decision-making authority is concentrated and where it might be distributed more effectively.
Signs that decisions are being delayed:
- Work pauses while waiting for approval from a specific person
- Routine matters require escalation that seems unnecessary
- People hesitate to act because they are unsure of their authority
- Your inbox or desk is a holding area for pending decisions
What Depends on One Person?
The first three questions address specific flows. This fourth question addresses the pattern that underlies many of the problems in a small business: excessive dependency on one person.
Dependency exists when the absence of one person would cause significant disruption, when certain knowledge lives only in one head, when certain relationships are held by only one person, or when certain decisions can only be made by someone because no one else has the authority or information to make them.
To answer this question, imagine that key people in your business were unavailable for a week. What would break? What would stall? What would no one else know how to handle? The answers reveal where dependency has accumulated and where resilience is lacking.
Signs of excessive dependency:
- Certain functions stop when a specific person is absent
- Knowledge about important customers, processes, or history exists only in one person’s memory
- One person is the default answer to most questions
- You cannot step away without the business suffering
Using the Framework
These four questions are not meant to be answered once and filed away. They are diagnostic tools that can be applied repeatedly as the business evolves.
The first time you work through them, you will likely identify multiple problem areas. This is normal. The goal is not to fix everything immediately but to see clearly where the problems are. The next chapter addresses how to prioritize among the issues you discover.
For ongoing use, these questions can structure periodic reviews. Every few months, walk through each question and notice what has changed. Have old problems been resolved? Have new ones emerged? Where is the business improving, and where is it stuck?
The framework is simple by design. Complex methodologies create their own overhead and often go unused. Four questions, asked honestly and regularly, can reveal more about the health of a business than elaborate assessments that never get completed.
From Diagnosis to Action
Seeing the problems clearly is necessary but not sufficient. Once you have identified where work gets stuck, where information gets lost, where decisions are delayed, and what depends on one person, you need to decide what to do about it.
Not everything needs fixing, and not everything that needs fixing needs fixing now. The next chapter addresses prioritization: how to identify the highest-leverage improvements and how to avoid the trap of trying to fix everything at once.
