Wednesday, September 10, 2008

Innovation - Beginning the Process

I've been on the road for awhile but it's time for me to continue my story. As you may recall, the teams labelled each group of ideas, for example, “registration process”, “speakers”, “social”, “receptions”, etc. Then they went to each group and began exploring them in more depth. It is critically important they no process of elimination of any ideas is permitted. Only exact duplicates can be removed.

The teams began to identify and list out the benefits of moving forward with each group of ideas. "What will be the benefit of using the ideas in under the registration process group?" What will be the benefits of the ideas, if implemented, under the speaker group?" etc. If you think for a moment of the greatest inventions of all time you'll probably think of the light bulb, electricity, the phone, the car, etc. Before moving forward with all of the ideas which led to these "group of thoughts", the inventors spent time thinking about the benefits before moving into the next stages of their innovation process.

My next blog will give you the next steps in the innovation process.

Thursday, September 4, 2008

Innovation - The Next Steps to Improve Your Conferences

My last Blog introduced you to the concept of holding an Innovation session for conference attendees focussed on creating the “ideal” conference format. I started the session by asking everyone to brainstorm everything that would happen, that they would be engaged in, that they would experience, etc. that would make it an amazing conference. Each idea was written on post-it notes. One idea per post-it note. No discussion, this is done individually. Then I had them break into teams of 8. Each team posted their notes onto flip chart paper and began the process of combining similar ideas into groups. This process, known as the development of an Affinity Diagram, generated many different groups of ideas in each team. They labelled each group. For example, “registration process”, “speakers”, “social”, “receptions”, etc. My next Blog will discuss the next steps.

Monday, August 25, 2008

Innovation - How to Get it Going at Your Conference

My last Blog spoke about the need to be more innovative in how conferences are managed. It is very difficult for staff and volunteers to break the mould. It is always easier to introduce small, incremental change. The best place to start on the Innovation Journey is to engage the conference participants. At the American Society for Quality’s World Conference I held two back-to-back concurrent sessions focussed on how to create an “ideal” conference for them. I needed a full morning to do this, hence the need for back-to-back sessions. When published in the conference brochure, it was certainly a different type of session from all of the others. Nevertheless, 150 people showed up. Wow!!! My next Blog will explain how I managed the session.

Friday, August 15, 2008

Innovation at Conferences

I have spoken at many conferences this year across Canada, the United States, Europe and Asia. The one thing I have found in common in all of them is the “same as last year” formula. Every conference is structured the same. An opening reception, a morning keynote speaker (this is where I am usually positioned), concurrent sessions, lunch, banquet dinner, etc. It is boring. Not the content, the format. It is time for these organizations to think more innovatively about their conferences. I will explain how to do this in subsequent Blogs so stay tuned.

Tuesday, July 29, 2008

Travelling and Auditing Projects

I know that this may seem a little unusual a combination for a blog title. I have been auditing projects for sometime now. I am always fascinated to identify the root causes of projects in crisis and then to provide the project manager and team with clear strategies on how to turn their projects around. Having created tremendous, measurable success on many construction, heavy industry and IT projects I was asked to develop a workshop on How to Audit Projects and Provide Risk Assurance. I hadn't really thought about educating others on my process but decided to take up this challenge and develop a workshop.

That was a couple of years ago and since then I have delivered it successfully in the United States, Canada, Australia and New Zealand. I'll be leaving in a few weeks to give this workshop in Jakarta on August 25 to 26, 2008. It is very practical. Participants keep telling me how much of an impact it has had on their projects. If you're interested in more information, drop me a line at mstanleigh@bia.ca It'd be great to meet you and see you there. I'd be happy to send you outlines and/or any other information you need.
All the best,
Michael

Tuesday, July 1, 2008

Providing Project Risk Assurance


My customers have told me and given us testimonials about how our coaching and training has improved their operational effectiveness. They love our articles and have learned a great deal when hearing my keynote presentations at various industry conferences. They have also suggested that it is time I got going on a Blog so that they could hear, more often, about my insights into what helps organizations to improve their profits, customer experience and staff engagement. So I have listened and here is my first one.

One of our core practice areas at bia™ includes the coaching and training of project managers and their teams. Often, several months later, they bring us back to help manage a project in crisis and/or one that is in a constant state of fire-fighting. After all of the training and coaching, why are they caught in these costly and stressful situations? There are of course many factors but ultimately we find that two major reasons: not using a continuous risk management process and not conducting regular project health checks and audits.

The risk management process ensures that they proactively identify what might go wrong on their project and what they can do to reduce its likelihood or manage it, should it occur. On-going health checks and project audits (often by a 3rd party such as Business Improvement Architects) ensures that they understand the factors which might be preventing success and identifying the root causes so that the project can be brought back on track. It provides the project manager and team with a list of lessons learned to date.

Your call to action is simple: Understand and use a Risk Management Process and Conduct regular (every 6 months) project health checks. I have free, in-depth articles on these subjects at http://www.bia.ca/articles/UndertakingaSuccessfulProjectAudit.htm and http://www.bia.ca/articles/rm-risk-management.htm
Thanks,
Michael