Getting your data ducks in a row
On my very first day, one of our directors asked if I’d ever used the rubber duck analogy. Amused by the name, I said I hadn’t.
He explained it as a technique where you talk through a coding or technical problem out loud, often to a rubber duck sitting on your desk. By explaining it step by step, you often uncover mistakes or gaps in your logic that you hadn’t noticed before. It’s a surprisingly effective method, especially when working with complex systems.
At this year’s #NHSconfedExpo, I spotted a fun display of rubber ducks and rushed over, assuming it was a tribute to this quirky debugging method. But the ducks weren’t there for that reason.
They were lined up neatly in rows, representing a different saying: “to have all your ducks in a row,” a reminder of the importance of being organised and thoroughly prepared before tackling a task.
Both ideas resonated with me, particularly when it comes to working with data.
Explaining your approach to a dataset, even if just out loud to yourself (or your duck), can help clarify assumptions, reveal flaws in your logic, and force you to think more critically. At the same time, having your “data ducks” in a row - that is ensuring your data is clean, complete, and structured correctly is essential for any kind of meaningful analysis. Without this foundation, insights can quickly become misleading or inaccurate.
Now, I keep my own rubber duck on my desk. It serves as both a conversation starter and a gentle reminder that whether you're debugging code or preparing a dataset, clarity and organisation go a long way.
If you’re curious to try it out but not sure where to begin, here’s a few helpful tips:
Find your “duck”
It doesn’t have to be a rubber duck. It could be a mug, a pen, a houseplant or anything that can be your silent listener.
State the problem clearly
Pretend your duck knows nothing about coding or what you're working on. Start from the beginning and explain what you're trying to do in plain language.
Talk through the steps
Go through your code or thought process line by line. Say out loud what each part is meant to do, as if you’re teaching it.
Listen to yourself
As you speak, you may notice things that don’t add up, or that you’ve misunderstood. That’s often where the problem lies.
Make adjustments as needed
Once you spot the issue, go ahead and tweak your code or plan. If you still can’t figure it out, you’ll have a much clearer understanding when you ask someone else!
Repeat when stuck
Don’t be afraid to do it again and again!
So whether you're knee-deep in code, analysing complex datasets, or just organising your thoughts, take a moment to talk it out. Sometimes, all you need is a duck, a bit of space to think, and the discipline to get your ducks in a row.