ISO/IEC/IEEE 15288
Systems and software life-cycle processes
Phase 2 to-be process designs map directly onto 15288 process groups; decision-record governance inherits 15288's Decision Management clause.
Methodology
ISO-anchored. Decision-first. Measured against a signed baseline.
Every Whiz engagement runs the same four phases. The measurement contract is set after we look at the as-is and signed before any execution work begins — so the outcome target is calibrated to the customer's situation, not promised in a sales conversation.
The transformation surface
People, process, and platform — co-equal legs, moved together.
A change to one leg without coherent change to the others is the canonical reason transformation programs stall. Every Whiz Phase-2 and Phase-3 deliverable must touch all three or be rejected as scope-incomplete.
- People
- Roles, decision rights, escalation paths, and the Knowledge–Skills–Abilities–Behaviors humans must develop to staff the to-be. Title change without performance change is not enough; KSAB lift without role redraw re-absorbs into the as-is.
- Process
- The workflows that actually produce decisions — gates, reviews, approvals, evidence, cadence — mapped to ISO clauses so the to-be process is auditable on terms the customer's standards staff already accept.
- Platform
- Tools, data models, integrations, authoritative sources of truth — plus the provenance graph (digital thread) that ties every committed decision to its evidence, actors, and approval chain.
The four phases
As-is → to-be → execute → measure. In writing, at every gate.
- 01
Phase
Characterize the as-is
Instrument and measure current decision latency, defect-escape rate, rework, and cycle time across engineering and adjacent functions. Establish a quantitative baseline before anything changes.
- Decision-latency baseline for one named decision class
- As-is people / process / platform map for one engineering subsystem
- Sized estimate of latency reduction available in the next phase
- 02
Phase
Design the to-be
Target-state architecture and operating model — roles, KSABs, workflow gates, evidence requirements, platform integrations, the provenance graph. The sponsor signs the baseline before any execution work begins.
- ISO-mapped role / process / tool matrix
- Change-management plan, treated as a deliverable, not an appendix
- Sponsor-signed to-be baseline with measurement contract
- 03
Phase
Execute the transformation
Phased rollout with the customer's engineering team. Whiz's runbooks (identity bootstrap, deploy scaffolds, partner onboarding, decision-record governance) are part of the deliverable — not just internal scaffolding.
- One decision class redesigned end-to-end across all three legs
- Adoption metrics, not just delivery metrics, in acceptance
- Documented runbooks the customer's team can re-run without us
- 04
Phase
Measure and iterate
Verify the transformation delivered the predicted decision-latency, cost, and capability deltas. Plan the next iteration. The engagement does not close on a date — it closes when the measured end-state is reached.
- Before / after report against the signed measurement contract
- Customer-sponsor reference statement (Pilot+)
- Next-iteration scope or formal hand-back
Standards backbone
Why ISO is in the contract, not in the footnote.
Our deliverables cite specific ISO clauses by name. Process maps, role matrices, and decision records inherit the clause structure so the customer's standards staff can audit our work on terms they already accept.
ISO/IEC/IEEE 42010
Architecture description
Provides the viewpoint-and-concern structure for every architecture artifact Whiz produces — making the to-be auditable, not just persuasive.
ISO 56002
Innovation management system
Frames the change-management plan against a recognized management-system standard so transformation activity is auditable on the same terms as quality and infosec.
The measurement contract
Fees against deltas, not against deck thickness.
Pilot Engagements carry an outcome bonus contingent on the latency reduction we name in the contract — typically a 25–40% improvement on the chosen decision class. The exact number is calibrated to the severity of the as-is established in the Diagnostic Sprint, not to a one-size promise made before we have measured the system.
Decision dominance is the joint movement of velocity and quality. Velocity alone is recklessness. Quality alone is paralysis. The measurement contract names both — and we do not close out an engagement on a date; we close it when the measured end-state is reached.