For many organisations, building a data-driven culture that everyone truly embraces is a difficult task. To understand this further and to explore different ways to encourage this culture change, let’s first understand what we mean when we talk about a data-driven culture.

This article aims to clarify what we believe the key aspects of being a Data Architect are, based on our experience, shedding light on the various skills and tasks that data architects undertake to enable effective data utilisation and decision-making.

Here we explore what some of the most common barriers to data literacy in an organisation are.

Have you taken the time to carefully select a data management tool for your staff and organisation to use, but are finding that hardly anyone uses it and that the uptake is fairly low? This article aims to explore why this might be happening in order to help us understand what can then be done about it.

If you have lots of data but somehow struggle to actually do anything useful with it, you probably have a data literacy problem. Everyone in your organisation needs to have some data literacy, and that doesn’t mean technical skills. Data literacy avoids wasted effort and the best way to spread it is by example.

Are you passionate about data but don’t understand why others aren’t? There are several common reasons that stop staff and colleagues from taking that next step and really caring about data.

In the Internet era, the data problems we have are different. In this first in a series of posts, we’ll examine how the different ways that people create and use data today impacts how we must shape a data architecture.