We all know the allure of diving deep into a dataset and generating some fascinating insight. But all too often, insights end up being interesting without actually being useful. For insights to deliver real value, they must drive action.
At Worklytics, we’ve dedicated substantial time to transforming passive organizational data into actionable insights. Over hundreds of cases, we’ve learned what makes an insight actionable. Here’s a guide of best practices to help ensure your insights lead to impactful change.
An example
In this guide, we’ll explore a common question we see organizations ask: Are we spending too much time in meetings?
This question is just one example, but the techniques below can apply broadly. So let’s start with a typical insight: Our teams spend 10 hours a week in meetings.
Interesting, sure—but how can we make it actionable?
Before generating any new insights, begin with a well-defined, high-priority problem that needs resolution. The fastest way to ensure an insight isn’t actionable is by providing one about an issue that no one cares about.
Sign You May Have Missed the Mark…
You’re chasing down your stakeholders to get a meeting set. If this is really a top priority, they’ll be beating down your door to get answers.
How to Do It Right:
You’ll Know You’re onto Something When…
You’ve identified a leader who’s pre-committed that she’ll do X if you find out Y.
Before an insight can be actionable, it must be trusted. If the insight is unflattering, people are even more likely to scrutinize its validity. If it’s not robust, trust in the entire analysis could erode.
Sign You May Have Missed the Mark…
They’re spending more time talking about your n than your insight.
Tactics to Build Trust:
You’ll Know You’re onto Something When…
Your resident skeptic refers to the project as “our” analysis.
Knowing that employees spend 10 hours a week in meetings isn’t enough. To decide whether to act, context is crucial. Is 10 hours excessive or reasonable? How does it compare to industry standards?
Sign You Missed the Mark…
You’re hearing crickets.
Ways to Contextualize Insights:
You’ll Know You’re onto Something When…
There’s a feeling of urgency. Stakeholders are pushing you to hustle up & get them answers fast.
Knowing where to direct action is vital. This involves understanding who and what are driving the issue.
Sign You’ve Missed the Mark…
You immediately get asked for a bunch of different data cuts.
Examples of Creating Insights for the Most Important Segments:
You’ll Know You’re onto Something When…
You’re using the same language and talking about the same segments as your stakeholder. You might even match your font and format to whatever their department prefers – after all, you’re a part of their team.
Now that you have a real problem, a trusted insight, a compelling narrative, and a focus for action, it’s time to intervene. Start by sharing this insight with those most empowered to make a change.
Sign You’ve Missed the Mark…
It’s been 4 weeks and nothing’s changed.
What Good Looks Like:
Within a week of receiving the insight, your stakeholder sends an email like this to Team Leads:
“We’ve looked into meeting time and found that the average employee spends around 10 hours a week—about 25% of their work time—in meetings. This is 30% more than comparable roles at other companies. We also found that employees who spend over 10 hours in meetings each week complete 40% fewer tasks. Additionally, the top 25% of meeting attendees are logging over 20 hours, which must be impacting their productivity. We’re reaching out because project managers and line leads account for 60% of these meetings. Let’s work together to develop an action plan to address this.”
You’ll Know You’re onto Something When…
Someone who wasn’t in the original meeting mentions the insight to you.
Taking action is a great first step, but changing behavior takes time and ongoing adjustment. A culture of continuous improvement is essential for lasting change.
Best Practices: