What to Do Next: Your First Move
You’ve read the model, the Sequence, and the Rhythm. The work from here is operational. This chapter gives you a scored starting point based on your AI Readiness Scorecard, three questions that form your minimum viable Signal, a team roster, and a one-page plan you can act on Monday morning. The only thing left is to write it down and go.
I’m on a call with a CEO I’ll call Katie. She came in knowing exactly what was wrong with her business. She’d been thinking about it for months. She had a list, and she was ready to talk about it.
I’m watching the clock because we’ve got thirty minutes and I know how these calls move. We get about eight minutes in and I ask her: “What does this problem cost you? Not in frustration, not in lost revenue abstractly — in dollars, per year, if nothing changes next year.”
She goes quiet. She’d never actually done that math.
That’s always the moment.
By minute twenty-five, we’d named something she hadn’t walked in with. Not the problem on her list — a different one. The actual constraint underneath it. And she said, almost to herself: Oh. That’s what it is.
The same thing happened the following week with a different CEO — I’ll call her Jill. Different industry, different list, same conversation structure, same moment at roughly the same point in the call. Neither of them had known their real constraint before the call. Both of them could name it by minute twenty-five.
Thirty minutes. Neither of them had to run a workshop or hire a consultant to get there. They had to be asked the right question in the right order and refuse the temptation to answer it with the first thing that came to mind.
This chapter is for one thing: the first move.
You have the language to describe what a Co-Intelligent Company is, the Sequence to build one, and the Rhythm to keep it compounding. The question now is where you start, and that depends on where you already are.
Pull your Scorecard to decide how much of the Sequence to run.
The Hybrid Org Today, the one-page document from the Rhythm chapter, is what this chapter fills in. It’s written in your own vocabulary, and it shows where you stand right now. New executives get briefed on it; the board sees it when it asks what the AI investments produced.
In the Diagnosis chapter you took the AI Readiness Scorecard. Five dimensions. Red, yellow, green. That score is your routing mechanism. It tells you how much of the Sequence to attempt in your first Sprint, which is to say how full the first version of your Hybrid Org Today is allowed to be.
If you scored mostly Red: start with Signal alone. Name one constraint. Put a dollar figure on it. That is your entire first Sprint. Don’t try to run the full Sequence — get one clean Signal and build from there. The constraint is the deliverable.
If you scored a mix of Red and Yellow: start with Signal and Source. Name the constraint, then map what you already know about it — the workflows, the people, the data. Two phases. One Sprint. You’re building the foundation for a Design phase in Sprint two.
If you scored mostly Yellow and Green: you’re ready for the full Sequence. Signal through Compound, one Sprint, using the instruments from the stage chapters. You have enough structural discipline in place that the framework won’t outrun you.
If you haven’t completed the AI Readiness Scorecard yet, go back to the Diagnosis chapter and do it now. It takes ten minutes and tells you exactly where to start.
Run minimum viable Signal on yourself.
Not after the offsite or the next tool evaluation. Now.
The first move is to run Signal on your own organization — the same discipline this book describes. Find the real constraint. Name it precisely. Quantify what it costs you in dollars and hours and headcount over a year.
Doing that step honestly, without rushing to a solution, is what separates the companies that produce results from AI from the companies that produce a second round of the same experiments they ran last year. It’s easy to skip and move straight to tools, because tools are concrete.
If you’ve read this far and done the thinking the chapters asked of you, you have a sense of where your real constraint lives. You may have already named it on the margin of a page. The job now is to sharpen it.
Three questions. This is your minimum viable Signal — the seed that the full Signal process from the Signal chapter will refine. (If you run EOS, think of Signal as the rigorous root-cause layer underneath IDS: instead of surfacing and solving issues week to week, Signal traces the structural constraint that keeps generating them.)
How to run minimum viable Signal
- Name the operational problem — Forces a specific, observable constraint sentence rather than a vague category — the entry point for every Sprint.
- Quantify the annual cost — Attaches a dollar/hour/headcount number so the constraint can be prioritized and Sprint ROI can later be measured.
- State what would have to be true to solve it — Reveals whether the constraint is Sprint-solvable or whether something upstream must move first, preventing wasted quarters.
1. What is the one operational problem costing you the most money or time right now? Write one sentence describing a specific, observable problem.
2. What does it cost per year? Write a number. Even a rough estimate works. If you can’t estimate it, that tells you something — your first Sprint goal might be measuring it.
3. What would have to be true for it to be solved? Write one sentence. This tells you whether the constraint is Sprint-solvable or whether something upstream needs to move first.
| Minimum Viable Signal | Your answer |
|---|---|
| The operational problem (one sentence) | |
| Annual cost (dollars / hours / headcount) | |
| What would have to be true to solve it |
Meridian’s three answers fit on three lines. The operational problem: quoting took days, and Elena was the only one who could do it. The annual cost: the deals that went cold while a quote sat in her queue. What would have to be true: the quoting knowledge had to live somewhere other than Elena’s head. That was the seed of their first Sprint.
If you can answer all three, you have the seed of a constraint. That answer goes in the Active Sprint row of your Hybrid Org Today. If you can’t, that’s your first Sprint: getting to where you can.
The most common failure on question one is answering with a category instead of a constraint. “Our marketing needs help” is a category. “Our office manager spends three hours a day on manual scheduling coordination” is a constraint. The constraint has a number attached. The category doesn’t.
Name three roles: Orchestrator, Owners, Builder.
You need three roles filled. The names land directly on your Hybrid Org Today: one becomes the Human Orchestrator on the Active Sprint, two or three populate the supervisor column of the Hybrid Accountability Chart.
The Human Orchestrator is the person who operates the redesigned workflow and supervises its agent team — not a technical role, not a new hire, but the operator who already owns that workflow and can judge whether the agent’s output is right (more on this role in the Designing the System chapter). The Hybrid Accountability Chart (if you run EOS: your Accountability Chart extended to include agent rows alongside the human ones) is where that role lands on paper.
How to name the Sprint roster
- Identify the Human Orchestrator — Assigns workflow ownership and agent-supervision authority to one named person before the Sprint starts.
- Name the daily-proximate supervisors — Identifies the two or three people closest to the problem who contribute to Signal and Source and catch what reports miss.
- Confirm the builder resource — Locks in who will construct the solution — internal developer, external partner, or Compound membership — so the Sprint is fully staffed.
Who owns the workflow where the constraint lives? That person is your Human Orchestrator candidate. They don’t need to be technical. They need to be ready to operate the redesigned workflow and direct its agents.
Who are the two or three people closest to the problem daily? They’re in the room for Signal and Source. They see what the reports don’t show.
Do you have someone who can build? Internal developer, external partner, or Compound membership. That’s your builder resource.
| Role | Named person |
|---|---|
| Human Orchestrator (workflow owner) | |
| Daily-proximate supervisors (2–3) | |
| Builder (internal / external / Compound) |
Meridian’s roster looked like this: Elena Ruiz (VP of Operations) as the Human Orchestrator — she owned quoting, knew the exceptions, and could judge whether a draft quote was right. Ty Banfield (Sales Lead) and Dave Kowalski (Senior Design Engineer) as the daily-proximate supervisors — Ty saw the quotes the way customers saw them; Dave knew which specs the agent would struggle with. A freelance n8n developer (three days of API work) as the builder. No new hires. No internal engineering team. That was the full roster.
You don’t need permission from IT or an AI strategy document. You need a constraint, an orchestrator, and a builder — everything else follows.
Book the Clarity Call if you want a peer in the room.
If you want a peer to pressure-test that constraint with you before you spend a quarter on it, we offer one mechanism. It’s called the Clarity Call.
Book a free 30-minute Clarity Call with a Compound strategist who will diagnose your constraint, not pitch you a product.
I was on a discovery call with a physical therapy practice owner. By his own description, his was one of the top private practices in the country, and I believed him. He’d just come back from a foundation retreat and he was lit up. His vision: an automated executive suite, with AI agents for every C-suite function, all of it running on agents trained on his institutional knowledge. AI agents are systems that hold a goal, run a sequence of steps toward it, and adjust based on their own outputs, unlike chatbots that answer one question at a time. He wanted to package that knowledge and take it to the world.
It was an impressive vision. So I asked the only question that mattered: “Who on your team would build this?”
He went quiet. Then: “I don’t have that person.”
The obstacle was the gap between the vision and the first step. He kept staring at the vision, the first step never appeared, and the quarter ended with nothing moved. That’s a sequencing problem. The Clarity Call exists to find the step.
“I don’t have that person” and “I don’t have that structure” are the same constraint. Both resolve with a named first Sprint.
The Clarity Call is not Signal. Signal is the rigorous diagnostic process described in the Signal chapter. The call is a 30-minute conversation that gives you a head start on it: it surfaces the constraint category, sharpens the question you take into the full process, and tells you whether your first Sprint candidate is real. You finish the call knowing where AI fits in your organization: your team, your industry, your headcount math, your numbers. You leave with a constraint you can act on, not a software recommendation or a sales pitch.
Book it at compoundorg.com/clarity-call.
Pick a path: self-guided or with Compound.
Once you have a constraint named clearly enough to commit a Sprint to it, you have two paths forward. Both produce the same artifact, Sprint by Sprint: a Hybrid Org Today that grows a new row each quarter until the design layer of the company is the company. The paths differ in speed and in how much support you want while you run the first one.
Path A: Run it yourself. The framework is in this book. The Sequence is here. The instruments are defined in the chapters behind you: the Knowledge Map, the Hybrid Accountability Chart, the Hybrid Org Today. Use the chapter instruments to guide each phase:
- Signal — Define the constraint with precision
- Source — Map the knowledge around it
- Design — Architect the solution
- Build — Construct and test
- Deliver — Deploy and validate
- Compound — Extract the reusable pattern
Set the quarterly Rhythm from the Rhythm chapter to make it repeatable. A disciplined operating team with EOS or Scaling Up already in place can execute a first Sprint on its own. Many will. We wrote the book so they could.
Path B: Run it with Compound. The same Sequence, paired with weekly retros, a cohort of peer CEOs running the same framework against constraints in their own companies, and a Compound strategist coaching you through each stage. The membership includes tools that run the same methodology, along with a Clarity Call (30 minutes, no cost) where a strategist walks through your constraint with you and tells you whether it’s Sprint-ready.
Either path works when the team already has operating discipline in place. The one that doesn’t work is the one most companies are still on: buying more tools and hoping a structure will emerge from them.
Decide which path you’re taking. Write it down. If Path A, schedule the Signal session with your team this week. If Path B, book the Clarity Call. The decision that doesn’t work is the one you defer.
Fill in the Sprint Planning Canvas.
You’ll fill in the full Sprint Planning Canvas using the nine-question walk-through in the Framework chapter (How to fill in the Sprint Planning Canvas). Everything you name in this chapter — the constraint, its annual cost, the roster, and the path you choose — becomes the inputs you bring to it.
You already have the template. The Sprint Planning Canvas from the Framework chapter is the artifact. Pull it back out now and fill it in based on everything the chapters behind you have built:
- The constraint you named in Signal
- The knowledge sources you identified in Source
- The ownership structure named on the Hybrid Accountability Chart in Design
- The quarterly review date that Rhythm requires
The Canvas already has the rows. The work now is to write in the right answers for your company.
This is the deliverable. The plan is the first version of your Hybrid Org Today, written before the first Sprint starts: one Active Sprint row, three named roles, one estimated cost, one date. After the quarter, you update it. After the year, it has four Active Sprint rows behind it and the company’s design layer is on the page.
Fill it in. The Canvas takes ten minutes.
Before the plan commits, two questions catch the gaps that turn into wasted quarters.
1. Is the constraint real, or is it a symptom? Signal traces the symptom to the underlying constraint; if the constraint you’ve named is the most visible problem rather than the structural cause underneath it, the Sprint will solve the wrong thing.
2. Does the named Human Orchestrator pass the Right Seat Evaluation? Run the three-criteria Right Seat Evaluation from the Designing the System chapter (Sees It, Wants It, Suited for It) against the person you’ve named; if they can’t evaluate the agent’s output, won’t own the outcome, or lack the authority to override when it drifts, name someone else before the Sprint starts. (If you run EOS, this is the GWC test — Get it, Want it, Capacity to do it — applied to the agent supervisor seat rather than a human role.)
If you can’t answer both, the plan isn’t yet ready to ship.
The math keeps moving whether you decide or not.
The Headcount Paradox keeps compounding while you decide. Pull revenue per employee for the last four quarters; in most companies it sits flat. We went from thirteen people to eight in one year without a crisis. The question is when you start.
Meridian’s three Sprints sit on their Compounding Scorecard now. The quoting bottleneck Elena was holding is a designed workflow. Two more Sprints are queued. That’s what one named first move, run on a quarterly Rhythm, becomes in eighteen months.
It’s time to start.
Reflection Questions
- Fill in the Sprint Planning Canvas — constraint in one sentence, estimated annual cost, three team roles named, path chosen, first step checked. Can you complete it in the next ten minutes? If not, which field is blocking you, and what would it take to fill it in before Monday?
- Run your minimum viable Signal: what is the one operational problem costing you the most money or time right now, what does it cost per year, and what would have to be true for it to be solved? If you can answer all three, you have a Sprint. If you can’t, your first Sprint is getting to where you can.
- The chapter describes Katie and Jill — both CEOs who discovered their real constraint wasn’t the one they walked in with. What is the problem on your list that you’ve been carrying for months? Have you actually run Five Whys on it, or are you working on the symptom because it’s more comfortable than finding the constraint underneath?
- What is your Monday morning action — the specific, named move that starts the Sprint? Is it scheduling the Signal session with your team? Booking the Clarity Call? Writing the Constraint Statement? Name the action, name the person who owns it, and name the date it happens by.