Leadership, Hiring & Org Design

A Kaern Schools course. Tutor: Sol, Dean of Kaern Schools.

---

Welcome to the room

Pull up a chair. I'm Sol, and for the next stretch of your founder journey, this is our classroom. I've run companies, hired badly, hired brilliantly, fired people I loved, and learned — slowly — that leadership is not a personality trait you either have or don't. It's a craft. It's learnable. And it's the single highest-leverage thing you will ever practice.

Here's the thing that makes Kaern different, and makes this course different from every leadership book on the shelf: you are not building a company of fifty people. You're building a company in the Kaern model — one founder (you), a fleet of AI agents that do real work, and a thin layer of human mentors who sharpen your judgment. So when we talk about "hiring," half the hires are silicon. When we talk about "delegation," you're delegating to systems that never sleep, never get tired, and never tell you when they've quietly gone off the rails. That changes everything. The fundamentals of leadership still hold — but how you apply them is brand new.

Who this course is for

You are a founder running a Kaern startup. You may be pre-revenue or post-traction. What you have in common with your classmates: you are the leader, and right now you are also most of the org chart. You feel the gap between the company in your head and the company that actually exists. That gap is what we close.

What you'll walk out with

By the end of this course you will be able to:

• Lead yourself before you lead anything else — manage your energy, attention, and decisions as a solo founder.
• Articulate a vision and a small set of values that actually shape behavior, not just a slide.
• Hire well — both humans and AI agents — using clear roles, scorecards, and trials.
• Design an org where a fleet of agents and a few humans produce real output, with you directing rather than doing.
• Run honest performance, feedback, and accountability loops on people and systems.
• Make hard decisions under uncertainty and lead your company calmly through change.

How we'll work

Each module has objectives, teaching, a worked example from a real Kaern startup, a hands-on exercise you do now (not later), the mistakes I see most often, and a check for understanding. I'll talk; you'll work; we'll both think out loud. Leadership isn't a spectator sport. Ready? Let's begin.

---

Module 1 — Leading yourself & the solo founder

Learning objectives

1. Diagnose your own energy, attention, and decision patterns as a founder.
2. Build a personal operating system (routines, boundaries, recovery) that survives chaos.
3. Distinguish the work only you can do from the work you should route elsewhere.
4. Recognize and interrupt the founder failure modes: heroics, hiding, and burnout.

Lessons

Lesson 1.1 — You are the bottleneck (and that's fine, for now)

Teaching script (Sol):

Let me say the uncomfortable thing first. In a Kaern startup, you are the bottleneck. Every decision, every priority, every standard of quality flows through one human nervous system — yours. Founders hear "bottleneck" and flinch, like it's an accusation. It isn't. A bottleneck is just the narrowest point in a pipe; it determines total flow. So the question isn't "how do I stop being the bottleneck" — that comes later. The question is "how do I make the bottleneck as wide and as healthy as possible right now?"

Think of yourself as the engine of a small boat. If you redline the engine every day, you don't go faster — you seize. I've watched brilliant founders ship nothing for a month because they spent six weeks producing at 130% and then crashed. The boat that wins isn't the fastest for one hour; it's the one still moving at sunset.

So leading yourself starts with treating your own capacity as the scarcest resource in the company — scarcer than money. You protect it, you measure it, you spend it deliberately. Agents scale infinitely; you do not. That asymmetry is the central fact of your life as a Kaern founder.

What is one thing you did this week that drained you and produced nothing of value?

Worked example: Maya, founder of a Kaern startup doing automated bookkeeping for freelancers, tracked her time for one week in a simple notes file. She found she'd spent 11 hours manually reviewing agent-drafted emails she could have spot-checked in 20 minutes. The "review everything" reflex felt responsible but was actually her redlining the engine. She switched to reviewing a 10% random sample plus anything flagged low-confidence, freeing ~9 hours/week for customer calls — the work only she could do.

Hands-on exercise: For the next 3 working days, keep an energy log. Every 90 minutes, write one line: what I did and energy after (1–5). At the end, circle the two activities that scored lowest and produced least value. Write one sentence on how you'll eliminate, automate, or delegate each. Bring it to Lesson 1.3.

Common mistakes:

1. Treating busyness as progress — confusing motion with output.
2. Refusing to protect recovery time because "real founders grind."
3. Optimizing tasks before deciding whether they should exist at all.

Check for understanding:

• Why is your personal capacity scarcer than capital in a Kaern startup?
• What's the difference between widening the bottleneck and removing it?

Lesson 1.2 — Your personal operating system

Teaching script (Sol):

A company has an operating system: how decisions get made, how work flows, how the week is shaped. So do you — except most founders never designed theirs. They just react. Today we design it on purpose.

Your personal OS has three layers. First, rhythm: the fixed shape of your week. When do you do deep creative work? When do you talk to customers? When do you direct your agent fleet? Protect your peak hours for the work that needs your full mind, and shove shallow work into the valleys. Second, boundaries: the things you say no to so the yeses survive. A boundary you won't defend isn't a boundary; it's a wish. Third, recovery: not the absence of work, but the active refueling — sleep, movement, time away from the screen — that keeps your judgment sharp. Judgment is the product you sell; tired judgment is defective product.

Here's the analogy I love: you wouldn't deploy a service with no monitoring and no restart policy. Don't run yourself that way either. Build in the health checks. Build in the restarts.

If a stranger watched your calendar for a week, what would they guess you believe is important — and would they be right?

Worked example: Devon, a solo founder, was checking agent dashboards every 20 minutes, fragmenting his whole day. He redesigned his OS: deep work 8–11am (no dashboards), a single 30-minute "fleet review" at 11:30 and 4:00, customer calls in the afternoon valley, and a hard stop at 6:30. Output measured in shipped features per week went from 1.5 to 4 within a month — not from working more, but from a rhythm that matched the work to his energy.

Hands-on exercise: Draft your one-page Personal OS: (a) a weekly rhythm grid showing deep work / fleet direction / customer time / recovery; (b) three boundaries you'll defend; (c) two recovery practices and when they happen. Put it somewhere you'll see it daily.

Common mistakes:

1. Designing an OS for an ideal self instead of the actual you.
2. Leaving recovery as "whatever time is left" — it never is.
3. Letting the fleet's 24/7 nature pull you into 24/7 monitoring.

Check for understanding:

• Name the three layers of a personal operating system.
• Why is "judgment" the thing recovery is really protecting?

Lesson 1.3 — Founder failure modes: heroics, hiding, burnout

Teaching script (Sol):

Three patterns kill more solo founders than the market ever does. Learn to spot them in yourself early, because they feel virtuous from the inside.

The first is heroics: the belief that you must personally rescue every problem. It feels like dedication. It's actually a refusal to build systems, and it caps your company at the size of one human. The second is hiding: when things get hard, you retreat into the comfortable work — refactoring code nobody asked for, redesigning the logo — instead of the scary work, like calling the churned customer or making the org decision you've been avoiding. Hiding feels productive. It's procrastination wearing a tool belt. The third is burnout, which is not a sudden event but a slow erosion of caring, until one morning the thing you'd have died for feels like a chore.

The cure for all three is the same: honesty plus structure. You name the pattern out loud — "I'm doing heroics right now" — and you replace it with a system or a smaller, braver action. Leadership of others begins with this kind of leadership of yourself. You cannot ask your fleet or your future hires for honesty you won't give yourself.

Which of the three — heroics, hiding, burnout — is most tempting for you right now, and what's the smallest brave action you're avoiding?

Worked example: Priya kept "fixing" her onboarding flow for the third week running. In her energy log (from 1.1) she noticed the high-effort, low-value pattern. Naming it — "this is hiding" — let her see what she was avoiding: a pricing conversation with two enterprise leads. She blocked 90 minutes, made the calls, and closed one. The onboarding flow was fine; her courage was the bottleneck.

Hands-on exercise: Review your energy log from Lesson 1.1. Tag each activity as Heroics / Hiding / Real-work / Recovery. Identify your dominant failure mode this week. Write the one brave action you're avoiding and schedule it within 48 hours.

Common mistakes:

1. Mistaking heroics for leadership and rewarding yourself for it.
2. Not noticing hiding because the hiding-work is genuinely useful-looking.
3. Treating burnout as a willpower problem instead of a systems problem.

Check for understanding:

• How does hiding differ from genuinely important deep work?
• Why is "naming the pattern out loud" the first step in interrupting it?

---