
There’s one thing I’d say to anyone taking on a new project: “Be prepared to pivot!” Whether you’re handling a software implementation, organising an event, or working on a marketing campaign, challenges and opportunities will arise.
Being able to pivot is an invaluable skill in managing projects in today’s landscape. To navigate changes successfully, I’ve discovered four strategies that help with pivoting, regardless of the type of project.
1. Love the problem, not the solution
Every project is primarily designed to fix a problem. Adopting the mindset that your project is a problem to be solved has a positive impact on project outcomes. This gives you the freedom to stay focused on the overarching goals, rather than fixating on the solution.
It also facilitates a more adaptable and open approach to change. When issues arise during a project, you’re not compelled to stick rigidly to the initial plan. This is crucial because it prevents you from losing sight of the problem you’re solving. You pivot in response to project need but stay anchored to your project purpose.
2. Prioritise outcomes and deliverables
To keep your focus on what matters, be sure to prioritise outcomes and deliverables. It’s then easier to decide what can be adjusted or sacrificed when you need to pivot. One popular method is MoSCoW — it’s a structured approach that keeps the project’s objectives at the forefront of your decision-making process:
- Must-have: Critical elements that are non-negotiable and a top priority.
- Should have: Important elements that contribute to project success but aren’t as critical as must-haves.
- Could have: Nice-to-have elements that would enhance the project, but the success of the project isn’t dependent on them.
- Won’t-have: Elements that are not part of the project scope.
3. Accept change as inevitable
Making changes in projects when you least expect it can be difficult. But change is an inevitable part of projects. Accepting it’s going to happen from the outset means you’re less likely to be thrown off balance when it occurs. See it as an opportunity for improvement rather than a setback. It’s been shown that embracing this perspective helps build a culture of adaptability in your team that encourages problem solving.
4. Identify key risk areas from the start
Every project has inherent risks. Some areas are more prone to issues than others due to lack of testing, new market conditions, or complex use cases. Identifying key risk areas at the start enables you to pivot when the need arises. Knowing the risks opens the way to set up contingency plans to mitigate issues before they arise. It might not catch every challenge, but you’ll be amply prepared for the biggest ones.
Projects rarely unfold as initially planned. External factors, stakeholder feedback, and unforeseen challenges demand us to respond. You may well need to realign project strategies, objectives, and resources in response to changes. Agility in this context minimises the risk of project failure, but also something else — something with a profound upside. It promotes innovation and continuous improvement, the path to more successful projects.
Author: Nathan Davis, CT: Evolve