Methodology Playbook

Summary

Founders must deliberately architect a leadership team that reduces dependency on themselves — this means hiring experienced specialists who own their functions independently, creating clear org structures with executable transition plans, and transferring enough context to enable others to lead. The goal is not just to fill roles, but to make the founder the least operationally essential person on the team. Without this, every function bottlenecks at the founder and the company cannot scale.

Methodology

Kevin begins by diagnosing the org structure for founder dependency — identifying which functions are staffed by junior or generalist talent, handled as add-ons to overstretched operators, or simply bottlenecked at the CEO. He then pushes founders to define a future-state org chart with clear functional ownership, followed by a sequenced interim plan that bridges from today's constraints to that vision. For critical hires, he insists founders develop a working understanding of the role before recruiting, so they can evaluate candidates and manage effectively post-hire. On enablement, Kevin treats knowledge transfer as a structural problem: if a CS leader can't run a customer meeting without the CEO in the room, that's a process failure to be solved, not a permanent constraint. He also addresses the human dimension — when co-founders go down or transitions create instability, the first move is to stabilize the team emotionally and project calm authority before redistributing workload, because confidence in the situation precedes willingness to step up.

Summary

Firing underperformers is not an ad hoc judgment call — it is an organizational capability that must be deliberately built, measured, and held to account. Companies that lack explicit systems and cultural norms around performance-based separations will inevitably accumulate underperformers, especially during periods of rapid hiring. The goal is to make firing a predictable, measurable leadership behavior rather than a last resort triggered by crisis.

Methodology

Kevin's approach requires two structural components working together: a cadence and an accountability norm. On cadence, OKRs must be reviewed quarterly — not biannually — so performance data is current and actionable. The framework then calls for identifying the bottom 10–15% of performers each quarter, with a clear rule: two consecutive quarters in that tier triggers separation. This removes the subjective, emotionally loaded nature of firing decisions by converting them into a process outcome. Critically, Kevin also targets the human bottleneck: conflict-avoidant leaders — such as a CTO who has never fired anyone — must be named and held explicitly accountable, because structural gaps are often a symptom of individual avoidance. HR systems must be designed to support this cadence, not merely document terminations after the fact.

Summary

Effective managers hold direct reports accountable by anchoring conversations to observable behavior and broken trust — not tasks, personality judgments, or emotions. Kevin teaches that over-softening feedback and self-limiting your managerial toolset out of fear of damaging a relationship actually erodes trust and authority faster than directness does. The goal is not to be harsh, but to be clear, prepared, and unafraid to express disappointment or set hard expectations when the situation demands it.

Methodology

Kevin's approach begins with naming the behavioral pattern clearly and neutrally — separating the observation from any accusation or character judgment, so the conversation stays anchored to what is observable and specific. He distinguishes between delivering corrective direction (no apology needed, just directness) and reversing prior guidance (where context is appropriate), teaching managers not to over-apologize as a default. He uses role-play extensively to help managers rehearse exact language, anticipate deflections, and build the muscle memory to stay on offense during tense conversations. A core coaching move is expanding the manager's perceived toolset — helping them see that expressing genuine disappointment, setting hard expectations, and requiring specifics behind surface-level confidence are all legitimate and necessary instruments, not signs of harshness. He also addresses the internal blockers that prevent managers from using these tools, such as the fear of damaging a relationship or the instinct to protect a report's feelings at the expense of accountability. For reports who deflect by claiming their manager doesn't trust them, Kevin provides a concrete reframe: the issue is not trust as a character judgment, it is a specific, repeated pattern of saying something and not doing it.

Summary

VP titles should be held until the company reaches meaningful scale — around $20M ARR — to ensure the designation carries real weight and isn't inflated prematurely. Once that threshold is hit, a concrete company-wide rollout date should be set within six months to avoid indefinite delay. For individuals being promoted ahead of a broader rollout, the framing matters: offer the title rather than announce a promotion, letting the substance of increased responsibility and compensation speak for itself.

Methodology

Kevin's approach is to use $20M ARR as a practical threshold before distributing VP titles, ensuring the company has enough scale that the title reflects genuine organizational weight. Once that milestone is reached, he advises against leaving the rollout open-ended — a concrete, near-term date (within six months) creates accountability and prevents the title question from lingering and causing internal uncertainty. For individual cases where someone is being recognized ahead of the broader rollout, Kevin coaches founders to be precise in their language: 'formally offering you this title' rather than 'promoting you,' which avoids creating confusion about what changed structurally. The emphasis is on letting the real changes — scope, compensation, responsibility — carry the emotional and motivational weight of the moment, rather than over-engineering the messaging. This approach keeps the conversation clean, reduces the risk of setting awkward precedents, and honors the person being recognized without overpromising or underdelivering.