Reinvention Implementation

Reinvention is not a project

The Last Word: Projects end. The ability to reinvent must not

Andrew WrobelNovember 8, 20263 min read
Dreamstime

‘If we want to reinvent something, shouldn’t we invent it first?’ That was the question put to me during a fireside chat at a Catalyse Kenya event a few weeks ago. It was a fair challenge, and a revealing one. Behind it sat an assumption I encounter often: that reinvention is a project, a piece of work we undertake after the original act of invention. First we build something. Later, when circumstances demand it, we reinvent it.

But an organisation does not have to reach a certain age before it needs the capacity to rethink itself. Even a new enterprise makes choices about customers, people, technology, and how decisions get made. Those choices create habits and some of them become strengths; others become constraints. The skill is knowing when to preserve them and when to think again.

This is why I see reinvention less as an event than as a capability. For an individual, it is the ability to question assumptions, learn something unfamiliar and act without waiting for certainty. For an institution, it is the ability to recognise change, make consequential decisions, and renew its ways of working before a crisis forces the issue.

The distinction is important because organisations love projects. Projects come with sponsors, budgets, milestones, and completion dates. They make uncertainty look manageable. We can announce a reinvention programme, appoint a team, track the deliverables, and celebrate a launch. What happens afterwards is harder to put on a dashboard.

None of this is an argument against projects. A new service, operating model or business proposition often needs a disciplined programme to become real but producing a different outcome once is not the same as acquiring the ability to produce different outcomes repeatedly. The first can be purchased from outside while the second must take root inside.

Kirsty Lamb, writing for the Association for Project Management, describes the gap between delivery and adoption. A project can finish on time and within budget, yet fail because people continue using old workarounds. The new system exists; the old behaviour survives. Her point is that implementation alone does not create value. What people actually do afterwards matters more.

I would take this argument a step further. Even when a project is adopted and delivers its promised benefit, questions remain: Is the institution any better at responding to the next change? Can it challenge an assumption without commissioning another grand review? Can it move resources without months of negotiation? Has it learnt how to learn?

There is a danger in presenting reinvention as perpetual disruption.

We can see the same confusion in the language of corporate reinvention. Some organisations announce a reinvention as though it were a product launch. Others encourage everyone to think of themselves as reinventors. The ambition is understandable. Yet a label does not confer a skill, and a programme does not by itself establish a capability. Neither can replace the everyday practice of noticing, questioning, experimenting and deciding.

The World Economic Forum’s Future of Jobs Report 2023 offered a useful perspective. Alongside analytical and creative thinking, it identified resilience, flexibility, agility, curiosity and lifelong learning among the important capabilities for a changing workplace. Reinvention was not a separate item on that list. I would argue it is the practice that helps connect them: not just coping with change, but actively reshaping what one can do.

There is a danger, of course, in presenting reinvention as perpetual disruption. People need continuity, and institutions need a memory. Good reinvention is not a demand to abandon everything that came before. It is the judgement to recognise which parts of the past still serve the future, and the courage to change those that no longer do.

I keep returning to the question from Kenya because it captures a genuine instinct. Surely we must create something before we can remake it? Of course. But the ability to reinvent should not arrive as an emergency measure once that creation starts to falter. It should be developed as we build, run and grow it.

A project can give an organisation something new. The skill of reinvention gives it a way to remain relevant when even that new thing becomes old.

Andrew Wrobel

Andrew Wrobel is chief reinvention officer at Reinvantage.