The COOPER Method

The problems change. The method doesn't.

COOPER does not sell fixed programmes, because businesses are rarely generic enough for an off-the-shelf answer. The engagement is shaped by the business and the problem. The COOPER Method is the consistent framework behind it, so bespoke never means unstructured.

Diagnose before prescribing. Understand context before recommending action. Compare options before prioritising. Then go beyond the recommendation into execution and review, rather than stopping at a report.

The six stages

One disciplined route from problem to improvement.

Select a stage to see what happens, what COOPER is looking for and what should exist before the work moves forward.

01Context

Understand the business before trying to fix it.

Establish what the business is trying to achieve, what prompted the conversation, who is involved, what has already been tried and what success needs to look like. The aim is to define the problem, desired outcome and boundaries before deciding where the answer sits.

ObjectiveTriggerPeopleConstraints
Output

A clear definition of the problem, the desired outcome and the boundaries of the work.

01 / 06
From assumption to evidence

Find the real constraint before choosing the answer.

The visible symptom is often only where the problem shows up. COOPER follows the evidence far enough across the business to understand what is actually creating it.

Result

We stop treating the symptom as the problem and establish what is actually constraining the business.

People and responsibilities
Current systems and CRM
Commercial and operating data
Processes and handoffs
Bottlenecks and duplication
Unclear ownership
Costs, subscriptions and resource
Previous attempts to solve the issue
From evidence to a decision

Choices become a recommendation.

Credible options are compared against the things that matter commercially. The point is not to create a longer improvement list. It is to decide what happens now, next, later or not at all.

Result

A recommendation, a practical order of work and an explicit decision about what not to do.

Prioritised against

01Business impact
02Urgency
03Effort
04Cost
05Risk
06Dependencies
07Speed to benefit
08Available resource
From recommendation to result

The recommendation only matters if something changes.

Actions get owners, dependencies and a measure of success. COOPER can stay involved through implementation, then review whether the original problem actually improved.

01Action
02Owner
03Deadline
04Measure
05Review
Result

A tested improvement, any final adjustments and clear ownership going forward.

Working principles

Structured without becoming consultancy theatre.

The Method adds discipline without adding ceremony for its own sake. Daniel leads the work throughout, from forming the view to helping make the change happen.

01Evidence before answers

COOPER does not arrive with software to sell or a fixed framework to impose. The evidence determines the answer.

02A decision, not a long list

Analysis should end in a recommendation, an order of work and a clear view of what should not be done.

03Implementation matters

COOPER can stay involved to configure, build, coordinate and deliver. The objective is a working improvement.

04Leave capability behind

The change should be measurable, understandable and maintainable by the people using it after COOPER steps away.

What does the business need to achieve next?

The conversation can start with the goal, the problem or the frustration. The method starts once we understand what needs to be different at the end.

Start a conversation