DEMETRA

A technical process built around evidence and constraints.

FrameAssessDesignValidateDeliverOperationaliseoperational feedback → next decision

  1. 01 — Frame

    Understand the desired outcome, the system context, constraints, stakeholders and the unknowns — before proposing anything.

    Typical activities

    • Clarify the desired outcome
    • Map the system context and stakeholders
    • Name constraints and unknowns
    • Review the existing architecture

    Outputs

    • Problem frame
    • Explicit assumptions
    • Initial risk map

  2. 02 — Assess

    Inspect what exists before proposing what should replace it.

    Typical activities

    • Architecture and code review where appropriate
    • Dependency, data and integration mapping
    • Delivery and operational constraints
    • Technology option assessment

    Outputs

    • Findings
    • Decision points
    • Option shortlist

  3. 03 — Design

    Define the technical direction.

    Typical activities

    • Option comparison
    • Architecture design
    • Non-functional requirements
    • Migration sequencing

    Outputs

    • Target architecture
    • Architecture decision records
    • Technical roadmap

  4. 04 — Validate

    When uncertainty is high, test it. Do not build a large solution to answer a small technical question.

    Typical activities

    • Proof of concept or technical spike
    • Integration prototype
    • Performance testing
    • AI evaluation where relevant

    Outputs

    • Evidence for the decision
    • Validated or revised design
    • Production-readiness view

  5. 05 — Deliver

    Implement in increments that can be reviewed, operated and changed.

    Typical activities

    • Incremental implementation
    • Testing and security hardening
    • Observability from the first increment
    • Integration with existing delivery processes

    Outputs

    • Operable increments in production
    • Test and security coverage
    • Operational visibility

  6. 06 — Operationalise

    Make the capability usable beyond the project.

    Typical activities

    • Documentation and runbooks
    • Handover and knowledge transfer
    • Operating-model guidance
    • Review of operational feedback

    Outputs

    • Runbooks and architecture records
    • A team able to operate and change the system
    • Next-stage roadmap

Engagement scope depends on the technical decision, system context and delivery model.

Contact →