At the beginning of the year our Consulting Team transitioned to an Agile Consulting model. I am not going to delve into the definition of Agile Consulting here, if you want more information then I highly recommend reviewing: What is an Agile Consulting Engagement (ACE) ?.
The interesting thing for me is not just the change in the process or approach to solving a problem but the subsequent evaluation of the consulting engagement and tying the elements of the success back to into process or approach change. In this case, it was a significant change and a significant investment across the team as a whole.
So, on to the problem. The problem with the consulting approach pre ACE was that it was static. Customer needs are fluid and change for many reasons:
- Education - In the versatility of the tool or the underlying business proces for example
- Growth - In requirements or stakeholders for example
- Time
- Iterations
- Etc ...
So, on to the evaluation. One of the driving elements in the Agile Consulting Engagement methodology is "demoing" the state of the engagement at the completion of a sprint.
The obvious reason for this, it to drive a review and signoff of the latest sprint. Common sense from a consulting perspective right? Well, the secondary benefits of this step in the ACE methodology, in my mind, are far more useful. Let me explain 
Have you ever been the victim of a change? You know, one day someone springs a new "time tracking" or "accounting" or "ticketing system" on you ...
By the time you actually get to see it and interact with it, it is completed and you have no say in how to implement it before it is in production and inflicted upon you?
Have you ever heard the dreaded:
"We are moving from the old system to the new system on Monday and we expect everyone to be up to speed and using it as of Monday"
without every having seen the new system and immediately started worrying? I know I have and I am not a big fan
Worse, it sets a bad expectation and colors the first impression of the new system in a negative fashion.
Now imagine a different approach, imagine that periodically during the project process; from planning, implementation and even through final delivery, you were asked your opinion, you were experiencing the changes first hand and you had input into helping drive/manage the changes.
Would you expect a better outcome?
Would you be happier?
Would you feel like the owner of the change rather than the victim of the change?
Now imagine a project lasting several months or perhaps even several years. Which approach would you feel has a better chance of success?
Last year, I had the tremendous opportunity to be involved in a project in Australia where a fortune 100 company level business process rearchitecture was happening. During that time I realized just how important selling your process change and resulting service was. The project lead in question leveraged my services quite often during the lifecycle of the project to help showcase the end results of the process change to his business. The results were very interesting and very powerful. I learned that creating internal advocates within your customer base fed upon itself to drive interest, buyin and even competition to be the first to be onboarded.
Why was xMatters the "shiny thing to show around" you ask? Because we are piece of the puzzle the customer actually gets to see and interact with and that interaction is a good piece of the overall perception of the entire solution.
Over the course of this year using our new ACE methodology I again experienced the power of this process to an unanticipated degree. I experienced how the impact of actively engaging your end users during the course of the project feeds upon itself and even "snowballs" to drive the project to a successful conclusion. More importantly, how actively educating the end users and involving them in the change creates internal evangelists, driving positive change and allowing the final migration to progress smoothly and cleanly by setting the appropriate expectations in advance.
Finally, perhaps most importantly a user base asking for more rather than dreading more.
If you would like to read about an actual customer experience I would recommend the following as it is probably the best example that I have seen in my time as a consultant:Re: Benefit of "Agile Consulting Approach" and DIA