Depth Without Stomping
Go deep on the details of the business, then course-correct by seeding hypotheses instead of overruling.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 90%
Gupta's method for running founder mode as a leader without demoralising her team. Collect far more detail about the business than you intend to act on, decide privately where a course correction is needed, then engineer the correction through a forum where the team presents their own strategy and you improve it with questions and a seeded hypothesis rather than a rewrite.
Origin
Anneka Gupta's practice as CPO at Rubrik; she was named by Nikhil Singhal of The Skip as a leader who excels at operating in founder mode.
Core principles
- 01Empowerment is not the same as ignorance — a leader can know everything and choose to act on almost none of it.
- 02Collecting information is free; acting on all of it is what destroys autonomy.
- 03Course-correct early, inside the team's own work product, not late over the top of it.
- 04Seniority silences rooms. Seed an assumption for discussion instead of stating a conclusion.
How to run it
- 1
Get into the details on purpose
Understand to the utmost extent what's working, what isn't, the financial goals, whether you're on track, and how decisions are being made. Reject the instinct that asking detailed questions is disempowering.
- 2
Hold most of the information without acting
Deliberately collect information you do nothing with. The information is what lets you choose, later and with clarity, where a big or small course correction is genuinely warranted.
Pro tip Explicitly frame it to yourself as a choice: 'I want the information; whether I act on it is a separate decision.'
- 3
Pick the strategic areas to intervene in
Filter to what is most important for the business, what will kill it if you get it wrong, and the biggest opportunities regardless of execution difficulty. Intervene only there.
Watch out Correcting everywhere you have information is exactly the stomping behavior you're trying to avoid.
- 4
Ask them to present their strategy
For an area you think needs a course correction, ask the team to present their strategy. This gives them the floor with their best thinking and gives you a legitimate forum to intervene early.
Pro tip Get in early. Late intervention always feels like a rewrite; early intervention feels like input.
- 5
Question, then seed a hypothesis
Ask questions first. When questions can't lead them there, share a hypothesis grounded in outside evidence — 'I was talking to security leaders in our customer advisory board and heard this; here's what it made me think about our strategy, what do you think?' — and end on the question.
Pro tip Attribute the hypothesis to external evidence (customer advisory board, market signal), which makes it debatable rather than authoritative.
Watch out State a conclusion instead of a hypothesis and, because you're the most senior person in the room, nobody with a concern will raise it — and you're often wrong.
In the wild
Rather than telling a team their plan was wrong, Gupta asks them to present their strategy for an area she suspects needs correcting. She then asks questions and makes suggestions inside their forum, improving their thinking rather than replacing it.
→ The correction lands without the team feeling their work was dismissed or stomped over — they experience it as their strategy made better.
Gupta shares a specific hypothesis: she had been talking to security leaders in Rubrik's customer advisory board, heard a piece of feedback, and offers what it made her think about the strategy — then asks the team what they think.
→ The team engages, raises follow-up questions, and a genuine discussion opens up — she gets her point of view into the room without shutting the room down.
Common mistakes
Confusing empowerment with staying out of the details
Leaders avoid detailed questions to seem empowering, and end up unable to spot the course corrections only they are positioned to make.
Announcing the correction
Arriving with the conclusion, from the most senior chair, guarantees silent compliance rather than the dissent that would tell you whether you're right — and you're often not.
Is it for you?
Best for
Senior leaders and executives who need to be deeply informed and directive without crushing the autonomy of strong teams.
Not ideal for
Crisis situations demanding an immediate top-down call, or very junior teams that need explicit direction rather than a seeded hypothesis.
From the transcript
“there's a lot of information that I collect about what's happening in the organization the decisions that we're making that I don't do anything with…”
“one of the tactics I use is I ask people to present their strategies for things that I think we may need to do a…”
“I want to be able to seed seed an assumption and then have a discussion based on that”
“what is most important for the business what's going to kill the business if we don't get right”
From the episode
Becoming more strategic, navigating difficult colleagues, harnessing founder mode, and more
Anneka Gupta (Chief Product Officer at Rubrik)