Senior delivery leadership for public sector programmes that need to move, without the overhead of a permanent hire.
Signal is Josh Greencroft, a senior delivery leader with over a decade of experience across UK central government.
I've delivered large-scale digital programmes at DEFRA, HMRC, MoJ, DHSC, UKHSA, and DESNZ, operating at programme and portfolio level. I established DEFRA's first Delivery Centre and have led programmes from Discovery through to Live across the GDS delivery lifecycle.
The cause of delivery failure is rarely the team. It is almost always the conditions around it. Signal exists to change that.
Genuine Discovery means understanding a problem before committing to a solution. Teams that skip it almost always build the wrong thing. The output is not a solution — it is enough confidence to know one is worth pursuing. Pointing a team at a predetermined answer and asking them to work backwards is not Discovery. It is waterfall with a GDS wrapper.
Before a team starts, make the decisions that can reasonably be made. Set guardrails, agree constraints, resolve dependencies. This is not designing the solution upfront — it is removing avoidable ambiguity before it becomes expensive. Teams that arrive to a prepared environment can focus on delivery. Teams that do not spend months navigating governance that should have happened before they landed. Stock the fridge. Then let the team cook.
Good governance helps the right people make good decisions, as close to the work as possible. It does not make those decisions itself. When teams spend significant time producing documents nobody meaningfully reads, governance has tipped into control. Clear ownership matters too: when nobody has authority to decide and be trusted to have decided well, governance becomes a substitute for leadership.
Tightly coupled organisations build tightly coupled services. When every decision needs consensus from half the organisation, delivery slows to the speed of the slowest dependency. Loose coupling is not the absence of dependencies — it is the deliberate reduction of unnecessary ones. Loosely coupled teams with clear outcomes and trusted autonomy build services that are more modular, adaptable, and resilient.
The most valuable programmes succeed because they changed what an organisation was capable of, not because they cut costs. Outcomes-led thinking asks: can users achieve what they need more easily? Can services adapt to changing policy? Activities are inputs. Outcomes are evidence that something has actually improved.
The most durable digital infrastructure is built by teams that deliver services deliberately, leaving reusable building blocks behind them. A capability not actively in use is a hypothesis, not an asset. The first service proves it works. The third to fifth prove it is worth standardising. Build only what you have evidence for. Invest heavily once reuse has been demonstrated.
Reaching for a complete picture before starting is understandable. In complex environments it is usually counterproductive. Uncertainty is not a problem to solve before delivery begins — it is the condition in which delivery happens. Clear ownership and delegated authority make uncertainty manageable: when things change, the right people have the authority to respond.
Engagements are typically fractional, two to three days a week, giving clients access to experienced delivery leadership at the moments it matters most, without the overhead of a permanent appointment.
Embedded senior delivery support for programmes and teams, typically two to three days a week. Ideal for organisations that need experienced leadership during a critical phase of delivery without committing to a full-time hire.
An independent assessment of delivery conditions, governance structures, and team ways of working, with clear recommendations for improvement. Useful at the start of a programme, at a point of difficulty, or as an external sense-check on an existing approach.
Half-day or full-day sessions for senior leaders and delivery teams, built around the Signal philosophy. Topics include preparing conditions for delivery, governance that enables rather than controls, and building high-performing teams in uncertain environments.
The instinct when things go wrong is to reach for more structure. These tools address symptoms rather than causes. They impose control on an environment that needs clarity and trust. — Josh Greencroft, Signal Delivery
The first thing many experienced people will think when they read this is: I have heard this before. Discovery. Empowered teams. Outcomes. Autonomy. Iterative learning. This has been the agile conversation since 2005.
That reaction is understandable. But it misses a distinction that matters. Most agile thinking focuses on the team — how it works, how it plans, how it iterates. Zero Drag Delivery is not primarily concerned with what happens inside the team. It is concerned with what happens around it. Governance. Funding models. Decision-making authority. Organisational design. Leadership behaviour.
Teams rarely fail because they do not understand agile. They fail because the environment around them makes success structurally impossible. Zero Drag Delivery addresses the system, not just the team. That is the distinction.
All engagements are tailored to the specific context. If something in this document sounds familiar, if your delivery is taking longer than it should, or the drag has become hard to work against, get in touch.