Waypoints

Most quarterly goal systems fail for the same reason: the goals are soft enough that they can always be declared partially successful. "Improve customer onboarding" is an annual priority at a hundred companies right now, and at the end of the quarter every one of them will be able to point to something that improved. The goal was achieved. The underlying problem was not solved.

This happens because the goal was designed to be achievable rather than designed to be binary. When you set a priority that can be partially true, you create an incentive to declare it partially true and move on. The quarterly review becomes a narrative exercise rather than a navigational one.

A Waypoint is the fix. It is not a goal, not an OKR, not a priority. It is a defined position the Expedition must reach by the end of the quarter. Either you reached the position or you did not. There is no partially-there. A ship is either at the waypoint or it is still en route. The binary nature is the point.

An Expedition carries three to five Waypoints per quarter. Not a backlog of everything the organisation wants to accomplish. Three to five positions that, if reached, represent meaningful progress toward the annual Horizon and ultimately toward True North.

Each Waypoint has a pass condition that is specific enough to be evaluated as a binary: did we reach this position or did we not? "Launch the new pricing model" is a Waypoint. "Make progress on pricing" is not. "Reduce average ticket resolution time to under 4 hours with the support Post handling 60% of volume" is a Waypoint. "Improve support efficiency" is not.

Waypoints are set during the Survey — the quarterly planning session. They are reviewed during every Bearing — the weekly meeting. The Bearing includes a binary check: on track or off track. If off track, why and what changes. If on track, acknowledge it and move on.

The Waypoints you set must account for the agents. If one of your Waypoints depends on a Post that has not been commissioned yet, the commissioning work is part of reaching the Waypoint.

In OKRs, objectives are qualitative and key results are quantitative. The system assumes that measuring the right numbers tells you whether you achieved the objective. In practice, teams hit their key results and miss the spirit of the objective regularly, because the numbers were proxies and proxies can be gamed or misread.

In EOS, Rocks are quarterly priorities owned by specific people. This is closer to Waypoints — Rocks are meant to be binary and owned. The gap is that EOS Rocks do not account for the agent layer. A Rock like "Launch the new SDR outreach sequence" does not specify which Posts are involved, what Groundwork needs to be complete, or what the governance requirements are for the agents doing the work.

Waypoints integrate the human and agent layers. A Waypoint is owned by a Station, which means the human accountable for reaching it also owns the Posts that will do part of the work. The Post Roster is reviewed at the same Survey where the Waypoints are set. The governance and the priorities are aligned from the start, not bolted together after the fact.

The most common mistake is setting too many. Five is the maximum. Three is better for a team under 20 people. Every Waypoint you add dilutes focus on the others.

The second mistake is setting Waypoints that are really tasks. "Migrate the database to the new provider" is a task with a deadline, not a navigational position. "The data infrastructure supports real-time Post analytics with sub-second query latency" is a position — it describes where the Expedition needs to be, not what it needs to do.

The third mistake is not connecting Waypoints to the Post Roster. If your Q2 Waypoint is "fully govern all customer-facing Posts," the Survey should review which Posts are customer-facing, what their Groundwork status is, and what the commissioning timeline looks like. The Waypoint drives the agent governance, not the other way around.

Start with: what three positions must we reach by the end of the quarter for the year to stay on track? Write them as binary pass conditions. Assign each one to a Station. Identify the Posts involved. Review them every week at the Bearing. That is the system.