EM-STR-02 · Subject model · W1
Goals, Key Results and Benefits
Goals, measurable target states, expected and realized benefits. The method of valuing benefit and harm is set by an explicit profile.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Objective
- KeyResult
- Target
- Outcome
- Benefit
- ValueAssessment
Deep research questions
- When does a deliverable actually produce an outcome?
- How is a benefit linked to several work items without double counting?
- How are value and negative consequences compared under incompatible scales?
Verifiable invariants
- A goal is not a metric
- A target value specifies the metric version
- Value/anti-value gets no universal formula without a methodology
End-to-end acceptance scenario
One benefit from two projects, a delayed measurement and a negative side effect preserve attribution and uncertainty.
Negative case
A planned effect is recorded as a realized result; a benefit is credited twice, to the program and to the project.
Approaches to compare
- ArchiMate: motivation, capability and realization relationships
- APQC: coverage of functions and processes
- PMI: benefit/business case; compare with a chosen OKR school and value-stream management
Candidates in the live catalogue
- WM-KNW-011 · Goal / Objective · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-025 · Observable Result Fields · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.