Design sits on the critical path
When design is the thing everyone is waiting on, a week of hesitation costs the whole programme, not just the design team.
Fast and rigorous. Not one or the other.
Transformation programmes ask design delivery to pick one: keep pace, or do it properly. Vijay Kandhalu, with extensive expertise in process, tooling and design leadership, does not have to choose.
The trade-off you've been sold
"Fast" usually means something got skipped.
Every transformation programme has seen both failure modes, and they cost the same money.
Fast without rigour
Ships something by the next milestone. It fails the service assessment, ignores the accessibility standard, and gets rebuilt by the team that inherits it.
Rigour without speed
Is still writing the discovery plan while the programme moves on without it. The delivery date hasn't shifted, so the rigour gets cut at the end anyway — just later, and more expensively.
Neither is a speed problem. Both are a capability problem.
What makes it possible
Four things, together. Not one of them alone.
Fast with rigour isn't a working style or a lucky hire. It's what happens when four capabilities arrive in Vijay Kandhalu — each one covering the failure mode of the others.
Industry expertise
Twenty years in software and user-centred design, most of it delivering to GOV.UK and GDS standards across transformation programmes in multiple departments. I've seen the pattern before it shows up, so discovery isn't spent working out what kind of problem this is.
Tooling
AI-augmented delivery, used properly. Working prototypes instead of slide decks, in hours rather than sprints — GOV.UK Prototype Kit, Next.js, Cursor, Vercel. Speed here comes from the toolchain, not from cutting scope.
Process
The Service Standard, the double diamond, and evidence at every gate. Process is what makes the speed defensible: assessors, auditors and the team who inherit the work can all see how a decision was made.
Leadership experience
Hands-on, but still leading. Knowing what to decide, what to escalate, and what to leave alone. Most delivery doesn't stall on design — it stalls on an unmade decision. Experience is what keeps that queue short.
Remove one and it breaks.Expertise without tooling is delay.Tooling without process is rework.Process without leadership is stagnation.Leadership without expertise is guesswork.
What it looks like in delivery
From day one — not from month two.
Transformation programmes don't wait for Vijay Kandhalu to settle in. This is what the first month looks like.
Delivery stages
Join the programme — Into the standups, the backlog and the constraints. I start with the decisions already made — not just the problem. Build something real — A working prototype the team can click through. Early, rough and specific enough to argue with — that's the point. Prove the decisions — Research, testing and accessibility checks against the standard — so the decisions hold up when someone senior asks why. Sustain the pace — Delivery at a rate the team can sustain without me driving it. Speed that only works while I'm in the room isn't speed. Hand over cleanly — Documented, standards-compliant and owned by a team that can carry it forward.
- 01week 1
Join the programme
Into the standups, the backlog and the constraints. I start with the decisions already made — not just the problem.
- 02week 1
Build something real
A working prototype the team can click through. Early, rough and specific enough to argue with — that's the point.
- 03weeks 2–3
Prove the decisions
Research, testing and accessibility checks against the standard — so the decisions hold up when someone senior asks why.
- 04ongoing
Sustain the pace
Delivery at a rate the team can sustain without me driving it. Speed that only works while I'm in the room isn't speed.
- 05handover
Hand over cleanly
Documented, standards-compliant and owned by a team that can carry it forward.
Why it matters on a transformation programme
Transformation timelines don't wait for design to catch up.
The standards don't flex
Service assessments, accessibility regulations and audit trails don't move for a deadline. Speed that ignores them isn't speed — it's rework with a later invoice.
It has to outlast me
Whatever gets built has to keep working as the team changes, which rules out the shortcuts that only look fast.
Looking for Vijay Kandhalu?
Send me the role as it stands.
The stage the programme is at, the standard it has to meet, and the outcome you need. If I'm the right fit I'll say so, and if I'm not I'll say that too.
Available for hands-on design leadership on digital transformation programmes. Remote, UK-based.