ICDL Data Analytics (ICDL) case studies
ICDL Data Analytics · Put your knowledge to work in context.
ICDL Data Analytics is a professional-level certification within the ICDL programme family, which the ICDL Foundation describes as a global social enterprise committed to raising standards of digital competence in the workforce, education and society. The ICDL PROFESSIONAL strand is positioned as professional digital skills for occupational effectiveness, so the Data Analytics credential is aimed at people who already handle data in a job or are preparing for one - analysts, administrators, marketers, and students moving into data-facing roles - rather than at complete beginners. The ICDL Data Analytics case studies are 5 cases and about 1,968 words.
1The Dashboard That Nobody Trusts
A regional clinic network publishes a monthly operations dashboard built from three sources: an appointment system (exported as CSV), a billing database (queried directly), and a hand-maintained spreadsheet of staff headcount. Last month the dashboard reported an average wait time of 18 minutes.
429 words, about 2 min2Choosing the Right Chart for a Mixed Audience
A logistics company must present quarterly performance to two audiences in one meeting: regional managers who need to compare 14 depots on on-time delivery, and the executive team who want the trend over eight quarters and the single worst-performing depot. The analyst has prepared a spreadsheet with on-time percentage per depot per quarter, plus delivery volume per depot.
390 words, about 2 min3The Survey That Proved the Wrong Thing
A retail chain runs a customer satisfaction survey after every purchase. Over one quarter it receives 4,200 responses out of 61,000 transactions.
371 words, about 2 min4Cleaning a Messy Import Under Deadline
A hospital finance team must submit a cost report in two days. The source is an export of 48,000 supplier invoice rows with these symptoms: dates appear in at least three formats (some as text 'DD/MM/YYYY', some as Excel serial numbers, some as 'YYYY-MM-DD'); supplier names have trailing spaces and inconsistent casing ('ACME Ltd', 'acme ltd ', 'Acme Limited'); amounts use a mix of '.' and ',' as decimal separators; and 1,100 rows have blank cost-centre codes.
400 words, about 2 min5The KPI That Drove the Wrong Behaviour
A software support team is measured on average ticket resolution time. To hit the target, agents have begun closing difficult tickets quickly and asking customers to reopen them if the issue persists, which resets the clock.
378 words, about 2 min