Your organization may have more information than ever.
Financial reports. Customer feedback. Employee surveys. Performance dashboards. Program evaluations.
Yet the same challenges keep showing up.
Priorities remain unclear. Teams repeat work that isn’t producing the desired outcome. Leaders review the numbers, then leave the meeting without a clear decision.
Data is available, but it isn’t translating into better results.
That is a leadership challenge worth examining.
Behind the numbers are people and choices
A turnover rate represents people leaving—and the experience of those who remain. A missed deadline may reflect unclear expectations, competing priorities, or a process that needs attention. Customer feedback offers a glimpse into how people experience your organization.
Data gives you signals. Understanding those signals requires context, curiosity, and conversation.
An increase in complaints might mean service is slipping. It might also mean more customers are using a newly accessible feedback channel. The number alone cannot tell you which.
Before acting, ask: What is this information helping us see, and what do we still need to understand?
Start with the outcome you want to improve
It is easy to build a meeting around whatever appears on the dashboard.
A more useful starting point is: What does success look like, and what do we need to know to move toward it?
For a business, that might mean profitable growth and a customer experience that brings people back. For a school or nonprofit, it may mean stronger outcomes for the people you serve. Across organizations, it may include a capable team, dependable execution, and sustainable use of resources.
Be specific enough to distinguish activity from progress.
The number of people who attended a training tells you about participation. Whether they apply the skill effectively tells you more about the result.
Both can be useful. They answer different questions.
Turn information into a leadership conversation
You don’t need a complicated process to begin. You need a few useful questions and the discipline to follow through.
1. What are we noticing?
Look for patterns, changes, gaps, and unexpected strengths. Compare the information with your desired outcome and an appropriate point of reference.
Check its quality, too. Is it current? Are definitions consistent? Who or what might be missing?
An average can also hide meaningful differences between teams, locations, or groups.
2. What might explain it?
Invite the people closest to the work into the conversation.
Separate what you know from what you suspect. Consider more than one explanation before choosing a solution.
If response times have increased, is demand higher? Are requests more complex? Are handoffs slowing things down? Is the team working with insufficient resources?
Different explanations call for different actions.
3. What matters most now?
Every finding does not require an immediate initiative.
Consider its effect on your mission, people, performance, and capacity. Identify the issue or opportunity that deserves attention first.
This is where data informs judgment—and leaders establish priorities.
4. What will we do differently?
Turn the insight into a clear decision or a focused test.
Define the action, who owns it, what support they need, and when you will review it.
“Improve communication” is difficult to execute.
“Assign an owner to each incoming request and confirm the next step within one business day” gives people something concrete to do.
5. How will we know whether it helped?
Choose a measure connected to the outcome. Establish a review date that gives the action a reasonable opportunity to work.
Look for unintended effects as well. Faster responses are useful, but not if accuracy or service quality declines.
Then decide whether to continue, adjust, stop, or learn more.
A practical example
Suppose a service organization sees declining customer satisfaction and longer response times.
The team reviews recent cases and hears from employees handling the requests. They discover that requests move between departments without clear ownership.
They test a change: one accountable owner for each request, with an agreed handoff process.
At the review, they examine response times, customer feedback, reopened requests, and the effect on employee workload.
The useful result is a better way of working, informed by evidence and refined through practice.
Build a rhythm for learning and action
Data becomes more useful when teams can discuss what it reveals, question assumptions, and act on what they learn.
When reviewing results becomes a search for someone to blame, people may become less willing to surface problems early.
Clear expectations and honest learning can work together. So can accountability and curiosity.
At UYES, I help leaders understand what’s happening, clarify what success looks like, and choose the best path forward. Data is one input, alongside the experience of your people and the realities of your organization.
What decision, action, or improvement will come from the information you already have?
If your organization has plenty of data but needs clearer next steps, share what you’re navigating. I’d be glad to help you think it through