Circle of control
Sort specific issues by what your team can directly change and what depends on someone else's decision, then plan a response for each.
Use this check when discussion keeps returning to external obstacles or people disagree about their authority. Define the role, permissions and time window first. This guide uses two categories: directly controllable and not unilaterally controllable. It does not add an influence ring.
A concrete problem, your role and authority, a time window, relevant records and external dependencies. Leave uncertain permissions open for checking.
Two groups of issues with reasons, one action you can take directly, and a plan to clarify, respond to and review external dependencies.
On this page
How to use it
- State the problem, participants, your authority and the time window.
- Split mixed problems into specific issues and attach records or decision rights to each.
- Separate directly controllable issues from those you cannot decide unilaterally. Check disputed authority; leave unknowns unclassified.
- Choose one action within your control. For external dependencies, identify whom to ask, how to respond and when to stop waiting without review.
- Assign an owner and review point. Reclassify when conditions change, and record actual outcomes separately from plans.
Keep its limits in mind
Control depends on the role, authority and time window; it does not make an individual responsible for everything. An external constraint still deserves attention. You can ask, negotiate or prepare alternatives, but cannot promise another person's reply or decision. Classification proves neither a cause nor an improvement.
Making progress while customer approval is pending
Fictional teaching example: Clear Lake Studio has five working days until an internal readiness check for a customer review pilot. Its project coordinator may organize drafts and send questions, but cannot appoint the customer's approver. Both drafts lack a named customer approver. The customer reply date and pilot approval are unknown.
On a small screen, scroll across the diagram to read it.
The mixed problem: 'The customer has not approved' combines draft preparation, identifying the approver and the actual approval. Only the first two contain actions the coordinator can initiate.
How the distinction was made: The fictional role card permits preparation and questions. The customer retains appointment and approval decisions. The five-day deadline concerns internal readiness, not a customer response promise.
Result and status: The team has two categories and a proposed response. Today's preparation and questions have not yet been carried out, and no customer approval or faster turnaround is claimed.
The five-working-day deadline applies only to internal readiness. Today's actions and the next-working-day review are plans; no message, customer reply or approval has been recorded.
Next step: The coordinator should carry out the planned preparation and question, then review actual replies on the next working day. Internal readiness does not substitute for customer approval.
Three limits to check before classifying an obstacle
First, pause when the role or time window is unclear. A coordinator may be able to prepare a question but lack permission to send it through a particular channel. What can be initiated today can differ from what can be completed before a later deadline. Classify a specific action under a stated role rather than calling the whole project controllable.
Second, do not classify an external decision as irrelevant. A customer’s authorization may be essential even though you cannot provide it. Keep the dependency, its owner if known, and what information is needed. Asking, negotiating, and preparing alternatives are possible actions; another person’s response remains theirs. This guide keeps two categories rather than adding an influence ring.
Third, stop if the distinction becomes a way to assign personal blame. Authority, resources, and interruptions affect what people can actually do. Identifying an action you can initiate does not guarantee its completion or make you responsible for every outcome. An obstacle outside unilateral control still deserves appropriate attention, including a request for support when needed.
Choose between authority boundaries, roles, dependencies, and scope
The control distinction helps separate an action from someone else’s decision. It does not establish why a delay happened or replace a delivery plan. Use related methods when the missing output concerns roles, scheduling, or the investigation itself.
| Available input and question | Method | Output and limit |
|---|---|---|
| An obstacle mixes own actions and external decisions | Circle of control | Two categories and proposed responses; no promised external outcome. |
| A deliverable lacks agreed execution or approval roles | RACI matrix | Responsibility discussion; a proposed role is not acceptance. |
| Activities have durations and dependencies | Gantt chart | A conditional schedule; external dates must be confirmed. |
| A broad problem exceeds the available mandate | Issue definition worksheet | A bounded task and exclusions; no new authority. |
Separate the two drafts from the customer’s approval
The complete fictional Clear Lake Studio packet contains two review drafts, both without a named customer approver. Five working days remain until an internal readiness check. The coordinator’s role card permits organizing drafts and sending clarification questions; the customer appoints the approver and decides authorization. No customer reply date or pilot approval is known. Today’s preparation and question are plans, not completed actions.
The statement “the customer has not approved” hides three different matters: draft preparation, asking who can approve, and the actual approval. The coordinator can initiate the first two within the supplied role, while appointment and authorization cannot be made unilaterally. Keep the missing name in both draft records until a relevant reply is received; do not fill both with a familiar customer contact.
The proposed response is to organize versions and open questions today, ask the customer about the approver, and prepare an internal checklist if no reply arrives. The next working day is a review point for actual replies, not a deadline imposed on the customer. Internal readiness may be assessed while authorization remains absent; that does not permit launching the pilot.
| Supplied record | Coordinator can initiate | External condition and status |
|---|---|---|
| Both drafts lack an approver name | Preserve the gap and ask who has authority | Customer appointment unknown; no guessed name. |
| Versions and questions need organization | Prepare a consistent review packet | Customer understanding and approval still unconfirmed. |
| Five working days to internal readiness | Plan internal preparation within the role | This is not a customer reply commitment. |
| No reply date or approval | Prepare an internal checklist and review next working day | No reply is not consent or automatic refusal. |
Record actions, replies, and permissions as different events
The output is a proposed response with a concrete check, not proof that the wait has shortened. When the coordinator acts, record what was prepared and what was actually sent. A drafted question is different from a delivered message; a message acknowledgment is different from a named approver or an approval. Preserve the question and actual response so later readers can see exactly what was confirmed.
At the next-working-day review, separate completed preparation, any reply received, unresolved authority, and any actual permission change. If there is no reply, use the internal checklist for the work it genuinely supports, and decide whether an authorized escalation or revised readiness scope is needed. Do not manufacture a response deadline or send a commitment on the customer’s behalf.
If the customer identifies an approver, check what that person may decide and whether the confirmation covers both drafts. Appointment does not itself authorize the pilot. If an approval later arrives, retain its scope and conditions before updating the plan. The two categories may need revision when actual roles or permissions change; keep the original basis rather than rewriting history.
Finally, assess whether the distinction helped the team identify a valid next action. That is separate from customer response time or project success, which require actual observations and defined windows. No faster turnaround, accepted pilot, or completed preparation is supplied here. The practical result is a clearer boundary between work the coordinator may start and decisions still belonging to the customer.
Check your work
- Classification follows the role, authority and time window, rather than whether an issue is inside or outside the company.
- Reasons remain visible, and uncertain permissions have not been forced into a category.
- Actions have an owner and review point; external replies and approvals have not been promised.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.