The cost of being indispensable
A creative leader can improve every piece of work and still weaken the team producing it. The color gets corrected. The person choosing it learns to wait.
Chris Do locates the problem in a familiar managerial instinct: the leader has promised a certain level of quality and feels responsible for delivering it personally. Delegating the execution does not relieve that pressure. Instead, it creates the temptation to supervise every choice as though another person's hands were an extension of the leader's own.
The exact shade of red matters. So does the blue, the typeface, the detail that would have looked different had the leader made it. In Do's account, those preferences become the daily machinery of micromanagement.
There is an understandable motive underneath the interference. The leader wants the work to be good and feels guilty about not doing it. But the method turns a promise to the client into a restriction on everyone hired to fulfill it.
Constant correction creates dependence.
Do describes people beginning to second-guess and then repeatedly reconsider their decisions because the leader keeps changing them. The concern is not simply that feedback feels unpleasant. It is that making a decision stops feeling useful when someone else will reliably replace it.
In that arrangement, the team still produces the work. The leader retains the judgment.
The distinction exposes the cost of this approach. A business can employ capable, expensive creative people while giving them little meaningful room to use their abilities. Do argues that this strips away the autonomy, intelligence, and creativity that made those people worth hiring.
His comparison is pointed: strong creative resources get reduced to the level of an intern or virtual assistant. The criticism concerns the mismatch between the capability being paid for and the responsibility being permitted, not the value of those other roles.
The team has been hired for more than execution. Yet execution is what remains.
That makes the leader's apparent indispensability a questionable achievement. If every consequential choice must return to the same person, the organization is not necessarily demonstrating that person's exceptional value. In Do's account, it can be demonstrating the dependence that person has created.
The difficult distinction is between protecting a standard and protecting a preference. The transcript's color and typeface examples show how easily the two become entangled. A leader can believe the intervention serves quality while insisting that the finished work resemble a personal solution.
Do does not argue that standards should disappear. He challenges the assumption that maintaining them requires the leader to make every decision. That is a different proposition, and a more demanding one.
The question underneath his argument is whether capable people are being allowed to become reliable decision-makers. Constant intervention can keep the immediate project close to the leader's taste while leaving that larger responsibility untouched.
This is the first trap: the work keeps moving, but its ownership never does.
Freedom without leadership is another failure
The obvious escape from micromanagement is to stop interfering. Hire excellent people, give them autonomy, and let them run. Do identifies this as the other familiar school of thought in managing creative teams.
Its appeal is easy to understand within the contrast he draws. Where the micromanager treats each decision as a potential mistake, the hands-off leader treats the hiring decision as sufficient assurance. The people are good. The work should follow.
But Do distinguishes empowerment from absence. In the version he criticizes, the leader celebrates autonomy and then leaves to pursue other priorities. The team has freedom, but little active leadership or quality control.
Sometimes that works, he says. Sometimes it does not.
When it fails, frustration travels in both directions. The leader is angry about the outcome. The team is angry because it was allowed to proceed without the intervention now being treated as necessary.
The disagreement is about more than the work itself. It concerns what the original freedom meant. Permission to proceed cannot fairly become, after the fact, evidence that the team should have known the leader wanted something else.
These are the two approaches Do places in opposition:
- Control through constant intervention: The leader changes decisions and weakens the team's autonomy.
- Autonomy through managerial absence: The leader withdraws, leaving quality and direction uncertain.
- Ownership with available support: The team retains responsibility and calls on the leader when input is needed.
The third approach is his alternative. It is not presented as the only possible model of leadership. Do explicitly allows that other models exist and describes this hybrid as the one he practices.
That qualification matters. This is an account of a working relationship, not a claim that every team at every stage should operate identically. The arrangement depends on what the people involved are ready to carry.
It also reframes the leader's transition away from direct production. The relevant change is not simply doing less creative work. It is deciding what kind of responsibility replaces that work, a tension adjacent to The Futur's Moving from Makers to Entrepreneurs.
Under Do's hybrid, the leader does not disappear. Nor does the leader remain the compulsory checkpoint for every creative judgment. Expertise stays available without becoming a permanent approval requirement.
The distinction is subtle enough to be lost in a slogan about trusting people. Trust alone does not describe when the leader should participate, who requests that participation, or what happens after advice is given. Do's explanation addresses all three.
The team initiates the request. The leader contributes perspective. The team continues making decisions.
This preserves something both extremes put at risk: a clear relationship between freedom and responsibility. The team cannot exercise real judgment if the leader continually takes it away. It cannot reliably access leadership if the leader has equated delegation with departure.
The alternative is not less leadership. It is leadership that stops competing with the team's ownership.
Competence that does not take over
Do gives his approach an intentionally uncomfortable name: intentional incompetence. The phrase sounds like an admission of inability. His explanation makes clear that it is a refusal to keep performing every ability on demand.
“You're not really incompetent,” he says.
The leader still knows how to do many things. That knowledge is precisely what creates the problem. Team members recognize the leader's capability, feel insecure about their own, and ask the leader to solve increasingly more of the work.
Over time, Do argues, the leader ends up doing the jobs of the people being paid to do them. What begins as help becomes a substitution. The business has added people without fully transferring responsibility to them.
Intentional incompetence is his way of interrupting that pattern. He describes feigning a lack of ability so others can step forward to care for the business, its clients, and the work. The explanation that follows is less about pretending to lack knowledge than declining to make knowledge constantly available as a replacement for someone else's judgment.
The practical arrangement is explicit. The team has received training. Its members have already done good work. At that point, Do leaves it to them to decide when they want his input.
Those conditions keep the idea from becoming a defense of neglect. He is not describing an unprepared person receiving a difficult assignment and being told to cope. He begins with preparation and evidence of competence.
The timing matters as much as the withdrawal. A leader who has trained someone and seen strong work has a different basis for stepping back than a leader who merely hopes an unfamiliar team will manage.
Do then removes the obligation to show him everything. Work does not have to pass across his desk simply because his desk exists. Uncertainty, rather than routine deference, becomes the reason to seek another perspective.
Yet he keeps the door open. The team is welcome to bring work whenever it wants feedback. There is no suggestion that asking for help should be treated as failure or that independence requires avoiding the leader.
Not compulsory review. Not prohibited review.
This is where the provocative name becomes a practical boundary. The leader declines to be the automatic answer while remaining a possible source of answers. Team members must first engage their own judgment, rather than bypassing it because a more experienced person is nearby.
The shift also changes what competence looks like in a leadership role. Personal execution is no longer the only available demonstration of skill. Restraint becomes part of the job when intervention would prevent another capable person from taking responsibility.
For readers considering the broader responsibility of running a studio, How To Grow A Small Creative Agency is a related discussion. Here, Do keeps the emphasis on the immediate relationship between the leader's ability and the team's opportunity to use its own.
The point is not to become less capable. It is to stop making everyone else's capability unnecessary.
A second opinion is not a handoff
Do's invitation to seek feedback comes with a condition: people should arrive with a sense that they know what they are doing. The request is for another pair of eyes, not for someone else to inherit the entire decision.
That distinction defines the review. A team can be competent and still want perspective. It can have a direction and still recognize that a consequential pitch deserves another look. Neither admission requires surrendering ownership.
Feedback should inform ownership, not replace it.
In Do's description, the team takes the work as far as it can before calling him in. The leader is not being asked to create a position from nothing. The team has done the thinking and identified where another perspective would help.
He offers the example of an important pitch. The team recognizes that it is not seeing clearly, explains what it knows, and asks for input before the opportunity to redirect has disappeared.
The useful content of that request is straightforward:
- The pitch is consequential enough to warrant another perspective.
- The team can explain what it already knows.
- The uncertainty is visible before it becomes too late to change direction.
- The request concerns feedback that can help the team continue deciding.
These are elements of Do's example, not a separate review system. He does not prescribe a meeting format, a reporting template, or a fixed schedule. The mechanism is the team's judgment about when assistance is valuable.
After he contributes, the authority does not automatically move with the advice. Team members are allowed to continue making their own decisions, now informed by what they have heard. His involvement adds perspective rather than ending the team's role as decision-maker.
That is an important departure from the first management style. Under micromanagement, the leader's opinion replaces the team's choice. Here, the opinion becomes something the team must consider while still carrying the work forward.
Do also sees a benefit in the voluntary nature of the exchange. People who elect to ask for feedback are probably more open to receiving it. He qualifies that claim rather than treating it as a guarantee.
The qualification is worth preserving. An invitation does not make every critique welcome or every disagreement disappear. It changes the starting condition: the team has recognized a reason to seek the leader's view.
The broader subject of creative exchange also appears in Learning, Collaboration, Critique & Feedback. In this account, the distinctive issue is not the wording of the critique but who initiates it and who remains responsible afterward.
A requested review can still be demanding. It can reveal that the pitch needs redirection. It can complicate a decision the team thought was nearly settled. None of that contradicts autonomy if the team remains responsible for using the input.
The leader has been invited into the work, not asked to remove the people already doing it.
A second opinion is valuable because it is additional. Turn it into the only opinion that counts, and the original dependency returns.
The team owns more than the design
Do's account of ownership extends beyond creative quality. The team is responsible for making clients happy and running projects within the numbers and guidelines already in place. Autonomy is not confined to choosing what the work looks like.
This is the commercial weight of the arrangement. A team cannot claim independence over the interesting decisions while treating the project's practical limits as someone else's concern. In the model Do describes, creative, client, and operational responsibilities travel together.
He names the expectations plainly:
- Produce good work.
- Keep the client happy.
- Stay on budget.
- Deliver on time.
These are not new standards introduced to compensate for the leader's absence. They are the responsibilities the team is expected to carry as part of doing the job. The leader's reduced interference makes that ownership more visible.
The distinction also explains why an elective review is not an exemption from accountability. Whether or not the team asks for input, the work still has to serve the client and fit the project's constraints. Choosing not to consult the leader does not remove those expectations.
Do then identifies a failure mode inside his preferred approach. Some people bring work for review because they do not want responsibility. The outward behavior resembles collaboration, but its purpose is to pass the burden back.
His response is blunt: “That's not going to work.”
The problem is not the frequency of requests alone. Do welcomes requests and later encourages teams to use his help as often as needed in sales situations. What matters here is whether the person asking still intends to own the result.
A request for perspective and a request for absolution can look similar from the outside. Both involve showing work to the leader. The difference emerges in what happens afterward: continued decision-making or an attempt to treat the leader's participation as a transfer of responsibility.
When Do sees that pattern, he calls for a conversation. He also acknowledges the possibility that the wrong people have been hired. The sequence does not justify assuming every uncertain employee is a bad fit; it establishes that unwillingness to take responsibility cannot remain hidden inside a feedback process.
This is the limit that keeps elective support from becoming micromanagement by invitation. If every review ends with the leader owning the next move, the team has recreated the same dependency without being forced into it.
The practical test therefore sits after the conversation, not merely before it. Has the team used the feedback to make a decision, or has the decision quietly become the leader's job again?
Do's model asks for confidence, but not certainty. It asks for responsibility, but not isolation. A team can admit that it does not see a pitch clearly while still accepting the obligation to improve it.
That combination is more exacting than either constant supervision or unchecked freedom. It requires people to carry the project and recognize when carrying it well includes asking for help.
Ownership is not proved by never calling the leader. It is proved by remaining responsible when the leader answers.
Call while there is still time
The clearest test of the arrangement comes when revenue is at risk. Do applies the same invitation to situations where the team feels a prospective client slipping away and expects a negative outcome.
He wants to hear about it before that outcome arrives. At that point, he can potentially intervene, join a sales call, and help land the client. The usefulness of his expertise depends partly on when it is requested.
Escalate while intervention can still matter.
This is not an instruction to bring the leader into every sales conversation. Do explicitly leaves room for the team to continue independently when it believes the opportunity is under control. Support remains available without becoming compulsory participation.
The distinction places a real decision with the team. It must assess the situation, notice uncertainty, and decide whether outside help would be useful. The leader does not remove that judgment by requiring involvement in everything.
Do says his team sometimes recognizes that a project is too big or that its approach is not connecting sufficiently to get the client signed. Those are moments when the team asks him to step in.
The request does not invalidate the delegation. It is one of the intended uses of it.
Sales adds urgency to the wider leadership argument because waiting changes the available options. Feedback on a live opportunity can still affect the next conversation. An explanation after the opportunity is gone cannot provide that same intervention.
The commercial setting has a natural connection to The Skill You Need To Win Clients That No One Talks About. Do's specific contribution here is about access to help: the team can call on a more experienced person before the sale has reached an unrecoverable point.
Crucially, he pairs that access with permission to lose. If the team proceeds on its own and the client does not sign, he says he will not blame it. His reasoning is grounded in his own limits: he does not win every opportunity either.
That promise belongs inside the model, not at its margins. Without it, the invitation to exercise judgment would sit beside an expectation of perfect results that the leader cannot meet personally.
The practical arrangement can be stated without turning it into an elaborate management system:
- Prepare people and recognize the good work they have already demonstrated.
- Leave the decision to request input with the team.
- Stay available when creative uncertainty or a slipping sale warrants help.
- Give feedback without automatically reclaiming the decision.
- Address attempts to transfer responsibility rather than genuinely seek perspective.
None of this promises that every pitch will succeed or every project will proceed smoothly. Do's account makes room for uncertain judgment, necessary intervention, and losses. The standard is responsible participation, not an uninterrupted record of wins.
For the leader, the challenge is to remain useful without remaining compulsory. For the team, it is to use support without treating support as an escape from the job.
Be available before the decision becomes irreversible. Then let the people hired to decide make the decision.
The leader can answer the call without taking back the job.
TRANSCRIPT
Enjoyed this? There’s more where it came from.
Get insights on running and growing a creative business.
You can unsubscribe anytime. By submitting, you agree to receive communications and to our Privacy Policy.
“They don't know how to make a decision without you because every decision they've made, you've changed it.”
— Chris Do
Key Takeaways
Subscribe
Details
- Topic
- BUSINESS