- ✓Data is raw, unprocessed facts and figures, while information is data that has been processed and given context to make it meaningful.
- ✓Organisations use data to support decisions at operational, tactical, and strategic levels, each requiring different types and frequencies of data.
- ✓Transactional data records individual business events, while analytical data aggregates and summarises transactions to reveal trends and patterns.
- ✓Data quality is critical; poor quality data leads to poor decisions, and organisations must implement validation and governance processes to maintain it.
- ✓Understanding how data flows through business processes is an essential skill for computing professionals building or supporting enterprise systems.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: We're starting Unit 10: Business Process Support today. First up is the role of data in modern business. Sam, data has become a bit of a cliche as a topic. What's actually important to understand here?
Sam: What's genuinely important is understanding how data flows through organisations and how it's used to make decisions at different levels. Data isn't just numbers in a database; it's the information that allows organisations to understand what's happening, predict what will happen, and decide what to do. The organisations that use data well have a significant competitive advantage over those that don't.
Alex: Can you explain the distinction between data and information?
Sam: Data is raw, unprocessed facts: transaction records, sensor readings, customer clicks. On its own, data is not inherently useful; a list of 10 million transaction records doesn't tell you much. Information is data that has been processed and given context to make it meaningful: the fact that sales of product X increased 30% in the north of England in the last quarter, derived from those transaction records. Information supports decisions; data is the raw material from which information is produced.
Alex: How is data used at different levels of an organisation?
Sam: At the operational level, data supports day-to-day decisions: is there enough stock to fulfil this order, has this payment been received, is this network device performing within acceptable parameters? At the tactical level, data supports medium-term planning: which products should we promote next quarter based on current trends, where should we allocate resources to maximise efficiency? At the strategic level, data informs long-term direction: what markets should we enter, what capabilities do we need to invest in?
Alex: What types of data do organisations typically work with?
Sam: There are several useful distinctions. Transactional data records individual business events: sales, bookings, logins. Analytical data aggregates and summarises transactional data to reveal trends and patterns. Master data represents the key entities of the business: customers, products, suppliers. And increasingly, organisations work with unstructured data: emails, documents, social media posts, images, and audio, which are harder to process but can contain valuable insights.
Alex: Data quality seems to be a significant issue.
Sam: It's huge. Poor quality data is one of the most common causes of failed analytics initiatives and bad business decisions. Data quality problems include duplicates, missing values, inconsistent formats, outdated records, and incorrect values. An organisation might have extensive customer data but if addresses haven't been updated, records are duplicated for the same customer, and phone numbers are in five different formats, the data is not fit for purpose. Data governance processes, including validation at the point of entry and regular data quality checks, are essential.
Alex: Any advice for computing professionals working with business data?
Sam: Always ask 'what decision will this data support?' before designing any data collection or reporting system. The purpose of the data should drive every design decision. And build quality in from the start: retrospective data cleaning is expensive and never fully effective. Getting the data right the first time is always cheaper.
Alex: Brilliant. Thanks Sam. Next we look at the ethics and governance of data use.