agilemindsv2

Jaguar Land Rover: An Agile Framework Built to Last

Mon, 01 Jun 2026 10:43:30 GMT

The Context

Digital customer journeys, electric vehicles, autonomous driving, connected cars. The complexity facing automotive manufacturers had multiplied. Government legislation and shifting public sentiment around fossil fuels added more variables. The industry’s environment was now unpredictable in a way it had not been before.

JLR recognised this. The business needed to be more flexible and bring solutions to market faster. Not just vehicles, but the systems, factories, and digital products that surround them.

The Challenge

Most agile transformations fail because they start with the framework and end with a PowerPoint deck. Teams are trained, posters go up, and six months later the organisation is delivering exactly as it did before.

JLR did not want that. They wanted agile that actually changed how work got done. Which meant starting with a real product, not a workshop.

What We Did

We identified a real pain point: dealer reserved stock. A dealer could reserve a vehicle, but if it did not sell it sat on the forecourt and lost value over time. We built an iOS application in sixteen weeks that let dealerships across the country search and reserve stock from one another.

That was the vehicle for the framework. While building the app, we developed JLR’s agile delivery framework. We worked through the implications for governance processes, internal standards, and how remote teams should be managed. We defined the role of the product owner, built the digital backlog, and worked out how applications were released into live.

Then we established agile guilds to own the framework, refine it, and make sure it was adopted across the organisation.

The Result

JLR had a working agile framework, proven on a real product, with internal guilds in place to keep refining it after we left.

That is the test of any framework: does it survive the consultants going home? In this case, it did. Because it had been built around real delivery, not a theoretical model.

What Made the Difference

We built the framework through a real product, not in a workshop. Teams learned agile by delivering, not by listening.

We established agile guilds inside the organisation, so the practice had owners after we left.

We adapted the framework to JLR’s reality, including governance, remote teams, and release processes. Not a generic model. A working one.

Services Utilised

Agile Framework Design
Agile Coaching
Product Owner Establishment
iOS Application Delivery
Agile Guild Setup
Governance Redesign

If your agile transformation has produced training certificates but not faster delivery, the framework was never the answer. The work is what teaches teams to work differently.

Free Project Assessment & Audit, Tailored to You

Think something might be off? Not sure where your project really stands? We come in, assess what's happening, and give you a clear and honest picture at no cost. Every engagement starts with understanding your specific situation, because no two organisations are the same.

Totally free. No commitment needed.

Halfords: One Digital Front Door for Two Brands

Mon, 01 Jun 2026 05:27:55 GMT

The Context

E.ON is one of the Big Six UK energy suppliers and part of the global E.ON group. The team had developed a proof of concept for a virtual power station: a network of commercial energy consumers whose demand could be scheduled to off-peak times. Lower bills for the customer. Predictable demand for the grid.

The business case was proven. What they needed next was an MVP that could move into pilot quickly, before the commercial window closed.

The Challenge

A traditional build would have taken too long. Sequential requirements, design, build, and test would miss the market. The team needed pace and rigour at the same time, with business, IT, academic, and manufacturing partners all in the same room.

What We Did

AgileMinds led the move from POC to MVP and embedded the agile practices that would carry the product into pilot.

We assembled a single co-located team across business, IT, and external partners. We confirmed the Product Owner, ran workshops to collate requirements, refined the features into prioritised user stories, and built an MVP definition the board could fund. Agile coaching, sprint planning, and team facilitation happened inside the work, not before it.

The Result

The MVP was approved, funded for pilot, and rolled out across UK sites. The product was commercialised through E.ON in Sweden, and the cross-functional team won the RITA RealIT Award for IT innovation.

The solution is now actively used across E.ON’s network. That is the truest test of any MVP: does the work survive contact with the market? In this case, it did.

What Made the Difference

A single co-located team that collapsed the distance between business, technology, and partners. Decisions were made in hours, not weeks.

Requirements built through workshops and user stories, not hundred-page documents.

Agile practice was embedded inside the work, so it stuck after we left.

Services Utilised

Project Management
Agile Coaching
Sprint Planning
Agile Training
Team Facilitation
Rapid Prototype Development

If you have a proven concept that needs to become a commercial product, the next three months will determine whether it lands or stalls. The first conversation is always free.

Book a Free MVP Acceleration Conversation.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.

E.ON: Building the Virtual Power Station

Fri, 29 May 2026 15:24:40 GMT

The Context

The business case was proven. What they needed next was an MVP that could move into pilot quickly, before the commercial window closed.

The Challenge

What We Did

AgileMinds led the move from POC to MVP and embedded the agile practices that would carry the product into pilot.

The Result

The solution is now actively used across E.ON’s network. That is the truest test of any MVP: does the work survive contact with the market? In this case, it did.

What Made the Difference

A single co-located team that collapsed the distance between business, technology, and partners. Decisions were made in hours, not weeks.

Requirements built through workshops and user stories, not hundred-page documents.

Agile practice was embedded inside the work, so it stuck after we left.

Services Utilised

Project Management
Agile Coaching
Sprint Planning
Agile Training
Team Facilitation
Rapid Prototype Development

If you have a proven concept that needs to become a commercial product, the next three months will determine whether it lands or stalls. The first conversation is always free.

Book a Free MVP Acceleration Conversation.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.

The Hidden Cost of Project Team Burnout (And Why It’s Worse Than Missed Deadlines)

Sun, 24 May 2026 16:38:11 GMT

When a project slips, the cost is visible. A delayed launch. A revised forecast. A frank conversation at the steering committee.

When a project team burns out, the cost is invisible. Until your best project manager hands in her notice three weeks after go-live and takes seven years of institutional knowledge with her. Gallup research has found that burned-out employees are 2.6 times more likely to actively seek another job, and that burnout is a leading driver of voluntary turnover in knowledge work.

The slipped deadline can be recovered. The departed practitioner cannot.

The Three Hidden Costs Most Leaders Underestimate

1. Loss of institutional knowledge

Senior practitioners carry context that isn’t written down. They know which supplier consistently misses estimates. They know which sponsor needs a draft a week before the meeting. They know which workstream is technically green but politically fragile.

None of that is in the project handover document. When a burnt-out senior leaves, that knowledge leaves with them. Their replacement spends six months learning what their predecessor already knew, and the next project pays the cost.

2. Cascading attrition

Burnout doesn’t happen in isolation. The first person to leave is rarely the most burnt out. They’re often the most marketable. Their departure increases the load on those still there, accelerates the burnout of the next tier, and triggers the next resignation.

By the time leadership notices a pattern, three or four resignations are already in motion. Replacing them takes nine months at mid-market salaries. Onboarding them to the same level of context takes longer than that.

3. Quality erosion before the resignation

Long before a burnt-out senior leaves, their work changes. Reviews get lighter. Risks get under-flagged. Status reports get more optimistic. They’re not gaming the system. They’re running on fumes. Harvard Business Review’s research on burnout makes the point clearly: burnout is a workplace problem, not a personal one, and the warning signs show in the work long before they show in the person.

That quality erosion is the most expensive cost of all, because it gets baked into projects that won’t fail until six months from now.

Why Mid-Market Project Teams Burn Out Faster

Large enterprises have depth. Bench resources. Specialist teams. A bad month for one project manager doesn’t collapse the portfolio.

Mid-market organisations don’t. The same five people are running fifteen projects. Each of them is the only person who really understands their workstream. None of them can take a fortnight off without something slipping. There is no margin in the system.

Add a transformation programme on top of that, and the maths stops working. The same five people are now running fifteen projects plus their part of the transformation, and being told it’s a great career opportunity.

It is not. It is the precondition for institutional knowledge walking out the door.

Four Things That Actually Reduce Burnout

1. Bring in experienced reinforcement, not graduate support

A junior PM added to an overstretched team adds load. They need supervision, context, and review. A senior practitioner added to the same team removes load. They can take a workstream off the senior who was carrying it, and the team can breathe again.

The instinct to “add capacity cheaply” is the most expensive form of false economy in project resourcing.

2. Cut the portfolio before you cut the people

If your team is running fifteen projects and burning out, the answer is not better time management. It is fewer projects. A portfolio review that ends with three projects deferred and two killed will do more for retention than any wellbeing programme.

3. Protect senior time

Your most experienced practitioners should not be filling in status reports, chasing inputs, or facilitating governance forums that should run themselves. That work needs to be done, but by someone else. Free up the seniors to do what only they can do.

4. Notice the early signs

The first sign of burnout is rarely tears or resignation. It is a quietly missed review. A risk that didn’t get raised. A meeting that didn’t get the usual challenge. Train yourselves and your sponsors to notice the drop in sharpness, because that is the leading indicator. By the time someone tells you they’re burnt out, you are already months behind.

The Real Maths of Burnout

Replacing a senior project manager in the UK mid-market costs between six and nine months of their salary in recruitment, lost productivity, and onboarding time. Replacing the knowledge they carried costs significantly more, and is rarely recovered.

Reinforcement, by contrast, is a fraction of that cost, and it is preventative rather than reactive. The question is not whether you can afford to bring in experienced help. It is whether you can afford the resignation that will follow if you don’t.

If your project team is running on the goodwill of three or four people, that goodwill has a shelf life. The first conversation is always free.

Book a Free Resource Health Check. No fee. No obligation.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.

How to Recover a Failing Project Before It’s Too Late (And the Warning Signs Most Boards Miss)

paul@agileminds.co.uk (Paul Thomas) — Mon, 04 May 2026 17:34:22 GMT

Failing projects don’t announce themselves. By the time a board paper flags red, the slippage has been building for months. Sometimes longer. The team knows. The PMO knows. The project manager has been quietly working weekends to stop the wheels coming off.

The board is the last to find out. And by the time they do, the recovery options have already started narrowing.

After 23 years of being called in when projects must not fail, the pattern is always the same. The warning signs were there. They were just being explained away.

Why Most Recovery Efforts Start Too Late

There is a window of roughly the first 90 days of drift, when a failing project can still be recovered with the team in place, the budget largely intact, and the scope mostly preserved. Outside that window, recovery means something harder. Re-baselining. Re-scoping. Hard conversations with the steering committee about what the programme will actually deliver.

The cost of inaction compounds quickly. A project that slips by three weeks in month one slips by three months by month four. Burnout sets in. Your strongest people start updating their CVs. Suppliers start hedging their commitments. The longer the drift, the fewer levers you have left to pull.

Most boards don’t intervene because the warning signs look like normal project noise. They’re not. They’re a pattern.

Seven Warning Signs Your Project Is Failing

These are the signals we see, in this order, almost every time we’re called in for a rescue.

1. Status reports stop telling you anything new

The RAG status has been amber for six weeks. The narrative is identical week-on-week. The risks list hasn’t been updated. When a status report becomes a ritual rather than a tool, the project has stopped self-correcting.

2. Milestones quietly move

Not once. Repeatedly. A delivery date slips from June to July, then July to September, with no formal change control. The team has stopped believing the plan, so they’re managing to a private timeline rather than the published one.

3. Your best people are working the hardest

Two or three names appear in every escalation. They’re in every workshop. They’re fixing other people’s deliverables in the evening. When delivery depends on heroics from a small group, you don’t have a project. You have a temporary arrangement that will collapse the moment one of them leaves.

4. The PMO has stopped pushing back

A healthy PMO challenges plans, flags risks, and refuses to accept poor-quality status updates. When the PMO is reduced to chasing inputs and producing decks, governance has quietly broken down. The board is now reading a summary of a summary.

5. Suppliers and partners are going quiet

Slower response times. Vague commitments. A reluctance to commit to dates in writing. Suppliers know when a programme is wobbling, often before the client does, and they protect themselves accordingly.

6. Decisions take three meetings

Issues that should take a day to resolve are bouncing between forums. Nobody is empowered, or nobody wants to own the call. Decision latency is the cleanest leading indicator of programme failure we know of.

7. The benefits case has gone quiet

Nobody is talking about the outcome any more. Conversations are about scope, dates, and budget. The inputs. When the team stops referencing why the project exists, the project has lost its anchor.

How to Recover a Failing Project: The First 30 Days

Recovery doesn’t start with a new Gantt chart. It starts with telling the truth.

Week 1: Stop and assess

Pause non-critical workstreams. Run a structured health check covering scope, plan, resourcing, governance, supplier performance, and benefits alignment. Talk to the practitioners, not just the leads. They’ll tell you where the project actually is. Produce one document, no more than ten pages, that names the gap between where the project is and where the board thinks it is.

Week 2: Re-baseline honestly

Strip the plan back to what can credibly be delivered with the team you have. If scope needs to come out, name it. If budget needs to grow, say so. If the original benefits case can no longer be met, raise it now, not in six months. A re-baselined plan that the team believes in is worth more than an aspirational plan that nobody trusts.

Week 3: Fix governance

Tighten the decision-making loop. Reduce the number of forums. Empower a single accountable owner for each workstream. Set a cadence the board can rely on, with status reports that show movement rather than narrative.

Week 4: Stabilise the team

Identify the two or three people the project cannot afford to lose. Take pressure off them. Bring in experienced reinforcement where the gaps are real. Make it visible to the team that the project is being run differently from now on. That visibility is what restores momentum.

When to Recover, and When to Stop

Not every failing project should be saved. Some have lost their business case. Some have technology choices that can’t be unwound at an acceptable cost. Some have lost the trust of the sponsor permanently.

An honest recovery assessment names both options on the table. Recover, or wind down with dignity. It gives the steering committee the evidence to choose. The worst outcome is a project that limps for another twelve months before being quietly cancelled. The cost of that drift is almost always greater than the cost of stopping now.

What Changes When the Right Help Arrives

Three months in. The plan is credible. The team is steady. Suppliers are responding again. The board paper tells the truth, and the truth is improving week by week.

That is what recovery looks like. Not a hero project manager riding in to save the day. A small, experienced team embedded alongside yours, working the plan, restoring confidence, and finishing what others started.

Your project may not be failing yet. But if three or more of the warning signs above are familiar, the next ninety days will determine whether it can still be recovered. The first conversation is always free.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.

Why PMOs Fail: The Five Reasons Mid-Market PMOs Get Shut Down in Year Two

paul@agileminds.co.uk (Paul Thomas) — Mon, 04 May 2026 17:34:22 GMT

More than half of PMOs set up in mid-market organisations are quietly disbanded, restructured, or absorbed into another function within two years. Academic research published through the Association for Project Management has tracked this pattern for over a decade: PMOs are often short-lived, and their value is difficult to evidence.

Not because the discipline of project management is broken. Because the PMO was set up to fix the wrong problem, with the wrong remit, reporting to the wrong person.

After 23 years of being called in to either rescue a PMO or replace one, we see the same five reasons it goes wrong. None of them are technical. All of them are solvable.

Reason 1: It Was Set Up to Solve the Wrong Problem

The most common origin story for a failing PMO is this. A high-profile project failed, a board asked why, and someone said “we need a PMO”.

That is the wrong answer to the wrong question. A PMO is not a fix for one bad project. It is a permanent capability for governing many projects. If you build one in reaction to a single failure, you build it to perform the autopsy, not to prevent the next one.

The PMOs that survive year two are the ones that were set up with a clear charter: which projects they govern, what decisions they own, and what outcomes they are accountable for. The APM Body of Knowledge sets out three core benefits a PMO must deliver: deployment support, process improvement, and resource flexibility. If your PMO charter doesn’t name those outcomes, it doesn’t have one.

Reason 2: It Was Staffed Too Junior

If the executive view of a PMO is that it produces reports, then it will be staffed by people whose job is to produce reports. Those people cannot challenge experienced project managers. They cannot validate the inputs they receive. They cannot tell the board what the real risk picture looks like.

The PMO becomes a copy-and-paste function. Its outputs are no better than its inputs. And when the outputs are poor, the executive concludes the PMO is not adding value. That conclusion compounds the problem, because nobody is going to invest in a function that has already been written off.

A mid-market PMO needs at least one senior practitioner who has actually delivered programmes. Without that, the function cannot do the one thing it exists to do: ask harder questions than the project managers it governs.

Reason 3: It Has No Real Authority

PMOs are often launched with a polite mandate. They can request information. They can recommend standards. They can produce reports. What they cannot do is stop a project, escalate over a sponsor’s head, or force a change in resourcing.

Without authority, the PMO has no leverage. Project managers learn quickly which reports they need to fill in and which they can ignore. The PMO becomes administrative theatre. Visible, expensive, and unable to change anything.

The fix is not bureaucratic. It is governance design. The PMO needs a sponsor at executive level, a defined remit, and a small number of decisions it owns outright. Once those decisions are real, the rest of the function gains traction.

Reason 4: It Measured the Wrong Things

Many PMOs report on activity. Number of projects in the portfolio. Percentage of templates completed. Hours logged against governance forums. None of these tell you whether the portfolio is healthy.

A useful PMO reports on outcomes. Are the projects delivering the benefits they were funded to deliver? Are the dates being held? Are resources being used where they create the most value? Those are the metrics a board cares about. Anything else is noise dressed up as rigour.

If your PMO dashboard can’t answer a single board-level question without footnotes, it is measuring the wrong things.

Reason 5: It Couldn’t Adapt

Mid-market organisations grow, restructure, and pivot. The APM Golden Thread research (commissioned by APM and conducted by PwC Research) shows the project profession now contributes £186.8 billion annually to the UK economy, a 19% increase in five years. The pace of change is real. A PMO built rigidly around one methodology, typically the one its first head championed, will struggle to keep up.

New projects arrive that don’t fit the template. Teams find workarounds. The PMO becomes a gatekeeper to a process that no longer reflects how the business actually works.

The PMOs that survive are the ones that flex. They have a core of non-negotiables: governance, reporting, risk. Around that core, they keep a wider layer of practice that adapts to the type of project being delivered. Waterfall where it fits. Agile where it fits. Hybrid where it has to.

What a PMO That Works Actually Looks Like

It has a clear charter, written and signed off by an executive sponsor.

It is staffed with at least one senior practitioner with real delivery scars.

It owns specific decisions, not just the production of decks.

It reports on outcomes the board cares about, not on activity it can measure.

It flexes with the business, instead of fighting it.

Building that takes three to six months of focused work, not a software rollout.

If your PMO is approaching its second birthday and the board has started asking what it’s for, that conversation is the warning sign. There is still time to reset it before the function is dismantled.

Book a Free PMO Assessment. No fee. No obligation.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.

Why Digital Transformation Fails: It’s Not the Technology, It’s the Middle Management

paul@agileminds.co.uk (Paul Thomas) — Mon, 04 May 2026 17:34:22 GMT

Boards approve digital transformations. IT delivers them. Consultancies design them. So why does McKinsey research consistently show that around 70 per cent of large-scale transformation efforts fail to meet their original objectives?

Not because the technology was wrong. The platforms are mature. The integrators are competent. The business cases were defensible at the point of approval.

Digital transformations fail in the middle layer of an organisation. The heads of function, the operational leads, the team managers. The people who are expected to absorb the change while still hitting last year’s targets. That layer rarely gets the support to do both.

The Top Floor Decides. The Shop Floor Adapts. The Middle Carries the Cost.

Look at how most transformations are structured. A board sponsor sets the vision. A programme team designs the future state. IT builds the platform. Training is rolled out to end users.

Now look at where the friction lands. The head of operations is being asked to learn the new system, retrain her team, hit quarterly numbers on the old system while the new one rolls out, and represent the change positively to her people. None of which she was resourced for.

She is not resisting. She is overwhelmed. And when overwhelmed middle management quietly de-prioritises the transformation in favour of the day job, adoption stalls. Without adoption, the benefits case collapses. McKinsey’s own transformation practice names a lack of engagement across the organisation as one of the most consistent reasons transformations underperform.

Three Reasons the Middle Layer Gets Left Behind

1. The transformation is treated as a technology programme

If the project plan reads like a system implementation, with phases for design, build, test, go-live, and hypercare, there is no workstream that owns the human change. The assumption is that training plus communications equals adoption. It doesn’t.

Real adoption requires people to change how they do their work. That requires time, support, and permission to slow down temporarily. None of which appear on a typical implementation plan.

2. The middle layer wasn’t involved in design

Programmes that go straight from board sponsor to technical design skip the layer that knows how the work actually gets done. The resulting solution is theoretically correct and operationally awkward. The people being asked to use it can see the friction immediately, and they were never consulted about it.

Once that gap is visible, trust in the transformation drops. Workarounds appear. Shadow processes emerge. The shiny new platform is technically live and operationally bypassed.

3. There is no slack in the system

Mid-market organisations run lean. The same managers who own the day-to-day are the ones being asked to own the change. There is no spare capacity to absorb the cost of transition. So either the day job gives, or the change gives, and the day job almost always wins, because that’s what their compensation is tied to.

If the programme didn’t plan for backfill, secondments, or temporary reinforcement at the operational layer, it didn’t plan for adoption.

How to Land Digital Transformation in the Middle

Treat adoption as a workstream, not an afterthought

Give it a senior owner. Give it a budget. Give it a plan that runs alongside the technical build, not after it. Adoption isn’t something you sprinkle on at go-live. It is built into the programme from week one.

Involve middle management in design, not just delivery

The people who run the operation should help shape the operation’s future. Not in a token workshop. In the design decisions that affect their daily work. The cost of involving them is a few weeks of their time. The cost of not is two years of slow adoption.

Resource the transition honestly

If the change is large enough to need a programme, it is large enough to need temporary capacity at the operational layer. Interim project managers, secondments, backfill: whatever it takes to give middle management room to lead the change rather than survive it.

Measure adoption, not implementation

Going live is a milestone, not an outcome. The real measure of transformation is whether the new way of working has displaced the old one twelve months after go-live. If it hasn’t, the platform may be running, but the transformation hasn’t happened.

The Pattern We See Most Often

Halfway through a transformation, the programme is technically on track. The platform is being built. The board reports are green. But there are quiet signals from the operation. Questions that aren’t getting answered. Training dates being pushed. Change champions going silent. The middle layer is starting to disengage.

That is the moment to intervene. Not at go-live. Not in hypercare. Now. The cost of fixing adoption mid-programme is a fraction of the cost of fixing it after launch, when habits have set and the platform has already missed its first benefits milestone.

If your digital transformation is technically on track but operationally quiet, that quiet is the warning sign. We help mid-market organisations land transformation where it has to land: in the layer that has to live with it.

Free Project Assessment & Audit, Tailored to You

Totally free. No commitment needed.