HR, Culture & Remote Teams

Welcome to the room. I'm Sol, your tutor for this one. I've spent years building and unbuilding teams inside lean, AI-augmented startups — the kind where four people ship what used to take forty. That's the world you're operating in. At Kaern, you're not students playing founder; you are the founders, and the companies you reference here are your own Kaern startups. So everything we do is live ammunition.

This course is about the part of company-building most technical founders dread and most over-funded ones get wrong: people. Not in the soft, poster-on-the-wall sense — in the operational sense. How do you build a culture on purpose instead of by accident? How do you hire when you can't afford to be wrong? How do you pay people fairly when cash is tight and equity is your real currency? How do you run a team where nobody shares a timezone, let alone an office? And how do you do all of this with AI as a teammate, not just a tool?

Outcomes. By the end, you'll be able to: write a values set that actually changes decisions; run a hiring loop that screens for signal, not vibes; structure compensation and equity that holds up to scrutiny; design async-first operations; build a growth and performance system that doesn't require a manager looking over shoulders; and stay on the right side of employment law and human wellbeing.

We learn the way it's done in a real classroom: I explain, we work an example together, you do the reps, we name the traps, and I check whether it actually landed. Let's build.

Module 1: Building Culture Deliberately

Learning Objectives

• Define culture as a system of repeated behaviors and decisions, not slogans.
• Write a values set where each value implies a concrete trade-off.
• Distinguish culture you declare from culture you reward.
• Audit your own early decisions for the culture they're silently teaching.

Lesson 1.1: Culture Is What Happens When You're Not Looking

Teaching script (Sol): Picture a riverbed. Nobody designs where a river goes — the water just keeps taking the path of least resistance until the channel is carved so deep that one day everyone calls it "the way the river flows." Culture is that riverbed. It's not your values page. It's the groove worn by every small decision: who gets praised in the standup, what behavior gets quietly tolerated, which Slack message gets a fast reply and which gets ignored.

Here's why this matters for you specifically. In a lean, AI-augmented startup, you have very few people and very high leverage per person. That means each behavior gets amplified — one founder cutting a corner under deadline isn't one data point, it's a precedent broadcast to a tiny, watching team. Culture compounds faster the smaller you are.

Most founders think they'll "do culture later, after product-market fit." But the riverbed is forming right now, with or without you. The only question is whether you're carving it deliberately or letting the terrain decide.

So before we write a single value, I want you to sit with this: what behaviors are your current habits already teaching your team to repeat?

Lesson 1.2: Values That Cost Something

Teaching script (Sol): A value that costs you nothing isn't a value — it's a decoration. "We value integrity." Cool. Who's against integrity? Nobody. That word can't help anyone make a hard call at 2am, which is the only time values matter.

Think of a value like a compass that has to point away from something tempting. Real values create trade-offs. "We ship fast and accept rough edges" means you're explicitly not prioritizing polish — and someone who loves polish now knows this isn't their shop. That's the test: a useful value tells you what you'll sacrifice.

Why does this matter in an AI-augmented team? Because AI removes a lot of the friction that used to force decisions into the open. The machine drafts the email, writes the code, summarizes the call — and the human values that should govern those choices can quietly evaporate. Your values are the thing that decides when the AI's fast answer is the wrong answer.

Here's a sharper way to write them: phrase each value as "We choose X over Y, even when Y is tempting." That forces the trade-off into the open.

So look at your draft values — for each one, can you name the good thing you're willing to give up to honor it?

Worked Example

A two-founder Kaern startup writes: "We value speed." Sol reworks it with them into a trade-off form:

Bias to shipping over consensus. We'd rather ship a B+ decision today than a perfect one next week. The cost: we will sometimes redo work. We accept that.

Now it's testable. When a designer wants three more days to perfect a flow, the value gives the team a shared answer — and it tells a consensus-loving hire this might not be their fit. They add a guardrail: "except for anything touching payments or user data, where we slow down." A value with a documented exception is stronger than a slogan.

Hands-on Exercise

Write three values for your Kaern startup in the format "We choose ___ over ___, even when ___ is tempting." For each, write one sentence naming a real recent decision it would have changed. Then, separately, list three behaviors you currently reward (with praise, speed, or attention) and check: do they match the values you just wrote? Note every mismatch — that gap is your real culture.

Common Mistakes

1. Writing aspirational values instead of actual ones — describing the company you wish you were, so the words never match daily behavior.
2. Too many values — eight values is zero values. People remember three.
3. Declaring culture without changing rewards — values on the wall while the loudest, corner-cutting person keeps getting promoted.

Check for Understanding

1. Why is "We value integrity" a weak value, and how would you rewrite it to cost something?
2. What's the difference between the culture you declare and the culture you reward — and which one wins?
3. In an AI-augmented team, why do values become more important, not less?