The Alignment Chain: From Keyboard to P&L

In Part 1, we covered the OP1/OP2 framework. In Part 2, we wrote SMART goals and established team tenets. Those tell you what to do and how to decide.

This post answers the question that makes all of it matter: how does the work connect to the numbers that run the company?

This is where most planning processes fall apart. Teams write solid SMART goals. They might even have tenets. But the goals float in isolation — disconnected from the company's financial reality. If you can't draw a line from what your team is working on this sprint to a number the CFO cares about, you have an alignment problem.

Reading the Revenue Structure

The starting point is the company's revenue structure — the kind of breakdown you see in quarterly earnings reports. Here's a simplified Sankey-style view of how revenue flows through a fictional SaaS company:

This is the picture leadership sees every quarter. Revenue flows in from segments, gets consumed by costs, and what's left is operating income. Every team goal should visibly connect to either growing a revenue stream, reducing a cost line, or protecting margin.

If a goal doesn't touch any of these flows, ask: why are we doing it? Sometimes the answer is legitimate (compliance, technical debt reduction that prevents future cost). But the connection should always be articulable.

The Vertical Chain

The fix for disconnected goals is explicit vertical alignment. Every goal at every level should trace upward to the next level, all the way to the metrics that appear in the company's quarterly financial reports.

Every level answers the question: "How does this contribute to the level above?" If you can't answer that, the goal is either misaligned or the connection hasn't been made explicit.

How to build the chain

1. Start from your nearest anchor. "The top" doesn't mean the CEO's quarterly earnings call — it means the nearest level of management above you whose KPIs were set through an OP cycle. What are their key metrics? Those are the targets your goals need to connect to. For a team lead, that's the director's OP2 targets. For a director, it's the VP's OP1 strategic bets. The formal accountability link is one level up — but in practice, teams make better decisions when they understand the context at least two or three levels up. Knowing why your manager's target exists changes how you pursue it.
2. Work downward. Each business unit identifies which of those metrics they influence most, and sets OKRs that move those numbers.
3. Departments translate. "Increase enterprise ARR" becomes "reduce time-to-value" or "improve renewal rate" at the department level — the operational levers that drive the financial outcome.
4. Teams write SMART goals that deliver on the departmental lever. This is where specificity matters most. The goal must be concrete enough that a team can execute against it.
5. Individuals connect their work to the team goal. Not as a formality, but as a genuine link: "My piece of this is X, and when it's done, the team goal advances by Y."

The alignment test

Pick any goal from any level. Ask two questions:

• Up: "If we achieve this, which metric at the next level moves, and by how much?"
• Down: "What specific work at the level below is making this happen?"

If you can't answer both, there's a gap. Either the goal isn't connected, or the connection exists in someone's head but hasn't been documented. Both are problems.

Putting It All Together

The three components from this series — SMART goals, team tenets, and vertical alignment — work as a system:

Component	Answers	Without It
SMART Goals	What are we doing, and how do we know it's done?	Vague objectives that nobody can be held accountable to
Team Tenets	How do we decide what to work on, what to say no to, and what makes us distinct?	Scope creep, duplicated effort, inconsistent priorities
Vertical Alignment	Why does this matter to the business?	Busy teams doing excellent work that doesn't move the needle

The most dangerous failure mode in planning isn't having bad goals. It's having good goals that don't connect to anything. A team can hit every target and still not move the company forward.

A Practical Workflow

Here's how this looks across the OP cycle from Part 1:

1. OP1 (strategic phase): Leadership defines or reaffirms the company's financial targets and strategic bets. Business units align on which metrics they own.
2. Tenet review: Each team reviews their tenets against the new strategic direction. Are they still right? Do any need updating? This takes an hour, not a week.
3. OP2 (execution phase): Teams write SMART goals that connect to departmental and business unit objectives. Each goal passes the alignment test (up and down). Tenets are used to filter and prioritise.
4. Quarterly check-ins: Review progress against SMART goals. Check that the alignment chain still holds — sometimes a company pivot changes which goals matter. Adjust scope, not ambition.

---

Final Thought

Planning is not a document. It's a system of connected decisions. SMART goals give precision. Tenets give focus. Vertical alignment gives relevance. Miss any one of them and the team will be busy without being effective.

The teams that consistently deliver aren't the ones with the most detailed spreadsheets. They're the ones where every person can answer: "What am I working on, why does it matter, and how does it connect to the numbers that run this company?"