The team is working. The work is waiting. A routine customer request, a small design choice and a scheduling adjustment are all sitting in the same queue: your approval.
This can look like high standards from the founder's chair. From the rest of the team, it may look like responsibility without permission. People can prepare a decision, but they cannot finish it.
Google's research on team effectiveness identified structure and clarity among the dynamics relevant to its teams. That is context-specific evidence, not a universal formula. The practical exercise here focuses on one form of clarity: who can decide what.
Find a queue before declaring a culture problem
For one working week, note decisions that arrive for your approval. Record the topic, why it came to you and what information was missing. Do not turn this into surveillance of the team. You are examining the structure you helped create.
Look for repetition. Perhaps the same kind of customer exception appears several times. Perhaps a designer cannot choose an image without you. Perhaps a delivery lead has responsibility for dates but cannot resolve a routine scheduling tradeoff.
Ask whether your approval adds information, manages a material risk or merely confirms a preference. Different reasons call for different changes. A missing policy cannot always be fixed by telling someone to be more confident.
Choose one bounded decision
Do not begin by announcing that everyone should “act like an owner.” Pick a decision with manageable consequences and a person who is ready to handle it.
Create a short agreement:
| Element | What to clarify |
|---|---|
| Decision | The recurring choice being transferred. |
| Owner | The person who can make and communicate it. |
| Boundaries | The limits and commitments they must respect. |
| Inputs | Information and people they need to consult. |
| Escalation | The circumstances that require another decision-maker. |
| Review | When you will inspect what happened and adjust the arrangement. |
For a fictional small agency, this might cover rescheduling a routine client session within an agreed delivery window. It should not silently authorize changes to the whole engagement.
Transfer context along with authority
Explain why previous decisions were made. Share examples of an ordinary case, an exception and a case that should escalate. Describe relevant customer promises and any information that must remain private.
Then ask the new owner to explain how they would handle a realistic scenario. This is a check of the agreement, not a test designed to expose them. If the answer differs from your expectation, find the missing boundary or context.
Authority also requires access. Someone cannot own scheduling while lacking the relevant calendar, or own customer communication while being unable to see the agreed scope. Fix the practical limitation before calling the transfer complete.
Do not take the decision back at the first difference
A choice can fall within the agreed boundaries and still differ from the one you would have made. If you routinely reverse such choices, the team learns that the authority was temporary theater.
Distinguish preference from consequence. If an outcome reveals a meaningful risk, discuss the risk and revise the boundary. If it simply reveals a different reasonable approach, allow the owner to learn from it.
When you must intervene, explain why. Quietly bypassing the owner can make the next decision slower because everyone now needs to discover where the real authority sits.
Review the system, not only the person
At the agreed review, inspect a few decisions together. Were the boundaries clear? Was information available in time? Did escalation happen for the right reasons? What did the customer or colleague experience?
Also inspect your own behavior. Did you answer questions that should have returned to the owner? Did you introduce new standards after the decision was made? Did the review become another approval meeting?
The aim is not to disappear from the business. It is to reserve your attention for decisions that need it while giving other people a real chance to complete their work. Start with one queue and one clear transfer. Growth becomes more practical when routine decisions have somewhere else to go.
Use a decision journal for choices whose reasoning deserves a longer record.
Questions worth asking
What should a founder delegate first?
Start with a recurring, bounded decision someone else is equipped to handle. Consider the consequences of error and provide the information and authority needed.
How can I retain oversight without approving everything?
Agree on boundaries, an escalation rule and a review cadence. Inspect selected decisions and outcomes instead of making every routine choice yourself.
