The Other Lessons Learned

From the Voices on Project Management Blog
by , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with - or even disagree with - leave a comment.

About this Blog

RSS

Recent Posts

End a Business Relationship and Keep Your Cred

Fair's Fair

Give Your Project a Home

A Hollywood-Style Move From PM to Scrum Master

To Have and To Hold

Email Notifications off: Turn on

Categories: Lessons Learned


At a project's end, I sometimes have to tackle non-project lessons learned — those issues or takeaways that arise beyond what went right and wrong on the project. Here's how I've implemented some I have faced:

Team adjournment. Team members must now move on to other teams and projects. To mitigate the sense of loss, arrange an end-of-project reward, such as a social gathering. And if emails, instant messaging, and social media — such as a company Facebook page — were arranged for project communications, encourage new discussions via these channels to foster continued friendships.  

Changes to the organization's processes. Lessons learned should provide direction on the processes that benefit the organization the most if adopted right away. Once those are identified, speak to sponsors or executives and request that a task force be appointed to evaluate these processes further. The task force should consist of key stakeholders who can make changes to processes. For example, I organized a task force to review our quality control processes on a recent production project. During the project, our quality manager only reviewed product consistency and workmanship in the testing phase. The task force, however, determined the quality manager should be involved earlier and review elements during the design phase. This ensured design elements were consistent with other products released to market and cut down on time spent on the testing phase.

For your projects, if you determine your organization can benefit from the process changes identified during a lessons learned, embed change management principles in project plans to lay the groundwork for employee buy-in. This lessens the impact of new processes for the employee — and the organization. Finally, the changes may require new training, which you should champion. Without it, you'll have new processes, but no team members capable of following them. 

Revenue breakthroughs, good or bad. Even when your project is facing cancellation, you can help drive discussion around its closing. Prepare reports that show in-depth understanding of the issues. After all, many of the projects that get cancelled may just need portfolio realignment. 

On the other hand, if your project was successful, there is a new bottom line to celebrate. So if appropriate, publish your accomplishment in the form of best practices with organizations such as PMI. You can also prepare training sessions and webinars or publish articles about the organization's steps toward success.

Do you look beyond the project's lessons learned for other challenges and opportunities?

Posted by Bernadine Douglas on: May 29, 2013 12:37 PM | Permalink

Comments

Please Login/Register to leave a comment.

ADVERTISEMENTS

"I don't like work - no man does - but I like what is in the work - the chance to find yourself."

- Joseph Conrad

ADVERTISEMENT

Sponsors

>