Every Decision Your Team Makes Without You Runs Through Chapter 1

A client called your office at 2pm yesterday.

She was frustrated. Her vendor was asking for system access your team had blocked the previous week. She wanted to know whether to approve the request herself, escalate it, or push back on the vendor. She needed an answer in the next 30 minutes because she had a meeting.

You weren't in the office. You were on a flight. Phone off.

Your account manager picked up. She had 30 minutes to make a call that affected your client's security posture, the vendor relationship, and your team's authority to enforce access policies. She made the call without you.

The question is what she ran the decision through.

Did she run it through your mission, which would have told her that protecting the client's work was the operational priority? Did she run it through your core values, which would have told her how to handle the conversation with both the client and the vendor? Did she run it through your BHAG, which would have told her what kind of business you are trying to build and how this decision either contributes to it or works against it?

If the answer is yes, your account manager made a decision aligned with how you would have handled it. The client got an answer that reflects the business you built. The vendor relationship gets managed the way you would have managed it. Your team's authority gets reinforced rather than undermined.

If the answer is no, she ran the decision through her best guess at what you would have wanted. Most account managers guess pretty well most of the time. But "pretty well" isn't alignment. And "most of the time" isn't a strategy.

Every decision your team makes without you runs through something. Either it runs through the documented foundation you built. Or it runs through their best guess. The choice between those two outcomes is whether Chapter 1 of your field guide exists in usable form.

WHAT CHAPTER 1 ACTUALLY DOES

Most owners think of Chapter 1 the wrong way. They think of it as the soft chapter. The culture chapter. The values-on-the-wall chapter. The chapter that matters for hiring and onboarding but doesn't really affect the day-to-day operation of the business.

That's exactly backwards.

Chapter 1 is the operational chapter. It's the chapter every other chapter, every system, every process, and every decision in your business runs through. The dispatch system runs through it. The escalation procedure runs through it. The QBR template runs through it. The hiring rubric runs through it. The choice between two acceptable technical solutions runs through it. The decision about which client gets called first when something breaks runs through it.

Chapter 1 is the operating context for every decision your team makes when you aren't in the room. Mission tells them what matters. Core values tell them how to behave. BHAG tells them what you're building toward. Without those three things documented and absorbed, every decision your team makes is a guess. Some of the guesses align with what you would have done. Many of them don't. You spend your weeks discovering which is which by reviewing decisions after the fact.

That isn't leadership. That's supervision.

Leadership is making sure your team has the decision-making foundation to operate aligned without you. Chapter 1 is that foundation. And until it exists and your team uses it, you will keep being the bottleneck on every meaningful decision in your business.

THE QUIET COST OF NOT HAVING CHAPTER 1 BUILT

Walk into your business tomorrow morning and ask three people on your team to recite your mission. Then ask them to recite your core values. Then ask them what your BHAG is.

If everyone gets all three right without hesitation, you have Chapter 1 built. You can skip the rest of this post.

If they fumble, guess, look at the wall, or admit they can't remember, you are paying a cost every single day that doesn't show up on your P&L but shows up everywhere else.

The cost looks like this.

Two of your techs handle the same kind of escalation differently because they are running it through different unwritten assumptions about what matters in your business. One thinks the priority is closing tickets fast. The other thinks the priority is getting the client what they need even if it takes longer. Both think they're doing the right thing. Both are guessing because the standard was never documented and absorbed.

Your account manager closes a sale on terms that conflict with your unwritten policy on scope creep because the policy is unwritten and she has been with the company eight months. She didn't violate anything documented. She just made the call her best judgment produced. You find out about it three weeks later when the project is in trouble.

Your dispatcher makes a routing call that prioritizes a big client over a small client because nobody ever told her your business values every client's work equally. She did what made business sense in her interpretation. The small client noticed. They mentioned it to a peer at an industry event. The peer was about to refer you. They didn't.

Your senior tech is teaching the new tech how to handle a complex situation. He teaches him what he was taught. What he was taught was what the previous senior tech thought was right. The previous senior tech learned it from the person before him. By the third generation, the standard has drifted three steps away from what you actually believe and you have no idea because the drift happened quietly in moments you were never in the room for.

Every one of those scenarios is a decision your team made without you. Every one ran through their best guess instead of through a documented foundation. Every one cost you something measurable. Most of them happen weekly in your business right now.

The cost isn't catastrophic. It's corrosive. It's the steady, quiet erosion of alignment that happens when your team is making good-faith decisions against a standard nobody bothered to write down.

HOW CHAPTER 1 CHANGES EVERY DECISION FROM THAT POINT FORWARD

When Chapter 1 is built and absorbed, the same scenarios play out differently.

The two techs handling escalations run them through the same documented mission. They reach the same kind of decision because they are starting from the same context. The client experience becomes consistent regardless of which tech is on the ticket.

The account manager closing the sale runs the terms through your documented values. She knows what your business stands for around scope creep before she puts the proposal in front of the client. The deal closes on terms aligned with how you would have negotiated it.

The dispatcher routing the ticket runs the decision through your value that every client's work matters equally. She prioritizes by impact rather than revenue. The small client notices that too. They mention it to the peer at the event. The peer becomes a referral instead of a missed one.

The senior tech teaching the new tech anchors the lesson in the documented values rather than in his own memory of what he was taught. The standard stays consistent across generations because it lives in a document the whole team works from instead of in the heads of whoever happens to be the senior person that quarter.

Every one of those decisions still gets made by someone other than you. Every one still gets made without your direct involvement. The difference is that every one runs through Chapter 1 instead of through a guess.

That is alignment. That is what produces a business that operates consistently whether you are in the room or not. And it only exists when Chapter 1 has been documented, rolled out, and embedded into how your team actually thinks about the work.

THE FIVE STEPS THAT BUILD THE FOUNDATION

Here is the rollout that turns Chapter 1 from a document into a decision-making foundation. Two to three weeks of work. Followed by ongoing reinforcement that makes the foundation hold instead of fading.

STEP ONE. FINALIZE THE THREE COMPONENTS.

Mission. One sentence that explains what your business exists to do in specific terms. Not a marketing slogan. A statement of purpose your team can use to make decisions when you aren't there. "We protect the businesses that protect people" is a mission. "We deliver excellent IT services" is a marketing line that says nothing useful.

Core values. Three to five values that pass the fire test. Would you actually let someone go for repeatedly violating this value? If the answer is no, take it off the list. Each surviving value gets a paragraph defining what it means in your business. Each one gets two behavioral examples. One of what living it looks like in real work. One of what violating it looks like. Each one gets the interview question that screens for it before hire.

BHAG. The long-range destination that gives your team and clients something to run toward. Specific enough to count toward. Human enough to care about. Connected to the daily work so every person on the team can find themselves in it. "Protect a million people by 2030" is a BHAG. "Grow to $10M in revenue" is a financial target nobody on your team lies awake thinking about.

If these three aren't in final form yet, spend a week sharpening them. The quality of the rollout depends entirely on the quality of the source material. A rushed Chapter 1 with a vague mission and a long values list will produce a rollout that lands flat and damages trust in the rest of the field guide build.

STEP TWO. PRIME THE TEAM.

Send a short message a few days before the rollout. Something like this.

"Over the next two weeks I am going to be sharing the foundation our entire business runs on in a way we have never documented before. Mission, values, BHAG. Every decision any of us makes from this point forward runs through these three things. I want every person here to know them, recite them, and use them. Look out for what is coming on Tuesday."

That framing matters. The team needs to understand that Chapter 1 isn't a culture exercise. It's the decision-making standard the business is going to operate from. The framing shapes how the rollout is received.

STEP THREE. RUN THE ROLLOUT MEETING.

Schedule 60 minutes. Get the team together in one room. No phones. No laptops. This is the meeting where Chapter 1 becomes real.

Walk through the mission. Tell the story of why you built the business. Connect the mission to a specific client or a specific moment that proves the mission is real. Then walk through a recent decision the team made and show how it either reflected the mission or drifted from it. Make the connection between the mission and daily decision-making explicit.

Walk through the values. For each value, give a real example of someone on the team living that value in the last 90 days. Name names. Tell the story. "Owns the outcome" isn't a value yet. "Last month when Jenny stayed two hours late to make sure the clinic's backup verified before she left, because she knew they had end-of-month billing the next morning and she didn't want to leave them exposed. That is what owning the outcome looks like in this business." That is a value being lived in a decision. Tell stories like that for every value.

Walk through the BHAG. Explain what you are trying to build over the next three to five years. Make it specific. Make it count toward something the team can imagine. Then show how a recent decision either moved you toward the BHAG or worked against it. The team needs to see that the BHAG is operational, not aspirational.

End the meeting with a commitment. From this point forward, every decision in the business runs through Chapter 1. In hiring. In performance reviews. In daily team meetings. In QBRs. In how you handle a difficult client situation. This isn't a one-time discussion. This is how the business operates.

STEP FOUR. SHOUT OUT DECISIONS THAT RAN THROUGH CHAPTER 1.

This is where most rollouts die. The meeting happens. The poster goes up. The team uses Chapter 1 for two weeks and then drifts back to making decisions on instinct.

The fix is reinforcement through decision-specific recognition.

Every week, pick one decision a team member made that ran through Chapter 1. Tell the story in the team meeting, in Slack, in email. Name the person. Name the value or the mission point they ran the decision through. Name the outcome.

"Marcus took a call from our nonprofit client at 6:45 last Thursday night when the executive director couldn't access her email before a board meeting. The fast move would have been to schedule it for the morning. Marcus stayed on the line with her for 40 minutes until she was back in because our mission says we protect the businesses that protect people, and she runs a clinic that protects people. That is what running a decision through our mission looks like. Thank you Marcus."

That paragraph does three things at once. It reinforces what Chapter 1 looks like in actual decision-making. It celebrates the team member who made the call. And it teaches the rest of the team that the decisions that get recognized in this business are the ones run through Chapter 1.

Within two months, the team starts running their decisions through Chapter 1 deliberately because they have seen how it gets noticed.

STEP FIVE. ANCHOR EVERY OPERATIONAL DECISION IN CHAPTER 1 FROM NOW ON.

This is the step that locks Chapter 1 into the operating system of the business permanently.

Every operational decision you make from this point forward gets anchored in Chapter 1 publicly. When you choose to invest in a new tool, explain how it serves the mission. When you make a hiring decision, explain how the candidate met the values. When you decline a client opportunity, explain why it didn't fit the BHAG.

The team is watching how you make decisions. If you anchor every meaningful decision in Chapter 1, they learn that Chapter 1 is the actual standard the business runs on. If you make decisions on instinct and reference Chapter 1 only when it's convenient, they learn that Chapter 1 is window dressing and the real decisions get made somewhere else.

You set the standard by how you make your own decisions visible to the team. Anchor every one of them in Chapter 1 and watch the team start doing the same thing without being told.

WHY THIS IS THE MOST IMPORTANT CHAPTER YOU WILL EVER ROLL OUT

Every other chapter in your field guide depends on Chapter 1 being in place.

Your dispatch system in Chapter 2 runs through the values from Chapter 1. Your hiring system in Chapter 3 screens for the values from Chapter 1. Your QBR process anchors itself in the mission from Chapter 1. Your AI deployment decisions run through the BHAG from Chapter 1.

If Chapter 1 isn't built, the chapters that come after it don't have a foundation to anchor against. They become process documents without a guiding standard. The team uses them but doesn't understand the why. The systems drift because the context that holds them together doesn't exist.

This is what owners get wrong when they treat Chapter 1 as the easy starter chapter. It's the easy chapter to build. It's also the chapter that determines whether every other chapter you build actually works as a system or just sits there as documentation.

Get Chapter 1 right and every other chapter compounds. Get Chapter 1 wrong and every other chapter limps because the foundation underneath them is shaky or missing.

Every decision your team made yesterday ran through something.

The decisions that aligned with how you would have made them ran through the documented foundation you have built. The ones that drifted from how you would have made them ran through your team's best guess. The ratio between those two outcomes is the visible result of whether Chapter 1 exists in usable form.

You can keep operating without Chapter 1 built. Your team will keep making good-faith decisions on incomplete information. Some of them will align. Many of them will drift. You'll spend your weeks discovering which is which by reviewing decisions after the fact and feeling the slow erosion of consistency you can't quite name.

Or you can build Chapter 1 in the next three weeks. Run the rollout. Anchor every decision in it from that point forward. Watch your team start making decisions you would have made without you being in the room.

That is alignment. That is what Chapter 1 produces when it is built, rolled out, and reinforced as the decision-making standard the business actually runs on.

Three weeks. One chapter. Every decision your team makes from then on runs through it.

Start at builttorunmsp.com

FREQUENTLY ASKED QUESTIONS

What goes in Chapter 1 of an MSP field guide?

Chapter 1 contains the three foundational components that every other system and decision in the business runs through. The mission statement, which is one sentence explaining what the business exists to do in specific, decision-guiding terms. The core values, three to five values that pass the fire test, each documented with a definition specific to the business, behavioral examples of what living and violating the value looks like, and the interview question that screens for it before hire. The BHAG, the long-range destination the team and clients can run toward together, specific enough to count toward and human enough to care about. Together these three components form the operating context for every decision the team makes when the owner isn't in the room.

Why is Chapter 1 considered the operational chapter rather than the culture chapter?

Most owners assume Chapter 1 is the soft chapter, useful for hiring and onboarding but not directly relevant to operations. The opposite is true. Every operational decision in the business runs through Chapter 1 whether the owner has documented it or not. Dispatch routing decisions run through the values. Escalation prioritization runs through the mission. Sales scope decisions run through the BHAG. Hiring choices run through all three. When Chapter 1 is documented and absorbed, the team makes those decisions aligned with the documented standard. When it isn't documented, the team makes the same decisions running them through their best guess at what the owner would have wanted. The decisions get made either way. Chapter 1 determines whether they align.

How long does it take to roll out Chapter 1 effectively?

Two to three weeks of focused work from the decision to start to the team being able to recite the mission, values, and BHAG and use them to make decisions. Week one is finalizing the three components. Week two is the rollout meeting with the team and the launch of weekly reinforcement through decision-specific recognition. Week three begins the systematic anchoring of every operational decision in Chapter 1 publicly. The team's full internalization of Chapter 1 as their decision-making foundation takes 60 to 90 days from the rollout meeting, sustained through consistent weekly recognition of decisions that ran through Chapter 1.

What is the difference between recognizing values and recognizing decisions that ran through Chapter 1?

Recognizing values means calling out a team member for living a value in their work. Useful, but it stops at the behavior. Recognizing decisions that ran through Chapter 1 means telling the story of a specific decision and showing how the team member used the mission, the values, or the BHAG to make the call. The recognition includes the situation, the decision, the part of Chapter 1 it ran through, and the outcome. This kind of recognition teaches the team that Chapter 1 isn't a culture artifact but the actual standard the business uses to make decisions. Over time, the team starts running their decisions through Chapter 1 deliberately because they have seen what gets recognized and what doesn't.

How does Chapter 1 connect to the rest of the field guide?

Every chapter that follows Chapter 1 depends on it. The dispatch system in the operational chapters runs through the values from Chapter 1. The hiring system screens for the values. The QBR process anchors itself in the mission. AI deployment decisions run through the BHAG. Without Chapter 1 in place and absorbed by the team, the chapters that come after it become process documents without a guiding standard. The team uses them but doesn't understand the why. The systems drift because the context that holds them together doesn't exist. Chapter 1 is the foundation that makes every subsequent chapter work as a system rather than as documentation.