A feature request is not an objective. A goal is not an objective. An objective is a measurable statement about what a named user will be able to do when the work is done.

Most backlogs are lists of things someone wants to build, organized by when someone wants them done. The Objectives Backlog℠ is something different: a catalog of user confidence gaps, written in the user’s voice, each one anchored to a specific service, placed at a specific tier, and equipped with the leading and lagging indicators needed to know whether it was actually achieved.

The writing discipline is the point. An objective like "I can get a rate for every input I enter without errors or timeouts" is testable. "Improve the quoting experience" is not. The Backlog’s authoring interface enforces the difference — it requires numeric indicators, not aspirational language, and surfaces a writing assistant that flags implementation-flavored or vague objectives before they enter the queue.

The objective is the unit of value in the framework. Every epic, every story, every sprint commitment traces back to one. If the objective is imprecise, everything downstream is building toward a target that can’t be measured — which means you can’t know whether you hit it.

• Author objectives in user voice with leading and lagging indicators
• Filter by value stream, domain, service, tier, or state to focus on what’s relevant
• Track the full lifecycle: Backlogged → Modeled → Pursuing → Met (or Failing)
• Bulk-update objective states at sprint boundaries or after ceremonies

Product managers authoring strategy. Anyone who needs to answer "how do we know when this is done?" with something a data system can confirm.

The Objectives Backlog is the system of record for the entire framework. The Impact Point Workshop renders it visually. The Five What-Ifs models it prospectively. The Alignment Ceremony transitions it collaboratively. The Development Backlog builds toward it tactically. Everything reads from here.