The Satellite Mission That Taught Us Where Delays Really Hide

STFC's Speqtre mission is the first satellite built through the UK's agile mission facility: designed to test quantum key distribution, (technology designed to make communications unhackable).

It's the kind of programme that makes you want to talk about the world-class quality of the engineering. But, what we focussed on was something less sexy: a brilliant, multidisciplinary team working incredibly hard, in a system that wasn't making that effort easy to see.

That's usually where we start: not with the technology, but with how the work actually flows.

Finding Clarity

Speqtre brought together optical, thermal, mechanical and electrical engineers, data scientists and international collaborators on a complex, high-uncertainty mission.

Individually, everyone was skilled and committed. Together, the picture was harder to read: collaboration was fragmented across disciplines, priorities and dependencies weren't visible in one place, planning and tooling varied team to team, and the mission's delivery timeline had stretched further than anyone wanted.

None of that came from a lack of capability. It came from a lack of shared sight.

Delays like this rarely live in the technology. They live in the handoffs between disciplines working from different backlogs, between plans that updated on different clocks, in dependencies nobody owned until they blocked someone.

So before changing anything, we spent time mapping and understanding the system of work as it actually existed (the team's structure, its health, its constraints) and worked with the team on what success would look like and where change would make the biggest difference.

Taking Action

Over six months, working both in person and virtually, we helped the team co-create a single, prioritised backlog of small improvements and experiments, then test them in monthly iterations: standardising tooling and process, monthly face-to-face planning and retrospectives, weekly discipline-specific alignment, and weekly cross-discipline dependency management.

Small, deliberately unglamorous changes. The kind that are easy (yet expensive) to skip.

Seeing the Results

After six months:

• 371% increase in the average number of tickets completed per team member each week (noting it's likely that tickets became smaller)

• 80% improvement in how the team prioritised work

• 80% more clarity on roles

• 60% stronger cross-team collaboration

• 50% better dependency management

• 30% more visibility of work in progress overall

There's a financial story here too, though it's worth being precise about it. Speqtre's design phase was completed by the time we joined, so much of that phase's timeline was already set. What the data does show is what this way of working is worth going forward: for missions of similar scope, RAL Space estimate it can avoid around £480k in cost through a six-month reduction in lead time.

As the mission's Lead Systems Engineer, David Pearson, put it: "The design phase for the Speqtre mission ran for 12 months. If we had applied this collaborative way of working from the start, I believe we would have completed the design phase six months earlier."

Embedding the Change

We front-loaded our support deliberately, so the team could see new behaviours modelled, learn by doing, and take ownership of the process, tooling and cadence themselves.

Eight months after our coaching ended, both productivity and team health were still improving: the clearest sign the change had actually taken root, rather than depending on us to sustain it.

As Jayne Price, Transformation Director, put it: "Their support led to productivity gains, a high-performing multidisciplinary team with a culture of psychological safety. I can't recommend Noel and his team enough."

Or as Andy Vick, Disruptive Tech Lead, summed up the mission itself: "SpeQtre is the first satellite developed through our agile mission facility, and a credit to the teams who have worked hard to deliver the payload for launch."

If any of this sounds familiar in your own portfolio (brilliant people, a system that isn't quite keeping pace with them), we'd welcome the conversation. [Book a call].