Why can I handle clean data but not messy data?

You can run the analysis once someone hands you a clean file. But when the data arrives messy — missing columns, inconsistent labels, duplicate rows — you stall. Your team waits. You feel exposed. This is not a skill you lack. Cleaning messy data is a series of small decisions, made in order — not one leap of genius. You have quietly decided that messiness must be solved before the real work begins. It is the real work. With others watching, the stall gets worse. Everyone defers to whoever seems comfortable with the mess. Someone must simply start making decisions, out loud, so the rest can follow or correct. That can be you.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

The block is less about missing technique and more about refusing to act before certainty, so coaching toward a first move matters more than more teaching.

How the two dials adapt to you →

What’s really going on

Messy data does not defeat you. The wait for clean data does. You have been taught to expect order before you act. Choose one small, ugly piece of the dataset today, not all of it, and clean that one piece. Competence is built in that choice, repeated, not in waiting for clarity.

🔒 What you’ll build togetherUnlock by starting

A movePick one messy file this week. Do not wait for a clean one. List every problem you see — missing values, wrong types, duplicates — in plain language, in front of your pod.

A moveFix the smallest problem first, out loud. Say why you dropped that row or renamed that column. Let others see the reasoning, not just the result.

A moveAssign one person to take the 'first cut' on any messy dataset your pod touches. Rotate this job. No one gets to always wait for someone else to go first.

A moveWhen you hit a decision you cannot justify — keep the row or drop it — write down the question and move on. One unresolved choice should not stop the whole file.

A moveAfter each messy dataset, write three lines: what was wrong, what you did, what you'd do faster next time. Share it with your pod.

PractiseThe First Cut · a Pod of 4 · 30 min

What changes unlock by starting

You open a messy file and start within minutes, instead of waiting for someone to clean it first.
Your pod sees your reasoning, not just your results, and starts trusting your judgment with ambiguity.
You build a short list of standard moves for common messes, so you stop solving the same problem from scratch each time.
Your team stops stalling together, because someone always takes the first cut without a debate.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.