A Great Leading Indicator for Future Trouble - Missing Milestones

I have done quite a number of inflight reviews and post-mortems of troubled and failed large system implementation projects. 

One pattern that emerges very clearly is the one of missing milestones whilst keeping the go-live date the same. 

It rarely ends well.

I see it again and again. Multiple important milestones are missed. Sometimes by months. And the ones that are marked as completed have their original scope reduced.

For example system integration tests (SIT) without all interfaces being completed and no production like data.

Or user acceptance testing (UAT) with systems that are not ready or contain so many bugs that end-to-end testing is not possible.

Astonishing is that in most cases both the project sponsor and project manager seem to be convinced all is “green” and it will work out until the project folds like a house of cards.

When you look at a typical large system implementation project it is still largely implemented like a waterfall. This includes ERP systems, CRM systems, Core Banking, etc. 

And this has not changed with the rise of software as a service (SaaS) offerings like Salesforce, SAP S/4HANA, Workday, etc.

Yes, the design and build phases are now iterative, but at a certain point your full solution needs to be tested end-to-end. This means one or more SIT phases and an UAT phase that includes all upstream and downstream systems and processes. 

You also need time to fix all the findings of your testing, and to do re-testing. If you are lucky one cycle is enough. Usually it is not.

You also need to train all your users and your support teams on the new solution and processes. Ideally on a solution that actually works. 

And when you are ready to go, you have a cutover phase from your old solution to your new solution. 

So yes, you design and build iteratively, but the rest is still shaped like a waterfall.

And this means that if you miss important milestones and you don’t change the go-live date you will steal time from the very important phases that come at the end of such a project. 

Starting these late phases without having completed the previous phase just does not make sense and will drive your test team and end users crazy.

Missing milestones does not mean your project team is doing a bad job, but they obviously underestimated the time it takes to do certain things.

Chances are this is a pattern that is repeated for the later phases of the project. 

So you will probably need more time for these phases as planned. Not less. 

In my experience there are only two probable outcomes of such projects:

1) They never go live

2) They go live too early 

The latter can be even worse as the first. 

See here and here for some prominent examples from multi-million projects that never went live, and here and here for projects that went live too early. 

You will find many more examples among my project failure case studies.

In a nutshell: missing milestones and not changing your go-live date is a great leading indicator for trouble in the future.

Read more…

Jobs to Be Done for CxOs in the Project Economy

We all have heard about the disruptions that are impacting our society and the business world: robotics, machine learning, artificial intelligence, shared economy, blockchain, big data, augmented reality, and so on. 

But, there is one disruption affecting our world that media and academia seem to have completely missed.

The Project Economy

For decades organizations have been run and structured in a very similar way: hierarchical; in which power, budgets and resources are divided over departments, the so-called “silos”. 

Management and management theory was focused on how to run and optimize the business best in an ever during quest for efficiency. Projects were an addition, but hardly ever a priority.

Today, due to the speed of change witnessed in the past decade, this model has become more and more obsolete. 

For many organizations the day-to-day running of a business will soon be carried out through automation and robots – and is already done so in many instances. Projects have become an essential part of any organization.

My prediction is that in the upcoming years, senior leaders and executives will spend much (maybe even most) of their time selecting, prioritizing and overseeing the execution of projects.

Ultimately, projects deliver value to stakeholders by solving their challenges, delivering products and aligning projects to an organization’s value streams. If done right, these initiatives also deliver financial and/or societal value.

This phenomenon is known as “The Project Economy”.

Jobs to Be Done

Taking the above into account there are a number of jobs that a CxO (like Chief Executive Officer, Chief Operations Officer, Chief Financial Officer, Chief Technology Officer, Chief Information Officer, etc.) will need to be able to do well when leading organizations in this project economy. 

Below you will find the (in my humble opinion) ten most critical jobs to be done for CxOs. 

1) Being an effective Project Sponsor.

2) Being an effective Steering Committee member.

3) Selecting the right Project / Program Manager for your initiatives.

4) Implementing change.

5) Executing a strategy with projects.

6) Selecting the right projects.

7) Prioritizing projects.

8) Killing a project.

9) Reviewing a project.

10) Recovering a project.

In a nutshell: In the upcoming years, senior leaders and executives will spend much (maybe even most) of their time selecting, prioritizing and overseeing the execution of projects.

Read more…

Can a Task Force Rescue Your Failing Project?

We’ve all witnessed projects in trouble—the ones that required a quick and firm intervention in need of help from a task force to bring it back on track.

No executive wants to be in such a difficult situation, especially not with one of his or her own projects.

But how do we, as the executive sponsor, handle saving a troubled project? Can it be as simple as mandating a task force?

Let’s start with exploring what a project task force is and when it could be useful. 

A project task force starts with a mandate given by the organization’s project sponsor or senior leadership to an experienced leader with the goal of finding the best option for resolving a particular problem in a very short amount of time.

A task force team is a small group, usually four to twelve people, that brings together a specific set of skills and experience related to the problem at hand.

A task force is a useful management mechanism that should be only used in exceptional situations. It generally requires disrupting other project activities and deploying the best people to solve the problem under possibly highly stressful and energy-depleting conditions.

So how do you handle this? 

I have been part of several task forces and have led a few as well. I have had both good and bad experiences. In order for task forces to be effective, you will need:

A Clear Mandate: It needs to be communicated to all stakeholders that the project is in task force mode, as well as who is leading the task force (see next point). You will need your stakeholder’s help in receiving quick turnaround times on information requests and decisions. You will need the best people in your organization for your task force team, so people need to understand it is urgent and important. 

An Experienced Leader: It can either be a senior project manager or a leader experienced with crises situations. Single leadership is the key to getting the job done! The last thing you would want is having two or more leaders debating how to drive the task force; one person has to call the shots.

An Expert Team: The task force leader will need to quickly assemble an expert team, formed with the best people who have the required field expertise to quickly understand and resolve the problem. The smaller the team, the easier it is for the task force leader to motivate and steer the team towards finding the right solution.

Laser Focus: The particular problem the task force is working on has to be clearly defined and known to the entire task force team. The objectives they will be working on also have to be clear to everyone involved. Several other project issues may come up along the way, thus, to be effective, the task force must remain focused on the specific problem.

Executive Support: At times, the reason a task force is needed in the first place is due to internal politics and resistance to change. One of the worst things that can happen to a task force is that they have no backing from their leadership to cut through this. 

Expectation Management: Many times, a task force can improve the status quo significantly, but you should not expect miracles. Further, you should strive to not communicate your desire for miracles upfront. Make clear to everybody that the goal of the task force is to find the best possible solution under the given circumstances.

A Short Time-Frame: Given the urgency and the high level of the task force team’s energy, they are only effective if conducted in a short time frame (a matter of days, or a few weeks). If efforts go on for longer, it is likely not a task force, as the energy and effectiveness will lower over time.

Simple Logistics: Due to the intensity and possible stressfulness of the situation, task forces require an isolated project space—or war room. This space needs whiteboards to facilitate brainstorming and for capturing the results of the task force (notes, action items, assumptions, decisions, solutions, etc.). Yes, we all learned during COVID-19 to cope with this remotely, and yes, for international teams, it is not always feasible either. But trust me, in a time of crisis, it really works better this way.

Solution Options: The task force’s outcome should include one or more options that lead to a solution to the problem, including a recommendation for the best option. This option, even if it is technically the best that the expert team can recommend, might not satisfy the risk appetite of the person or organization that has mandated the task force. Therefore, every option should also provide the related pros and cons.

Qualified Assumptions: Beware of unqualified assumptions. If the identified options are building upon assumptions that are not fully validated, highlight the risks or needs for confirmation before making a final decision.

A Clear Ending: To end the task force, its leader and the expert team will have to reduce the complexity and summarize the outcome of their work (options with pros and cons, along with assumptions and their risks or opportunities). Ultimately, the task force leader will communicate the outcome, confirm the decided solution, and conclude the mandate of the task force.

If set up and executed properly, a task force can be an effective tool to resolve crises situations in projects. 

Typically, these situations occur relatively late in the project when nothing else has worked. Interestingly, they usually work relatively well, as they are given the highest priority. 

Due to their ability to solve such issues, task force leaders are often celebrated as heroes. 

But task force teams work only at the expense of all other projects! All other projects endure even more pressure and are good candidates for further task force teams. Thus, they should be deployed wisely.

In a nutshell: A task force can be an effective tool to rescue failing projects if set up and executed properly.

Read more…

How a Transformation Office Can Help Your Transformation Initiatives Succeed

A new year has just started, but also in 2021 companies will be talking about digital transformation often. I think digital transformation is a terrible description for what is just another transformation. See my article “Digital Strategy Does Not Exist” on why that is. 

But we shall use the term for a moment to analyze the situation. Digital transformation is nothing new. It is a daily reality for all companies. Some are the disruptors and others are disrupted. And Covid made this even more clear. 

All understand that digital transformation—not evolution—is required to maintain a competitive edge. That is why so many digital transformation initiatives have been started around the world. 

But it seems that 70 percent of all digital transformation initiatives do not reach their goals. In 2018, of the $1.3 trillion that was spent on digital transformations, an estimated $900 billion went to waste. [1] 

Companies need to shift their approach to ensuring they reap business value and desired business outcomes from digital transformation initiatives. Across industries, most organizations are using standardized project management practices such as a traditional Project Management Office (PMO).

But digital transformation requires much more than status-tracking and risk escalation—it requires a robust capability that drives execution with a value-realization focus: A Transformation Office. 

This is not just semantics, not just a lift-and-shift, not just a glorified PMO. It is a truly different undertaking to ensure digital transformations deliver on their promise. 

And the same is valid for any other critical transformation initiatives your organization is planning. Not just digital transformations.

Transformation can take many shapes, from transforming business models to cater to a shared economy to transforming the way that critical services are delivered to clients. 

The Transformation Office

A Transformation Office enables organisations to manage multiple program and project management initiatives towards one common goal. It is more than a PMO with a fancy name – it’s about bringing strategy to life.

The Transformation Office is responsible for driving complex initiatives on both operational structures and the strategy of the organisation. It is a critical link between the executive vision and the work of the organization. 

Some companies call this function a Strategic Implementation Office, while Gartner refers to this as a Strategy Realisation Office. 

Regardless of the name, one element that sets a Transformation Office apart from most PMOs is that the C-suite proactively supports the Transformation Office’s mandate to transform the organisation entirely, which ensures it has the highest priority when implementing and affecting change.

They will be the strategic architect working with the CEO to integrate and drive and choreograph a transformation agenda. They will have to play the integrator function as well because often if you are driving customer agendas on one part of the organization, cutting costs in another part, going after a digital agenda in a third, all of those will be interrelated, and there will be interdependencies that someone will need to play air traffic controller for.

Core Competencies

The most effective Transformation Offices will house several core competencies necessary for successful transformation, including:

Enterprise Architecture to define an updated or even an entirely new structure for the organisation with which transformation activity can be planned around and clearly communicated to everyone involved. This includes Design Assurance to safeguard its integrity across projects and alignment with the vision set out in the business architecture. This critical role aligns IT and other support functions behind the business design.

Project Portfolio Management including prioritization to ensure investment flows to the highest value initiatives and that the investment method is transparent and collaborative.

Project Management to track, govern and manage the transformation whilst reporting progress.

Change Management to ensure users and other stakeholders adopt the changes that the transformation brings. 

Benefit Realization Management to ensure execution delivers the intended benefits and outcomes, by continually monitoring progress and adjusting to keep the delivery on course.

The Transformation Office not only sets the schedule and the tone of the transformation, but it also keeps score, with consistent ways of measuring and tracking business value. It ensures everyone has access to the same simple rulebook and is trained to understand its unambiguous processes and policies. 

The Transformation Office is a coach to help the organization grow and get better with the responsibility of ensuring that efforts are not stifled by old-fashioned bureaucracy that the company might have become accustomed to.

Single Source of Truth

Any organization undergoing a transformation will have a pipeline of improvements, subdivided into actions, owners, and dollars at stake. An important role of the Transformation Office is to ensure that all participants have a “single source of truth.” A transparent view of what flows through the pipeline and a central record of the progress of each initiative owner.

Tracking and approving initiatives can be done through a structured stage-gate process that goes from initial identification to final realization.

Armed with the truth, the Transformation Office has the credibility to spot potential conflicts or overlaps among work streams, raise the issues with stakeholders in its regular meetings, and work with owners and executives to achieve the best outcome for the business. 

Without this sort of planning and intervention by the Transformation Office to remove bottlenecks, one or two project teams can cost an organization millions of dollars.

Parallel Organization

The Transformation Office exists in addition to the line organization. Now why is that? 

Most organizations rightfully say, "We prefer that the line should just implement the change. The line organization needs to own and embrace the change."

And that's an understandable and very aspirational ambition that you should have for a well-run company. But the reality is that while in a transformation phase the line organization will need to change as well. 

The operating model, the kind of executives you had, the skills in the organization that made them successful in the past may not be the same as what you will need to have in the future. 

And so, as you are transforming the line organization, you will need this kind of office to create a bridge until the newly transformed line organization—the redesigned and transformed organization of the future—can actually inherit the initiatives and operate them smoothly.

In a nutshell: A well-executed Transformation Office can improve your transformation across four areas: value, design, execution and business adoption. Think of the Transformation Office as a risk mitigation insurance policy on your most critical transformation initiatives.

References

[1] Harvard Business Review, "Digital Transformation Is Not About Technology", March 13, 2019

Read more…