Research and prototyping

The idea is interesting. That does not mean it deserves a full project yet.

When a technology opportunity is new or uncertain, a small structured experiment may be more valuable than a large proposal. We help turn promising ideas into questions that can be tested.

The situation

It often starts with something quite ordinary.

Leadership sees an emerging technology demonstration and asks whether the company should build something similar. The team begins estimating a large project without deciding what successful evidence would look like.

What is really getting in the way?

Enthusiasm has skipped the stage where assumptions about value, users, systems and practical constraints should be tested.

The question worth asking
What is the smallest responsible experiment that could change our decision?
Choose what sounds familiar

Which conversation are you having in your organisation?

These are illustrative situations, not claims about a particular client. Select the closest one to explore an appropriate first response.

What may be happening

A team believes a model can simplify work but has not tested exceptions or oversight.

A sensible first move

Build a bounded pilot with real process cases and explicit human review.

Discuss a situation like this →
How we think about it

Start with the decision, then examine the technology and work around it.

01

State the claim

Define the business outcome and the assumptions that must be true for it to happen.

02

Choose the test

Identify a feasible prototype, research sprint, small data test or workflow trial.

03

Decide what evidence changes the plan

Set success, failure and stop criteria before the experiment begins.

The work in practice

What this service can involve.

No fixed package is presumed. The right mix depends on what we find when the problem is examined.

Technology and market research

Evidence synthesis, assumptions, implementation realities and sector-specific implications.

Proofs of concept and prototypes

Small working experiences that demonstrate technical or behavioural feasibility.

Experiment design

Success measures, comparison cases, constraints, learning and stop criteria.

Decision brief and roadmap

Interpret findings, trade-offs and the next sensible scale or delay decision.

Useful outputs might include

  • Research and feasibility brief
  • Clickable or working prototype
  • Pilot plan
  • Findings and decision memo
  • Next-stage implementation options

These are possible deliverables, not a promise that every engagement needs all of them.

A few practical questions

Before you decide what kind of help you need.

Is a proof of concept a finished product?

No. It is a focused test of a critical assumption, not a guarantee of production readiness.

What if the experiment fails?

A well-designed unsuccessful test can still save money by disproving a costly assumption early.

Can the project stop after research?

Yes. “Do not proceed yet” is a useful outcome when the evidence points there.

A practical conversation

You do not need a perfect project brief to begin.

Bring the situation, even if the right solution is not yet clear. We can start by examining what deserves attention.

Discuss this challenge →