founder-mode_skill

Overview

This skill captures a practical founder operating mode used to scale companies while retaining hands-on conviction and context. It helps founders decide when to delegate versus when to stay engaged, avoid the traps of becoming a "professional CEO," and maintain velocity through growth. The guidance is actionable, focused on decisions that only founders can make and on delegating outcomes rather than losing understanding.

How this skill works

The skill inspects situational signals—impact, ambiguity, people capability, and timing—to recommend whether to dive in or delegate. It uses proven principles: staying close to the work, skip-level checks, hiring for founder-mode tolerance, and delegating outcomes not understanding. It flags critical failure modes and validates decisions against strict constraints so advice remains practical and risk-aware.

When to use it

• When deciding whether to delegate a high-stakes initiative or retain direct control
• When rapid product or strategy pivots require founder judgment and context
• When a board or investor pushes to hand over operational control
• When scaling teams and you need to preserve velocity without micromanaging
• When evaluating hires for their ability to operate under founder expectations

Best practices

• Delegate outcomes, not the underlying understanding—insist on a founder-level briefing before stepping back
• Use skip-level conversations regularly to verify assumptions and avoid information loss
• Hire candidates who thrive with founder attention and tolerate ambiguity
• Create small, fast feedback loops to maintain velocity as responsibilities are shifted
• Document decision constraints and acceptance criteria so delegated work aligns with founder intent

Example use cases

• Choosing whether to lead a product redesign personally or empower the PM to run it
• Responding to investor pressure to recruit a professional CEO while retaining strategic control
• Onboarding a VP with explicit expectations around founder-mode involvement
• Assessing whether a scaling engineering org needs more founder-level reviews or better delegation
• Preventing founder burnout by identifying roles that can be fully delegated versus those that cannot