Key Takeaways

  • Senior executives stepping back into builder roles will fail if the organization treats them like junior individual contributors waiting on approvals.
  • Approval chains carry a higher organizational cost than small experimental failures when modern tools make building cheap.
  • Splitting a leader's time between management duties and hands-on execution creates context switching that degrades both disciplines.
  • Fast execution at startups like Lovable relies on flat structures and AI agents in Slack rather than information passing through human middle managers.
  • Elena Verna structures this shift around Elena Verna's 5 Prerequisites for the HI-IC Operating System.

Elena Verna's 5 Prerequisites for the HI-IC Operating System

1. Ungate Information Access: Eliminate organizational filtering and management layers that gate context. Provide full access to data and documentation across teams, using mechanisms like team-trained AI Slack agents to scale transparent institutional knowledge.

2. Authority Travels with Accountability: Grant the builder complete decision-making and shipping authority without multi-layered approval chains. Permit meaningful, revenue-impacting failures as long as learnings are captured and propagated.

3. Scope Defined by Business Outcomes, Not Functional Silos: Allow HI-ICs to cross functional boundaries (core product, growth, marketing, analytics) to solve problems end-to-end rather than restricting them to a single department.

4. Decouple Pay and Status from Headcount: Compensate HI-ICs at leadership-level pay grades and maintain executive influence without requiring direct reports, ensuring management is not the only path to career and financial growth.

5. Eliminate the Dual Manager-IC Role: Require individuals to choose either management or IC paths. Avoid hybrid roles where leaders attempt to maintain IC craft while managing people, as the context-switching penalty degrades performance in both.

When This Works (and When It Doesn't)

This operating model works when a company hires experienced leaders who want to build directly using modern AI stacks instead of coordinating large teams. Tools like Lovable allow senior talent to prototype and ship production code in hours. As Verna notes: “So if it's cheaper to try than to debate, make sure that when experiments are cheap, approval chains are the expensive part.” When coordination overhead drops, an experienced operator can outpace a ten-person department.

It breaks down in organizations with high regulatory risk, legacy enterprise codebases, or strict siloed security perimeters. If legal or compliance teams mandate six-week review cycles for every user-facing change, an unblocked IC loses their speed advantage. It also fails when an IC lacks broad business judgment. Giving unchecked production access to someone who does not understand downstream retention or unit economics turns rapid shipping into technical debt.

What to Do With This

Take your most senior IC or a former VP who wants to return to building. Run their role through this checklist this week:

1. Check their Slack and document permissions. Remove any restricted channels or dashboard walls preventing them from seeing company-wide revenue, churn, and product analytics.

2. Pick one live initiative where they currently wait on approval from product leads or executives. Grant them direct permission to ship experiments without prior sign-off.

3. Audit their current calendar. Strip out recurring 1-on-1s, quarterly team headcount planning, and performance review duties. Set their sole KPI to an outcome metric like activation rate or expansion revenue.