Goal-Setting Framework#

MSX uses a lightweight OKR-based framework to connect strategic direction to day-to-day work. The hierarchy runs from the organization's reason to exist down to individual deliverables tracked in GitHub issues.

Layers#

Why OKRs and not KPIs#

• Objectives are qualitative, aspirational, and outside-in. They describe a state of the world we want to see.
• Key Results are measurements that confirm the Objective is being met. They drive incentive in the right direction without prescribing the path.

A good OKR is one that anyone — contributor, user, or agent — can read and immediately have ideas about how to contribute. See Principles for the full rationale.

Current OKRs#

OKRs are tracked as sub-issues of the Mission issue in the org .github repository. They evolve over time; the direction they encode stays constant:

• Every developer — and every agent — ships with confidence.
• Automation handles the mechanical, so human attention is spent on judgment.
• AI is a first-class, reliable contributor to the work.

From strategy to delivery#

Initiatives are the bridge between strategy and execution. An Initiative is a sub-issue of an OKR and maps directly to an Epic in the relevant repository. From there it decomposes into PBIs and Tasks through the Issue Hierarchy.

Mission (org-level, evergreen)
└── OKR (qualitative objective + key results)
    └── Initiative (concrete bet to move a KR)
        └── Epic (in a repository) → PBIs → Tasks