MetriqOne · SMART Logic · PI Design Discipline
Strategic. Measurable. Achievable. Relevant. Trackable.
SMART Logic is the PI design discipline within MetriqOne. It governs how Performance Indicators are specified, calibrated, and logged. One dimension has been modified from the conventional SMART framework — Trackable replaces Time-bound — and that modification is the difference between an evaluation tool and an evidence system.
SMART Logic governs how every Performance Indicator is designed, calibrated, and logged within MetriqOne. Two letters have been modified from the conventional framework. Those two modifications are the difference between a goal-setting tool and an evidence system that survives real-world disruption.
Modified
S
Strategic
was: Specific
Aligned with mission integrity. Every PI must trace a direct, evidential path to the Vision — through Module and CSI. Not just specific on its own.
M
Measurable
Quantifiable indicators that can be compared across terrains and time periods. No vague scores. No impressions.
A
Achievable
Realistic within the actual limits of the actors — schools, small businesses, cooperatives, community units. Not aspirational fiction.
R
Relevant
Context-sensitive and actor-specific. Resists generic industry templates adopted because they are easy to count, not because they matter here.
Modified
T
Trackable
was: Time-bound
Observable over time. Proves continuity through patterns — not through deadlines that collapse under disruption.
S — Why Strategic Replaces Specific
A Specific goal is evaluated in isolation — does this statement describe something precise? A Strategic goal is evaluated by its position in the architecture. It asks a harder question: does this PI have a structural home?
The evidential path requirement: Every PI must directly feed a Module. Every Module must support a CSI. Every CSI must align with the Vision. If a PI cannot trace this path — however specific and well-written it is — it does not belong in the system. This rule prevents cascade drift: the organisational trap of adopting metrics because they are easy to count, not because they carry evidence upward.
T — The Most Consequential Modification
MetriqOne's most theoretically consequential departure from conventional SMART
Fixed deadlines assume stable environments. Stable environments do not exist.
Typhoons, political instability, market shocks, power outages, floods — these make deadlines meaningless. When a system declares "failure" because a typhoon hit in Week 7 and the Q4 target is now impossible, the system gets abandoned. The team that maintained maximum effort through the crisis is recorded as having failed. Trackable survives what Time-bound cannot. The moving average drops, the environmental cause is documented, the system continues. No artificial deadline violated. No blame assigned. Pattern observed. Learning extracted.
Traditional — Time-bound
"Achieve 80% retention by Q4 2026."
Typhoon hits Week 7. Q4 deadline is now impossible. System declares failure despite full team effort. Measurement abandoned. No learning extracted.
MetriqOne — Trackable
"Maintain 80% retention, tracked via moving average."
Typhoon hits. Moving average drops. Environmental cause documented. System continues. Pattern visible. Team effort recognised. Learning preserved.
The SMART Validation Test
For every CSI, PI, or Module — ask all five questions. All five must be YES. One NO means redesign before deployment.
Criterion
Test question
Pass condition
S
Strategic
Does this PI link to Stability, Safety, or Continuity — and trace directly to the Vision?
Evidential path complete
M
Measurable
Is there a number, count, or percentage — not a feeling or impression?
Numeric or % value
A
Achievable
Can the actors influence this with available resources — without exceptional conditions?
Within actor capacity
R
Relevant
Is this specific to this organisation's context — or a generic metric borrowed from elsewhere?
Context-specific fit
T
Trackable
Can this be calculated via moving average — without depending on a fixed deadline?
12+ periods, no deadline
Weak vs Strong — Applied Example
❌ Not SMART-compliant
"Improve team morale."
[NO] Strategic — no link to mission
[NO] Measurable — no quantification
[NO] Achievable — no defined scope
[NO] Relevant — generic, context-free
[NO] Trackable — no measurement protocol
✓ SMART-compliant
"Maintain billable time ≥70% of total hours, tracked via 3-period moving average."
[YES] Strategic — links to revenue sustainability
[YES] Measurable — percentage from daily logs
[YES] Achievable — 70% realistic for this firm
[YES] Relevant — specific to billable service model
[YES] Trackable — moving average, no deadline
The Fatal Failure Mode — Miscalibration
A PI that passes all five SMART criteria can still destroy the system if its calibration threshold is wrong. Miscalibration is not a data problem — it is a governance design problem.
Trigger
Calibration threshold is set too low. The PI reads green even under poor performance conditions.
↓
Stack effect
PI logs green. Module reports green. CRI reads calibrated. Leadership receives a false positive signal.
↓
Decision layer
Resources are not allocated. Corrective action is not taken. Underlying deterioration continues undetected.
↓
Outcome
When the actual failure event occurs, the governance record shows no warning. The system has failed silently.
Prevention: Thresholds are pre-declared in the Calibration Log and cannot be retrospectively adjusted without a logged governance decision.
Go Deeper
SMART Logic is fully documented in Book I.
Including worked PI examples, calibration log templates, and the full design discipline for fragile operating environments.
