IT is not the answer
It is always tempting to think that a new tool will solve all your problems. The reality is that many tools do more or less the same thing functionally, but that doesn’t mean they will all work for your business. And certainly not without a plan to deploy and support those tools ongoing.
Technology investment is traditionally the province of IT departments. But when it comes to data solutions – be it databases, reporting software or data science tools – the user experience is at least as important than more technical or functional considerations.
In organisations we work with, it’s not uncommon to discover any of these artefacts of initiatives past:
In organisations we work with, it’s not uncommon to discover any of these artefacts of initiatives past:
• Expensive, unused licenses for reporting tools
• Complex data models that few people can navigate
• ‘Self serve’ reporting that only one person knows how to use
• Legacy ‘black box’ processes with no documentation and no institutional knowledge.
• Complex data models that few people can navigate
• ‘Self serve’ reporting that only one person knows how to use
• Legacy ‘black box’ processes with no documentation and no institutional knowledge.
To deliver successfully, you need to consider not only tool selection but, change management, cultural fit and a sustainable support model.
IT departments play a key role in procurement and may even lead the process – but the requirements must be led by the business, and the users must be involved. Here are our top tips for introducing a new BI, reporting, data or analytics solution to your business.
A tool is not a plan
If you plan to introduce a new reporting capability to your business, for instance, the software is one part of the picture. A team must be ready, data literate, trained up and focused on the right deliverables. Senior managers should have realistic expectations, and the high level business requirements should be well defined before the tool is selected.
Training is not a magic bullet
If you select a complex, high end tool and try to train up non-specialists the gulf will be too large. In many cases usability and ease of integration are far more important than functionality. Think about who will be using the tool as well as what it can do.
Focus on essentials
Prioritise your key requirements – leave room for future growth, certainly, but don’t be swayed by fancy AI features unless you have a clear use case in mind. Better to get the basics right and deliver value quickly.
Get a support plan in place
Analytical software is still software – and a level of technical support is essential. Your IT department may not have the depth of knowledge in place, so make sure you are comfortable that the right technical support is in place if anything goes wrong.
Protect your institutional knowledge
Where specialist resource exists in the business to support a particular solution, make sure you have the skills coverage and documentation you need and succession planning in place. If your expert leaves the entire ecosystem is at risk of collapse.
At Realise we have helped many businesses understand their needs and navigate change. Contact us to find out how we can help you find the right solutions for your business.
IT departments play a key role in procurement and may even lead the process – but the requirements must be led by the business, and the users must be involved. Here are our top tips for introducing a new BI, reporting, data or analytics solution to your business.
A tool is not a plan
If you plan to introduce a new reporting capability to your business, for instance, the software is one part of the picture. A team must be ready, data literate, trained up and focused on the right deliverables. Senior managers should have realistic expectations, and the high level business requirements should be well defined before the tool is selected.
Training is not a magic bullet
If you select a complex, high end tool and try to train up non-specialists the gulf will be too large. In many cases usability and ease of integration are far more important than functionality. Think about who will be using the tool as well as what it can do.
Focus on essentials
Prioritise your key requirements – leave room for future growth, certainly, but don’t be swayed by fancy AI features unless you have a clear use case in mind. Better to get the basics right and deliver value quickly.
Get a support plan in place
Analytical software is still software – and a level of technical support is essential. Your IT department may not have the depth of knowledge in place, so make sure you are comfortable that the right technical support is in place if anything goes wrong.
Protect your institutional knowledge
Where specialist resource exists in the business to support a particular solution, make sure you have the skills coverage and documentation you need and succession planning in place. If your expert leaves the entire ecosystem is at risk of collapse.
At Realise we have helped many businesses understand their needs and navigate change. Contact us to find out how we can help you find the right solutions for your business.