Everyone on your team is a data person

Short on time? Here's the gist.

Your team handles data every single day, whether they consider themselves "data people" or not. Frontline staff see what clients need, what programs accomplish, and where things get stuck. When you ask them to talk about or work with that data, you’re met with hesitation, worry, or silence.

This issue covers how to lower that friction, engage your colleagues without adding busywork, and help everyone see the practical value in what they already know.

Things that make you go hmmmm. 

Every person is a data person.

Everyone in your organization collects information about your mission, the quality of your services, and your impact. The front desk knows which days run busy and why. Program staff hear what clients say when no survey is in front of them. These colleagues hold insights and context that make sense of the numbers in your reports.


Most of them do not call themselves data people, because the picture in their heads includes databases, spreadsheets, trendlines, and KPIs. Your organization depends on their knowledge of whether or not a process captures it, and your data work improves when they see themselves as creators, stewards, and consumers of what you collect.

People carry data trauma.

Many people have lived through a system rollout that required hours of training and was replaced a year later. Some have used systems that made their jobs harder and made things harder for the people they serve.

  • A payroll system made time entry confusing and held up paychecks.

  • An intake form required every single field before saving, stranding staff and clients who did not have every answer. 

  • Direct service workers ended up troubleshooting software errors instead of helping people. 

  • Data was used against people.

Even if none of this happened at your organization or under your leadership, the hesitancy, anxiety, and concern shape how people respond to your next data request. A colleague who has been burned by a system will not volunteer as a data person until the work stops costing them something.

From the field

Each September, one organization re-enrolls its clients. The staff who handle data collection and entry also carry about 16 other job responsibilities. Forms came back incomplete, clients called the administrative office for help, and everyone ended up serving as tech support. Staff began to dread the month.

The organization spoke with staff to learn their three biggest pain points and designed the solutions together.

1. Volume. More than 100 forms were completed by hand. The organization brought in temporary staff for September and October.

2. Client questions about the online platform. Clients needed help navigating the site and understanding what the form questions meant, and their questions arrived while staff were handling other direct service work. The organization bought iPads and set them up at the front desk, opened the computer lab after work hours, and placed translators on site for the three most commonly spoken languages.

3. Feedback. The organization checked in with staff to find out whether the pain points had eased.

What changed.

  • Staff spent their time on the work they love, which lowered resentment toward the data and the system.

  • People felt heard, which made them more open to other conversations about data use.

  • Data forms contained fewer null values.

Putting it to work

Engage staff in solutioning.

Pause before you ask staff to adopt a new system or change a data process. An empathy map helps you see the work from their seat before you propose anything.

  1. Choose one role, such as the front desk coordinator or a program manager.

  2. Consider: what they see, what they think, what they do, and what they feel in their role.

  3. Mark the places where your assumptions and their experience might differ.

Get the empathy map.


Help your team see themselves as data people. 

Set aside time in an upcoming meeting for staff to share a personal annual report. Ask each person to pick one or two numbers that represent something meaningful to them from the past year, whether a personal habit, an athletic milestone, or a professional win. The activity shows staff that they already gather, summarize, and present information, and the exercise carries no connection to anyone’s performance.

Having staff think about and use personal data as a tool for storytelling can make future conversations about program metrics less intimidating.  Download our facilitation guide and staff template.

Are you struggling to help your team become data people? Schedule a call; we’re happy to chat and think things through with you.

Next
Next

Could your team explain this without you?