Achieve real value with a
Proof of Concept
When considering an upgrade in technology, many organisations start the process by planning for the big bang launch. Consequently rolling out many applications into many departments within an organisation all at once. Taking the ‘big is better’ approach without really giving some thought to how those new technology offerings are going to solve problems within the organisation. They don’t consider a proof of concept.
Solving specific problems one at a time based on user feedback within the organisation is not the most common business practice. Many organisations roll out technology and offer the latest and greatest, hoping the upgrade with some user training will be the right choice. This process, they foresee, will solve current problems.
Software needs and business requirements are as different as the thousands of industries that roll-out new technology themselves, so why have a one fits all approach. #ProofOfConcept Click To Tweet
This type of thought process is very common amongst organisations, and justifiably too. This is common practice within the world of rolling out technology upgrades.
Organisations roll-out, give a few comms here, a few training sessions there and then ‘bang’, mark the project as complete.
Organisations give the same out of the box type experience for every type of business – from mining to education. From Local Government to Storage solutions. All being offered the same software goes against one definite fact. All companies work differently, as do employees within those organisations. So why would rolling out all the same software without any testing be the first choice for improvement?
Consider doing a proof of concept.
A proof of concept is a test in seeking value that resonates positively with organizational strategy. It is a test that takes place before rolling out new software into an entire organisation. PoC is a test that enables an organisation to realise the actual problems it has and which specific technology solutions will solve those issues and make savings in productivity, time and cost.
A test that starts small, and ensures successful results in the way they specifically do business and then rolls out the best solutions. Doesn’t that sound like a better way of using technology? Making it specific to your organisation. Not a one plan fits all and as a result, a perfect fit just for you.
Implications for staff travel.
An Australian airport organisation’s work practices consisted of their staff working between three different terminals and numerous building. Staff were required to travel to these different locations anywhere from 1-5 times a day for various meetings and business operations.
Time cost (in travel) – 9 mins in good traffic, 15-20min in heavy traffic each way, adding on time for parking, walking into the terminals and time sitting around before starting the meetings.
The cost to staff – (excessive frustration and downtime) Doing this once a day was annoying, but doing it numerous times a day was frustrating staff in addition to increasing health and safety risk by having team members on the road so much.
Consider this was your day to day work life. How much of your own work would you get done? How productive would you be outside of always travelling back and forth to meetings? What about flying on those same day return flights for business meetings. Your entire day really is a broken into fragments of focused time.
Solving one pain point at a time
Rather than this company rolling out every application in the Office 365 suite and hoping for the best. They instead started small. They took one pain point – one problem and tested ways that it could be solved. Tested ways they could unlock value from their technology. In this instance, the biggest pain point was the excessive travel. They were looking for a way they could use technology to improve the way they work.
To discover this, they invested in a proof of concept. They took the time to think about productivity problems, therefore time to discover what the value will be by rolling out one type of technology vs another. To discover excessive travel was the biggest pain point of the business. They took time and tested technology in a small group, measured the stats and then took that and shared it with the next team and the next. Team by team, one at a time. Ensuring success in small steps and a huge upsurge in user adoption.
Microsoft Teams was the solution
This organisation found by utilising ‘Microsoft Teams‘ to hold meetings from their desk, made a substantial difference in improving their productivity and drastically reducing employee frustration and safety risks. Being able to work at their desk right up to the minute before a meeting started, was a big win for a big problem. And so they rolled this out a team at a time.
The value of going through this process is you can think about the way you work together, amplify the way you work together and improve the way you work together. Proof of concept gives you space and though to think about that.
In conclusion, in what ways would you like to improve the way you work. What is your biggest pain point, what solutions are you looking for? Proof of concept will give you the space to find those solutions without the extraordinary cost of all in one technology roll-out and investment.
Where to start a conversation?
– struggling to understand how to use a proof of concept. This article offers suggestions for how to start your conversations.
Good Stories creates awareness
– discovering what is at the heart of an organisation can make all the difference to effectively employ the tools that the business is paying for.
Our associated services
Microsoft Teams and Proof of Concept
Work with our team to understand the key business use cases that make sense for teams in your organisation before investing in technology.