Why should we discuss that?

“Why would we discuss that, it will never happen? I have more important things to do now, that are actually happening…”

This was the phrase I heard in a meeting I created to start the risk management process. We were supporting a growing company to implement their Project Management Framework and PMO.

We have gone through all Project Management Knowledge Areas, and understood which good practices were fit to their size and culture. We knew at that time they were not mature enough in project management at that time to embrace all desired tools and techniques, and their business model also wouldn’t allow them to do so.

One of the biggest challenges we faced was around Risk Management. This is a tricky area, because on one hand it is easy to understand that something will go wrong, no matter how hard you try to avoid it. On the other hand, it is hard to turn that abstract concept into tangible issues and action plans.

We really looked at Risk Management with care. We created templates to help with risk identification, response plans and even contingency plans, and risk management meetings that were supposed to take place weekly, and they did for a while. After some weeks, we realized that these meetings were getting empty because there were no more risks to be identified, they said, and the evolution of those identified earlier was very uncertain.

Even though we were not the project execution team, we attended some of their meetings as support. On doing that we realized something remarkably interesting. They were discussing risks at their weekly status meetings. The real problem here was they were discussing risks, but not treating them as such.

After this finding, we suggested adding risk as a mandatory subject in the agenda of the execution status meetings. This way, risk tools, such as the risk identification sheet, or the risk response forms were brought as an asset to the meetings.

This approach streamlined their process, as there was no longer the need to transfer the notes from the minutes to another document. They were now bringing the appropriate template to help them make the right questions around the issues, or risks, they were foreseeing.

In the end, those intangible ideas were related to what was happening in the project. The perspective change helped them answer that question they asked in the beginning: “Why should we spend time on something that may not even happen?” because now they could correlate that to the real world.

You can hear this post here

What’s worth doing something good, if that’s not expected?

Last week I have been confronted with a very interesting situation.

It was presented to me a simple yet powerful list of Frequently Asked Questions (FAQ) that was shared to a global team, regarding to transformational initiatives that are being deployed through all levels of their operations.

That, per se, is a big deal, and a FAQ is a must in these cases.

I received an email asking my thoughts around it in a table, right after receiving another notification of a news article mentioning the importance of this FAQ, and where to find it.

When I received both notifications and gone through the article and the file, an idea came to my mind. Why not use the same content using a better tool?

The table format is awesome to brainstorm, understand the problem and visualize the results at once, but it is not responsive enough to be used in every situation.

So I turned it into an online list that could provide different views of the same content at once, solving the responsiveness issue of the table.

Problem solved! Everything worked and I added one more ability to my skillset! Awesome, eh?

Not so much, I was so enthusiastic about what I did, that when I shared it with the person who provided the first table, I didn’t remember to send him a simple heads up mentioning what I was thinking, and asking what he really needed.

There were some next steps to this process, such as advertising this new formatted list to everyone, and settling that as a normal procedure when they need information about the transformation process.

Now I have this additional step: Understanding what was the expectation around it, and if what was done, as good as it is, matches this expectation.

We all go through this, we sometimes infer what’s to be done, and do it right away, without checking with our stakeholders what they think about it, to save some time.

Making it right the first time becomes a matter of luck in these cases. But it is uncommon, and we end up making it wrong, which makes us lose all the work done, or worse, work twice to correct it.

Doing something good is different than doing it right, because the right thing to do is what is expected, or even better, exceed expectations!