Start here
Two short modules for complete beginners: read a work table, then turn a colleague's request into a number people can use. No coding: you work on the data of Raket Parts, a fictional maker of rocket parts.
You will be able to
- read a work table and say what one row stands for
- name the system a record comes from
- read blanks, codes and dates
- turn a colleague's request into the right count and reply clearly
What data looks like at work
Read a work table, say what one row stands for, name the system a record comes from and read its blanks, codes and dates.
Why your team uses data
Turn a colleague's request into the right count, check a belief against the data and reply with the number, what it counts and its period.
Start here / Module 1
What data looks like at work
It is your first week at Raket Parts, and colleagues start sending you lists. Learn to read a table, say what one row stands for, see where the data comes from and read blanks, codes and dates.
Sections
Start here / Module 1 / Free practice
Try it on your own question
Run it in the practice editor
The practice editors have the Raket Parts tables loaded. Type a query or a formula, run it and change it as often as you like. Nothing is marked.
Start here / Module 2
Why your team uses data
Most data work starts with a message: someone needs a number, for a reason, by a deadline. Learn to read the request, let the reason decide what you count, check a hunch, and send back an answer people can use.
This module builds on module 1. If you are new to this, start with module 1.
Sections
Start here / Module 2 / Free practice
Try it on your own question
Run it in the practice editor
The practice editors have the Raket Parts tables loaded. Type a query or a formula, run it and change it as often as you like. Nothing is marked.
Start here / Module 1 / 1.2
1.2 What one row means
Section 1.2 complete
Next: 1.3 Where data comes from
Start here / Module 1 / 1.3
1.3 Where data comes from
Section 1.3 complete
Next: 1.4 Blanks, codes and dates
Start here / Module 1 / 1.4
1.4 Blanks, codes and dates
Section 1.4 complete
Next: Module 1 check
Continue to the module check Recap this section Back to module 1
Start here / Module 1 / Check
Module 1 check
Module 1 complete
Next: Module 2, Why your team uses data
Continue to module 2 Try it on your own question Recap module 1 Back to module 1
Start here / Module 2 / 2.2
2.2 Why they asked
Section 2.2 complete
Next: 2.3 Data checks a hunch
Start here / Module 2 / 2.3
2.3 Data checks a hunch
Section 2.3 complete
Next: 2.4 Send the answer back
Start here / Module 2 / 2.4
2.4 Send the answer back
Section 2.4 complete
Next: Module 2 check
Continue to the module check Recap this section Back to module 2
Start here / Module 2 / Check
Module 2 check
Module 2 complete
Next, choose your Path
Next, choose your Path Try it on your own question Recap module 2 Back to module 2
Start here / Module 1 / Recap
Recap card
1.1 Rows and columns
Rows and columns
- Row: runs across and records one thing
- Column: runs down and holds one kind of fact
Common mistake
Reading down for one record. To find X-RET-0020's quantity, find its row, then read across.
Start here / Module 1 / Recap
Recap card
1.2 What one row means
What one row means
- Say it first: one row is one …
- Count rows for that thing, count different codes for anything else
Common mistake
Rows taken for customers. 83 service cases came from 50 customers.
Start here / Module 1 / Recap
Recap card
1.3 Where data comes from
Where data comes from
- A moment at work writes each row
- Each system holds its own team's records
Common mistake
Asking the wrong team. Delivery messages sit in X-CARRIER; online orders in X-WEBSHOP.
Start here / Module 1 / Recap
Recap card
1.4 Blanks, codes and dates
Blanks, codes and dates
- Code: names one thing on every list
- Date: year, month, day
- Blank: not recorded yet
Common mistake
Turning a blank into zero. 317 deliveries have no time recorded; that does not mean they failed.
Start here / Module 1 / Recap
Recap card
Module 1: What data looks like at work
Rows and columns
- Row: runs across and records one thing
- Column: runs down and holds one kind of fact
Common mistake
Reading down for one record. To find X-RET-0020's quantity, find its row, then read across.
What one row means
- Say it first: one row is one …
- Count rows for that thing, count different codes for anything else
Common mistake
Rows taken for customers. 83 service cases came from 50 customers.
Where data comes from
- A moment at work writes each row
- Each system holds its own team's records
Common mistake
Asking the wrong team. Delivery messages sit in X-CARRIER; online orders in X-WEBSHOP.
Blanks, codes and dates
- Code: names one thing on every list
- Date: year, month, day
- Blank: not recorded yet
Common mistake
Turning a blank into zero. 317 deliveries have no time recorded; that does not mean they failed.
Start here / Module 2 / Recap
Recap card
2.1 A number someone asked for
A number someone asked for
- A clear request: what to count, the period, the reason
- Missing part: ask before you count
Common mistake
Guessing the period. "How many enquiries by phone?" needs a month, quarter or year first.
Start here / Module 2 / Recap
Recap card
2.2 Why they asked
Why they asked
- The reason decides which rows you count
- No reason given: ask for it
Common mistake
One number for every asker. From 54 returns, Mira needed 11 and Teun 29.
Start here / Module 2 / Recap
Recap card
2.3 Data checks a hunch
Data checks a hunch
- Hunch: a belief from experience, to check
- Data checks it; a person decides
Common mistake
Checking one measure only. 6 of 436 customers, yet 72.8% of invoiced sales.
Start here / Module 2 / Recap
Recap card
2.4 Send the answer back
Send the answer back
- Clear reply: number, what it counts, period
- Limit: one line on what it does not show
Common mistake
Sending a bare number. "129" leaves Bram asking what and when.
Start here / Module 2 / Recap
Recap card
Module 2: Why your team uses data
A number someone asked for
- A clear request: what to count, the period, the reason
- Missing part: ask before you count
Common mistake
Guessing the period. "How many enquiries by phone?" needs a month, quarter or year first.
Why they asked
- The reason decides which rows you count
- No reason given: ask for it
Common mistake
One number for every asker. From 54 returns, Mira needed 11 and Teun 29.
Data checks a hunch
- Hunch: a belief from experience, to check
- Data checks it; a person decides
Common mistake
Checking one measure only. 6 of 436 customers, yet 72.8% of invoiced sales.
Send the answer back
- Clear reply: number, what it counts, period
- Limit: one line on what it does not show
Common mistake
Sending a bare number. "129" leaves Bram asking what and when.