Scale & Strategy
This is Scale & Strategy – we tee up the best of business insights, so you can hit non-stop home runs!
Here’s what we got for you today:
- When "Micromanaging" Works: A Founder's Guide to Detail and Delegation
When "Micromanaging" Works: A Founder's Guide to Detail and Delegation
The Good, The Bad, and The "Micro": Rethinking Hands-On Leadership
When you step into management, the collective wisdom often boils down to one directive: “Don’t micromanage.” It's the golden rule. But has this well-meaning advice created an anti-pattern, pushing managers to under-manage instead?
Hareem Mannan, a product and design leader, recalls this early struggle: "I was so allergic to micromanaging that I ended up under-managing, which was probably the biggest place I failed early on — to the detriment of my direct report." Veteran CTO Will Larson echoes this, noting that some executives become "resource allocators," detaching themselves from the ground truth. "As you get too far out of the details, you just become a bureaucrat," he warns.
This piece explores the often-controversial topic of micromanagement in the startup world. How much, and what kind, is productive? Can you stay involved in the minutia without stripping teams of autonomy? We've scoured the archives of The Review and the In Depth podcast to surface how founders and leaders from Apple, Rippling, Carta, and more strike this crucial balance.
Flying Close to the Details: When to Go Hands-On
Startup leaders are swamped with meetings, making it impossible to pore over every detail. The key is strategic involvement.
Model the Behavior You Want to See
For Lattice co-founder Jack Altman, "micromanagement" isn't inherently bad; it's a potent tool when used sparingly. The wrong way? Hovering over someone fundamentally incapable. The effective way? "Standard setting and demonstrating the caliber of thought, work and effort that you want to see." This could mean writing a blog post or fixing a bug yourself, signaling where energy and investment are needed. "Micromanagement is a shortcut that you don't want to always use," Altman advises, "but shortcuts have value."
Look for Data Anomalies: "Go and See"
Rippling COO Matt MacInnis lives by one of their nine leadership principles: "go and see." Leaders shouldn't just live in dashboards. "When the anecdotes disagree with the data, you've got a problem. You have to go and see for yourself." This means getting to the atomic level: reading customer support tickets, watching sales call recordings, or dissecting website interactions.
MacInnis shares an example: watching a sales call reveals a rep failed to highlight a key product "superpower." This observation can trigger a cascade of questions: "It implies the rep doesn’t understand what our superpower is... Which implies our training sucks, which implies the product marketing organization has failed, which implies we’re screwed." This hypothesis is then presented to department heads to either disprove or debug. As MacInnis puts it, "I’m not a micromanager, but I’m microinterested."
Create Review Systems to Maintain Quality
Stripe is renowned for its reverence for taste and craft, largely thanks to Krithika Shankarraman, their first marketing hire. She attributes this consistency to robust organizational reviews, which helped decentralize knowledge and ensure brand fidelity as the company scaled.
Stripe used two key tactics:
- "Red pen holders": Designated individuals in each domain (e.g., marketing) who would "mark up anything that went out the door to an audience of more than 100 users." Their role was to view the project with zero context, ensuring clarity and brand consistency for the user. "It was about improving the work rather than questioning the strategy," Shankarraman explains.
- 20% and 80% checkpoints: Reviews weren't saved for the last minute. A 20% strategy review ensured alignment on goals, and an 80% review checked execution, allowing ample time for changes. "I don’t think you can build a good brand without micromanagement," Shankarraman asserts. "It gets a bad rap for depriving people of independence or autonomy — but it’s about putting your user first."
Establish a Cadence to Go Deep on a KPI
Mike Brown, who oversaw Uber's expansion in Asia, advocates for a regular cadence of zooming into different projects. He calls this "porpoising": knowing what's happening at a surface level, but strategically diving deep into select initiatives. Brown would "porpoise" quarterly or semi-annually, focusing on projects tied to various KPIs (people/culture, growth, cost, customer experience). He also stresses immediate deep dives during existential threats, like when the Philippine government temporarily shut down Uber's business.
"Conflict Mining" with ICs for Micro-Context
Imprint CTO Will Larson advises new leaders entering a role or company to gain context quickly through "conflict mining." This involves long conversations with individual contributors (ICs) who are closest to a problem and might be skeptical of an executive's game plan. Larson learned this when his attempt to replicate a system from Uber at Stripe met resistance from an engineer. Instead of dismissing it, he dug deeper, realizing his new colleague had crucial architectural context he lacked. "You can’t lie to them," Larson says of ICs. "They know the truth of how things run."
Micromanage Your Product on Behalf of Your Users
Rippling CEO Parker Conrad famously approves every expense over $5 and still runs payroll for his 3,000-person company. Why? Because Rippling is a payroll platform, and it's the best way to keep a pulse on the product and customer experience. This dogfooding is a charter for all Rippling leaders. Matt MacInnis emphasizes, "If you stop being the most critical user of your product, you are toast." It ensures a "founder mindset" toward the product, rather than an "employee mindset."
Zooming Out to Empower Your Team: Delegating Without Sacrificing Quality
Hypergrowth demands delegation, but it also requires systems to recognize and stop unproductive micromanagement while maintaining high standards.
Treat Micromanagement Like a Symptom — and Get to the Root Cause
Former PatientPing founder Jay Desai popularized the "user guide," a personal manual for coworkers. In his guide, he views micromanagement as a symptom of distrust. "I am hands-on until I trust you. Once I trust you, I’m hands-off," he writes. If he finds himself "in your hair again," it's a signal that trust is splintering or progress is stalling. He encourages direct intervention: "Micromanagement is a great trigger that this is happening... That’s when I tell them I'm starting to lose confidence in them."
Give Regular Feedback to Stem the Need for Micromanagement
Sidharth Kakkar, co-founder and CEO of Subscript, built his fully asynchronous company culture on zero micromanagement, seeing it as the founder's role to build systems that prevent bad or misaligned decisions. His vehicle for ensuring effective team operation is feedback. He recommends making feedback regular (monthly, even), lightweight (like the "Start-Stop-Continue" framework), and inclusive of high performers. This proactive feedback reduces the need for reactive micromanagement.
Set Up Peer Office Hours
Design leader Hareem Mannan provides plenty of feedback to avoid micromanaging, but she also empowers peers to deliver it. At Segment, she shored up the team’s design critique process with weekly office hours led by design leads. If a designer's work wasn't meeting expectations, she'd encourage them to attend office hours rather than critiquing it herself in 1:1s, sometimes briefing the lead on areas for improvement. She also fostered "Design Hangouts" to build social connections, recognizing that "you can’t expect critique sessions or office hours to work unless you create forums for folks to connect with each other socially."
Give Your Team a Box Filled with Ideas
"As an engineer, nothing ticks me off more than micromanagement," says Apple engineering leader Michael Lopp. Instead of barking orders, Lopp's communication style is grounded in storytelling, offering his team a "box and fill it with interesting ideas." This allows team members to explore and apply their own approaches. "Your goal is to get your people thinking and give them as much information as possible," he explains. He likens it to providing the "soup" and letting them "season it yourself," empowering autonomy even if some prefer more direct instruction.
Hire Managers Who Can Do the Work Themselves
Sam Corcos, co-founder and CEO of Levels, initially regretted stepping away from writing code as his company scaled, noting that velocity "ground to a halt." Now, across functions, he seeks managers who are capable of performing the tasks of those they manage. "We no longer hire pure ‘managers’ at Levels," he states. "If they manage engineers, they need to be able to write excellent software. If they manage marketers, they need to be exceptional marketers themselves." This ensures that when issues arise, the CEO isn't the one forced to "swoop in to micromanage."
Ultimately, effective management isn't about a blanket ban on "micromanagement." It's about discerning when strategic, deep involvement is necessary to set standards, identify issues, and ensure quality, while simultaneously building trust, fostering a culture of continuous feedback, and empowering teams to operate autonomously. The best leaders master the art of "altitude shifting"—knowing precisely when to fly close to the details and when to zoom out.
Was this email forwarded to you?
That’s it for today and as always It would mean the world to us if you help us grow and share this newsletter with other operators.
Our mission is to help as many business operators as possible, and we would love for you to help us with that mission!
