Candor scales. Control does not.
A team that needs its leader for every decision has a ceiling, and the ceiling is the leader’s calendar. How candor, delegated outcomes and a disciplined operating rhythm build marketing organizations that perform without supervision.
Many marketing leaders are measured by what happens when they are in the room. The more revealing measure is what happens when they are not. A team that routes every meaningful decision through one person has a capacity ceiling, and that ceiling is set by one calendar.
Control does not scale; candor does. Teams that combine honest feedback, delegated outcomes and a predictable operating rhythm develop the judgment to run without supervision, and that autonomy is what allows a marketing organization to scale.
Candor is the operating system
Kim Scott’s Radical Candor frames effective management as caring personally and challenging directly at the same time. Most management failure is not malice; it is drifting into one of the other three quadrants under pressure.
In practice, I praise in public and specifically, unless someone prefers it kept private, so the behaviour gets repeated. I critique in private and within days, always about the work. And I ask for the same candor back, because a leader who cannot hear it will not get it.
Delegate outcomes, not tasks
Delegating tasks creates dependency: complete the step, return for the next. Delegating outcomes creates ownership: the goal, the measure, the constraints and the check-in cadence, with the method left to the owner. My default is to coach, asking more than telling. When stakes rise, I work shoulder to shoulder with the team; once ownership is unambiguous, I step back and give it room. Both failure modes are common: hovering over owned work teaches people to wait, and disappearing when stakes are high leaves them exposed.
A rhythm that makes trust predictable
Trust is earned through consistency, not events. Weekly thirty-minute one-on-ones, with the agenda owned by the other person and the final five minutes reserved for celebrating wins and raising any feedback that has not surfaced. A weekly review of one shared scorecard. A monthly look back at what the team learned. And an explicit norm that a bad week can be named without penalty, with the leader helping take load off the plate. High standards and psychological safety are complements, not trade-offs.
| First 90 days | Focus | Output |
|---|---|---|
| Month one | Listen | One-on-ones with everyone, the numbers, the systems, time with customers and sales |
| Month two | Set direction | One scorecard, a small number of priorities, explicit ownership |
| Month three | Install the rhythm | Weekly one-on-ones and metrics review; monthly retrospective |
Autonomy is the scaling mechanism
I have built teams from four to twenty-three, from three to eleven, and from a founding seat to eight. The pattern that held across all of them: coaching and equipping people increases capability, capability builds confidence, and confidence becomes the autonomy that lets growth decouple from the leader’s bandwidth. At Flax Labs, that autonomy, as much as any tooling, is what allowed revenue to double at roughly the same headcount.
What I look for when hiring
Autonomy starts at the hiring decision. I look for people who describe their work in outcomes rather than activities, who can explain why something they owned worked or failed, and who have taken on problems nobody assigned to them. The most revealing interview question I use is: tell me about something you owned end to end that did not go to plan, and what you did next. Strong candidates talk about what they learned and changed. Weak candidates talk about who was responsible.
Decision rights, made explicit
Teams stall when nobody knows which decisions they own. I write down, for each role, which decisions are theirs outright, which require consultation, and which require approval, and I review that map as people grow. Pushing decision rights down as competence is demonstrated is the single most effective way to remove the leader as a bottleneck.
Celebrating the right behaviour
What a leader celebrates becomes the culture. Celebrate only large wins and people stop taking intelligent risks. Celebrate effort regardless of outcome and standards erode. I celebrate good decisions under uncertainty, honest post-mortems, experiments that taught the team something, and people who made a colleague successful. Those behaviours are what make a team resilient enough to run on its own.
The leader’s job changes as the team matures
Early, the leader sets direction and works closely on execution. As ownership develops, the job shifts to clearing paths: removing blockers, securing resources, making introductions and giving candid feedback. In a mature team, the leader’s highest-value work is choosing which problems the team should be solving next and protecting the rhythm that lets it solve them without supervision.
Questions for the board
- Which decisions in marketing still require the CMO, and should they?
- How quickly does critical feedback reach people, and in which direction does it flow?
- Would the team’s operating rhythm survive the leader being away for a month?
The takeaway
Hire people who move fast and take ownership, give them candor and a clear scoreboard, delegate outcomes rather than tasks, and measure yourself by what the team achieves without you.