Best Practice Guide
Delivering a single view
Every organisation wants to be able to make improved decisions, ease the burden of compliance, be more customer-centric and offer better services or products. All of these things – and many more besides – rely on you having all the right information in front of you when you need it.
Customers, citizens, products and more
While this may sound simple, bringing together all the information you hold about a given entity – be that a customer, citizen, patient or asset – is a complex undertaking. This is because the information you need is likely to be stored and updated across multiple systems, databases, spreadsheets and the like. Finding it is one challenge, then making sure it’s all in sync is the next.
Faced with these not insignificant issues, how do you go about creating a ‘single view’ of your important entities? The answer is to roll out the right software tool in a controlled way, and to put in place the structures and governance to support it. This guide will introduce you to the problem area by looking at some real-life examples, and then highlight why it’s important that you look beyond a pure technology solution.
- Creating a single view doesn’t necessarily require major investment. Small tweaks in the right places can deliver real step-changes
- Failure to invest in a single view could leave your organisation open to significant risks
- Creating a single view requires more than just a technology platform
- You'll typically require a Master Data Management (MDM) tool, Master Data framework and Data Governance structures
- You need to think about the impact a single view will have on the people and processes in your organisation
- Your single view vision will determine what kinds of tools you should use: operational or analytical
- A single view can deliver operational and analytical benefits – some of which you won't have expected