Process

From first conversation to handoff brief

Our process keeps application analytics work tied to the decisions product leaders must make, so the resulting usage dashboard strategy can be implemented without guesswork.

  1. Scoping conversation

    We confirm the product surface, audiences for reporting, and whether an audit, workshop, framework, or retainer fits. You leave with a written outline of scope and fee range.

  2. Intake and access notes

    You share existing reports, decision calendars, and descriptions of instrumentation. We do not require production credentials; screenshots and redacted extracts are enough to begin.

  3. Stakeholder interviews

    Short conversations with product, support, commercial, and analytics roles reveal which usage questions change plans and which ones are ceremonial.

  4. Metric map and narrative draft

    We propose primary indicators, supporting context measures, and a spoken dashboard narrative ordered for weekly review meetings.

  5. Review workshop

    Stakeholders pressure-test the draft. Disagreements are documented with decision criteria so later builders inherit the reasoning, not only the chart list.

  6. Handoff and optional retainer

    You receive a strategy brief and implementation notes. Many teams continue with monthly advisory sessions while internal builders ship the first revision.

What we ask of your team

Nominate a single product owner for decisions, free interview participants for thirty to forty minutes each, and keep one working session free for the narrative review. Travel to Glasgow or your United Kingdom offices is arranged when workshops benefit from shared whiteboards.

Team collaborating at a long table during a workshop