The KERNYRA process
Seven stages. One continuous line of evidence.
The shape changes with the engagement, but the logic stays consistent: understand the real system, make choices explicit, validate what matters, and leave a stronger operating baseline.
Sequence
- 01
See the system
Discover
Understand users, operations, constraints, existing technology, risk, and the decision the work must enable.
Evidence at this stage
Shared context · constraints · current-state map
- 02
Set the boundary
Define
Translate discovery into outcomes, scope, measures, priorities, responsibilities, and explicit exclusions.
Evidence at this stage
Product brief · success criteria · release boundary
- 03
Make it tangible
Design
Shape journeys, states, information, interactions, and system behaviour before implementation hardens assumptions.
Evidence at this stage
Experience model · prototypes · technical decisions
- 04
Build the core
Engineer
Implement in coherent increments with quality, security, observability, and delivery controls built into the path.
Evidence at this stage
Working software · architecture · delivery pipeline
- 05
Challenge the work
Validate
Test behaviour, usability, performance, security, integrations, and operational readiness against agreed evidence.
Evidence at this stage
Test evidence · resolved risks · launch decision
- 06
Change the state
Launch
Release deliberately, monitor the transition, support users, and keep rollback and response paths clear.
Evidence at this stage
Production release · monitoring · ownership handover
- 07
Improve the baseline
Evolve
Use product signals, incidents, support patterns, and new priorities to guide the next engineering cycle.
Evidence at this stage
Learning loop · prioritised evolution · maintained system
- 01
See the system
Discover
Understand users, operations, constraints, existing technology, risk, and the decision the work must enable.
Evidence at this stage
Shared context · constraints · current-state map
- 02
Set the boundary
Define
Translate discovery into outcomes, scope, measures, priorities, responsibilities, and explicit exclusions.
Evidence at this stage
Product brief · success criteria · release boundary
- 03
Make it tangible
Design
Shape journeys, states, information, interactions, and system behaviour before implementation hardens assumptions.
Evidence at this stage
Experience model · prototypes · technical decisions
- 04
Build the core
Engineer
Implement in coherent increments with quality, security, observability, and delivery controls built into the path.
Evidence at this stage
Working software · architecture · delivery pipeline
- 05
Challenge the work
Validate
Test behaviour, usability, performance, security, integrations, and operational readiness against agreed evidence.
Evidence at this stage
Test evidence · resolved risks · launch decision
- 06
Change the state
Launch
Release deliberately, monitor the transition, support users, and keep rollback and response paths clear.
Evidence at this stage
Production release · monitoring · ownership handover
- 07
Improve the baseline
Evolve
Use product signals, incidents, support patterns, and new priorities to guide the next engineering cycle.
Evidence at this stage
Learning loop · prioritised evolution · maintained system
Process principle
Good process does not add ceremony. It reduces the cost of discovering the wrong thing late.
First step
Start with what you know. We will help expose the rest.
You do not need a perfect brief. We need honest context, a meaningful decision, and a willingness to test assumptions.