type
Post
status
Published
date
slug
good_enough
summary
tags
Reflection
Text
category
Knowledge
icon
password
Kia ora, whānau! Dr. Huang here. Let’s grab a virtual coffee. Lately, I ran into a pretty common but thought-provoking situation at work recently. I was reviewing a data project, saw clear potential to enhance its impact, and suggested some improvements. And guess what the response basically was? "Thanks, but we think it's good enough as it is. No need to spend more effort on changes."
That exact phrase, "good enough," really sparked a lot of thoughts for me. This standard, or perhaps this mindset, definitely doesn't just pop up during project reviews. I've realised that whether I'm pushing for better data utilisation in government, trying to 'upgrade' the behavioral patterns of my two teenagers at home, or even deciding when that DIY project in the garage is truly finished, this ghost of 'Good Enough' seems to be everywhere, constantly challenging us: do we settle for the status quo, or strive for something better?
Surviving the pressures and shifts in the public sector, including recent layoffs that have affected many colleagues, really makes you reflect. It sharpens the focus on what truly matters in data analytical work. Forget the glossy corporate jargon; this is a dad's-eye view, seasoned with data science, DIY mishaps, and the daily chaos of raising kids who find my spreadsheets less exciting than watching paint dry (even the fast-drying kind!).
The "Good Enough" Trap: Why Functionally Adequate Isn't Impactful
We data folks - data scientists/analysts/engineers often take pride in and strive for technical excellence: pursuing precise models, ensuring clean data, developing dashboards that slice and dice data six ways from Sunday. The products we deliver might seem technically flawless when judged solely against specs and checklists, ticking all the boxes. But does this alone truly deliver the desired impact? Often, the actual feedback received might just be a resounding 'meh,' falling far short of truly outstanding results.
Why does this happen? Because merely meeting technical specifications and surface-level requirements often results in something that's "functionally adequate but contextually barren." Judged by its actual impact, it ends up being just "good enough.". It's a bit like New Zealand's KiwiBuild initiative. From a technical standpoint, the goal was to build houses, and indeed, many houses compliant with building codes were constructed. But in its actual implementation, it encountered a series of real-world 'contextual' problems: a mismatch between location and demand, prices that remained too high for the target demographic (first-home buyers), and challenges in fully integrating these developments with existing community infrastructure and amenities. Technically, the houses were fine, but when it came to achieving the intended impact on the core goals of 'addressing housing affordability and meeting real market demand', it didn't quite fit the real-world situation or 'struggled to adapt'.
What Leaders Really Need (Hint: It's Not Just More Data)
So, what do leaders really want when they ask for a data product, especially in the public sector where trust and impact are paramount? Forget 'just good enough'. They're usually looking for:
- Actionable Insight, Not Just Raw Data: Leaders aren't short on data; they're often drowning in it. They need the 'So what?'. Simply delivering data doesn't guarantee its use; it needs to be embedded in decision-making processes and clearly answer strategic questions. Think of it as the difference between handing someone timber (data) versus blueprints and instructions (insight) for the bookshelf they need.
- A Compelling Narrative, Not Just Charts: Those articles you see about 'data storytelling'? They're onto something crucial. Numbers alone rarely inspire action or secure buy-in. You need context, a narrative that connects the dots and explains why it matters. Research confirms that stories make data more memorable and persuasive, helping to bridge the gap between analysis and action. It's translating complex data language (like kinetic chain reactions in gait analysis) into a human story that resonates. Just showing a dashboard isn't storytelling; that's like pointing at a dictionary and calling it a novel.
- Answers to the Next Question: The best data products anticipate follow-up questions. This requires stepping outside our technical bubble and genuinely understanding the leader’s strategic landscape, their pressures, the policy context (climate change, healthcare, education – each with its own lingo and goals). It’s like figuring out why your teenager is obsessed with a particular band – there’s usually a deeper layer.
- Robustness Under Pressure: Does the analysis hold up if conditions shift? Have we considered biases, ethical implications, or the 'technical debt' in our choices? Leaders need to trust the insights aren't fragile. Public sector work demands rigorous attention to data privacy and ethics; it's not just a checkbox but a core responsibility when handling citizens' information. We must also ensure our work aligns with Te Tiriti o Waitangi principles, respecting Māori data sovereignty – a non-negotiable aspect of integrity in Aotearoa. It’s like building a deck – it needs to withstand a classic Wellington southerly, not just sunshine.
Dr Huang's Approach: A Public Sector Data Workshop Mindset
My approach? Less 'data factory', more 'custom workshop', especially suited for the public sector environment:
- Embrace the Mission & Debug the Request: Remember why you're here. Public sector data is a public asset, meant to serve citizens. Treat the initial request like buggy code. What are the hidden assumptions? What policy goals are driving this? Talk to stakeholders – it’s ethnographic fieldwork to understand their world before designing the tool. Align your analysis with agency goals, not just flashy metrics.
- Build Data Literacy Bridges: Most colleagues aren't data fluent. Even your boss might struggle to interpret the data, let alone know what questions to ask. Frequently, the request you get is just: “I need the data on XXX, can you pull that for me?” Your job is translating complexity. Host 'data 101' workshops (less lecture, more play), sit in on policy meetings to listen, and use analogies. Explaining predictive modeling like planning a rugby play often clicks better than discussing algorithms. Increasing data literacy across government is fundamental for smarter decision-making.
- Prototype the Insight & Pilot Small (MVP Thinking): Forget the 'big reveal'. Share early findings, mock-ups, napkin sketches. Government isn't a startup, but agility matters. Start with small, outcome-focused pilots – like testing a tiny feature before scaling. Nail a quick win (e.g., cutting service wait times), show measurable impact, and broadcast that success to build buy-in. Use rapid prototyping with basic models on small datasets, then iterate. And remember, as discussed, your colleagues and leaders often don't even realise the potential of data. Putting something in front of them, even an imperfect prototype, is usually necessary to give them a concrete starting point. That's when they can grasp it, raise questions, and meaningful follow-up discussions can actually start.
- Master the Craft (Pragmatic Tools & Essential Skills):
- Tech Stack (Kiwi DIY Style): Embrace cost efficiency. Open source (Python, R) and accessible BI tools (Tableau, Power BI) are your mates. Focus on the tools that solve the problem effectively, like ensuring you can build that bookshelf rather than buying the fanciest drill. Seriously though, don't underestimate Excel. Why? Because it could very well be the only data tool your colleagues or boss are comfortable with. You can build the most sophisticated reports, but at the end of the day, you might still need to dump it into Excel just so they can approve or sign off on it.
- Data Wrangling is King: Get your hands dirty cleaning and preparing data. GIGO (Garbage In, Garbage Out) is real. Know the data inside out – like fixing a wonky fence, it takes effort but yields solid results.
- Visualization as Storytelling: Craft dashboards and reports that tell a compelling story, making insights accessible.
- Skills Beyond Code: Sharpen critical thinking (question data, scrutinize sources, identify bias), problem-solving (be a data detective), and communication (simplify, tailor your message, back it up). These are vital, just like figuring out if your teen really did their homework.
- Navigate the System & Yourself: Government has its complexities – silos, red tape, risk aversion. Navigate with empathy. Understand stakeholder fears and frame solutions as low-risk, high-reward. Be patient; culture shifts take time, like sanding rough wood. And optimize your personal OS. Set boundaries, reflect weekly ("What worked? What's my technical debt?"), lean on your network of fellow data nerds, and commit to lifelong learning. Avoid burnout; this work carries weight.
Final Thought: Data as a Craft for the Public Good
Being a data analyst in the public sector is like woodworking in my garage—messy, iterative, demanding patience, but deeply satisfying. You’re not just crunching numbers; you're crafting insights that shape society, contributing to something bigger. It can be challenging, but the stability can be welcome, and the work is undeniably meaningful.
Ultimately, moving beyond 'just good enough' requires empathy, communication, strategic thinking, and a commitment to understanding the context. It’s about optimizing our own 'delivery system' – a constant process of iteration, much like trying to be the kind of dad my kids might, one day, see as more than the guy who fixes the WiFi and occasionally burns the toast.
It’s a work in progress, both in the office and the garage. And that’s okay. The pursuit of 'better' is infinitely more rewarding than settling for 'good enough'.
Now, if you’ll excuse me, I think I hear the distinct sound of a teenager needing 'help' with their homework, which probably translates to a lecture on responsible screen time. Wish me luck… and happy data-ing!
中文版请点这里: