Why do we want to find and share success stories?
Well when we do things well, we want others to know about it, to learn from it, to be inspired by it. This is no different when we are dealing with success stories from a technology project. There is often a project implementation review with the project team and stories are often shared here.
Making those success stories available to the wider organisation or even to your clients could provide a greater insight into who you are and how you do things. Gathering success stories from the field or wider organisation also allow others to see benefits have been realised or where real value has been gained.
Where do you find the success stories?
Well, just about anywhere. It could have been a quick post on Yammer or an email that was distributed that told of a success. It may need to be teased out a little, with a good conversation, but crafting it into a story that is accessible to others, will mean that others can learn from it. It might simply be having a conversation with someone in the lunch room.
Hearing how the new technology has changed a process for the better. Get that story out there for others to see. We are all too busy to continue doing things the hard way. So, when someone else has come up with a bright idea that will save time or effort, and then they take the time to share it, it not only means an increase in productivity but an increase in the unity of teams.When someone has come up with an idea that will save time or effort, and that idea is shared, it not only means an increase in productivity but an increase in the unity of teams. Click To Tweet
Projects often provide reports about a technology project, providing graphs and data to show how successful an implementation was. However, success stories are more powerful than data because it comes from the grassroots end user. And when it comes from our colleagues, we trust the information. These are the “off the ground” stories, which provide real instances of where change has been effective, that are relevant and true – not just a graph or statistic on a page.
In successful projects, stories are also gathered at the beginning of projects. They may not be success stories yet – but they are the pain points or problems that need to be solved using the technology. Sharing how these stories were turned into success shows the full circle of the project.
At A&E, we see it all the time. We recently assisted an organisation with a Yammer Launch and we saw the stories unfolding before our eyes. Offices that were previously quite insular, were now sharing ideas and designing processes collaboratively. In another organisation we saw benefits realised by a true dollar value saving $46,500 and unlocking 76.5 days of additional productive time by their team leveraging Skype for Business to connect with stakeholders around the country, reducing their operational expenditure.
We have also seen how the leverage of Office 365’s new tools like Forms and Power Apps can change the way an organisation process otherwise mundane tasks. During one engagement, a particularly cumbersome process was identified by time-poor employees. By working with our consultant’s, a plan was put in place to design, build and implement the new process resulting in a massive time-saving exercise. Why wouldn’t you share that? By sharing these stories, we make others aware of the possibilities, but it also assists the organisation to know that their Return on Investment is being realised.
Stories don’t have to be on the grandest scale. Sharing productivity tips and tricks within your team or wider organisation is also beneficial. The thing is, we don’t know, what we don’t know. Often you will see someone do something new, and ask, how did you do that? By sharing that information with others, you may just also help someone else.
The old pay it forwards philosophy. So find those stories, listen carefully to what your teams are saying, dig a little deeper and share, share, share, anywhere, anytime – every meeting. Stories enable, inspire and reinforce the change.