Skip to content
Elyntara

Approach

We do not begin with a product. We begin with the problem.

A method that starts in the business and ends in production. Six phases, each with a defined output. An engagement can start at any of them.

  • Complexity into clarity
  • Strategy into architecture
  • Architecture into systems

01The method

Six phases, each with an output someone can act on.

The sequence matters less than the discipline: establish the constraint before designing against it, and evaluate options before committing to one.

  1. 01

    Discover

    Understand the business before the estate.

    What this phase involves

    We start with how the organisation earns, what constrains it, and what the executive team is actually accountable for. Technical discovery follows: operating environment, commercial commitments, regulatory position and the constraints that cannot be designed away.

    Output

    • Business and operating context
    • Constraint and dependency register
    • Stakeholder and decision map
  2. 02

    Assess

    Establish the current state honestly.

    What this phase involves

    An accurate current state is more valuable than an ambitious target. We assess architecture, infrastructure, resilience posture, technology debt and concentration risk, including the parts the organisation has stopped looking at.

    Output

    • Current-state architecture
    • Risk, debt and resilience findings
    • Cost and vendor exposure position
  3. 03

    Design

    Produce a target state and real alternatives.

    What this phase involves

    Target architecture is developed with genuine options, not a single recommendation dressed in alternatives. Each option carries its own resilience, scale and cost profile, and the conditions under which it is the right answer.

    Output

    • Target architecture
    • Solution options with trade-offs
    • Transition-state sequencing
  4. 04

    Decide

    Evaluate technically, commercially and operationally.

    What this phase involves

    A decision that is technically correct and commercially unaffordable is not a decision. We evaluate options across all three dimensions and support the executive or board process until a choice is made and recorded.

    Output

    • Evaluation against weighted criteria
    • Commercial and vendor assessment
    • Recorded architectural decisions
  5. 05

    Deliver

    Hold the architecture through implementation.

    What this phase involves

    Designs change under delivery pressure. We remain engaged as design authority, adjudicating trade-offs, overseeing delivery partners, and escalating where a proposed deviation carries consequences the executive should see.

    Output

    • Design authority and assurance
    • Delivery partner oversight
    • Deviation and risk escalation
  6. 06

    Optimise

    Measure the outcome against the intent.

    What this phase involves

    After transition, we compare what was delivered against what was decided (availability achieved, cost to operate, capability realised) and identify what the next increment should address.

    Output

    • Outcome measurement against intent
    • Operational cost and performance review
    • Next-increment recommendations

02Scope of view

We stay involved past the point where advice usually stops.

Strategy without architecture is theory. Architecture without execution is documentation. The value sits in holding the line between them, through design, through commercial evaluation, and through the delivery pressure that erodes both.

That is why the engagement model extends to design authority and implementation oversight. Not to deliver the work, but to remain accountable for whether the decision still holds when it meets a live environment.

Decision chain

  1. Business Objective

    What the organisation is trying to achieve, commercially.

  2. Technology Strategy

    Direction, sequencing and investment priority.

  3. Architecture

    The structure that makes the strategy possible.

  4. Solution Design

    Specific, buildable, testable design.

  5. Commercial Evaluation

    What it costs to acquire, and to run in year three.

  6. Implementation Oversight

    Design authority held through delivery.

  7. Operational Outcome

    Availability, cost and capability in production.

03Independence

What independence actually means.

Independence is not the absence of relationships. It is the absence of an incentive to reach a particular conclusion.

Elyntara is not remunerated by vendors for recommendations and does not resell technology. Where a relationship with a supplier, carrier or platform exists, it is disclosed at the outset of the engagement.

In practice this changes the order of work. Requirements first, evaluation criteria second, market second-to-last, and the product decision last, made against a specification the client owns.

Start here

Have a complex technology challenge?

Whether you are evaluating a transformation, redesigning your architecture or working through a difficult technology decision, it starts with a conversation.

Discuss a technology challengeExplore our services