What derails a transformation in a large organisation
A large organisation lacks neither project ideas nor available technologies. What it lacks is the capacity to bring these projects to completion, in an order that makes sense, with teams that are not committed on every front at once. Project and transformation management addresses this problem: it brings together the practices that make it possible to choose initiatives, govern them, coordinate those who carry them out and check that the result is used.
The difficulties look alike from one industry to another.
- Too many projects open. Each department launches its own, no one stops any. The same experts are assigned everywhere and make progress nowhere.
- Massaged information. Indicators stay green until the committee that announces the delay. Leadership discovers the problems when the options for correction have gone.
- Dependencies that no one keeps hold of. The application project waits for the platform, which waits for the data, which waits for an architecture decision. Each team keeps to its schedule, and the whole slips.
- Delivery without use. The tool is in production, acceptance has been signed off, and users carry on working as before.
None of these difficulties is technical. All of them stem from the way the organisation decides, coordinates and supports. The choice of a technology, however judicious, is therefore not enough to obtain a result.
Our reading of transformation management
Our consultants work within your teams; decisions remain yours. Four convictions guide our work in this area.
Managing means getting decisions made. Steering arrangements are judged by the decisions they bring about: launch, strengthen, redirect, stop. Arrangements that produce reports without ever asking for a trade-off are a burden, not a help. Our consultants help build governance bodies and indicators starting from the decisions to be taken, not the other way round.
Formality must be proportionate. A short, low-risk project does not justify the committee structure of a regulatory programme. Applying the same framework to all wastes small projects’ time and gives false reassurance about large ones. A useful framework provides several levels of requirement and states clearly which one applies.
Method is a means. V-model, agile approaches, PMI frameworks, PRINCE2, SAFe: each responds to a situation. The useful question is not which is superior, but which suits the project’s uncertainty, the maturity of the teams and the organisation’s constraints. A large organisation often runs several delivery modes side by side. It is this coexistence that needs to be organised.
A project ends when the value is there. Go-live is a milestone, not an end point. Expected benefits are tracked beyond delivery, with a named owner on the business side, and adoption is prepared from framing onwards.
Why an AI, data and cloud expertise firm keeps project management at the centre
Management Square has its roots in project, programme and portfolio management advisory. Our expertise today covers artificial intelligence, data, cloud and software engineering, but this original profession has not become a support function. The reason is simple: a technology only creates value if the project that carries it succeeds.
Today’s technology projects make this observation more acute. An AI use case can convince in a demonstration and never reach production, for lack of ready data, a business sponsor or a decision on risks. A migration to the cloud strings together numerous cutovers that depend on one another. A data platform is only worth as much as the teams that use it. In each case, the main difficulty is organisational: prioritising, sequencing, arbitrating, getting things adopted.
Our four-phase approach (Frame, Prove, Industrialise, Operate) reflects this conviction. Each move from one phase to the next is a management decision. Should you invest beyond the proof of concept? Is the organisation ready to industrialise? Who will operate the system once delivered? We address these questions with the tools of a traditional programme, adapted to the uncertainty specific to these technologies.
How we work: six disciplines
The area breaks down into six services. You can call on just one or combine them, depending on the difficulty that dominates in your organisation.
- When leadership lacks a reliable view of its projects, we start with setting up or strengthening a PMO: governance, routines, indicators.
- When the question is choosing between projects rather than tracking them, our consultants help establish project portfolio management: prioritisation criteria, a reading of capacity, an arbitration body.
- When a set of related projects must produce a common outcome, our consultants strengthen your programme management: trajectory, dependencies, benefits.
- When many agile teams must deliver together, our consultants help organise agile at scale: common cadence, synchronisation, value-driven management.
- When a project is a cause for concern or a commitment milestone is approaching, our consultants help you carry out a project audit: an independent view, substantiated findings, a recovery plan.
- When the result depends on what users will do with it, our consultants support change management: impacts, communication, training, measurement of adoption.
These disciplines share a precise vocabulary, which we document in our glossary: there you will find, for example, the definition of a PMO and that of PPM, project portfolio management.
Whatever the entry point, we work with your teams and not in their place. Transferring the method is part of the assignment: steering arrangements that only work when consultants are present have not been established.
The link with our other areas of expertise
Project management is not a separate area: it runs through the other four. An artificial intelligence roadmap is a portfolio of use cases. It is prioritised and arbitrated like any portfolio, with greater uncertainty about feasibility. A cloud and platforms programme is run in waves, with tight dependencies between applications, infrastructure and security. Data workstreams shift responsibilities between the business and IT: they are change projects as much as technical projects.
On a technical assignment, we therefore combine expertise in the domain with expertise in project management. The first says what is feasible and what is risky. The second keeps hold of the trajectory, the trade-offs and adoption. This combination avoids two symmetrical failings: management that ignores the technology, and technology delivered without management.
Where to start?
Three situations come up most often, and each calls for a different first step.
You do not know the real status of your projects. The first step is a diagnostic of the existing steering arrangements: governance bodies, roles, quality of the information reported. It leads to a governance foundation tested on a pilot scope.
A specific project or programme is a cause for concern. The first step is an independent review, which establishes the facts before any decision to reinforce, refocus or stop.
You are launching a large-scale transformation. The first step is framing the programme: mandate, trajectory, governance and adoption arrangements, settled before teams are mobilised.
In all three cases, an initial conversation makes it possible to clarify your situation and the level of decision to be informed. You can set it out for us via the contact page.