the method
hear. challenge. build. optimise.
Four steps, in that order, every time. Not because process is comforting, but because the order is what stops us solving the loudest symptom instead of the real problem.
why a method, and not just experience.
Orange Jelly works across marketing, commercial change, operations, systems and AI. Without a method, that looks like a company that will do anything, which is another way of saying a company that's good at nothing.
The method is what connects them. It starts with the problem and ends with evidence, and it's the same sequence whether the answer turns out to be a campaign, a pricing change or a piece of software.
It also decides when to stop, which most engagements never do.
01
HEAR.
Understand what is really happening, not what the brief says.
We get close to the operating reality: the leader, the people doing the work, the data, and where it helps, the customer. Leadership interviews, staff conversations, a walk through the journey and the systems, and a proper look at the numbers.
What you end up with: A problem statement in plain words, a map of how it works today, the baseline we will measure against, and an honest list of what the evidence does not cover.
Listening is not enough. The job is to hear the difference between what people say is happening and what the numbers show.
02
CHALLENGE.
Test what everyone assumes, against the evidence.
This is the uncomfortable part and it is the part that pays. We connect the visible symptom to the rest of the business, take apart the comfortable explanation, and make the trade-offs explicit. Root cause, funnel, margin, process, journey, systems and data, then sizing and prioritising what is actually worth doing.
What you end up with: A Growth Pressure Map, an agreed definition of the problem, a prioritised short list, and the measures we will judge it by.
Do not solve the loudest symptom. Find the few pressure points that can change the outcome, and say so even when it is not what anybody wanted to hear.
03
BUILD.
Build the fix, not a document about the fix.
The solution might be a proposition, a conversion journey, a pricing change, a booking system, a dashboard, an automation, an operating rhythm, or an AI tool that earns its place. The problem decides. We start with the smallest intervention capable of making a material difference, prototype early where we are unsure, design it for the people who have to use it, build the measurement in rather than bolting it on, and write down what you need to run it after we have gone.
Avoid unnecessary technology. If the answer is a pricing change and a phone call, that is the answer.
04
OPTIMISE.
Measure it against the baseline, then keep going until it moves.
Success is agreed before anything is built, so there is nothing to argue about afterwards. Then we compare against the baseline, look at the leading indicators as well as the lagging ones, fix the adoption problems that always appear, and iterate.
What you end up with: An impact report with before and after, a learning log, an honest handover, and a recommendation to scale it, change it or stop.
Work is not finished because something was delivered. It is finished when the change is implemented, understood, and measured as far as the engagement allows.
the growth pressure map.
The artefact that comes out of CHALLENGE. It maps the business across six connected areas and says, for each one, where the pressure actually is.
- Demand
- Whether enough of the right people know and care.
- Conversion
- What happens between interest and a decision.
- Margin
- What is left after the sale, and where it leaks.
- Operations
- What the business spends effort on that it should not.
- Experience
- What people remember, as opposed to what you deliver.
- Scale
- What breaks first at twice the size.
It's not a generic scorecard with a total at the bottom. A score invites a league table and false precision. The map is built around your business model and is there to focus the next move, not to grade you.
what we agree before anything is built.
- The problem we are solving, in one sentence we both recognise.
- Why it matters now.
- The baseline, or the honest admission that there is not one yet.
- What success looks like, as a number where possible.
- What is in scope and what is not.
- Who can make the decisions, and who owns implementation.
- What data and access we need.
- How we will review progress.
- What would make us stop, change direction or expand.
Every one of those is agreed in writing before the first day of build. It's not paperwork: it's the list of things that, left unsaid, turn into the argument at the end.
what this stops happening.
- Starting with a tactic somebody asked for before anyone has understood the problem.
- Treating every problem as a marketing problem.
- Using AI where it adds nothing.
- Handing over a strategy the business cannot actually implement.
- Measuring activity instead of impact.
- Carrying on after the useful outcome has already been reached.
- Letting everyone avoid the decision the business actually needs to make.
the order is the method.
It starts with an hour on the phone and no charge. Tell us what's happening and we'll tell you what we think.