The Key Objective Standard

Status: canonical framework (v1, captured from John, 2026-06). What makes a project's key objective strong, why it matters, and a worked example. The PM sets it in week 1; consultants serve it; directors and advisors rely on it to calibrate guidance. Change-control: HIGH-IMPACT — edit via PR.

The key objective is the spine of a project. Setting a good one is the highest-leverage thing a PM does in week 1, and a weak one quietly undermines everything downstream.

What it's for — three audiences

1. The team (consultants + PM): keeps them answering the right question, and makes a wide body of research cohere — all of it brought together in one presentation around the objective, instead of scattered findings that don't add up.
2. The client: an anchor they remember the engagement by — what the work is focused on and where it traces back to.
3. Advisors and directors: anyone the team goes to for guidance instantly understands the scope of what was asked, so their advice is calibrated rather than generic.

What "strong" looks like

A strong key objective is specific enough to guide a wide research effort, yet tight enough that everything lands back on one core problem. It opens up exploration without losing the center.

Worked example — Seattle Mariners (ticketing office)

The client wanted to increase ticket sales — but specifically through theme nights and partnerships. Framing the objective as "increase sales through partnerships/theme nights" did two things at once:

• It legitimized broad research that still pointed home: an audit of how theme nights are run across the major leagues and beyond (a full league-wide audit).
• It surfaced a real pain point from the client/prospect side — how does a group know the Mariners' arena fits their needs? — which produced an interactive arena-mapping tool that let people envision themselves in the space, engage with it, and generate their own data-grounded suggestions.

Everything diverged into research and converged back onto the objective, ending in an actionable deliverable the client could operationalize. That convergence is the mark of a strong objective.

What "weak" looks like

Too vague — e.g. "a B2B strategy for a company." The problems with vagueness:

• The team can't tell when research is on-target or whether they're landing on the goal.
• Findings don't cohere — there's no central problem pulling them into one presentation.

[NEEDS JOHN'S INPUT] We confirmed vague/too-broad as a failure direction. Open question: is too-narrow also a failure mode (an objective so tight it boxes the team in and misses the real problem)? Confirm so the standard warns against the right direction(s).

The test

A key objective is strong if it is specific enough that:

1. the team knows on-target from off-target as they research;
2. everything produced traces back to one core problem; and
3. an outside advisor immediately grasps the scope from the objective alone.

If it fails any of the three, tighten it before the team builds on it.