What makes the difference between a successful and unsuccessful change approach? Engagement.

Just like in relationships - you learn there is a big difference between dating someone and being engaged. Engagement has commitment and a clear intent.

An ineffective change manager or leader will approach change like dating. Spend a little time with their stakeholders, and even if it was a memorable moment, don't follow through or create that genuine relationship. It's superficial with some brief communication before and after. There might be questions asked but it's patchy as to whether there are answers provided. A successful change strategy contains more than that. It enrols leaders, stakeholders and impacted audiences through impactful interventions.

So how do you create powerful engaging dialogue with those who are affected by the Change?

• Involve the customer of the change in the design of the solution. Such an easy concept and yet it still isn't followed. With many technical speci
...

Effective stakeholder management is critical for success of any initiative and smooth delivery of any project. The fact of the matter is, it doesn't matter what your end product is if you are 'burning' your stakeholders through lack of involvement or shutting them out. Every time you are delivering something new into your organisation or you are running a project, effective stakeholder management is a MUST!

Here are the three fail-safe strategies to put into place when working on projects or working with teams across an organisation to deliver an outcome:

1) Take the time to make sure you are involving the right people. This may sound silly but if you haven't taken the time to note down exactly who you consider your stakeholders to be, you need to put a pen to paper or finger to your keyboard right now and get to it.

Why? Often we forget who we need to involve or who need to know about your initiative. This results in complaints or 'white-anting' your initiative.  Listing out who sh...

Many people in business don't like to consult. They would prefer to just get on with the job and deliver something. The urge to move forward and just get something done is strong and any consultation is seen as inconvenient and unnecessary. Unfortunately when the product or service is ready to be implemented, it takes twice the time to engage and often results in a solution that doesn't work for the consumer.

We see it time and time again. IT solutions designed with leaders, not the 'doers' and delivered only to find out it doesn't meet the need of customers or staff. Processes mapped on 'best practice' not matching the reality of the business and capability in which to deliver them. Example after example. More money spent on projects to redo what the previous project failed to deliver and the major difference the second time around? Consultation and engagement with those who are responsible for the process takes place to deliver the right solution.

So what is my reply to those who w...