Metra Praxis

From Domain Expertise to a Defined System.

Metra Praxis is the design and discovery method behind every edition of Standard. It starts with the people who know the work, writes the whole system down before anything is built, puts the picture in front of the experts for review, and delivers a bounded first release that is verified against the work itself.

The method

Five Steps, in Order.

Learning and research overlap; everything else runs in sequence.

  1. Learn the Work

    The people who do the work describe it in their own words: the roles, the records, the workflows, the standards that bind them, and the numbers that matter. The operator writes it down exactly and never proposes a solution during this stage.

  2. Define the System

    The whole system on ten pages: every record as a subject with its lifecycle, the spine record that cannot be wrong, who sees what, the standards mapped to the records that prove them, the integrations, the volumes.

  3. Review with Domain Experts

    The picture is read against the interviews and the research, section by section. A section that does not hold sends the operator back to the expert with a specific question, not to their own judgment.

  4. Deliver a Bounded First Release

    A first product on one page, with a bounded scope and an acceptance audit written before the building starts. What ships first, and how everyone will know it worked.

  5. Verify It Against the Work

    Evidence from working software, checked by people who did not write it, against the records the experts said mattered. What is proven is recorded with how it was observed.

Three seats

Who Holds What.

The seats are named so that knowing, writing and deciding stay distinct acts.

The domain expert
Knows the work and owns the truth about it. Never touches code. Ratifies the description of their own domain.
The operator
Runs the interviews, does the research, writes the system picture, and runs the method. May know nothing about the domain on day one; the process is designed so that this is fine.
The ratifier
Decides. Where one founder holds both seats, the seat is still named, so that the decision is a distinct act from the writing.

Five artifacts

What Discovery Produces.

Each artifact is a file with a named owner. Discovery is over when the fifth is ratified.

Domain PackRatified by the domain expert
The domain in the customer’s own words: personas, records, workflows, standards, numbers, vocabulary, and what is off limits.
Research BriefRatified by the domain expert
What the outside world says: standards read in full, regulators, incumbents, integrations, procurement. Every claim tagged observed, claimed, or inferred, with its source.
System PictureRatified after review
The whole system on ten pages: subjects and lifecycles, the spine, the trust map, the standards map, integrations, volumes, non-functionals, open questions.
Foundation DecisionRatified
The infrastructure the picture needs and the stack that supports it, with the reasons. Each question has a default and a stated condition under which the default is wrong.
Wedge BriefWritten with the domain expert
The first product on one page, with its bounded scope and its acceptance audit.

The spine test

Find the Record That Cannot Be Wrong.

Every domain has one or two records where being wrong is catastrophic rather than inconvenient.

The interviews ask, for every record, what the worst thing is that happens if it is wrong, missing, or altered, answered in consequences rather than adjectives. The record with the worst answer is the spine, and the whole system is designed outward from it: what must be append-only, what must be signed, what must be numbered, what must be verifiable from outside, and what the audit trail must prove. In a calibration business it is the certificate. Everything else in the system can be ordinary. The spine cannot.

Discipline

Timeboxed, Sourced, Reviewed.

The method carries its own limits so that a project's shape is a decision, not a drift.

Timebox
Discovery runs five to ten working days. A Discovery that runs past ten is read as a sign that the first scope is too wide, not that more research is needed.
Sources
Nothing enters the research brief from memory. Every claim carries a source and a tag: observed, claimed, or inferred. The tag is what lets a reviewer tell knowledge from confidence.
Review
The system picture is read against the worksheets and the brief by someone who did not write it, and ruled on section by section: holds, holds with a correction, or does not hold.
Our position
We report; the customer decides. Findings carry their basis, and where there is a choice the options and their costs are laid out without a direction.

Read it

The Discovery Document.

The method, as written, with its worksheets and its stages.

The Discovery phase is published in full in the library, with the intake questionnaire, the eight interview worksheets, the research checklist, the system picture template, and the foundation questions.

Open the Library

Talk Through Fit.

If your industry has records that cannot be wrong and software that treats them as ordinary, we would like to hear how the work actually goes.