I work inside your organisation part-time to put the fixes into practice, until they run without you or me holding them together.
"He made a lasting impact on our growth. He brought structure to decision-making, empowered the team to take ownership, and created a culture of constructive feedback and improvement."
A new hire, a new tool, a new process. Each can look like progress for a while.
Then, slowly, things slide back to the way they were.
That isn't bad luck. It usually happens because the fix changed the organisation, when the real lever was how decisions and context were being held at the top.
This work starts by finding the right layer, before a single hour goes into building on the wrong one.
The first two weeks are the Clarity X-Ray: your read of what's causing the fires, set beside your team's, and a sequenced plan for what to fix first. If you've already done one, we start from its findings. We only go further if we genuinely agree on what's driving the fires. Fixes built on a diagnosis you don't believe rarely hold.
Not therapy, and not about your history. We pin down the exact moments that pull you back into a decision you meant to delegate, or into day-to-day work you meant to step out of. Knowing precisely when a pattern shows up is what makes it possible to build around it.
Two concrete things. Written decision boundaries: what's yours to decide alone, what needs a heads-up, and what the team can simply act on. And a shared place for the context that currently lives only in your head, so people stop deferring to you because nobody else has the full picture.
You back the new way of working in front of the team, with the reasoning behind it, and then you're seen using it yourself. Systems get adopted when the person at the top treats them as real. If you're the one exception to a new rule, it quietly becomes optional for everyone.
We try it with a small, real part of the organisation first, often as a simple interim rule with a fixed date to revisit it. We check whether it's actually being used rather than assume it, and change what isn't sticking.
Only when decisions and visibility are working, not just built, do automation or AI tools go on top. Automating a broken process doesn't fix it. It makes the chaos move faster.
The engagement is designed to make me unnecessary as quickly as possible. Success isn't a good final presentation. It's the system still running, unprompted, after I've left, and ideally someone on your team extending it on their own.
That last step has happened before. At The Agency Fund, the decision framework kept running after I left, and another team lead built their own version of it. See my results.
Most of my work has been from the inside, staying long enough to see whether a change held. A few examples, each tied to a step above.
I was brought in to turn around struggling intervention operations on a 27,000-participant health trial, with more than 100 team members spread across 2,000 sq km. I led the build of a central, data-driven war room connected directly to every one of them.
The team's performance nearly doubled in six months. The war room is still running, long after I left.
The first thing I did was run a diagnosis, interviewing the founder and the team. The biggest issue they raised: work scattered across eight different tools, and context trapped in people's heads, so people waited on each other for even basic questions across teams.
We chose a single project management tool that covered everything we needed: chat, tasks, documentation, message boards, direct messages and scheduling. Then we rolled it out over three months. I pitched it to the team, a couple of teams volunteered to try it first, and their success stories became the pitch to everyone else. Internal-facing teams moved over first, external-facing teams after them.
Years later, it's still how Nirogam runs as a remote team spread across cities and time zones.
We first rolled out a full-featured performance management tool. Within months, nobody was using it. So we replaced it with something much lighter: monthly team and individual targets, and six-monthly learning goals, posted in the project tool everyone already opened every day.
For the first time, in the founder's words, people were putting their goals in writing and answering for them.
A separate study at the same organisation had stalled for months. I was brought in specifically to fix it, with no authority over any of the people who actually mattered: government health workers, district officials, and a senior hospital doctor actively steering patients away.
I treated it as a behavioural problem, not a management one.
A public ranking system made health workers compete for training instead of avoiding it. I figured out what the antagonistic doctor actually wanted, recognition in front of international visitors, and made sure he got it.
Within seven months of my taking over as programme director, the study was back on track. The results it delivered helped secure $1M CAD in scale-up funding.
Before we start, we agree how the working relationship runs, the same way we'll set up decisions and visibility in your organisation.
In the words of the founders and teams I've worked alongside.
"Within days of joining, he had established robust HR protocols and SOPs that brought unprecedented clarity and efficiency… Sometimes the best leaders are those who make leadership itself obsolete."
"Raghav Krishna is one of those rare managers who also naturally serves as an inspiring mentor for the whole staff… [His] ability to motivate a team to care about its project and be invested in the project's success."
"Raghav has a rare ability to look at a chaotic system, identify the friction points, and build sustainable, scalable solutions that save everyone time."
"Raghav ensures that everyone has the right context to move forward confidently. Working with him not only improves current operations but also elevates the thinking and capability of the entire team."
"He has a remarkable knack for cutting through noise and making things more manageable and focused."
"I got the feeling that he is the friend you'd call if you need honest advice that doesn't just make you feel good but actually helps."
A partnership runs for six months, and it's scoped around the areas we agree to work on and how much of my time they need. After our first conversation, I send you the scope, timeline and price in writing, before you commit to anything.
Finding the right problem to solve is half of impact. This partnership is the other half: building an organisation that can actually solve it, and keeps solving it without you holding it together.
Don't settle for a fix that looks good for a quarter. Build one that holds.