Acuity Strategy

A Product Discovery and UX approach

Plan data and AI transformation around business and user needs

I combine Product Discovery, user experience (UX) and programme leadership to clarify the problem, test assumptions and build a realistic delivery plan.

Discuss your priorities
Bauhaus composition representing research and experimentation

Principle

Technology is not the starting point

A technically successful initiative can still fail when the problem is unclear, process constraints are discovered too late or users are not involved.

I start by understanding how people work: their decisions, tasks, pain points, available data and expected outcomes. This helps identify how technology can improve the process.

Method

Six Product Discovery steps

  1. 01

    Understand users and their context

    Use interviews and observation to understand processes, user journeys, available data and constraints.

  2. 02

    Define the problem and outcomes

    Connect every opportunity to a user, situation and measurable result.

  3. 03

    Assess possible solutions and expected value

    Explore the options, data requirements, performance, explainability and risks.

  4. 04

    Prototype, test and prioritise

    Test risky assumptions before committing to full delivery.

  5. 05

    Define the initial product scope and roadmap

    Use the findings to define scope, success criteria, governance and the decisions needed.

  6. 06

    Deliver, learn and support adoption

    Keep discovery connected to delivery and measure behaviour after launch.

Deliverables

Findings to guide decisions and delivery

  • User research and journey maps
  • Documented problems and use cases
  • Prototypes and summaries of test findings
  • Multi-criteria prioritisation matrix
  • Executive decision pack and roadmap
  • Adoption and usage measurement plan

FAQ

Frequently asked questions

Do you use a fixed framework?

No. Product Discovery and UX provide principles. Interviews, workshops, prototypes and tests are selected according to the context.

Will involving users slow the programme down?

I involve users at key stages to reduce late changes and the risk of building a solution people will not use.

What if specialist technical expertise is required?

Data, AI, architecture, security or compliance specialists contribute where needed, with a focus on business value and adoption.

Your context

Choose an approach that fits your organisation

Share the problem, the people affected and the decision you need to make. Together, we can agree how much discovery and delivery support you need.

Discuss your priorities