How we engage
It starts with an hour.
You email. A director replies, personally. An hour later you know whether we can help, and so do we. There is no process after that, because there is no standard problem.
The hour
An hour on what needs to be better, not on the technology you suspect is the answer. Most people who meet us were introduced, so it runs both ways: this is where you find out whether the recommendation was any good. Ask us anything, including the hard questions, and measure the answers against how the problem is being handled today.
If we cannot help, we say so, and usually who to talk to instead. Sometimes the answer is that you do not need us yet.
What is always true
The shape changes every time, because the problem does. These do not, and they are the closest thing we have to a method.
That list has grown over twenty-seven years and it will keep growing. What it will not become is a diagram with four boxes, because the day we can draw the work that way is the day we have stopped paying attention to the problem in front of us.
Then what
We write down what we agreed, in a page, so nobody is guessing later. Then we start. What it looks like depends on the problem: sometimes a working session with your leadership, sometimes senior judgement alongside your team while the decisions get made, most often your own people building with us in the room. Usually some of each. We work that out with you after the hour, not before it.
The people who won the work do the work. Where something needs deeper specialist expertise we bring it in and stay accountable for it. Your people get stronger as we go, because that is the point: we would rather be needed less next year than more.
Where we start
Small, and additive.
We do not arrive asking you to stop anything. Whatever you are already running carries on untouched, and nobody has to declare that it was not working. We start instead with one pressing problem at senior level, build the intervention around that problem rather than lifting something off a shelf, and agree up front how it will be measured. Your people do the hands-on, on your own data and systems. The verdict arrives in weeks and it is yours to make.
If it works, it earns the next piece. If it does not, you have spent a small, bounded effort finding that out, and you will know quickly. That is the whole commitment.
What changes
The first piece is not the interesting one.
A few months in, once people have genuinely been using these tools rather than hearing about them, the questions change. They get more ambitious, and more importantly they get better founded, because they are grounded in what somebody has watched work with their own hands rather than in what was claimed at a conference.
We do not scope that work in advance, and we would be suspicious of anyone who offered to. Nobody can specify it yet, including us. What we can say is that it arrives, reliably, and that we are there when it does.
Common questions
What if we are not sure what we need?
That is the normal starting point, and a better one than arriving with a specification. You describe what needs to be better. We work out what the actual problem is. Sometimes the answer is that you do not need us.
How long before we see value?
A working session proves itself in the room, on the day. Anything longer is agreed with a way of telling whether it worked before it starts, and you make that judgement, not us.
How do we know it is the right call?
That is the real question, and the one we are built to answer. Our product is judgement, and it is independent: we recommend what the problem needs, including the simpler tool, or no technology at all. The standard we hold ourselves to is behavioural, not cosmetic: if we offered to take the new capability away, would your people fight to keep it? If they would not, it has not worked, whatever the dashboard says. And we do not judge it on the day: we measure Next Monday, when the enthusiasm has gone and the task is back.