Metra Praxis · Discovery and development method
Learn the work.
Then define the software.
Metra Praxis turns domain expertise into a defined system and a bounded first release. The people who know the work establish the requirements; the software is judged against those requirements.
- 01
Learn the work
Interview the people responsible for the roles, records, workflows, standards, and difficult decisions. Use their vocabulary.
- 02
Define the system
Describe the records and their lifecycles, access, obligations, integrations, and operating scale.
- 03
Review with domain experts
Check the proposed system against the interviews and evidence. Resolve gaps with the people who know the domain.
- 04
Bound the first release
Decide what ships first and the acceptance criteria before building it.
- 05
Verify against the work
Use working-software evidence and review to establish whether the defined scope holds.
The record that matters most
What is the consequence
if this record is wrong?
That question identifies where the design needs its strongest discipline. In a calibration business, the issued certificate and its evidence demand particular care.
- Domain expert
- Establishes the facts of the work and reviews its representation.
- Operator
- Conducts discovery, researches the requirements, and writes the system picture.
- Decision owner
- Approves the scope and makes the tradeoffs explicit.
Discovery outputs
A shared picture before implementation.
The method produces reviewable artifacts, with decisions and open questions made explicit.
- Domain pack
- Roles, vocabulary, records, workflows, and obligations in the experts’ terms.
- Research brief
- Sourced requirements and external constraints, with evidence distinguished from inference.
- System picture
- Record lifecycles, trust boundaries, integrations, and operating needs.
- Foundation decision
- Infrastructure choices and their reasons.
- First-release brief
- A bounded scope and the acceptance criteria used to judge it.