Most data mistakes aren't caused by bad code. They come from a rushed decision, a question nobody asked or a worry that never got mentioned. This is why the skills that keep data work honest and useful are mostly soft ones.

This article looks at six essential soft skills. Each is shown through a small scene from a task many teams do: pulling information from public websites to inform business decisions. You don't need to be technical to follow along. If you work with information in any form, this applies to you.

6 Essential Soft Skills for Working with Data

1. Critical thinking: ask whether you should, not only whether you can

   It's tempting to start with the tool. Someone says, "Let's track our competitors' prices," and by the afternoon a script is running. The better first move is a pause. What decision will the data support? How often will anyone look at it? Is there already a report, a feed or a colleague who has the answer?

   Take a marketing assistant asked to monitor rival prices every day. She asks what the team will do with the numbers and learns they only review pricing monthly, and a supplier already sends a monthly price list. Critical thinking and a two-minute question saved days of work.

   A habit worth copying: write your goal in one sentence before you begin. If you can't, you're not ready yet.

2. Problem-solving: expect things to change

   Websites get redesigned. Files arrive in new formats. A process that ran smoothly for months stops without warning. Good problem-solvers don't panic or paper over the gap. They work out what changed, test one fix at a time and write down what they learned.

   Picture an analyst whose weekly report suddenly shows blank fields after a site redesign. She could patch the output and hope nobody notices. Instead she pauses the job, finds the cause and tells her team the figures can't be trusted until it's fixed. That honesty costs a little embarrassment and prevents a lot of bad decisions.

   When something breaks, three questions help: what changed, what does it affect, and who needs to know?

3. Decision-making and risk assessment: weigh the cost before you act

   Every data project carries some risk. It might touch people's privacy, your organisation's reputation or the accuracy of whatever comes next. Strong decision-makers don't pretend risk away. They name it, judge how likely and how serious it is, and pick a proportionate response. Raising a concern early is a strength, not negativity.

   Imagine a team lead asked to collect contact details for a sales campaign. He asks whether personal information is really necessary. It isn't, so the team gathers company-level details only, and most of the risk disappears before any work begins.

   Try listing the worst realistic outcome, how likely it is and what would reduce it. Keep it brief, or nobody will use it.

4. Communication: bridge the gap between technical and non-technical colleagues

   A lot of data trouble starts with silence. The developer assumes the manager signed it off. The manager assumes the developer checked. Neither did, and nobody finds out until something goes wrong.

   Explaining your work in plain English closes that gap. Here's a fair test: if you can't describe your approach to a colleague outside your field, you may not understand it well enough to defend it. Listening matters as much as talking, so ask questions, repeat back what you've heard and welcome challenge.

   One small team agrees to share five facts before starting any new collection: the source, the pages or fields involved, how often it runs, where results are stored and whether any of it relates to individuals. Writing that note takes five minutes and heads off weeks of confusion.

   To practise, give a 30-second summary of your project to someone who knows nothing about it.

5. Attention to detail: good data needs good habits

   Accurate data rarely happens by accident. It comes from small habits repeated until they're automatic: checking samples, labelling files clearly, and recording where each value came from and when you collected it.

   Location is part of that. Many sites show different prices or content by country, so a team comparing rival prices across markets might use residential proxies from a provider like Byteful to see what local visitors see, and note which location each figure came from. When two numbers disagree, they can trace why in seconds.

   Those records protect you, too. When someone questions your numbers, you can show your working calmly. Over time, careful habits earn something harder to measure: other people's trust.

   An analyst who logs every data run, with an owner, what was collected and any errors, can answer "why do these two reports disagree?" in minutes rather than days. Give every task an owner and a date, because unowned work is where mistakes hide.

6. Ethical judgement: know when to raise a concern

   Not every problem is technical. Sometimes the question is whether something is fair, respectful or in keeping with the spirit of the rules, even when nobody has called it wrong. Following a website's terms of use and the law is the baseline. Rules change, so check current guidance rather than trusting your memory. If you're unsure where the line sits, ask a manager, a legal or compliance contact or a more experienced colleague.

   Speaking up takes nerve. Teams that make it easy, with no blame and no awkwardness, catch problems early.

   Consider a junior team member who notices a project has quietly grown beyond its original scope. It now covers far more sites and countries than anyone agreed, and nobody has reviewed the plan since. She could say nothing. Instead she raises it at the next check-in, and the team trims the project back.

   A simple team rule helps: anyone can pause a task to ask a question, and nobody gets criticised for it.

---

Conclusion: Responsible data starts with good judgement

These skills work as a loop: think, decide, communicate, check, review. A short monthly look at what went well, what went wrong and what nearly did is enough to keep it going. Start small by choosing one skill this month and practising it on your next task.

Technical knowledge lets you do the work. Soft skills help you do it well, in a way colleagues, clients and the public can trust.

Reflection questions

1. Which of these six skills do you use most confidently? Which would you like to develop?

2. Think of a recent task where a clearer question or a quick conversation would have saved time. What would you do differently?

3. Do people on your team feel comfortable saying "I'm not sure about this"?

---