Day 1 & Day 2 Reference Deck | Dr Caroline Ang, AI Growth Catalyst

100K+
Global Community
3K+
Engagements
200+
Organisations
39 yrs
Practice
Doctorate UWTSD · MBA Cardiff Met · Knight's Award 2023

"Most organisations have a thinking problem. Not a technology problem."
AI & Intelligence Systems — AI literacy, human-AI collaboration, governance, and decision intelligence
Corporate Governance & Strategy — Board advisory, risk, succession, and transformation
Executive Learning — Masterclasses for boards, C-suites, universities, and communities
Ventures & Ecosystem Building — Strategic advisor to ProppyApp, New Energy Valley, ITEC SEA
This programme sits at the intersection of two things I care deeply about — making data intelligence accessible to everyone, and helping people in career transition build real, marketable skills. You are not starting from zero. You are starting from experience.
C² Compass™ · C³ OS · C⁴ Ecosystem · linkedin.com/in/drcarolineang




linke.to/perkeso1
Slides are updated regularly — refresh the link for the latest version.

This programme is not about starting from zero. Every one of you brings real-world experience — industry knowledge, problem-solving habits, and an understanding of how organisations work. Data science is a set of structured thinking tools that lets you apply that experience more powerfully.
Over five days you will learn to ask sharper questions, work confidently with evidence, prepare and evaluate information, use AI tools responsibly, and communicate findings clearly. These are practical employability capabilities that employers across every sector value.

Introduction to Data Science
Data Collection & Preparation
Exploratory Data Analysis
Data Visualisation Techniques
Introduction to Machine Learning
Dr Caroline Ang facilitates Day 1 (Part 1) and Day 2 (Part 2). Appointed specialist trainers lead the sessions ahead. This deck is your reference for the full five-day arc, with a deep dive into the first two days.

Six participants, each with prior industry experience, now upskilling through PERKESO's Employment Insurance Scheme to build new, in-demand capabilities and re-enter the workforce with confidence.


Data science is not just programming or statistics. At its core, it is a disciplined way of turning raw, messy information into decisions that are grounded in evidence rather than gut feeling alone. It combines curiosity, critical thinking, domain knowledge and — yes — some tools and techniques.
Frame a clear, answerable question
Gather relevant, trustworthy data
Find patterns and test assumptions
Share findings to enable action
You do not need to be a programmer to contribute meaningfully to this process. Domain knowledge, careful thinking and clear communication are equally important skills.

AI did not make data scientists obsolete. It made data science accessible to everyone — including you.

Every responsible data project follows this arc. The goal is never to produce a chart or a model — the goal is to support a better decision and to learn from what happens next. Keep this framework in mind throughout all five days.

Look at the three statements below, drawn from the fictional JobSeeker360 Dataset. Discuss in pairs and decide how to classify each one.

A programme manager at an employment-support organisation notices something troubling: some professionals in career transition find new work within weeks, while others are still unemployed months later. The organisation has data, but no one has yet asked the right question.

The first instinct is to ask "How do we help people get jobs?" That is too broad to answer with data. Good data science begins with a precise, measurable and responsible question.
"How might we use training, job-search activity, skills and support-channel data to understand which re-employment pathways are associated with shorter time to placement, without claiming that an association proves causation?"
Notice what this question does well: it specifies the fields to examine, names the outcome of interest (time to placement), and explicitly guards against a common mistake — treating correlation as proof of cause.

You have a budget of ten tokens. Bid on the questions you believe are most useful and answerable with the JobSeeker360 Dataset. Discuss why some questions are more precise, more responsible or more actionable than others.
"How many participants completed at least one training course?"
"Why do participants in some skills categories take longer to find work?"
"Which participants are most likely to be placed within 60 days?"
"What support actions should the programme prioritise to reduce average placement time?"
After bidding, debrief: which question type is easiest to answer with data? Which carries the highest risk if answered carelessly?

Clarify the question and purpose
Gather data from appropriate sources
Clean, validate and structure the data
Identify patterns and anomalies
Apply statistical or machine-learning techniques
Present findings clearly
Support a decision or change
Evaluate outcomes and feed learning back to Define
Each stage feeds the next, and Review feeds back into Define. Skipping stages — particularly Prepare — is the most common cause of misleading analysis.

Each participant receives one card printed with a lifecycle stage. Working together, arrange the eight stages in the correct sequence and agree on what each stage produces as an output. Two mistake cards are hidden in the deck:
Building a model before checking the data. If the data contains errors, duplicates or missing values, the model will amplify those problems rather than solve them.
Assuming correlation proves cause. Two variables moving together does not mean one causes the other. Responsible analysts always separate association from causation in their language and their reports.
When you find a mistake card, explain to the group what went wrong and how the correct lifecycle stage would have caught the error earlier.

Before you can analyse data, you need to understand what kind of data you are working with. Different types require different handling and different analytical techniques.
Counts, measurements and amounts. Examples: days_to_placement, applications_submitted, interviews_attended.
Labels and groups. Examples: skills_category, industry_background, placement_status, support_channel.
Dates, timestamps and durations. Require consistent formatting. Example: enrolment dates stored in mixed formats cause errors.
Unstructured entries such as open comments. Harder to analyse, but rich in context. Requires careful handling before use.


Before closing this session, each participant drafts a personal problem statement using the template below. This will reopen the next session and anchor all the data-preparation work to a real question.
"We want to understand [outcome] so that [decision-maker] can [action]. We will use [data sources] and will avoid claiming that [association] proves [causation]."
"We will know we have answered the question when we can show [evidence] to [audience] in a way that supports [responsible action]."
Keep your problem statement visible. It is the compass for everything that follows over the next four days.

Day 2 | Facilitated by Dr Caroline Ang

We begin Day 2 by returning to the problem statement you drafted yesterday. Before any data can be collected, cleaned or analysed, the question must be clear enough to define exactly what data you need and what quality that data must meet.
You identified a focused, responsible question about career transition pathways. Today, we translate that question into specific data requirements.
By the end of today, you will produce a data-readiness note that certifies whether the synthetic dataset is ready to pass to the next trainer for Exploratory Data Analysis.

This is a synthetic, fictional dataset created for training purposes only. It does not represent actual real participant records, real participants or real outcomes. It is designed to look realistic so that you can practise genuine data-preparation skills.

You receive a copy of the JobSeeker360 Dataset that has not been validated. It contains six categories of problem, each of which could distort any analysis built on top of it.
The same participant appears more than once, inflating counts.
"IT" and "Information Technology" treated as different categories.
Blank cells in placement_status and days_to_placement.
Some entries use DD/MM/YYYY, others MM-DD-YY.
Negative values in applications_submitted and days_to_placement.
Does "placement" mean employed, or simply referred to an employer?

Working in three pairs, each team investigates a different category of data problem in the synthetic spreadsheet. You have 20 minutes to find as many issues as possible, document what you find and propose a resolution.
Find all rows where key fields are blank. Identify any participant IDs that appear more than once. Decide whether to remove duplicates or flag them for review.
Find all inconsistent category labels (e.g. "IT" vs "Information Technology"). Identify date entries that use a different format. Propose a standard label set and a single date format.
Find any numerical entries that seem implausible. Identify any field whose meaning is ambiguous. Draft a proposed definition for each unclear field.


Before passing data to any analytical stage, check it against all six dimensions. A single unchecked dimension can undermine an otherwise well-conducted analysis.

Not every field in a dataset earns its place. Some fields are essential to answering the question; some are useful but not critical; some are sensitive and require justification; and some add noise without adding insight. Review each field in the JobSeeker360 Dataset and assign it a status.
Document your decisions. They become part of your data-readiness note at the end of Day 2.

A data dictionary is the contract between the people who create the data and the people who analyse it. Without it, two analysts can interpret the same field in entirely different ways and reach entirely different conclusions.
The exact column name as it appears in the file. No abbreviations or alternative spellings.
A plain-language explanation of what the field means and how it was collected.
Numerical, categorical, date, or free text. Specifies how the field should be stored and handled.
The complete list of valid entries, or the valid numerical range. Anything outside this range is an error.
Who is responsible for this field and where the data comes from. Essential for traceability.

Five fields from the JobSeeker360 Dataset go on trial. Each round, four participants take a role and debate the correct definition before the group reaches a verdict.
Argues for the definition that makes the field most useful for analysis
Explains how the field was actually collected and what the original intent was
Asks whether the definition supports the programme's reporting needs
Offers a suggested definition based on common conventions — but the group must verify it
Fields on trial: training_completed, placement_status, days_to_placement, support_channel, locality. For each field, the group votes on the final accepted definition.

Upload the synthetic JobSeeker360 Dataset to ChatGPT Data Analysis. Ask it to report on data quality before any analysis begins. A responsible inspection prompt looks like this:
"You are a data quality assistant. Please inspect this file and report: row count, column names, data types, missing values per column, duplicate rows, inconsistent category labels, suspicious numerical values, date-format issues and any fields whose meaning is unclear. Do not make recommendations or draw conclusions until I ask you to."
ChatGPT should return a structured report. Review it carefully: it may miss issues, invent plausible-sounding values or misidentify data types. Treat its output as a first draft, not a final audit.

A Custom GPT is a version of ChatGPT configured with specific instructions so that it behaves consistently for a defined task. The fictional Data Readiness Coach is configured with four standing rules:
Never attempt analysis before reporting on the state of the data.
No jargon. Any team member should be able to understand the report.
Clearly label what is observed, what is inferred and what is unknown.
Confirm with the user before deleting rows, relabelling categories or imputing missing values.

A ChatGPT Project is a persistent workspace where you can store files, chat history, custom instructions and saved outputs together. For this programme, a project workspace might contain:

Gemini Notebook is a research and briefing workspace. You upload reference documents and ask questions that Gemini answers using only those sources — citing each claim back to its origin. This makes it ideal for learning, summarising and preparing briefing notes from trusted materials.
"Using only the uploaded sources, explain what each field in this data dictionary means, identify any missing definitions, and produce a short briefing for a beginner. Cite the source for each material statement. If the sources do not answer a question, say that the information is not available."
For this programme, upload the DS2010 course outline, the synthetic data dictionary, a short methodology note and a permitted reference document. Gemini Notebook is not the primary numerical data-analysis engine — use ChatGPT or Manus for calculations and statistics.

Manus is an AI agent that can handle an end-to-end workflow: inspect data, identify patterns, generate visualisations, write explanatory text and produce a presentation-ready brief — all from a single structured prompt.
Ask Manus to audit the prepared synthetic dataset for quality issues
Ask it to report no more than three evidence-based patterns, clearly labelled as observations
Ask it to create one simple visual summary, such as placement status by support channel
Ask it to write a plain-language explanation of the visual for a non-technical reader
Ask it to produce a short decision brief that separates observed results, possible interpretations and unknowns


Is this AI use clearly justified by the task?
Does the data contain anything that could identify a real person?
Has the data been validated before being fed to the model?
What assumptions has the AI made that have not been stated?
Continued on next slide →

Questions 5–8
Has a person checked the output before it is shared or acted upon?
Could this output disadvantage any group or individual unfairly?
Can you explain how the finding was reached in plain language?
Is there a record of the data, tool, prompt and output used?

At the end of Day 2, each group prepares a data-readiness note — a short, structured document that certifies the state of the dataset before it is handed to the next trainer. This mirrors professional data-handover practice.
Continued on next slide →


Working as a full group, complete the data-readiness note for the synthetic JobSeeker360 Dataset. Each pair contributes one section based on their Escape Room findings. The group then reads the note aloud and votes: Ready, Ready with conditions, or Not ready — more work needed.
The dataset moves to EDA. The note travels with it as the official record of what was done, what was assumed and what remains unresolved.
Identify the single most important issue to resolve first. Agree who is responsible and what a resolution looks like. This is realistic — most datasets need at least one iteration before analysis can begin responsibly.

Day 3 | Delivered by an appointed specialist trainer

Exploratory Data Analysis (EDA) is the stage where you look systematically at patterns, distributions, relationships and anomalies in the cleaned dataset. EDA asks what is happening — it does not automatically tell you why it is happening. Interpretation requires domain knowledge and careful reasoning.
How are values spread across a field? Are most participants placed within 30 days, or is the spread wide?
Do placement rates differ by support channel or skills category? EDA surfaces these differences for further investigation.
Which data points fall far outside the typical range? Are they errors, or genuinely unusual cases worth understanding?
The next trainer will guide you through structured EDA using the cleaned dataset you prepared and handed over at the end of Day 2.

Day 4 | Delivered by an appointed specialist trainer

In Day 4, you will learn the principles of effective data visualisation: choosing the right chart type, designing for clarity, and avoiding common misrepresentations. As a preview, consider how one validated finding from EDA might be communicated visually.
Suppose EDA reveals that participants who used online support channels were placed faster than those who used in-person channels. A simple grouped bar chart — placement status by support channel — communicates this finding in seconds to a decision-maker who has not read the analysis. Using a tool such as Manus, you can generate a draft of this chart from your prepared data and then refine it in Day 4.

Day 5 | Delivered by an appointed specialist trainer

Machine learning (ML) uses patterns in historical data to make predictions about new cases. In our career transition context, a simple classification model might prioritise which participants may benefit most from additional support — based on features such as training completion, number of applications and support channel used.
An input variable the model uses — e.g. training_completed, applications_submitted
The outcome the model is trained to predict — e.g. placement_status
The model's output for a new, unseen participant
Model predicts "needs support" but participant would have been placed without it
Model predicts "on track" but participant actually needs support

The data-readiness note you produce at the end of Day 2 travels with the dataset through the sessions ahead. It is your professional contribution to the full analytical pipeline.

Reusable tools for post-class practice, independent study and your first role.

Copy, adapt and reuse these prompts in your own projects. Always replace the bracketed placeholders with your actual context.
"Inspect this dataset and report: row count, column names, data types, missing values, duplicate rows, inconsistent labels, suspicious values and unclear fields. Do not recommend actions yet."
"Inspect the attached data, identify no more than three evidence-based patterns, create one simple visual summary of [finding], explain the visual in plain language, and produce a short decision brief that separates observed results, possible interpretations and unknowns."
Continued on next slide →

Copy, adapt and reuse these prompts in your own projects. Always replace the bracketed placeholders with your actual context.
"Using only the uploaded sources, explain what each field in this data dictionary means, identify any missing definitions, and produce a short briefing for a beginner. Cite the source for each material statement. If the sources do not answer a question, say that the information is not available."
"Separate your response into three sections: (1) what the data clearly shows, (2) what might be inferred but requires further investigation, and (3) what is unknown or not addressed by this data. Do not mix observations with interpretations."



State the question this dataset was prepared to help answer. One or two sentences.
File name, date, and version number of the file being handed over.
List every retained field with a one-line justification for its inclusion.
Describe every cleaning action: duplicates removed, labels standardised, formats corrected.
List problems that were identified but not fully resolved. Be specific.
Record every decision made where the data did not make the answer clear.
What can this dataset NOT answer? Where might it be incomplete or biased?
Flag any sensitive fields and describe how they were handled.
List every outstanding question that requires a human decision before EDA begins.

Take ten minutes before leaving today to reflect on your learning journey so far. Use the questions below as prompts — honest reflection is one of the most effective learning strategies you can practise.
Which concept or activity gave you the clearest "aha" moment? Why did it click?
Where did you feel uncertain or confused? Naming the gap is the first step to closing it.
Identify one concrete action you will take in the next two weeks — a prompt to test, a dataset to inspect, a question to ask.
What question are you most curious about as you move into EDA, visualisation and machine learning?
Name one way data literacy could strengthen your value in your next role or industry.

You have built a solid foundation over the sessions so far. Here is what the appointed specialist trainers will take you through next, building directly on the cleaned dataset and problem statement you have prepared.
Systematically examine the cleaned dataset. Surface patterns, distributions, group differences and outliers. Learn to distinguish observation from interpretation.
Choose the right chart for each finding. Design for clarity and honesty. Use visualisation tools to communicate insights to decision-makers who were not in the room.
Build your first classification example. Understand features, labels, predictions and errors. Learn when to use ML — and when human judgement must take precedence.
Good analysis begins before the analysis. The work you did on Days 1 and 2 makes everything that follows more reliable, more honest and more useful.

This cohort unites professionals from various fields, including content moderation and 3D animation. They are all upskilling through PERKESO's Employment Insurance Scheme, bringing rich, diverse experiences to their learning journey.

In data science, diverse industry backgrounds are a profound strength. Your unique experiences provide invaluable perspectives, helping you identify critical insights and ask pertinent questions, enhancing outcomes beyond what a pure technician might achieve.
Classification & Evaluation. Understanding harmful patterns and human judgement at scale is directly relevant to data labelling and model evaluation.
Visual Storytelling & Spatial Reasoning. Expertise in rendering pipelines is directly relevant to data visualisation and communicating complex findings.
Domain Knowledge. Whatever your background, your specific domain knowledge helps you ask better questions and find more relevant insights than a pure technician could.

All tools demonstrated today are free to use. We will walk through each one live using the JobSeeker360 Dataset as our working example.

Click "+" and upload your CSV file.
Ask ChatGPT to describe rows, columns, and fields.
Ask which sector has the highest time-to-employment.
Request a bar chart by age group.
Download the generated chart as an image.
Note: ChatGPT writes Python behind the scenes — you just ask.

Gemini Notebook (formerly NotebookLM) lets you upload multiple documents and ask questions that are answered only from those sources — with citations. It now also runs code for data analysis (Ultra/Pro users).
Research papers, reports, policy documents
Google Sheets and Excel/CSV data files
Google Docs and Microsoft Word/PowerPoint files
Video transcripts and web page content
Recorded interviews, lectures, and podcasts
Note: All answers are grounded in your uploaded sources — Gemini will not hallucinate beyond them.

Note: Each answer includes a citation — click it to see exactly which source it came from.

Extract key statistics or summarise any uploaded document.
Ask Claude what changed between two document versions.
Turn EDA findings into a one-page executive brief.
Verify that your conclusion logically follows from the data.
Note: Claude can also output Excel, Word, and PowerPoint files.

Manus is an autonomous AI agent. You give it a task and it works through it step by step — browsing, writing code, generating charts, and producing a final report — without you needing to guide each step.
Sign up at manus.im (free — 300 credits/day)
Start a new task: "Analyse this CSV file. Identify the top 3 factors associated with faster re-employment. Produce a 1-page visual summary."
Manus inspects the data, writes Python, generates charts, and writes explanatory text.
Download the finished report as a PDF or presentation.
Think of Manus as a junior analyst who works overnight and hands you a finished brief in the morning.
Note: Free plan uses Manus 1.6 Lite. Complex multi-step tasks may consume credits quickly — keep tasks focused.

Gamma is not just for presentations. You can use it to turn raw data findings, PDFs, or notes into a polished, shareable report in minutes.
A Gamma report is responsive, mobile-friendly, and always up to date — unlike a static PDF.
Live demo steps on next slide →

Here are my EDA findings: [paste 3 bullet points from your analysis]Turn this into a 3-section report with a summary, a chart, and a recommendationNote: Your report is live instantly — no download, no file attachment needed.

Most job seekers treat LinkedIn as a digital CV — something you set up and forget. But LinkedIn generates rich, real-time data about how visible you are, who is finding you, and whether your profile is working. Learning to read that data is a data science skill in itself.
Your headline, summary, skills, and experience are structured data fields. Each one is indexed and searchable.
Post impressions, comments, reactions, and shares tell you what content resonates with your target audience.
Who viewed your profile, what industry they are in, what job title they hold — this is your market research, for free.

Look at the four key metrics on screen. What story do you think the data is telling?

A 299% spike means one post dramatically outperformed your baseline. Which post was it? What made it different? That is your content data telling you what to repeat.
Steady but slow. 1% weekly = ~63 new followers. The real question: are they recruiters, peers, or potential clients in your target industry?
174% more people visited your profile vs the prior week. Something triggered this — a viral post, a comment on someone else's post, or a new connection sharing your profile.
You appeared in 61 searches but growth is flat. This means your keywords are working — but not expanding. Time to add new skills or update your headline.
Note: Each number is a data point. Together they form a story about visibility, relevance, and momentum.

Ask: "Score my LinkedIn headline and summary out of 10. What are the top 3 things to change?"
Ask: "What keywords am I missing that recruiters would search for in this role?"
Ask: "Write 5 LinkedIn headlines for someone upskilling in data science. Make them searchable and human."
Ask: "What story do these LinkedIn metrics tell? What should I do differently this week?"
Your LinkedIn profile is not a document — it is a living dataset. Treat it like one.

Most job seekers apply and hope. Data-savvy job seekers analyse first. Before sending a single application, you can use AI to map exactly what the market wants — and how well your current profile matches it.
Scrape and analyse 10–20 job listings for your target role. Find the most common required skills, keywords, and qualifications. This is real data.
Compare your resume against those job listings. Identify what you have, what you're missing, and what to prioritise learning next.
Use ChatGPT or Claude as a personal career coach. Feed it your resume and a job description. Ask it to interview you, score your fit, and give you a development plan.

Go to LinkedIn Jobs, JobStreet, or Indeed. Search "Data Analyst Malaysia". Copy the full text of 10 job descriptions into a single document.
Paste all 10 job descriptions. Ask: "Analyse these 10 job descriptions. List the top 10 most frequently required skills, tools, and qualifications. Show me the frequency of each."
ChatGPT will return a ranked list. Common findings: Excel (9/10), SQL (8/10), Python (6/10), Power BI (7/10), communication skills (10/10). This IS data science — applied to your own career.
Ask: "Which of these skills appear in more than 70% of listings? Which are mentioned but not required?" Now you have a prioritised learning roadmap.
Note: You just did a frequency analysis on real market data. That is EDA applied to your job search.

Paste your resume + one job description into Claude or ChatGPT. Use this exact prompt:
"You are a senior recruiter for a data analytics role in Malaysia. I will give you a job description and my resume. Score my fit out of 100. List: (1) my strengths for this role, (2) the gaps I need to close, (3) the top 3 skills I should learn next, and (4) one sentence I should add to my LinkedIn summary to better match this role."Take it further — ask AI to simulate a job interview:
"Based on my resume and this job description, ask me the 5 most likely interview questions for this role. After I answer each one, give me feedback on how a recruiter would score my answer."This is not cheating — this is data-driven career strategy. Every competitive job seeker should be doing this.

Go to JobStreet or LinkedIn. Find one real job listing for your target role. Paste it + your resume into ChatGPT. Ask for a fit score and top 3 gaps. Share your score with the group.
Search "Data Analyst Malaysia" on LinkedIn Jobs. Copy 5 job descriptions. Ask ChatGPT: "What are the top 5 skills that appear across all these listings?" Use the answer to shortlist what to learn first.
Paste your resume into Claude. Ask: "What role do you think I am best suited for in data science, based on my background? Then ask me 3 interview questions for that role."
What was the most surprising thing AI told you about your own profile?

Each tool has a sweet spot. Use this as a quick reference when you are deciding which AI to reach for.

Upload the CSV and screenshot your best chart.
Upload CSV, ask about career transitions, generate Audio Overview.
Paste findings and ask Claude for a 200-word summary.
Debrief: What surprised you?

You do not need to wait for a full-time data role to start earning with data skills. Freelance platforms let you take on small, paid projects while you are still learning — building your portfolio and income at the same time.
Your first freelance project does not need to be perfect — it needs to exist. Every expert started with their first RM50 gig.

AI tools handle the mechanical work. You define the question, interpret the result, and make the decision. That judgment cannot be automated.
Pick one tool. Try one task. The goal today is not mastery — it is familiarity. Mastery comes from repeated use on real problems.
A content moderator sees bias risks others miss. A 3D animator communicates findings visually. Your prior career is not baggage — it is your competitive advantage in data science.
The best data scientist in the room is not the one who knows the most code — it is the one who asks the best questions.

Data Science Foundation