house-operational-architecture skill

---
name: House Operational Architecture
description: A three-part structural framework for building a scalable company—Foundation (Founding Documents), Posts & Beams (Supporting Structures), and Mechanicals (Operating Cadence). Use when moving from PMF to scaling the org.
---

# The 'House' Operational Architecture

> "Product market fit is just the product, and that is not a company, and that will not scale." — Claire Hughes Johnson

## What It Is

A three-part structural framework for building a company that scales. It treats company building as a **construction project** requiring a foundation, supporting beams, and mechanical systems to function.

## When To Use

- Moving from "finding PMF" (0-1) to "scaling the org" (1-N)
- Typically around **50-150 employees**
- When the org feels **chaotic despite good product**
- Preparing for **hypergrowth**

## The House Model

```
     ┌───────────────────────────────────────┐
     │         🏠  THE HOUSE                 │
     ├───────────────────────────────────────┤
     │  🔌 MECHANICALS (Operating Cadence)   │
     │  • Planning cycles                     │
     │  • QBRs                               │
     │  • Launch events                      │
     ├───────────────────────────────────────┤
     │  🏗️ POSTS & BEAMS (Structures)       │
     │  • Levels & Ladders                   │
     │  • Hiring Rubrics                     │
     │  • Goal-setting (OKRs)                │
     ├───────────────────────────────────────┤
     │  🧱 FOUNDATION (Founding Documents)   │
     │  • Mission                            │
     │  • Values                             │
     │  • Long-term Goals (3-5 years)        │
     └───────────────────────────────────────┘
```

## Core Principles

### 1. The Foundation (Founding Documents)
Codify Mission (why we exist), Values (how we work), and Long-term goals (3-5 year aspirations).

### 2. The Posts & Beams (Supporting Structures)
Implement frameworks like Levels/Ladders, Hiring Rubrics, and Goal-setting systems (OKRs) that replicate up and down the stack.

### 3. The Mechanicals (Operating Cadence)
Establish the "wiring" and rhythm—planning cycles, QBRs, and launch events—that provide predictable stability.

### 4. Replication
Build structures so they can be copied by teams as they grow, rather than every manager inventing their own process.

## How To Apply

```
STEP 1: Document Foundation
└── Write Mission Statement (1 sentence)
└── Define 3-5 Core Values with behaviors
└── Set 3-5 Year Long-term Goals

STEP 2: Build Structures Early
└── Levels & Ladders (even if painful)
└── Hiring rubrics and interview guides
└── OKR or goal-setting framework

STEP 3: Establish Cadence
└── Annual planning cycle
└── Quarterly Business Reviews
└── Weekly/Monthly exec syncs

STEP 4: Enable Replication
└── Document everything in a handbook
└── Train managers to use shared tools
```

## Common Mistakes

❌ Waiting too long to implement levels/ladders (creating a "bloodbath" later)

❌ Changing operating cadences too frequently before they can take root

❌ Skipping the foundation and jumping straight to processes

## Real-World Example

Stripe implementing "Levels and Ladders" early (at ~160 people) to avoid unfair compensation structures later, despite it feeling like "ripping the band-aid off."

---
*Source: Claire Hughes Johnson, Lenny's Podcast*