Translating Findings Into Strategic Direction - How data becomes direction and direction becomes action
In our work with mission-driven organizations, we spend a lot of time listening. We design focus groups. We conduct interviews. We develop and administer surveys. We sit with stakeholders across roles, identities, and experiences. By the end of the project, we are often holding hundreds of pages of notes, transcripts, and data points. (No, really – a current project in process has 518 pages of transcripts and notes alone!)
And then comes the moment that matters most: How do we translate what we heard into something that actually moves an organization forward? Because raw findings, even insightful ones, are not the goal. Strategic direction is.
From Data to Meaning: Identifying the Signal
Before we can develop strategy, we have to interpret what we heard. This means moving from:
Individual comments → patterns
Patterns → themes
Themes → meaning
For example:
Individual comment: “Every office does things differently, so I never know where to go.”
Pattern: Inconsistent processes and decentralized information
Theme: Lack of clarity and coordination across units
But this still isn’t enough. The key question now becomes: What does this mean for how the organization needs to operate differently?
Translating Findings Into Strategic Language
Strategic language does three things really well: (1) it captures the essence of the finding; (2) it points toward a future state; and (3) it creates a bridge to action. Let’s look at some deeper examples of how that translation works in practice. It’s important to note that we wouldn’t assume a theme or shape strategic language based on a single finding or comment; but, for the sake of these scenarios, assume that the “Finding” is one example of a prevalent theme in the dataset.
Example 1: Communication
Finding: “Information lives in too many places. I hear things too late, or not at all, and it makes me feel left out.”
What it Means: Communication is fragmented, inconsistent, and reactive.
Strategic Language: Develop and implement an integrated communication ecosystem that ensures timely, accessible, and coordinated information sharing across the organization.
Notice the shift that happened. We moved from a complaint to identifying a system-level issue. We moved from looking at a past experience to visualizing an ideal, future state. And we went from a vague frustration to a clear, specific station with direction and action.
Example 2: Student Experience
Finding: “I felt supported when I first got here, but after that, I kinda had to start figuring things out on my own.”
What it Means: Strong onboarding, but weak ongoing engagement and consistent support.
Strategic Language: “Design a holistic student experience model that extends beyond onboarding to provide sustained, proactive support across the student lifecycle.”
This moves the insight from a moment in time to a full lifecycle approach.
Example 3: Organizational Silos
Finding: “We are all doing good work, but we’re just not doing it together. I don’t even know half the people in my department.”
What it Means: Limited cross-functional collaboration and shared ownership, which may result in a lack of collegiality or community-building.
Strategic Language: “Strengthen cross-functional alignment through shared goals, integrated planning processes, intentional collaboration structures, and community-building opportunities.”
Here, we’re naming both the problem and its potential impact before addressing the mechanism for change.
The Role of Tension in Strategy
One of the most important, and often overlooked, parts of this translation process is holding tension.
Stakeholder data is rarely clean or consistent. When you gather perspectives across roles, levels, and lived experiences, you will almost always surface competing truths:
“We need more structure” along with “We need more flexibility”
“Everything would make more sense if it was centralized” along with “Protect local autonomy”
The instinct, especially in strategy work, is to treat these as contradictions to reconcile - to find the middle ground, soften the edges, and produce language everyone can technically agree with. That instinct is understandable. It's also where a lot of strategic plans go to die.
These aren't contradictions. They're tensions. And there's an important difference. A contradiction means one side is wrong. A tension means both sides are pointing at something real, and the strategy has to be sophisticated enough to hold both. That might mean designing systems that provide structure at the organizational level while preserving flexibility at the unit level. It might mean centralizing certain functions while explicitly protecting local decision-making authority in others. The point isn't to pick a winner. It's to design intentionally for the complexity that actually exists.
This is where strategy stops being a document and starts being a reflection of the organization's maturity. Anyone can write a plan that resolves everything neatly. It takes real interpretive work to build one that acknowledges the friction and designs around it honestly.
It's also worth noting that the presence of tension in your data isn't a problem to apologize for. It's usually a sign that your engagement process worked. You heard from enough people, across enough perspectives, to capture the real texture of the organization. That's valuable. Don't flatten it in the name of clarity.
To learn more about how growth often happens in the tension rather than around it, check out our recent blog on team development and the dynamics of the storming phase.
A Practical Test: The “So What?” Check
One of the simplest tools we use internally and with clients is the “So What?” test. For every finding, we ask:
So what does this mean?
So what needs to change?
So what would success look like?
If your strategic language doesn’t answer those questions, it’s not ready yet.
Here's the thing: a lot of strategic planning processes stop at the first question. They name the issue, declare it important, and move on. But meaning without direction is just analysis. Direction without a picture of success is just intention. You need all three to build something people can actually act on.
We've found this test is also useful as a gut-check before presenting findings to leadership. If we can't answer "so what?" clearly, confidently, and without a lot of hedging, that's a signal we haven't finished the interpretive work yet. And if we can answer it but the answer sounds vague or obvious, that's a signal we haven't pushed far enough into the nuance. Strategy shouldn't make people shrug. It should make them lean in.
The Big Takeaway
TL;DR: Listening is essential, but it’s only the beginning. The real value of stakeholder engagement comes from what happens next:
Interpreting what you heard
Naming what it means
Translating it into strategic direction
And building a path to action
When done well, stakeholders can clearly see themselves in the strategy, not just as a list of quotes, but as a set of priorities that reflect their lived experience and move the organization forward. Because the goal isn’t just to hear people, it’s to turn what they shared into something that matters.
