Your Team Is Making Calls Your Strategy Never Covered

Most strategy doesn’t fail in the boardroom. It fails later, on the floor, when someone under pressure has to make a call the strategy never told them how to make. The plan was sound and the room agreed, and then the work got busy, the groups pulled back into their own lanes, and people fell back on whatever got them through the day.

The gap sits between the vision and the decision. You have the bold statement at the top and the OKRs at the bottom, and in between sits the part nobody equips: what a person does when the pressure is on and no leader is in the room.

Three things close that gap, and each does work the others can’t. A guidepost names what you’re trying to do. Guardrails mark the edges nobody should cross. Simple rules say what to do first when there’s no time to think it through. Together they let a team make the call you would have made, without waiting on you to make it.

1. Find the real problem, not the one they walked in with

A client came to me certain they had a churn problem. They didn’t. Customers were leaving because the only time they ever heard from the company was when something broke, so the work wasn’t to chase churn at all. It was to turn the relationship around and reach customers before the thing broke.

“Be more proactive” is useless to a team already drowning. It has to become something a person can act on at their desk, and that’s the job the three tools do.

2. Write the guidepost

A guidepost isn’t a restatement of strategy or a value on a poster. It’s a short, shared sentence that helps a team make the right call under pressure, especially when the manager isn’t there.

The client’s guidepost: “Increase customer loyalty by creating consistent, proactive experiences that show we understand what matters to customers — before they ask.”

3. Set the guardrails

Without edges, teams either freeze or make messes that come back later. Guardrails give people permission to move, with the boundaries already built in. This client’s leadership wrote three:

• If it lowers employee effort but raises customer effort, it’s a bad trade.
• No quick fix that creates a bigger problem later.
• If it’s worth explaining once, it should be captured and findable for everyone.

Those three turned doing the right thing into the expected move rather than the exhausting one.

4. Define the simple rules

Simple rules aren’t checklists. They’re the first moves a team makes to act fast and stay consistent when no one’s watching. The front-line team wrote four:

• Check the customer’s recent history before reaching out, so there’s context.
• Escalate friction the moment you see it.
• Follow up after every resolution, not only the hard ones.
• Update the knowledge article right after the interaction, while it’s fresh.

5. Bring the other groups in, because strategy dies in silos

A guidepost the whole company doesn’t share is a guidepost in name only. This client’s loyalty goal ran through Sales, Marketing, Product, and IT, so they brought those four groups in to build it with them.

They started plainly, asking whether each group agreed with the guidepost and the guardrails and rules under it. Then they let the real questions surface. How does proactive loyalty affect your numbers, what breaks if this fails, what would make it easier for your team to do it. Territory turned into shared ownership.

6. Measure the behavior, not just the outcome

Measure only outcomes and you find out you failed once it’s too late to change anything. Measure whether the right behaviors are taking hold and you can still help them while it matters. For this client that meant watching the share of interactions customers rated easy and helpful, the number of problems caught before the customer noticed, and the drop in repeat contacts on the same issue. The small behavior shifts, guided by a clear guidepost, showed up in the numbers first.

Why this is also your AI foundation

AI doesn’t learn from your strategy deck. It learns from what your operation recorded, the tickets and knowledge articles and decisions someone wrote down, and it scales whatever it finds. The workarounds your people carry in their heads never reach it.

So the same work that fixes execution decides what your AI inherits. An operation where the intent is clear, the boundaries are known, and the first moves are consistent hands an AI a system worth learning from. An operation running on confusion hands it confusion to scale, faster and to everyone who asks. The guideposts, guardrails, and simple rules your people use to make good calls are the ground your AI stands on.

---

The ServiceDNA™ Diagnostic shows which groups know the goals and their part in them, in about thirty days.

The conversation is thirty minutes

If your plans keep dying somewhere between the boardroom and the work, that gap is fixable, and it’s usually closer to the surface than it looks.

Book a call with Phil.