Change Management & Leadership


I've never met a Project Management Office (PMO) I like. There – I said it.
Too often, they inhabit a world of meticulous nomenclature and endless reporting requests, adding to a project team's burden rather than lifting it. They become a bureaucratic layer, inadvertently slowing down the very delivery they're meant to facilitate. When was the last time a PMO clearly articulated its own quantified value to the organisation?
The path to redemption for PMOs is clear: become problem-solvers and value-drivers. Instead of demanding status updates, offer solutions that genuinely accelerate delivery. This means providing shared tools that simplify reporting, proactively identifying and mediating cross-project conflicts, and porting across best practices between teams that properly empower them. By shifting their focus from policing to enabling, and demonstrating their impact in concrete terms – like reduced project costs or faster delivery – PMOs can become partners rather than perceived obstacles.
So, PMOs, if you’re listening, here is your challenge: streamline, coordinate, share best practices, demonstrate your worth … and ensure you minimise overhead rather than adding to it

Although tangled and messy, the Redback Spider’s web functions in three dimensions rather than the two dimensions of the typical spider web.
Does your organisation’s or division’s strategy operate in two dimensions, or three? Are there mutually reinforcing facets: think of the way Walt Disney’s TV appearances in the 1950s fed awareness of and interest in the newly built Disneyland, which in turn prolonged and reinforced Disney characters and films. Or do they only operate only on a single plane? Are your operational and risk management systems multi-faceted enough to function three-dimensionally or are they merely ‘flat-file’?
Next time you see a spider web, let it prompt you (as you're reaching for the pest spray) to think about the depth and breadth of your strategy.

I’ve had clients ask me how to transmit a vision through the organisation: how do you establish a clear line of sight from high-level mission through to implementation and execution?
The truth is: there is no secret to this, no arcane management methodology is required. There is only:
- collaborative clarity
- a structure by which to hold people accountable for results and timeframes, and
- relentless follow-up.
That’s pretty much it.

Here are my top four change management tips, culled from the literature and validated by years of work in the field:
- Focus on real business problems (reducing operating costs, improving customer response times) rather than abstractions (‘participation’)
- The single biggest cause of failure of any change effort is absence of senior management support
- People support what they help to create
- People don’t resist change; they resist ambiguity

Need to garner support for a corporate initiative? Here are my top three tips on how to do it.
- Crystallise the benefits of your initiative for the major players: the key here is to make the benefits *tangible* (as distinct from *large*)
- Meet the players face-to-face: get in front of them and give them a chance to have their say (and outline the benefits for them – see point above). There’s something compelling about being face-to-face with people which is not as strong with other forms of communication
- Create a bandwagon that has such momentum that it’s a no-brainer that people would get behind it. Senior leaders have to bang the drum for an initiative loudly and constantly, publicising exemplars and providing plaudits for early followers: be loud and proud.

The first type of change metric is for the change effort itself; typical metrics here include:
- frequency of communication
- percentage of business units with change champions embedded
- actual versus scheduled timeline for change project.
The second is for business-as-usual KPIs which reflect a demonstrable difference in results as a result of the change effort. Examples might include:
- unit costs
- customer satisfaction
- defect rates.
The two types are shown in the graphic, using a change effort aimed at reducing average costs as an example.

