VIDEO - “I deliberately understaff every project” - Leadership lessons from Rippling’s $16B journey

#leadership #engineering/culture #media #yt #watch-list #team-management

My Notes

Everything tends to shift towards disorder
That's the reason why we have to put so much effort into maintaining things (even if they may seem like it doesn't matter at first)
only antidote to the entropy is the energy → we have to put energy into what we want to achive!! (and a lot)
Our whole life is a fight against entropy → The minute we were born, it was our temporary victory, but since then we are fighting and losing and eventually we will lose.

When you see that somebody should hear feedback and you don't give it to them, who are you optimizing for?
- It is not for them ("i dont want to hurt that person"), but for yourself
- It is fundamentally selfish → just cecause you don't want to be uncomfortable.

Learning from your mistakes is make me feel good bullshit.
You learn more from the winning team than from your own mistakes.
If you fuck up something, it doesn't mean you will make it right next time.
Success breeds success and you should want to join winning team.

How to Communicate Need of Growth (& Why)

If you want to achieve something really extremely successful, it's going to be really fucking difficult.
If you ever find yourself in a comfort zone, you had to have screwed up something massively.
→ This is something we have to remind people all the time.

Traits

S - Smart: Not just raw intelligence, but curiosity and lateral thinking.
- Can they apply knowledge to new domains? (Matches your "learning rate" mantra).
P - Passionate: Missionaries, not mercenaries
- Do they have "fire" for the mission (healthcare/product) or a personal interest? Passion fuels momentum.
O - Optimistic: Belief that "anything is possible"
- Rejects "we tried that already." Requires trusting that others are fundamentally good.
T - Tenacious: Relentless resilience
- When they hit a wall, do they stop or find a way? (Essential for startup "unlimited problems").
A - Adaptable: (Inferred/Contextual)
- Ability to pivot and thrive in changing environments.
K - Kind: (Inferred/Contextual) Empathy and fundamental decency
- builds the 20.09. Psychological Safety required for a "blameless" culture.

Mindmap

mindmap

Main Idea

This text features Matt MacInnis, CPO of Rippling, discussing the operational philosophy required to build high-performance product teams. He argues that extraordinary outcomes require extraordinary effort, deliberately understaffing teams prevents politics, and leadership's primary role is injecting intensity to fight organizational entropy. He introduces frameworks like "High Alpha vs. Low Beta" for balancing innovation with process and emphasizes rigorous product quality checks.

Relevance

This is maximally relevant to you as a Senior EM aiming to transition teams from output to outcome-driven; MacInnis provides specific mental models for increasing efficiency without increasing headcount ("understaffing"), defining product quality (The Pickle), and instilling a "product engineer" mindset through high-intensity feedback loops.

Relevance Scale: 5/5

Key Learnings

Extraordinary Effort: Top 1% outcomes require uncomfortable levels of effort; comfort zones are a sign of failure in high-growth environments.
Deliberate Understaffing: Overstaffing leads to politics and work on low-priority tasks; understaffing forces strict prioritization and reduces waste.
Alpha vs. Beta: Processes exist to lower volatility (Beta) but often suppress outperformance (Alpha); apply process strictly only where consistency is more valuable than innovation (e.g., payroll vs. new features).
Entropy vs. Energy: Organizations naturally decay toward disorder (entropy); a leader's job is to relentlessly inject energy and intensity to maintain high standards.
Feedback as Altruism: Withholding feedback is selfish because it prioritizes your comfort over the recipient's improvement.
The Pickle (PQL): Implement a "Product Quality List"—a checklist of non-negotiable standards (e.g., no feature flags at ship) used during a "factory inspection" before release.
Escalations as Gifts: Treat customer escalations as opportunities to trace root causes back to the system or leadership failure that allowed them.
Conway’s Law: Locally optimized teams (e.g., a great mobile team but poor backend support) create globally incoherent products; leaders must force global coherence.
Modeling Intensity: Leaders must publicly demonstrate the intensity they expect, participating in bug bashing and feedback channels visibly.
Hiring Heuristic: Use the SPOTTAK framework to decode intuition about candidates: Smart, Passionate, Optimistic, Tenacious, Adaptable, Kind.

User's Special Query: Leadership Lessons & Practical Usage

Leadership Lessons Mentioned:

Fight Entropy: The natural state of a team is to optimize for local comfort. You must be the source of energy that prevents this decay.
Mirror the Founder: As a leader, do not buffer your team from the CEO's intensity; mirror it to prevent a drop-off in standards.
Factory Inspections: Don't just trust; verify. Leaders must inspect the final output (the "factory inspection") before it reaches the user.

Practical Usage in Your Context:

The Pickle for R&D: Since you use Storybook and specialized stacks (iOS/Android), create a "Product Quality List" specific to your tech stack. Before any feature moves from "In Review" to "Done" in Jira, it must pass this specific checklist (e.g., "Does it work in Dark Mode?", "Are all loading states defined?").
Intensity in Demos: During your Agile sprint reviews, do not accept "it mostly works." Adopt the "extraordinary effort" mindset—if a feature isn't polished (High Alpha), it doesn't ship. This reinforces the "Product Engineer" mindset you are building.

Main Ideas

Deliberate Understaffing: "It is really important to me that we feel that we've deliberately understaffed every project... If you overstaff, you get politics. You get people working on things that are further down the priority list than necessary."
- Importance: This counter-intuitive approach forces teams to focus only on the most critical problems, aligning with your belief that efficiency replaces headcount growth.
Entropy and Leadership Energy: "The only antidote to entropy, the only antidote to decay in a system is energy... Your job as an executive, as a leader, is to fight that entropy tooth and nail every single day."
- Importance: This defines the Engineering Manager's role not as a passive unblocker, but as an active injector of standards and intensity to prevent "good enough" culture.
Alpha vs. Beta in Process Design: "Processes in a business exist for the sole purpose of lowering beta... The downside of a process is that it suppresses alpha."
- Importance: This helps decide where to apply strict Scrum rigidities (Low Beta areas like Infra/Payments) vs. where to allow loose creativity (High Alpha areas like new feature experiments).
The Selfishness of Withholding Feedback: "Fundamentally, the most selfish thing you can do is withhold feedback from someone... you're optimizing for your own comfort."
- Importance: This reframes "Radical Candor" from a management technique to a moral obligation, essential for your value of a "culture of direct feedback."
Success Begets Learning: "You don't really learn from your mistakes, you learn from your successes... seeing how it's done right... is more informative."
- Importance: Challenges the "fail fast" mantra; suggests emphasizing and dissecting your team's wins (e.g., a successfully adopted feature) rather than just conducting post-mortems on failures.

Actionable Ideas

Create a "Pickle" (Product Quality List): "The product quality list is lightweight in the sense that it just articulates in the simplest ways the standards we want you to meet when you ship a product."
- Action: Create a shared Notion/Obsidian document listing 5-10 identifying traits of a "Done" feature (e.g., "No console errors," "Analytics events fire," "Mobile responsive") and mandate its use.
Public "Factory Inspections": "I personally review every one of those flows... always in a public channel so that every other product manager and engineering manager can jump in and see how the process has worked."
- Action: As a Senior EM, perform random "spot checks" on features in staging, record a Loom of you testing it, and post feedback in the public Slack channel to model the standard.
Hire for "High Alpha" or "Low Beta": "You have high alpha people who are very valuable... You also have low beta people who are also very valuable people... processes in a business exist for the sole purpose of lowering beta."
- Action: When hiring for your Platform team, look for "Low Beta" (consistent, process-driven); for Feature teams, look for "High Alpha" (creative, volatile, outcome-driven).
Escalation Analysis: "You went and you found the software that created the data error and then you found the system that created the software that created the data error."
- Action: When a bug hits production, don't just fix it; have the team trace the "system that created the software" (e.g., did the PR review process fail? Was the spec ambiguous?).
Mirror Intensity: "Your job is to preserve that intensity at its highest possible level... Parker Conrad is modeling personal intensity."
- Action: Do not be the "chill boss" who buffers the team from commercial reality; clearly communicate business urgency to your DRs so they understand the "Why" behind headlines.

Step-by-Step Plan

Immediate Action (Next 24 Hours):

Draft "The Pickle": Based on your tech stack (React/Python/Mobile), write down the top 5 non-negotiable quality standards that are often missed. Call it the "Quality Checklist" or "The Standard."
Audit Staffing: Look at your 2 feature teams. Identify if anyone is working on "priority #6" items. If so, pull them off and tell the team you are deliberately understaffing the top priorities to increase focus.

Short Term (Next 2 Weeks):
3. Implement Factory Inspections: Before the next release, personally test the main user flows. Record a Loom video of your walkthrough (narrating your thoughts/critiques) and post it in your R&D public channel. This models "intensity" and "product-orientation."
4. Tag "Alpha" vs "Beta" Roles: Review your 10 direct reports. Categorize them mentally as High Alpha (innovators) or Low Beta (stabilizers). Ensure the Low Beta devs are on the Platform team or critical infra, and High Alpha devs are on the feature/experimentation teams.

Medium Term (Next Month):
5. Refine Hiring with SPOTTAK: Update your interview scorecards to include the SPOTTAK attributes (Smart, Passionate, Optimistic, Tenacious, Adaptable, Kind) to filter for mindset over just technical skill.
6. Feedback Calibration: In your next 1:1s, explicitly state: "I learned that withholding feedback is selfish. I commit to giving you direct feedback to help you grow, and I expect you to do the same for me and your peers."

This article was originally published on https://craftengineer.com/. It was written by a human and polished using grammar tools for clarity.
--

Follow me on X (Formally, Twitter). Or read my stories on engineering management, and how to be a better engineering leader on Vibe Manager Blog.