Skip to main content
SpenddaRequest a diagnostic conversation
Observe • Map • Deliver • MeasureSheet 02 / 06

The work as performed, not as described.

We do not begin with software. We begin with the work as performed, the evidence that describes it, and the decisions the organization must actually make. Each stage is bounded, dated and reviewable.

  1. 01

    Observe the operation.

    Preserve how work actually happens before proposing how it should happen.

  2. 02

    Establish what the evidence supports.

    Every material claim receives one state: Supported, Assumption, Unverified or Rejected.

  3. 03

    Prioritize the roadmap.

    Scoring, context, risk, effort, dependencies and human judgment produce an approved roadmap.

  4. 04

    Deliver and measure.

    Approved initiatives move into implementation. Adoption, exceptions and operating change are measured.

Detail 01 · evidence structure of a single findingMethod example · not a named client
Method example | finding 01

Weekend visit exceptions are handled through an unowned message chain.

This example shows the evidence structure used in a diagnostic. It is not a claim about a named client.

  1. FindingException handling has no single accountable owner.
  2. ClaimsFour role accounts describe different escalation paths.
  3. Source evidenceInterview notes, rota export and escalation procedure.
  4. VerificationCross-source comparison and operator walkthrough.
  5. ReviewerIndependent diagnostic reviewer.
  6. DateMethod example, 10 August 2026.
supportedConfidence recorded separately
Source line | Spendda diagnostic method note, controlled example 01, rev. 1.0

Diagnostic phases

A controlled path from question to action.

The method separates what people report, what the evidence supports, what remains unknown and what the organization chooses to change.

  1. 01

    Qualification

    Determine whether a diagnostic is appropriate and bounded.

    Spendda work
    Clarify the operating problem, decision path, timing, likely evidence and fee band.
    Client supplies
    A candid problem statement, prior attempts, decision participants and budget acknowledgment.
    Artifact example
    Qualification record with scope hypothesis, exclusions and next decision.
    Participation
    Sponsor or decision owner, 45 to 60 minutes.
    Sequence and timing
    Before any proposal or evidence request.
  2. 02

    Discovery

    Map the operating context before drawing conclusions.

    Spendda work
    Interview executives, department leads and operators. Establish boundaries, systems and observed handoffs.
    Client supplies
    Access to named participants, current procedures and a reliable engagement coordinator.
    Artifact example
    Interview records, context map and initial assumptions register.
    Participation
    Sponsor, leaders and representative operators, usually one to two weeks.
    Sequence and timing
    Begins after scope, fee and participation are agreed.
  3. 03

    Evidence

    Test accounts of work against controlled source material.

    Spendda work
    Register evidence, track requests, preserve source coordinates and identify what cannot be established.
    Client supplies
    Authorized records and timely answers to bounded evidence requests.
    Artifact example
    Evidence register, request register and numbered exhibit set.
    Participation
    Record owners and subject specialists as required.
    Sequence and timing
    Runs with discovery, then closes under an agreed cut-off.
  4. 04

    Diagnosis

    Convert verified claims into findings about the operating system.

    Spendda work
    Apply declared maturity and opportunity rules, develop findings and conduct independent review.
    Client supplies
    Factual correction and dispute, not pressure to alter supported conclusions.
    Artifact example
    Claims register, findings register, process records and reviewed scores.
    Participation
    Targeted validation with people closest to the work.
    Sequence and timing
    After material evidence has been received or marked not established.
  5. 05

    Roadmap

    Sequence changes according to value, risk, dependency and readiness.

    Spendda work
    Define actions, owners, acceptance criteria, prerequisites and measurement expectations.
    Client supplies
    Decision constraints, capacity limits and ownership commitments.
    Artifact example
    Prioritized roadmap with explicit assumptions and action risk.
    Participation
    Sponsor and accountable leaders in a decision workshop.
    Sequence and timing
    After diagnostic review, before implementation pricing.
  6. 06

    Proposal

    Turn approved priorities into a controlled implementation engagement.

    Spendda work
    Price a defined scope, state caps and exclusions, set governance and acceptance terms.
    Client supplies
    Approve priorities, provide authority and confirm the commercial decision process.
    Artifact example
    Implementation proposal linked to roadmap items and evidence.
    Participation
    Authorized commercial and operational decision makers.
    Sequence and timing
    Only after the roadmap decision, unless a separately verified brief exists.

Controlled method note

Take the operating standard into the room.

The note sets out phase controls, evidence states, review duties and the boundary between a diagnostic and later implementation.

Next step

Request a diagnostic conversation.

Request a diagnostic conversationRead the evidence standard →