Managing Transitions

Questions

The things worth asking before hiring someone like me, answered properly rather than briefly. Definitions of the terms I use are at the bottom of the page.

Before You Get In Touch

Ten questions, answered straight.

You haven't finished the PhD. Why hire you now rather than waiting eighteen months?

Because right now I have a foot in both worlds at once, and that stops being true when the thesis does.

On one side I'm inside the academic machinery: methodology, ethics review, what the current research actually says rather than what got cited five years ago. I'm still learning it, which means I'm not reaching for the same method every time.

On the other, I work full time for an international NGO. I co-manage an EU co-financed programme and run the relationships across it, from community-based organisations through to government ministries, donors, and the comms people who have to make it all sound like something.

I'm at the tail end of interview data collection, so the fieldwork is nearly done and the write-up is next.

There's also the plain version: I'll cost less now than I will afterwards.

Why a solo consultant instead of a firm with a team behind it?

Because the thing I study and the thing I'm selling are the same thing: how people build enough trust to work together inside constraints they didn't choose.

That runs on relationships, and relationships don't survive being handed down an org chart. It matters that I can sit and have a coffee with the nurse. It matters that I can send a WhatsApp message and the whole team at the other end answers, because they know who I am and they know I'll still be there in six months. A firm sells you a partner and delivers you an associate.

There's also nothing sitting between you and the answer. No internal review, no account manager, no version that has to be run past someone first.

I take on few engagements and keep them small, so nothing is being handled in the background while I'm with you.

Where a firm beats me is anything needing a bench. A financial audit, a software build, translation: different skill sets, and I'd tell you to hire for them rather than stretch to cover them. What I can do is scope and source the right people to work alongside me, or slot into a team you already have. What I'm not offering is a firm.

You're a British consultant advising on localisation. Isn't that exactly the problem you describe?

I occupy the position I'm critiquing. That's the honest starting point, and I'd rather work with it in view than pretend to stand outside it.

What I don't believe in is the unmediated version, where localisation means handing everything to local staff and stepping back. And then what? That isn't where the funding sits and it isn't where the power sits. While the money comes from Brussels or Geneva, someone translates between what a donor requires and what the work actually needs. Pretending that role doesn't exist doesn't remove it, it just leaves it unexamined, which is how it ends up being done badly by someone who never had to think about it.

So I'm not selling contextual expertise. A Gambian or Ugandan colleague will read the political and cultural specifics better than I will, every time. I'm selling a method.

There's probably a gatekeeping question underneath all of this, about whose knowledge gets counted as knowledge and who decides. I don't think it resolves cleanly. I'd be wary of anyone selling a version where it does, including me.

If the donor checklist just gets passed downward, two things follow. Local actors carry the compliance burden on top of the work they were already doing. And it becomes their job to explain to the Global North how the Global North should reform, which it shouldn't be.

My side of it is listening to local actors and changing how donors, policymakers and academics work. Not the reverse.

Isn't "aid dependency exit" just a polite way of managing budget cuts?

Partly, yes. Worth saying that plainly rather than dressing it up.

US aid has been cut and FCDO budgets are down across the board. A lot of what's replacing them is corporate CSR and philanthropic money, which tends to arrive with outcomes-based or results-based financing attached. The ground has shifted under everyone, and a fair amount of transition work happening right now is a budget line being managed backwards.

But the principle didn't arrive with the cuts. Any decent programme should be trying to put itself out of business, and so should the NGO running it. Sustainability has been written into ODA programming for years.

The problem is what happens to it in practice. GEDSI and localisation get treated the way sustainability does, as a box to tick. A funder marks it "reduces dependency," and what actually happens is withdrawal: the budget drops each year and the local partner is told to diversify its income, with no plan for how and nothing transferred that would make it possible.

That isn't a transition, it's a withdrawal with a sustainability section. The difference between the two is whether anything moves other than the money.

What kinds of work do you turn down?

The main one is the engagement where the conclusion is already written and what's wanted is someone with the right letters after their name to sign it. An evaluation commissioned to confirm a decision that's already been made. A localisation review scoped tightly enough that the answer is fixed before the first interview. This happens more than the sector admits.

I'd also be uncomfortable with work where the local partners haven't been told it's happening, or where they won't be allowed to see what comes out of it.

Being straight about it: as a consultant I'm early enough that the list of things I've declined is short. Stating a red line is easier than proving one. What I can say is that I'd rather tell you at scoping that you don't need the work you're asking for than take it and write around the problem.

Do you hand over a report and leave, or stay through implementation?

Either, depending on how the work is scoped. Some engagements are genuinely short-term advisory: come in, do the piece, hand it over, go. Others carry on as a retainer through whatever the findings turn out to require.

What I try to avoid is the usual fate of a report. One internal meeting, then a drawer, then it gets pulled out eighteen months later because a donor asked whether anyone had looked at the problem. Nothing moved in between.

So I treat the report as the first stage rather than the deliverable. The honest position is that you can't scope the second stage until the first one is done, because until the interviews are finished nobody knows what they're dealing with. I'd rather say that up front than sell you an implementation phase I've priced before I know what's wrong.

What if your honest finding is that the programme should close, or that the donor's premise is wrong?

Then I say so. That's most of the reason to bring someone in from outside. I don't have years invested in the programme, and I don't have the internal relationships that make saying it expensive.

It's an uncomfortable thing to hear. But if the point of the programme is the people it serves, then stopping something that isn't working is a good outcome rather than a failure. Carrying on once you already know is the harder position to defend.

In practice: if I'm scoped for twenty-one days and it's obvious by day two, I don't spend the remaining nineteen writing the report I was hired for. We talk then. If it makes sense, we repoint the work at what a wind-down would actually involve.

How do you scope a piece of work, and how is it priced?

A first conversation, free, to work out whether there is anything here.

If there is, a Transition Exposure Review at a fixed fee. Two weeks, written findings and a ninety-minute session. The fee depends on whether we are looking at one country or a portfolio, and I will give you the number in that first conversation rather than have you work it out from a page. It is small enough that it is usually a decision one person can make.

Larger pieces are quoted against the deliverable and the date, agreed before work starts. If it turns out bigger than we scoped, we work that out together as it happens. Nothing gets billed that we haven't agreed first.

What if we have already made the decision and just need to execute it?

That is the common case and it is the right time to call. The review is not a second opinion on whether to restructure. It assumes the decision is made and works out what has to move, in what order, and what stays behind.

Most organisations plan the reduction well and the transfer thinly, and the transfer is where the risk sits. That is not an impression. In a study of twenty-three UK international NGOs' published transition documents, five put a figure against money moving to partners and six gave a handover timetable separate from their redundancy timetable.

We don't have budget for consultancy right now.

Most organisations in this position don't, and that is why the review is priced where it is.

The other route is to build it into a proposal as a costed transition workstream, which means it sits in a grant line rather than coming out of reserves. If you have a submission coming up, that is usually the easier conversation, and it is worth having before the budget narrative is written rather than after.

Glossary

Terms I use, and what I mean by them.

Some of these are borrowed and credited. Others are mine, and are working definitions rather than settled ones.

Localisation Theatre
Following Femke Mulder: the performance of participation, consultation, and local sign-off, staged to satisfy donor compliance, while the funding, the timeline, and the real decisions stay exactly where they were.
Governance-in-Practice
Localisation understood not as a policy commitment but as the accumulation of ordinary administrative tasks, funding rules, and reporting routines that quietly decide who actually holds power.
Harnessing Constraint
The small, repeated adaptations through which local actors work inside donor-imposed limits: reinterpreting a brief, adjusting an imported part, building the workaround that keeps a clinic open.
Project Logic vs. Systemic Coherence
The gap between individual interventions that each look successful in isolation, and a wider system that never stabilises, because funding cycles, leadership, and reporting requirements don't talk to one another.

Where these come from, and the research behind them, is set out on About.