The Money Files

I’m continuing my deep dive into continuous improvement this month as it’s such an important topic for project managers. There’s this expectation that we will use the retro and lessons learned processes to make improvements, and yet there is rarely the time to fully implement lessons. That’s one of the major challenges, and I want to talk more about challenges in making changes to ways of working today.

Resistance to change

The first challenge is resistance to change. Resistance can come about for lots of reasons, not least because people are worried about the extra workload of having to deliver project management process changes on top of their project execution activity.

Also, humans seem programmed to not like change. Having to learn a new way of working is a pain.

We can address this in the same way as you address change resistance to any of your projects: understanding the concern, clear communication, training and support and demonstrating the benefits. Plus a bit of management ‘this is the new way of working and you will follow the process’ can be useful!

Sustaining momentum

Improvement programmes might start out well, but it’s challenging to keep them going. After all, there are only so many improvements that are simple to make and easy to implement, so you might feel your goal of improving continuously is struggling because people have already suggested the easy wins.

Team members might not engage with it any longer. Keep celebrating success, keep recognising good contributors (without making those who cannot suggest improvements for whatever reason feel bad).

Pace out your changes so there is a small strand of work happening throughout the year instead of a big push and then nothing.

Resource constraints

I’ve mentioned this a lot throughout the series because I really do think it is the hardest thing to overcome. We have to balance improvement activities with project deliverables.  In resource-constrained environments (isn’t that everyone’s project environment?), you may find it challenging to allocate time and resources for improvement initiatives. Management might not see the value.

People doing the work might prefer to focus on their project work, which probably already has to be balanced against their business as usual activity. Now you’re asking them to do even more, and even if they are willing, they have to make prioritisation calls, and frankly, changing processes is probably way down the list.

They might be incentivised on other things. Their personal performance metrics or team objectives and KPIs probably don’t include the new improvement that has only just been thought up. So unless you’re going to work with line managers to write in a percentage of their availability to work on improvements, expect to see some up and down commitment throughout the year. People will do what they can, but creating the space for them to do that is important.

I’d love to hear your suggestions for helping teams find the time to overcome resource constraints for project improvements? Do you build it into their personal objectives or make it part of the expected ways of working for the squad? Let me know in the comments below!

That concludes my deep dive into continuous improvement. It’s an important aspect of project management practice, and it helps us create an environment where we can contribute to the business in more ways than simply project delivery. We can be the driver for change as project managers, and help our teams, and our organisations, deliver more in difficult times.

It’s very easy to talk about continuous improvement, but if you’re anything like me, it’s a lot harder to build the actions into the workflows and processes you use to ensure that the improvement actually happens.

OK, perhaps that is an exaggeration. There are some simple activities that, once you realise, are easy to change and within your sphere of influence. Those are the improvements we can make simply and with minimal effort, and that everyone appreciates.

But the world of work is increasingly more complex, more VUCA, more intertwined, and changing one thing has an impact on other things. We’re not talking about updating a document template to add a new section, but rewriting workflows within project management tools, or changing how benefits are owned, tracked and reported on across the company. Those types of continuous improvements warrant projects of their own. Projects that often we don’t have the time put aside to deliver on.

Continuous improvement in project teams

What do we actually mean by continuous improvement? In my experience, when people talk about it in a project management environment, they mean the ongoing effort to enhance processes, increase efficiency, and drive better results. Whatever that takes. Like I said, it could be small tweaks or organisation-wide transformation of how projects are run in the business. And frankly, that makes it kind of hard for the average project team to effect any major change.

Still, it doesn’t mean we shouldn’t try. So, if you want to create an environment where people have the opportunity to raise their voices when they see things that can be improved, here are some suggestions.

Set the right example

If we want to foster the right culture, people have to believe they are already in a culture where their suggestions will be listened to. So we want to demonstrate:

Leadership commitment: That’s leading by example, speaking up and suggesting improvements, pointing out where things could be better and encouraging others to do the same whenever we hear them mention a good idea.

Communication: Unsurprisingly, communication needs to be taken seriously and you need to create the time for it. If everything is rushed, they won’t feel that they can share feedback and lessons learned (outside of structured conversations or retros). Create feedback loops or ask about improvement ideas in regular check ins.

Recognise the wins: Celebrate improvements and suggestions, even if they don’t turn out to be implementable – you’re recognising the fact that an idea was brought to the group. Hopefully this will encourage others to do the same and to feel that their ideas are valued.

Make it easy to suggest improvements

People need to feel empowered to suggest improvements and to act on them. Granted, most organisations don’t have dedicated ‘innovation’ time or slack in the calendar where people can work on their own projects. But you can remove the barriers to making suggestions.

Let people work their own way: Encourage ownership on the project and let people run their area of the project the way they feel best. If they find ways to improve or change the process, let them.

Suggestion schemes: In the olden days we used to have a box at work for suggestions. These days there are forms online where we can submit ideas. If you think people would be more open to suggesting ideas anonymously, make sure these systems are in place.

Incentivise innovation: In my very first corporate job we had a scheme where we sent in suggestions and got cards back. If you matched the cards to make a picture, you got a prize. Or something like that. It was a long time ago, but there was an incentive scheme for pointing things out. What could you do that’s similar?

Build in creativity training

Building problem-solving and creativity skills is a… skill. And we can train people on skills. Find some time for training on problem solving techniques, process improvement methods, creative thinking and so on. The Six Sigma training I did in my early career was so influential in how I approach problems today. But let’s just say I’m not naturally someone who would whip out a control chart.

Something else that’s easy to do and within your control is cross-skilling team members. Cross-functional learning and an appreciation of what other people do in their job helps people see the project from different perspectives and find improvement opportunities that way.

This is an interesting topic for me and I think there’s more we can cover, so next time I’ll look at tools and techniques for continuous improvement. Watch this space!

Have you ever made a bad decision? I’m sure I have but I don’t think I’ll be owning up to them here! The point I’m making is that people who make decisions aren’t always making the best decisions. And part of that reason is bias. No one is immune to it; the best we can do is call it out and be aware that it is happening.

I was asked to talk about bias in decision making at a university recently so I thought I’d summarise some of my key thoughts on the topic here to share with you.

Biases are cognitive shortcuts, often subconscious, that impact decision-making. And research has shown that there are lots of them. I read a few papers in Project Management Journal that pointed to many biases being identified. The key ones that I wanted to call out are these.

Confirmation Bias

This is where you seeking information that supports pre-existing beliefs. For example, only looking at data that supports your conclusions, or data from successful projects and ignoring data sets from unsuccessful projects. In daily life, this might be looking out for a particular type of car and then seeing it everywhere.

Anchoring Bias

This is where your future thoughts and opinions are anchored around a particular number. For example, if you’re talking about pricing a product and someone says it should retail for £50, you might get suggestions of setting the price at £40 or £60 but it’s unlikely that anyone is going to suggest £300 as the group has been anchored around the first number they heard.

Sunk Cost Fallacy

Bent Flyvbjerg calls this escalation of commitment, which is where you justify increased cost in a project even though it isn’t performing to plan. In other words, people talk themselves into continuing a failing project because of the investment that will be ‘wasted’ if they stop now.

Optimism Bias

Haven’t we all been guilty of this? It’s where you underestimate risks and overestimate project success. We all think our estimates are realistic even when past experience shows that we need to add buffer time.

Groupthink

When a group agrees with something, dissenting voices aren’t heard with the same volume. There is pressure to conform to collective opinions, even if you don’t truly agree. Diverse groups tend to make better decisions because they bring diverse experience and opinions.

Status Quo Bias

This is where people prefer familiar approaches over innovative solutions. I think there is also an opposite to this that I have – I’d rather use new tech and explore options and learn a different tool than use the old boring tool I’ve used before. Although this is not a good thing and means I have to spend a lot more time preparing for presentations because I’m trying out new gadgets or software that I haven’t used previously!

Bias contributing to project outcomes

You don’t have to look far to see examples of the sunk cost fallacy or optimism bias in public sector projects.

But there are examples of where bias has contributed to positive outcomes – or rather, structured decision making processes let people regularly challenge assumptions to avoid getting stuck with inappropriate solutions. I asked ChatGPT for examples of bias leading to project success and it could only come up with Toyota’s lean production system actively combating bias through data drive decision making. Maybe you have other examples from your experience – if so, leave them in the chat below please!

Overcoming bias

So what can we do about it?

• Encourage diverse perspectives: keep a focus on structured debate and let the dissenting voices be heard!
• Use data: seek out evidence that will provide impartial inputs
• Externally validate data and solutions: can you use external data reference sets or focus groups to confirm (or reject) your position?
• Consider failure: what does failure look like and what might lead you there? Pre-mortems are worth a go to discuss all that before you get started.
• Reassess the business case: keep the business case under review so you avoid throwing good money after bad.

Bias is inherent in how humans navigate decision making, but it’s manageable if you are open to talking about it and thinking about ways to reduce it. What’s one bias you’ll watch out for in your own decision-making?

I’ve been thinking recently about the role of intuition in project management. We often rely on the data, processes and logical structure of project management, but if you’re anything like me, you’ve probably spent more than one afternoon feeling that something just isn’t quite right and wondering how you can define the problem when you just can’t put your finger on it.

It’s a sense that something’s off. Maybe a project is veering off track, or a team member isn’t quite clicking with the rest of the group, but there’s nothing tangible to fully explain why. Maybe a stakeholder seems hesitant to commit, or you sense the team’s morale is low, even if the status reporting is telling you everything is on track. These things might not be much today, but they might cause bigger problems in the future.

That’s where intuition often comes into play. It’s often said that project management is part art and part science, and the intuition part is definitely not science! But the art is where we navigate the complex, human part of the job.

Managing uncertainty

So much of what we do as project managers is working in an uncertain environment. It’s juggling all the facts and then applying what feels right, while sticking to the boundaries and governance structure – just writing that out makes me feel it’s a balancing act. And one we don’t always get right!

A lot of what we do as project managers is solving problems, or helping teams solve problems, and the kinds of problems my teams are faced with today feel stickier and more intertwined than the projects of 10 years ago. No matter how careful the planning, there are unforeseen challenges. And that’s where intuition steps in. It helps connect the dots between facts, previous experience and what we know will work, which is handy if you don’t have lots of time to solutionise.

Experience shapes intuition

How much do gut feelings play when you are faced with an uncertain situation? And how much are those gut feelings influenced by the years of experience and knowledge of corporate strategy and conversations with your sponsor? Probably more than we acknowledge.

We must internalise all the things to do with project context, plus all our lessons learned experience on the way, and so while it feels like we’re making a decision based on gut feeling or intuition, isn’t it really a decision shaped by professional practice and experience? (Or is that the same thing?)

Experience feeds our intuition and guides us when the situation is high-pressure or the decision is woolly. The more experience you have, the better your instincts tend to be – and not just in project management but across all facets of life generally. It’s a deep understanding of your environment and how people and processes play together. You’ve seen it happen before, either on your own project or someone else’s, or you’ve read about it or heard a conference presentation. All these things contribute to your ability to act instinctively. They inform your decision-making, creating a kind of ‘mental database’ that helps you respond more quickly and effectively when things don’t go as planned. Which is quite often, on projects!

Let process lead

We can’t manage everything on feelings, the project management process is there for a reason. However, we can’t help but manage a little bit on instinct and experience as well. The more experience you have, the easier it is to trust your gut. But as we say at work, trust but verify. Once you’ve got a sense of where you feel you should be going, check in with that reluctant stakeholder, or ask the team about how they are feeling. Get tangible data where you can to back up what you instinctively know, and go from there.

I’ve been focusing all month on ways to improve and develop your career as a project manager, and today I wanted to talk about how to expand your knowledge base. Too often, I think project managers get stuck using the same sources time and time again. And we can learn a lot by accessing materials that are available for free, as long as we know where to look. So if you haven’t considered any of these knowledge-sources this year, put some time in your diary to check them out.

YouTube

Not just for funny cat videos! There are lots of quality project management vloggers out there, talking about everything from a day in the life to running projects transparently and reporting back on the results, to PMP® prep videos helping you understand the more complex concepts. 

Subscribe to a few channels and check them out. Look for content producers who have a lot of likes, and who post regularly on the platform, sharing new videos on a regular basis. You don’t have to leave a comment, but you’ll often find that creators will respond to new comments if you post them soon after the video has been shared. If you get alerts from the channel, you’ll get notified when a new video is available and the creator may respond to your comment.

LinkedIn Learning

Similar to YouTube, there are plenty of LinkedIn Learning trainers sharing amazing insights in well-produced training content. Search for the project management topic you are interested in and see what is out there. Your employer might have access to a corporate subscription that you can use. I have access via my university as an alumna.

There are a lot of courses to choose from, so look for topics that are relevant to your current work (or that you would like to learn more about) and providers who have good customer reviews. It feels to me that LinkedIn Learning courses are quality checked, so you should be in good hands whichever one you go for.

Webinars

There are lots of webinars here on projectmanagement.com, taught by experienced trainers and covering a range of cutting edge and established project management ideas. And there are plenty of webinars out there run by other organisations, including PMI Chapters and software companies. Do a search to find out what is coming up in the near future and then regularly make a point of signing up to one webinar a month to expand your horizons.

Podcasts

Podcasts are another way to get real-time, current knowledge and get exposure to people you would never normally get the chance to chat to in real life! Subscribe to a few that sound good and then switch them out if you want a change. There are literally hundreds of relevant podcasts and episodes on all kinds of topics.

Interview-style podcasts are good ones to focus on, and tune into any that promise case studies or sharing research results as these will help you broaden your knowledge and stay current in the market. 

Expanding your knowledge base is a really good way to stay up to date on new methodologies, trends, and technologies which in turn can help you stay competitive. But more than that, it’s a way of helping you stay connected to the profession and continuing to develop your skills so you can add more value to the teams you work with.