(That sentence makes me happier than it probably should.)

Our club puts on Rover Rendezvous once a year. We reserved an entire campground, and the weekend ran on camaraderie and campfire stories. On Saturday, John and I took on White Mountain, a trail rated moderate to difficult.

I’m not fully comfortable on difficult trails yet. So when things got serious, John took the wheel.

Things got most serious at the big hill climb. It’s steep and technical, and a spotter named Keith was working it, moving rocks for some rigs and showing drivers where to go. We were second to last up the hill.

There’s a running joke that when John drives, spotters give up early. Keith gave him one quick signal, a little to the left, then dropped his hands and waved us through. We made it up. It went like that the whole day. We never needed a spotter.

Plenty of other drivers needed Keith, and that says nothing bad about them. Every driver brings a different comfort level, and every rig brings different capabilities.

I made my call back at the trailhead. I knew where my skill ran out on that trail, and I knew John’s didn’t run out there.

Which is a little ironic, because I’ve written a book about leadership, and its first chapter is called “The Passenger Seat.” That chapter is focused on the people sitting in it. It’s about leaders who drift, going along with decisions because staying quiet feels easier than choosing.

On Saturday, I rode in the passenger seat on purpose.

Choice and drift can put you in the same seat. What matters is whether you decided to be there. Part of leadership is knowing when to trust someone else to lead, and making that call with clear eyes.

That’s what the whole book is about: seeing the ground you’re actually standing on before you commit people to it.

Read the Terrain: Leadership Under Real Conditions launches November 2.

Now for the ask.

I’m looking for 15 to 20 advance readers. (Thirty would make my year, but I’m trying to be a grown-up about this.)

If you raise your hand, you’ll get an ePub copy of the book next week. It runs about 150 pages, so think a few evenings with a cup of coffee. I’ll check in with you in mid-October to see how the reading is going.

What I’m hoping for in return is an honest review on Amazon, Goodreads, or both, ideally during launch week (November 2 to 9), and no later than mid-November. Honest means honest. If a chapter didn’t work for you, say so. That’s more useful to me (and to the next reader) than five polite stars…even though I do love stars.

To join, fill out this short form by Sept 30: Book Launch Page

Oh, and here’s my question for you this week: where are you sitting in the passenger seat right now, and did you choose it?

P.S. White Mountain has its own chapter in the book. The last time I wrote about that trail, the day ended with a two-vehicle winch and a sidewall caught on a rock. (This weekend went better.) Advance readers get the whole story first: https://forms.gle/xwjrCJjzLrV5yHNz7

Twenty-five years ago was around 2001. We had indestructible Nokia brick cell phones and T9 texting, but carrying a phone was an entirely different experience of reality. A phone was an appliance. You hoarded your minutes until 9:00 PM when they were free. When you finished a call, you put the phone back in your purse. You lived with long stretches of quiet and the simple grace of not knowing where everyone was every second of the day.

As I looked at the distance between that tactile world and this one, I wrote:

We are the last of the non-digital.

The irony was sitting right there in my thumbs. We were two people marveling at the lost beauty of an untethered existence, yet our reflection was mediated entirely through glowing glass rectangles and cell towers.

We are not living in that analog world anymore, and pretending we can retreat into it is a fantasy. But as modern technology expands at a velocity that outpaces our ability to metabolize it, we have created an environment of profound cognitive dissonance that leaves our newest generation of workers stranded between our unexamined assumptions and our outdated institutions.

Subscribe now

The Consumer Trap

For the past fifteen years or so, most organizational leaders have operated under a comfortable myth: Because younger workers grew up with screens, they must be digitally fluent.

We assume that living inside an ecosystem means knowing how it works. The generation entering the workforce today was handed consumer technology engineered to be entirely frictionless. Apple, under Steve Jobs, spent billions ensuring that users would never have to see a command line, manage a local file directory, understand a data protocol, or troubleshoot an operating system. Modern interfaces are designed to keep people inside walled gardens where every gesture is measured, predicted, and monetized.

These young adults did not fail to learn systems architecture; they were insulated from it. They were handed slot machines, not flight simulators.

By contrast, my generation had to understand how the machine functioned just to make it run. To get online in 1996, when I bought my first Gateway PC, I had to configure hardware, diagnose connection failures, and understand where files lived on a physical drive. That frustrating friction built a durable mental model of systems logic.

When we call modern young adults “digital natives,” we flatter ourselves into thinking we gave them a head start. In reality, we gave them black boxes they were never taught to take apart.

The Industrial Hangover

This deficit hits an immediate dead end in workplaces still nursing an industrial hangover.

Knowledge work remains organized around the factory clock. We pay people by the hour and evaluate performance by visible seat time. The entire system rewards friction: typing out emails keystroke by keystroke, manually reformatting spreadsheets, and spending full days on clerical busywork that signals value.

When modern tools make it possible to compress an eight-hour clerical backlog into twenty minutes of high-level synthesis, legacy management structures freeze. If an organization measures value by elapsed time, high-leverage work looks like cutting corners, and spending all day on administrative minutiae looks like dedication.

The whole setup makes no sense. In school, using modern tools is treated like cheating, and students are rewarded for taking the longest, slowest path possible. Then they enter the workforce, where bosses assume they are computer geniuses, offer zero training, and quietly punish them for finishing early because the company still pays by the hour. We expect young people to survive the wild west of modern tech while judging them on old factory habits.

Share Read the Terrain

A Two-Way Street

It is easy for older generations to slip into a tired routine: rolling our eyes at screen habits or grumbling when an entry-level worker cannot find a document saved to their own drive. You know the drill…

But that critique misses the mark entirely.

If this exchange only flows in one direction, it isn’t leadership; it’s just a tired lecture. And the generation coming up behind us has plenty to teach us about the reality of living inside the machine.

They have a better built-in BS detector than any generation before them. After spending their entire lives swimming through targeted ads, sponsored content, and algorithmic sales pitches, they can spot performative nonsense from a mile away. When they push back against sitting in an office chair for eight hours just to look busy, they aren’t being lazy. They just refuse to play along with an obvious charade. In the process, they force the rest of us to admit how much time we waste doing things the hard way just to look productive.

They also know firsthand what it feels like to spend their formative years under a digital microscope. While older adults study screen addiction and tech habits from a safe, theoretical distance, younger people have lived the constant stress of being watched, scored, and recorded since middle school. They know where the water is toxic because they grew up swimming in it.

The real goal is not to lecture them about how great life was before the internet, nor is it to throw up our hands and let phone apps run the workplace. The real work is meeting in the middle. We need to throw out the obsolete factory habits that waste their time, pull back the curtain on how modern software actually works under the hood, and build an environment that values real human insight over mindless busywork.

Yet if the cost of this dissonance is so clear, why are we so stubbornly terrified of engaging with it?

Why do school boards, corporate policies, and community leaders cling so desperately to magnetic pouches, digital firewalls, and total prohibition?

To understand that, we have to look directly at our own generation: at the grief, the fear of obsolescence, and the quiet panic of being the last people who remember what the world felt like before the lights were turned on.

Leave a comment

(Next up in Part 2: The Psychology of the Pouch: why we retreat into prohibition, the realities of synthetic information warfare, and how to build cognitive firewalls instead of locked gates.)

I used the word mandate. Out loud. More than once. As if saying it harder would make it happen faster.

What I didn’t do was look at who was in front of me. Some of those teachers were a few years from retirement and had long since made their peace with letting technology pass them by. Others were spending every ounce they had teaching five-year-olds to read, which does not leave a lot over for learning to build a webpage. None of that slowed me down. I had a plan and a timeline, and I pressed.

The superintendent said it kindly, which somehow made it land harder. You are pulling a rubber band, he told me. Far and fast. A rubber band pulled that way snaps. Tug it a little at a time and it stretches, it accommodates, it will hold far more tension than you’d think. But only if you let it adjust to each new length before you ask for more.

That was the day I struck the word mandate from my vocabulary. I have not used it since.

I’ve been writing here for a while about what happens when leaders start managing how things look instead of reading what is actually in front of them. Those essays were not practice for something else. They were the book showing up in pieces, before I was willing to say the word book out loud.

So. Read the Terrain: Leadership Under Real Conditions. Coming this winter.

Eleven patterns. Passenger-seat leadership. The applause trap. The load-bearing leader. Each one is something you can already feel and have never had words for, which is the whole point of naming them. You cannot interrupt a pattern you cannot see.

There are no borrowed frameworks in it. No research citations, no expert I’m quoting to make the argument for me. Everything in it either happened to me or happened in front of me, and a fair amount of it is me getting it wrong first. There’s a chapter about the day I lost a job for saying the thing out loud. There’s a chapter about a hill climb in Last Chance Canyon, where I had two ways up and picked the harder one rather than admit in front of the group that I was out of my depth. (The Rover had opinions about that. So did the radio, which I ignored.)

If you are the calmest person in a meeting that is on fire and also the most alone in it, I wrote this for you. If everyone leans on you and nobody holds you steady, same.

Why I’m telling you before I’m ready

The whole book is my attempt to not pull the rubber band too tight, too fast, on people who are growing into their own leadership. Which would be a strange thing to write and then hand you as a finished, perfect object with a countdown clock attached.

So you get the middle. The proof copy that comes back with errors in it. The cover I’ve looked at so many times I can no longer tell if it’s good. That part is more useful to you than the polished announcement would be, and it’s more honest about how any of this actually gets made.

There’s a page now: laurakspencer.com/thebook

Sign up there and you’ll get the cover before it goes anywhere else, the release date the day I actually have one, and a shot at the early reader team. (That last one means a free copy in October and a small favor asked of you in November. I’ll explain when we get closer.)

That’s the whole ask. No preorder, no launch team energy. Just tell me you want to know.

A question for you

Where are you pulling the rubber band right now? Not whether you’re pulling. How fast.

Reply and tell me. I read all of them, and I’d bet money at least one of you names a pattern I missed.

Leave a comment

I keep blocking gray rectangles on the fall calendar for things that do not exist. No agenda, no title, just a hard border drawn against October. A placeholder for a breath I have not figured out how to take yet.

For longer than I want to admit, I measured my life by how much I could carry without visibly shaking. A good week was a heavy week where nothing dropped. Stack the boxes high enough and exhaustion starts to feel like purpose. It is a seductive trap because people praise you for it. They watch you hold the roof up with one hand and they say, I don’t know how you do it. And I would smile, and my shoulder would keep giving out where nobody could see it.

The tally I keep now is different, and a lot less flattering.

I count how many decisions had to come through me. Not the visionary work that goes in slide decks. The low-grade friction of everyone waiting on a nod, a sign-off, a “Did I do good, boss?” When that number spikes, I have stopped calling it a busy season. A busy season implies weather. Something that blew in off the coast that I just have to wait out under an umbrella (which doesn’t happen to often in So Cal).

It is not weather. It is architecture. I built it, usually out of an unexamined instinct that if I let go of the wheel for twelve seconds the whole thing ends up in the ditch.

Looking at that number honestly the first time was like catching my reflection in a dark window before I was ready for it. The impulse is to fix it fast. Write a few brisk emails, hand off three projects, call it delegation. Real handoffs do not work like that. It’s taking a lot of time. Some things are becoming clumsier in the process while they find new definition because they missed nuance I spent ten years learning the hard way.

That middle stretch, where the work is worse than what I would have done and I am not allowed to reach in and take it back, is close to unbearable. It takes everything I have not to grab it out of their hands. But if I sit still long enough, something else happens. It comes back better. Different, sharper, not mine anymore. And in the process, they get to develop their own nuance and experienced ways.

Most of what I want from my work right now is not an addition. Not a bigger stage, a larger team, another project with my name on it. It is an absence.

I want a list of things that stop happening.

Fewer calls I replay at two in the morning, dissecting my own tone. Fewer moments where I hold whatever I am actually feeling so I can be the steadiest nervous system in the room, because the room is brittle and needs an anchor. There is a specific kind of tired that comes from being everyone’s shock absorber. I did not notice how much of the road I had taken into my own bones until I tried to sit still.

I don’t have a clean lesson here to give you. No three-step framework for reclaiming my time, or whatever we are calling it now.

I just have gray blocks sitting on the screen for mid-October, and a question I have not answered:

Am I worn out by the terrain of this particular year, or have I outgrown the shape of the container I built?

I don’t know yet.

Where does that land for you?

Except nobody remembers a policy manual when the school year actually hits.

The stuff that actually holds a school together, the stuff that keeps kids safe, keeps families enrolled, and builds real trust, happens in tiny, unscripted moments. It’s a teacher’s voice on a first call home. It’s how someone speaks to a kid in a crowded hallway. It’s whether a nervous parent feels heard or just processed when they try to navigate the system.

If you want a school year that actually works, stop optimizing for transactional task lists. Start building for real human connection.

1. Tone Sets the Climate; Leaders Set the Standard

Basic customer service in a school is transactional. It’s passing out a syllabus, grading a quiz, or logging attendance. Hospitality, though? That’s transformational. It’s the deliberate effort to make every student, parent, and coworker feel seen and valued.

Good leaders don’t just dump a bucket of compliance tasks on their staff during kickoff week. They get their teams to look closely at tone. They test out how the exact same sentence hits differently depending on the warmth behind it, and they map out how people should actually feel during an interaction. Tone isn’t something that just happens by accident. It’s a choice your organization makes.

2. Anchoring Promises: The Core Non-Negotiables

If you don't want your culture to end up as a cheesy poster in the breakroom, your team has to build non-negotiables out of real empathy. Skip the rigid, top-down rules. Successful teams make promises anchored in human impact:

“Because we want our families to feel [Value], we will [Action].”

When teachers and staff write their own commitments from a place of empathy, you don't have to police compliance. It happens naturally because people are driven by purpose instead of policy.

3. Operationalizing “The Connected Moment”

Culture lives or dies in your daily operations. Every team, whether they’re teaching math, running special ed, or working the front office, has specific touchpoints with kids and parents.

A connection-first launch makes teams zoom in on their single most important touchpoint. We call this their Connected Moment. They take that moment and completely redesign it. When you turn a routine onboarding call, an academic check-in, or a basic email into a high-touch, human connection, it changes the entire trajectory of your year.

Building a Connection-First Culture

You can't expect teachers to build connection-first classrooms if you aren't running a connection-first organization. When you front-load your school year with culture, curiosity, and genuine hospitality, you build up a relational bank account that keeps your team afloat when the year gets tough.

Tasks tell people what to do. Hospitality reminds them why it matters.

If you are an educational leader looking to reimagine your staff launch, shift your culture toward radical connection, or operationalize hospitality across your teams, feel free to reach out—I love partnering with schools to design transformational experiences.

Sandstone Canyon is easy to miss if you’re moving too fast. It branches off Fish Creek Wash without much announcement. A sign. A turn. If you weren’t already in the mood to slow down, you’d keep going.

Once you’re inside, the walls come up quickly. Fifty feet, maybe seventy. The floor is still sand and crushed dirt, still nothing anyone would call technical, but there isn’t much extra room. You notice that right away. The way the canyon quietly narrows your choices.

We’re used to places that reward momentum. Sandstone doesn’t. It asks you to pay attention, and not just in the don’t-hit-anything sense. This is a canyon that took millions of years to become a canyon. The walls hold light differently depending on the hour. The color shifts as you move. If you’re only focused on getting to the end, you miss almost everything that’s actually there.

Every so often you have to wait for someone coming the other way, or ease past a narrow stretch. That part isn’t hard. It just makes it very clear that you don’t get to set the pace.

Most days, you think you do.

The speed I was rewarding

For years I ran my days as a queue. Clear the thing, clear the next thing, feel the small hit of finishing, move on. It felt efficient. Over time it just became automatic. Automatic looks like efficient from the outside. It is not the same thing.

I rewarded it in other people too. The fast reply. The closed loop. The person who kept things moving. I was measuring pace because pace was easy to see. Attention is harder to see. It doesn’t show up in a status update.

And living at that speed flattens things. Even good weeks start to feel thin. You get through a lot. You notice almost none of it.

What the canyon insists on

Out in Sandstone that speed is harder to keep. The canyon keeps interrupting you. The walls keep catching the light. The scale of it keeps insisting that you are moving through something that does not care how quickly you want to reach the end.

Most of the leadership work I actually care about behaves the same way. The conversation that changes something. The person who has quietly stalled and is waiting to see if anyone notices. The pattern under the pattern. None of it survives being rushed. You can process it fast. You cannot see it fast.

One of my standing questions about any tool or habit is what it makes too easy to do poorly. Speed makes attention too easy to skip. You can run at that pace for a long time and call it leadership, right up until you miss the thing that mattered.

The pace was never mine to set

You leave the canyon, of course. You always do. You go back to regular weeks and the usual noise, and slowly you start moving too fast again. Until the next place makes you notice.

The work does the same thing, if you let it. It narrows. It catches the light. It refuses to be hurried. The pace was never yours to set. The only choice was whether you were going to pay attention while it set it for you.

A question for you

What have you been trying to get through lately, that might actually be asking you to slow down and look?

Hit reply and tell me what you saw once you stopped moving.
I read every one.

Leave a comment

Then he said it. “We never lose. We either win, or we learn.”

I wrote it down fast. Then I sat with it on the drive home and the second thought showed up, the one that usually does. I have seen that line before. It is on a mug somewhere. I wrote it down anyway, which tells you something about how good it feels to hear.

The mug leaves off the important part.

A loss does not teach you anything on its own. It just sits there. Raw material. Someone has to convert it, and that conversion has a price. The debrief nobody schedules. The honest question about who dropped what. The willingness to say the plan was wrong and not just unlucky. That is the work. It is boring, it is expensive, and most of us skip it.

So the team loses. Everyone gathers. Somebody says a version of “well, we learned a lot from this.” Heads nod. It feels like a lesson. Then Monday arrives and nothing is different. The words did the emotional work of learning without any of the actual work. Everyone feels resolved. Nothing changed.

The rollout I was sure of

Years back I was Executive Director of Innovation for a district. Big role. A real step up, and I was eager to show I could do things with it. My team got handed a job I was sure of. Move parents off their idea of what school was for and toward the thing we all knew was coming. Collaboration. Design thinking. Executive functioning.

Our parents had done everything right. Lawyers. Doctors. People for whom school had been a clean staircase to a good life. We were asking them to trade the staircase for something they could not picture yet.

We built the whole rollout. Parent sessions. Workshops. A sequence, a timeline, the works. Good on paper.

It did not take. And slowly the admin drifted back to what they had always done. Past practice, quietly restored, like the initiative had never happened.

Not enough buy-in, I said.

That diagnosis cost me nothing. It put the failure on the parents. It let me keep the plan, keep the theory, and keep the version of myself who had run a smart rollout that other people were not ready for.

The lesson I did not pay for was harder. I had aimed a persuasion campaign at a belief that had personally made every one of those parents successful. No workshop out-argues a life that worked. And I was so eager to prove I belonged in the role that I mistook my own certainty for a plan. I felt the loss. I named it something that let me off the hook. Then I moved on and changed nothing, and the admin sliding back to old habits was the proof.

There is a quieter version of the same move. Sometimes we reach for “we learned” so we do not have to sit in the loss at all. You lost. You are allowed to say that first. The learning does not start until you stop reaching for the reframe.

The bill comes either way

A loss does not make you wiser. It hands you an invoice. The lesson is whatever you are willing to pay for it afterward, in time and in honesty, and the first explanation you reach for is usually the one that keeps you comfortable. Next time your team says it learned a lot, ask who the explanation protects. Then ask what is different on Monday.

A question for you

Think of the last real loss your team took. What actually changed after it, and what just got called a lesson?

Reply and tell me. I read every one.
Thursday, the paid companion turns this into a debrief you can actually run.

Leave a comment

Point true north, he said, or something close to it. I don’t remember the exact words because my memory is shot. But I do remember thinking it was a cool thing to hand someone, and I remember, years later, understanding why it was the thing he chose to give me. He gave me the compass because he couldn’t give me a career’s worth of experience. (This was long before I ever wrote a word about reading terrain, by the way. Funny how the universe works…)

There’s a quote I have seen so many times in leadership blogs and Instagram quote accounts: Success leaves clues. Study the people who made it, find what they did, do that. It sounds so smart because it is half of a true thing. The half it leaves out is the part that I think matters more

The Clarity Was Not a Technique

My boss led with clarity and integrity, and when I was new I tried to figure out how he did it. I studied his every move. His presentation style; his email tone; and the way he walked in to a room. I even watched how he ran a hard conversation and tried to copy the moves.

I could not copy it. Not because I wasn’t paying attention, but because the thing I was trying to copy wasn’t a technique. It was a residue. His clarity was built off of thirty years of mistakes wearing a clean shirt, and I did not have the mistakes yet. If I had successfully copied the output, I’d have copied the one thing that couldn’t transfer, because it wasn’t a skill he was performing. It was a scar that had healed a certain way.

Most successful leaders show up polished and let you assume they walked in like that. They present the finished version. The clues are there, technically, but they’re buried under the presentation, because nobody’s incentivized to show you the wound.

My boss did the opposite. That was the rare part, and the part I value so much more than any leadership book or training.

The Empty File

He told me once about a person he couldn’t terminate.

The employee wasn’t able to do the job. My boss knew it, the team knew it, and when he finally moved to let the person go, the union stopped him cold. He didn’t have the paperwork. No documented attempts to counsel, no record of redirection, no file showing he’d tried to bring the person along before giving up on them. The file was empty. So the person stayed, and the mission carried the cost of it, for a long time.

That was the wound.

And it explained something I’d felt without understanding. He had no hesitation about hard conversations with me. He’d tell me straight when I was getting something wrong, and I got a lot wrong that first year. After all, I was a new leader making rookie mistakes at a respectable clip, so he had material to work with. But it never felt like a reprimand. It felt like he wanted me inside the success of the thing we were building, and he was clear that this was the reason.

I understand now that his directness wasn’t a personality trait. He wasn’t born unafraid of conflict. He’d once been conflict-avoidant enough to leave a file empty, and it had cost him a person he couldn’t remove and a mission that dragged. The grace he brought to a hard conversation was scar tissue over that exact place. He talked to me directly because he knew, in his body, what silence could cost.

That’s the clue. Not his clarity. The empty file underneath it, and the fact that he chose to show me the file.

What He Could Not Hand Me

You cannot give someone your mistakes.

That’s the real limit of success leaves clues. The clue that matters most is usually the one that doesn’t transfer, because it isn’t a move, it’s a mark left by something that already happened to you and hasn’t happened to them yet. He couldn’t hand me the empty file. He couldn’t hand me the years. So he handed me a compass, which is a beautiful object and also, I think, a confession that the most important thing was the one thing he couldn’t pass across.

What he actually gave me wasn’t the direction. It was the permission to make my own scars legible instead of smoothing them over. To leave the clues out where the next person can read them, empty file and all, rather than presenting the clean version and letting them believe I arrived this way.

Success leaves clues only when someone decides to leave them. Most success buries them. He dug his up and set them on the table for me.

A question for you

What is one scar underneath how you lead that you’ve never let anyone see, that would teach the person coming up behind you more than any polished version of you ever could?

Reply and tell me. I read every one.

(Thank you to Claude AI for helping me ground this reflective moment into something tangible for others!)

This is the part where I tell you what to actually say, because “give each group the opposite” is easy to nod at and hard to do at 6pm with a broken bridge and no plan B in sight.

Since the panicker is loud and the shrugger is quiet, leaders tend to spend all our energy calming the noise and none reopening the calm. So let’s discuss both.

The panicker needs a fact, not a feeling

When someone is spiraling, the instinct is to reassure. It will be okay. We’ve got this. Reassurance is a feeling, and a spiraling person cannot hold a feeling. They can hold a fact. “This bridge broke last year too. We fixed it in four hours. Here is the plan B, go run step one.” Specific past. Specific number. Specific next action. You are handing them peor estaba in a form they can actually use.

The shrugger needs a question they cannot answer with “it’s fine”

This is the harder one. So I wrote you a prompt for it.

Read more

So I plan for it. I keep launch day clear. I tell the team ahead of time to have a manual plan B ready, because the bridge is going to do what the bridge does. This is not pessimism. This is simply learning after multiple years of the same appointment.

This year it broke again. I sent the warning, asked for the backup plan, and then heard nothing for hours. So near end of day I sent the question I actually needed answered: do I need to buy five Monster energy drinks because I am fixing this by hand all night, or do we have the bridge working?

The replies came back in two flavors. And they are the whole story.

The panickers

One group was already spiraling. Is it still broken. Oh my gosh. This is bad. Everything is on fire. You know the energy. It fills a thread fast, and it is loud, and it is genuinely convinced the sky is coming down this time.

There is a grandmother saying for these people. A friend of mine grew up in Mexico, and her grandmother used to say peor estaba ... it was worse before. Whatever you are panicking about now, there was a harder version you already survived. For the spiraling group, that phrase is medicine. Dude, it will be fine. We fix this one every year. By tomorrow you will not remember it was broken, because it will not be broken. That is not dismissal. That is perspective handed to someone who has lost theirs.

The shruggers

The other group was calm. Too calm. It is better than last year. That was the whole message. Not, here is what broke and here is the root. Just, it is better than last year, so let us not go digging.

And here is where the same saying flips on you. Peor estaba is medicine for the panicked. For the calm, it is anesthetic. It is better than last year is how a broken thing survives multiple years. It is the reason the bridge is still a manual triage every single launch instead of something we actually fixed. Nobody is upset. That is exactly the problem. The comfort of “at least” becomes the ceiling nobody names.

The part the grandmothers say with a laugh

There is a funnier version of this saying, and it says the quiet part out loud. Peor estaba antes, que ni novio tenía. Roughly, it was worse before, when I did not even have a boyfriend. You say it with a shrug about a mediocre situation you are keeping because the alternative feels worse than settling.

That is the calm group’s real position, said honestly. It is not only that the bridge is better than last year. It is that a broken-but-familiar bridge feels safer than the work of tearing it apart and building something that holds. Better a bad boyfriend than none. Better the process you know than the discomfort of fixing it. “It is better than last year” is often just this, dressed up in a status update.

What the saying is actually for

The saying is a tool, not a temperament. Same five words, two opposite prescriptions, and the leader’s job on launch day is to know which one a person needs.

The panickers need peor estaba poured over them like cold water. It was worse before. You will survive this. Now breathe and fix the thing. The shruggers need the opposite. They need someone to take the comfort away, to say yes, it is better than last year, and we are still going to find out why this bridge breaks on the same day every year. Hand the calm to the panicked. Take the calm from the comfortable. That is the whole move.

Share Read the Terrain

A question for you

Where are you telling yourself “it is better than last year” as a reason to stop looking?

Reply and tell me what your bridge is. I read every one, and I answer.

Leave a comment

It did not happen that fall. It happened over years, and I only saw the shape of it later.

At the start my mother ran everything and my youngest orbited her. Little things first. Biscuits. Basting the turkey. My mother narrated the whole time. My youngest listened more than she cooked.

Then the work started to split. She took over the sides. She started helping plan the oven, which dish went in when so it all came out hot at once. My mother sat down more. Directed from the kitchen table. The questions got fewer.

Then the knee went, and there was no one else at the stove.

Someone sent me a TikTok video about teaching a kid to bake a box cake. First time, the parent does most of it while the child watches. Second time, they split it. Third time, the child bakes it and the parent stays out of the kitchen. Three passes.

The video called it executive functioning. Planning the steps. Holding the sequence. Knowing what goes in the oven before you need it there. A kid learns all of that on a box cake, and the cake is almost incidental.

I have watched leaders skip that same purpose their entire careers. We hand out tasks. We almost never teach the executive function underneath them.

We hand over the cake and call it delegation

Some of us never leave the first pass. It is faster to do it ourselves, and we promise we will teach it properly next quarter. Next quarter we are still holding the spoon.

The rest of us jump straight to the third. Here, you own this now. Good luck. Then we act surprised when it comes out raw in the middle. We gave them the outcome and none of the passes that make the outcome possible.

The middle pass is the slow one. Standing next to someone while they do it worse than you would (and yes, I snatch the spoon back more than I will admit, the same as my mother did at that stove in the beginning). Answering the questions. Letting them ruin one before they get one right. That is the pass that does the teaching, and it is the first thing we cut when we are busy.

What a forced exit reveals

By the time you are pulled out of the kitchen, the teaching is done or it never happened. The exit only tells you which. My youngest was already a cook before the surgery. The surgery just moved up the day I found out.

The real question is a simple one. Does the dinner still happen when you are on the couch with your leg up?

A question for you

When you were last out unexpectedly, sick, traveling, offline, what did your team handle without you, and what fell apart?

Hit reply and tell me. I read every one.

Share Read the Terrain

Most leaders treat this as one problem. There are two.

The first is capability risk. The team cannot function without this person, and that exposure is real whether or not they ever leave.

The second is retention risk. This person has every reason to take the next offer, because the place that relies on them most is the place doing the least with their career.

You cannot fix one by fixing the other. Promote them out of the bind and the hard jobs still come back wrong. Build redundancy and stay silent, and they read it as you quietly arranging their replacement. Both have to move at once.

Run the two-week test first

Before any of the moves below, do this. Picture the person gone for two weeks. Not quit. Just out, no phone.

Write down every task, decision, and judgment call that stalls or routes to someone scrambling. Be honest about the small ones, the “oh, only she knows the trick for that” ones. That list is your dependency map.

(I have been the leader who ran a version of this test with my IT team and then quietly hoped nobody would quit. Hope, it turns out, is a prayer with a spreadsheet attached.)

What the list actually tells you

The list you just wrote looks like proof of how good they are. Read it again. Every line is a place the work lives in one head and nowhere else. That is an audit of how exposed you are, and you have until their next offer to close it.

Read more

He is good in the way that takes years and cannot be faked. People seek him out for his opinion on the tough jobs they can’t get right. New welders get sent to him for guidance, because he can explain the part the blueprint leaves out. By any honest measure, he is one of the most skilled people in the facility. (Yes, I’m proud, but it’s true)

He has never been offered a path up. People with less of his skill move into management, because they can be replaced. He stays at the bench, because he cannot.

I used to think that was a quirk of one shop. Unfortunately, it is not. I have watched the same thing happen in schools, in central offices, in the military … in every org I have led or sat inside. The most capable person becomes the one the system quietly decides to keep exactly where they are.

Load-bearing is a job description no one writes down

The system cannot promote the person it cannot afford to lose. That is the whole mechanism. Move him, and the hard jobs start coming back wrong. So he gets counted on. The promotion goes to someone the shop can picture doing without.

Counted on is comfortable for everyone above him. It asks nothing new of the org. It just asks more of him. His reliability is doing the work a real system is supposed to do. And because he is so reliable, nobody has to build the system.

Run it through the four questions

This is where I stop guessing and start diagnosing. Four questions, asked about the practice itself. The practice of resting the work on one person.

What is this for? On paper, keeping him at the bench is for quality. The hard jobs get done right. Today’s risk goes down.

What does it strengthen? This quarter. The order that ships Friday. The manager who gets to say the tough job is handled.

What does it replace? The slow work of building depth. Nobody else learns the hard welds, because he is always there to catch them. Documentation, cross-training, a second person who can do the thing... all deferred, because one person absorbs the whole need.

What does it make too easy to do poorly? This is the one that stings. It makes it too easy to never plan for the day he is gone. To read one person’s steadiness as a working system. To skip the expensive, uncomfortable work of redundancy. And to ignore the offer that is coming for him, because someone outside the building will do the math the shop refused to.

You did not keep him. You stalled him.

The shop believes it protected itself by holding him in place. It did the opposite. It built a single point of failure and called it dependable. Indispensable people do not stay indispensable inside one building. They get an offer, and the promotion this place would not give them becomes the first line in the next one. There was a clock running the whole time. The org just refused to look at it.

A question for you

Who is the load-bearing person on your team right now, and what would actually break if they took a better offer next month?

Hit reply and tell me who came to mind. I read every one.

Back Tuesday with the next field note.

Leave a comment

I had to tell a staff member we were not renewing his contract.

I knew the decision was right. I had known for weeks. And I still walked in and stuttered through it. I started about three steps back from the actual news, easing in, laying context, building a runway nobody asked for. By the time I got to the sentence that mattered, he had already done the math on my face and gone defensive, and I had gone defeated, and the two of us just sort of performed the rest of it. He left upset with the organization. The maddening part is that the decision was sound. What he reacted to was me, stalling, making him sit inside the not-knowing while I warmed myself up.

For years I thought conversations like that went badly because I was not brave enough walking in. So I worked on the bravery. I pep-talked myself in elevators. I told myself to just be direct. It did not help, and I could not figure out why. I would walk in steady and walk out having made it worse.

The bravery was never the missing piece

Here is what I eventually noticed, mostly by getting it wrong in front of people who deserved better.

The conversation almost never fails in the hard middle. It fails in the opening. In the first thirty seconds, while I was still warming up and softening and easing in, the other person had already figured out something bad was coming and stopped listening to me entirely. They were now running their own internal monologue (am I getting fired, do I argue, do I call someone) and everything I said after that landed in an empty room.

The softening was the problem. Every gentle preamble I added to spare them just stretched out the worst part, which is the not-knowing. I told myself I was being kind. I was being kind to me. I was the one who needed the warm-up.

What winging it actually costs

When you walk in without a structure, you improvise. And under pressure, improvising means you do whatever lowers your own discomfort fastest. You over-explain, because explaining feels like control. You apologize too much, because their face is doing something and you want it to stop. You go vague on the actual message, because the clear version is the one that hurts.

So the person leaves without the one thing they needed, which is to know exactly where they stand and what happens next. They fill that gap with the worst available story. And now you have a second problem stacked on the first one: a person walking around with a version of events you did not intend and cannot easily correct. (Mine walked around with his for a while. I earned that.)

I have cleaned up after my own kindness more often than after my own bluntness. By a wide margin.

The reframe

Having a script for the hardest conversations feels slimy. Like you are handling someone, running a play on a human being who trusted you. I resisted it for years on exactly those grounds. Then I understood what the script is actually for. It holds you steady when your own nerves are screaming at you to escape, and that steadiness is what lets the person in front of you get your full attention instead of your panic. The structure is the kindness. The preparation is how you show up human.

So here is the structure I use now...

Read more

My father did the opposite. He would come in, sit down, and say one line. “I’m very disappointed in you.” That was the whole opening. And it hit. Every time.

It hit because there was a relationship underneath it. It hit because he led with the thing that actually needed to be said. No throat-clearing. No how was your day. And he never stopped at the disappointment. He always pointed at the way out. Here is what happened, here is why it matters, here is how we fix it.

I did not carry that into leadership for a long time.

Early on, I led like my mother. I came in hot. I figured intensity would communicate how much something mattered. Then I would watch people go quiet, or defensive, or both, and I would overcorrect in the other direction. Cold. Clipped. Very disappointed in you, minus the part where my father had earned the right to say it. Neither version built anything. One scared people. The other confused them.

Most leaders never get that far, because most leaders avoid the conversation entirely. They tone the hard thing down until it dissolves into nothing. Or they reach for the sandwich. A compliment, then the criticism, then another compliment. The structure most of us were handed in some training at some point. The research has not been kind to it. People hear the bread and forget the meat. Or they brace through your opening praise waiting for the but, and now they trust the praise less too.

There is a better way in, and it is not complicated.

Open with the issue

Do not ask about their weekend. Do not ask about their kids. They know why the meeting is on the calendar, and the small talk only stretches the dread for both of you. Say the thing. Plainly. The numbers slipped two quarters running and I want to understand why. The tone in last week’s meeting concerned me. Whatever it is, lead with it. You can be warm and direct in the same sentence. Warmth lives in how you say it. Directness lives in not making them wait for it.

Practice before you walk in

This sounds small. It is not. Say the opening line out loud before the conversation happens. In the mirror. In the car. Staring at your own face in the Zoom window while you wait for them to join. You are not memorizing a script. You are getting the first sentence to leave your mouth without your voice shaking. The dread lives in the anticipation. Once you have said the words once, even to an empty room, they lose some of their charge.

The kindness is in the clarity

The padding feels like kindness. It is usually fear wearing kindness as a costume. The kindest thing you can do for someone is tell them the truth early enough that they can still do something about it. My father understood that. He opened with the hard part because he respected me enough not to make me guess at it. Lead with the issue. Leave with a path forward. Trust the relationship to hold the weight in between.

A question for you

What is the conversation you are softening right now, and what would it sound like if you opened with the actual point?

Reply and tell me. I read every one.

More next week.

Leave a comment

The program behind it gave students points for passing a quiz after every book they read. Harder books, more points. The quizzes drove everything. It took the joy out of reading, and the kids who struggled with tests were, in effect, being told they were crappy readers. Meanwhile the adults got a clean story. Teachers could say they were tracking reading and pushing literacy. Were they?

It took me six years of railing against it before anyone pulled the plug, which tells you something about my powers of persuasion. The program had been in place for years. Nobody wanted to reopen it. Easier to write the check than dig into the impact.

I thought about that program on Tuesday, when LAUSD did the thing I could never get done.

The second-largest district in the country approved the strictest student screen-time limits in America. No devices before second grade, hour caps through fifth, weekly limits after that. The caps got the cameras. Buried in the same resolution was a quieter order: review every existing classroom technology contract and publish what the review finds.

That is the line worth copying. The screen limits are a decision about the future. The review is a decision to go back and look at the past, in public, where the looking can be checked.

Here is why almost nobody does it. Almost nobody asked the right questions going in. These programs get bought in the name of innovation, and innovation is the easiest word in this business to hide behind. It turns a purchase into a virtue and a hard question into an attack. The reading software arrived with a dashboard and a pitch about literacy, and that was enough. Nobody asked what it would make easy to do poorly.

It made it easy to look like you were building readers while quietly teaching kids to game a system. The contract sat there doing exactly that, on budget, for years, because the activity looked like progress and no one was assigned to check. Multiply that by every district, every platform, every pilot that quietly became permanent. That is a staggering amount of money spent on the appearance of progress.

So here is what I am rooting for. If LAUSD actually reads every contract, in the open, it will not just find screens. It will find snake oil sold under the banner of innovation, of progress, of being “future-ready”, sitting on budgets nobody wanted to reopen, and it will have to write the names down where the rest of us can read them. Once one district publishes that list, the others lose the excuse.

Most snake oil in schools gets sold under the word innovation. A public audit is how you finally read the label.

A question for you

What did your team buy in the name of innovation that no one has been willing to reopen? What does it make easy to do poorly?

Hit reply and tell me which one came to mind. I read every reply.

This post is too good not to share, so please forward it to a colleague!

Hands went up for all three. Someone made the case for paper because it strips out the distraction. Someone argued for the AI version because of the instant feedback. Someone defended the Google Doc because it’s flexible and shareable. Good arguments, all of them, delivered with the confidence of people who do this for a living.

Then I changed the question. Assume all three were badly designed. What would make them bad? The room got quieter, and the answers got sharper. A worksheet that only asks a student to recall a definition is thin whether it’s printed or pixelated. An AI tool can deepen thinking or skip it entirely, depending on what you ask it to do. The quality of all three came down to one thing: how much actual thinking the task demanded. The format had very little to say about it.

That is the conversation I keep ending up in, and it is rarely just about schools. The same shape shows up around a new CRM, an AI meeting assistant, a reorg, a fresh policy. We debate the tool with real energy and skip the question sitting underneath it, which is whether we designed the thing on purpose. So I started running everything new through four questions before anyone gets to vote.

1. What is this for?

Say what the thing is for in one sentence you’d be willing to write on a whiteboard. If the honest answer is “everyone else has it” or “leadership wants to see us using AI,” you’ve found your problem, and no tool is going to fix it. (At CUE, the people who wrestled most with this question weren’t the skeptics. They were the ones already three tools deep, who couldn’t finish the sentence “this is for ___” without trailing off.)

2. What does it strengthen?

Every tool strengthens something, so name the actual muscle and be honest about whether it’s the one you care about. Speed? Output? Collaboration? This is where the research gets a little uncomfortable. John Hattie’s work keeps landing on the same place, which is that clarity of purpose and cognitive challenge move learning far more than the format you deliver it in. Daniel Willingham put it plainly: we remember what we think about. So if the shiny new thing strengthens activity without strengthening thinking, you’ve bought motion and called it progress.

3. What does it replace?

People skip this one, because the honest answer is usually “a person, a habit, or a moment of friction that was doing quiet work nobody credited.” Cognitive load research has a warning here too: stack a new system on top of the old ones without removing anything, and the only thing you reliably add is weight. The AI note-taker I once approved replaced the thirty seconds a team used to spend at the end of a meeting asking “so what did we actually decide.” That friction looked like inefficiency, which is exactly why it was first on the chopping block. It was also the only moment we reliably turned talk into a decision.

4. What does it make too easy to do poorly?

Every tool lowers the cost of some action, and it lowers the cost of doing that action badly at the same rate. This is the question most people skip, because answering it means saying the downside out loud. AI writing makes it easy to send a thoughtful-sounding note to someone you should have called. Dashboards make it easy to manage the number instead of the thing the number stands for. And my favorite, the one that got the biggest laugh of recognition in the room: a classroom (or a meeting, or a Slack channel) can look busy, collaborative, fully engaged, and demand almost no thinking at all. Students copy-pasting into a shared doc look exactly like students building an argument together... right up until you read what they wrote.

Every tool you adopt is a quiet decision about what your people will stop paying attention to. Most teams never write that part down, so they learn it the hard way, in a room that looks engaged and is quietly thinking about nothing.

A Question for You

What are you currently defending in your work that you have not actually examined?

If a tool or a policy came to mind while you read that, hit reply and tell me what it was. I read every one, and the things people are quietly defending are usually the interesting part.

Before you go.

If this essay said something you have been trying to put into words, the most useful thing you can do for someone else who needs to hear it is share it.

Read the Terrain grows when leaders pass it to other leaders. Not through algorithms, not through ads, just one quiet recommendation at a time.

Refer a friend

You will earn access to subscriber-only content the more people you bring along. They get something worth reading. You get acknowledged for being the person who sent it. Everyone wins.

Clear expectations. Specific next steps. Everything she needed one staff member to finally hear, written down in one place.

What came back was a reply. Polished. Complete. The right length, the right tone, every box checked.

And generated by AI. She could feel it right away... the smoothness where the friction should have been, words that technically answered her email without ever truly answering it.

Months of conversations built up this moment, and the response told her nothing about whether any of it had landed. So she asked me the real question. How do you lead someone who will not put in the reflection time?

The task was the thinking

I told her this first. The reply was never the thing she needed. What she needed was evidence that this person had sat with the feedback and turned it over, and the email was only ever the container that evidence was supposed to show up in.

But she sent that ask in an email. And “respond to this email” is a task software can finish in nine seconds.

So it did.

The staff member may not have skipped the assignment out of defiance. They may have genuinely believed the assignment was to send something back. (Most people have never been told that the point of a reflection is the reflecting, not the artifact. Go figure!) The deliverable got completed. The work it was supposed to represent never happened.

Some work cannot live on the page anymore

This is the part that shifted for all of us this year, quietly, and most leaders have not adjusted for it.

Anything you can request in writing can now be returned in writing with no human mind in between. When the written response is what you are grading, the person can step out of the loop entirely and you would never know. You end up assessing their software and calling it their work.

So you move it.

Reflection you need to witness has to happen somewhere it cannot be generated for them. A conversation. A question you did not send ahead. A “walk me through your thinking on the second point” that has to be answered in the room, in real time, with you watching them find the words.

You cannot outsource your way through a conversation. That is the entire reason it works.

A generic reply is still information

She had been too frustrated to see it, but that email was still telling her something. It was data.

If she names it plainly, “this read as generic, and what I need is your actual thinking, not a polished response,” one of two things happens. Either the person engages, and she gets the reflection she was after. Or they do not, and the disengagement stops being a feeling she carries around and becomes a pattern she can point to.

Even the second outcome is a win. A vague frustration has turned into something she can name, and that is the conversation finally getting honest.

The reframe

Leadership is partly a question of where you put the work. Put reflection somewhere it can be handed off, and someone, eventually, will hand it off. The move is to stop accepting proof that was never theirs to give, and to put the thinking somewhere only they can do it.

A question for you

Where in your leadership are you accepting the deliverable, when what you actually needed was the thinking behind it?

A small ask, if this resonated.

The leaders who read this newsletter tend to know other leaders who would read it too. The people quietly doing the work. The ones who think carefully before they speak. The ones who notice what the room missed.

If someone like that came to mind while you were reading, send this their way.

Refer a friend

Every referral unlocks more of what is behind the curtain, exclusive subscriber posts, deeper frameworks, and content I do not share publicly. Build the room with me.

Read the Terrain has been growing one reader at a time, mostly because someone who already subscribes mentioned it to someone who needed it. That word of mouth is the only reason this publication reaches the people it reaches.

So I have set up a simple way to make that easier, with a few thank-yous along the way.

If you share Read the Terrain and people subscribe through your link, you will hit a few milestones:

• Five referrals: a curated reading list of the essays readers return to most, sent to you as a PDF.

• Ten referrals: access to a monthly written Q&A, where I answer a reader question in more depth than I can fit into a regular essay.

• Twenty-five referrals: a 30-minute conversation with me, one on one, about whatever you are navigating in your own work.

You will find your personal share link at the bottom of this email and on every post going forward. No pressure to use it. The writing keeps coming either way.

But if something here has been useful, and there is someone you think it would serve, passing it along is the most meaningful thing you can do.

Thank you for being here.
Laura

Refer a friend

Organizations are very good at accumulating things.

New systems. New priorities. New tools. New communication channels. New expectations layered on top of old expectations that never fully went away in the first place. Somewhere along the line, “doing more” quietly becomes confused with “working better.”

That distinction gets a lot easier to see under real conditions.

Not during strategic planning sessions. Not inside polished presentations. Not when everything is calm and theoretical.

You see it when timelines compress. When communication starts breaking down. When too many initiatives are competing for attention at the same time. When good people start spending more energy navigating the system than doing the work itself.

The Trail Wasn’t the Problem

Off-roading convoys run into this all the time.

The trail is passable. The rigs are capable. The drivers know what they are doing. But once everyone on the radio is calling out lines, second-guessing the spotter, adjusting plans, and reacting to each other instead of to the terrain... progress stops anyway.

The rocks are not the problem.

The chatter is.

Sometimes the system around the obstacle becomes the obstacle.

I remember thinking about that afterward because organizations are not that different.

Not through incompetence. Usually through good intentions, stacked too quickly on top of each other.

An initiative gets added to solve a problem created by the previous initiative. A platform gets introduced to organize communication that already feels overwhelming. A process stays in place long enough that nobody remembers whether it still serves a purpose.

None of this happens dramatically. That is part of what makes it hard to see while you are inside it.

Most organizational strain doesn’t arrive like a crisis. It arrives like background noise that slowly gets louder.

The confusion increases. Work gets duplicated. More of the organization starts depending on a handful of people to hold things together behind the scenes.

What I Kept Running Into

I think that has been one of the bigger leadership shifts for me. I am less interested in speed for its own sake than I used to be. What holds my attention now is whether the system around an idea can actually support it once the implementation is over.

That sounds obvious written down afterward. Almost every leadership lesson does. Reality has a way of charging tuition before it provides clarity.

What I kept running into was this tension between responsiveness and sustainability.

Modern leadership environments reward quick movement. Fast answers often look like competence. Immediate action is reassuring, especially when people are waiting for direction. Slowing down long enough to question whether the system itself is becoming too complicated can feel almost irresponsible in the moment.

But complexity compounds quietly.

And strong people often hide weak systems for far longer than anyone realizes.

The work still gets done, so everyone assumes the structure is functioning properly. Meanwhile, certain individuals are compensating constantly behind the scenes. They’re filling gaps, translating confusion, and carrying institutional memory in their heads because the system never found a durable place to put it.

Eventually you realize the organization is not running smoothly because the system is strong. It is running because certain people are exhausted.

That realization changed some things for me.

I found myself spending more time thinking about clarity, ownership, decision-making pathways, communication load, and what actually needed to exist versus what had simply accumulated over time because nobody stopped to reexamine it.

I also became more aware of how easy it is for leaders to unintentionally create fragmentation while trying to solve fragmentation.

That one stings a little. (I have personally done this more than once... possibly this quarter.)

Because leadership attracts problem-solvers. And problem-solvers like to help. But organizations can slowly become collections of solutions instead of coherent systems if leaders are not careful.

The Work of Subtraction

Not every problem needs another layer added on top of it.

I’ve become more interested in subtraction than I used to be. Sometimes simplification accomplishes more than another solution. Sometimes the harder discipline is leaving space alone instead of filling every operational silence with something new.

I have not mastered this. Not even close. (My team would probably agree.)

But I do think I have become more conscious of the cost of unnecessary complexity. More aware that sustainable leadership is often less visible than performative leadership and considerably less dramatic. It is rarely the thing people notice first.

You don’t always get immediate applause for preventing fragmentation before it happens. Humans prefer before-and-after stories. Preferably with a branded framework and a keynote slide deck. Civilization remains deeply committed to turning everything into a productivity TED Talk.

Still, I think some meaningful shifts happened.

Conversations became more grounded and priorities became clearer. Teams seemed more willing to question whether activity was actually connected to outcomes instead of assuming motion automatically meant progress.

The Reframe

I am becoming increasingly convinced that leadership is not measured by how much a person can carry.

It is measured by how little unnecessary weight the system places on everyone else.

A Question for You

Where have you seen a system continue working only because certain people were quietly compensating for it?

What helped you recognize it?

Before you go.

If this essay said something you have been trying to put into words, the most useful thing you can do for someone else who needs to hear it is share it.

Read the Terrain grows when leaders pass it to other leaders. Not through algorithms, not through ads, just one quiet recommendation at a time.

Refer a friend

You will earn access to subscriber-only content the more people you bring along. They get something worth reading. You get acknowledged for being the person who sent it. Everyone wins.