Data-AI Strategy
Data and AI strategy are inextricable. Success in one drives the other, and vice versa. Written separately, AI plans promise answers the data cannot yet support, and the data plan hasn't incorporated the AI vision set by leadership.
Why data and AI strategy belong together
AI has not replaced the data agenda. It has raised the stakes, changed which data counts as strategic, made governance more imperative, and restructured the econonmics of insight.
AI runs on context, and most of yours isn't in the warehouse
A model is a general capability. What makes it useful to you is the context you can put in front of it: your protocols, registries, notes, and definitions. Most institutional knowledge never made it into the warehouse. It lives in documents, narratives, and images that modern models can now use at scale. The ceiling on your AI is the reach and quality of the data you can safely deliver to it, and data strategy sets that ceiling.
Every AI decision is a data decision
Can this leave our tenant? Whose consent covers it? Is PHI in scope? Which version is the system of record? Who answers when the output is wrong, and who owns the quality of what the model reads? These questions stall AI pilots late, after the model already works. Every one of them is a data governance question. Settled early, they are what lets a pilot reach production instead of stalling there.
AI changes data economics
Boards are asking for customer-facing chatbots that make the interface easier to use. But what if the interface isn't the real bottleneck? What if the data needed to answer strategic and tactical questions either does not exist or takes too much effort to assemble? Data pipelines are held up by decisions, and AI can make many of them while still allowing human oversight. Narrative data has been back-burnered for years, and AI now makes it usable for better answers to more questions. What is your bottleneck: the interface or the data?
So we write one strategy, in which the AI ambitions justify the data investments, the data investments make the AI ambitions achievable, and AI makes those investments cheaper to carry out.
Alignment
The organizations that struggle most with data are rarely the ones with weak people or small ambitions. Usually it is the opposite. The talent is real, the vision is wide, and the work still does not add up. Effort behaves like a wave, and waves that arrive out of phase cancel.
Destructive interference
- Excellent teams, each doing real work on a roadmap that makes sense on its own terms, including its own AI pilots and tools.
- A wide executive vision that no one disagrees with and no one has operationalized or budgeted.
- Frustrated customers who cannot tell you what they want, because no one has shown them what they should be able to ask for.
- Effort moving in many directions at once, which cancels out at the organizational level.
Constructive interference
- One strategic priority that connects executive vision to where the budget and headcount actually go.
- Sequenced investment, so foundational work is funded because everyone can see what it unblocks.
- Customers who know what is coming and when, and who have learned which questions are worth asking.
- Work that compounds, because each team's output is the next team's input, and AI pilots build on shared, governed data.
Why this is so hard to see from the inside
Destructive interference does not look like failure. Every team can show you good work, every leader can point to a win, and every roadmap defends itself on its own terms. The loss is hard to see because it sits between the efforts rather than inside any one of them. It shows up only in aggregate: initiatives that never quite compound, the same data rebuilt three times, and stakeholders who have quietly stopped asking.
Nothing in that picture is fixed by better people or a bolder vision. You already have both. What is missing is phase.
Getting an organization into phase is what a data-AI strategy is for, and that requires something concrete for people to align to.
The North Star Use Case
Most data roadmaps stall because every department has its own list and priority is tactical and goes to the squeaky wheel. The North Star addresses that. It is a single use case, broad enough that no one team can deliver it alone, stated in one sentence that a board member and a data engineer can both repeat. Below are two examples from different sectors. We write one for your organization, in your language.
One sentence that no single department can deliver alone
A good North Star spans functions deliberately, so that collaboration is the only way to reach it. It should hold the organization's attention for at least two years, and it should break into components that each deliver value on their own. It often takes the form of a question or a statement the organization cannot currently answer.
Every highlighted term is a core data element. We don't start with a list of data projects and try to decide which ones matter most. The North Star tells us what data matters and why, so a long list of competing priorities becomes a short list of things to get right, each tied to a source and a clear purpose.
Once it exists, the North Star does real work:
- It gives teams across the organization a single shared purpose.
- It identifies the 5–10 core data elements that matter most to achieving the North Star.
- It becomes the test for proposed investments: does this move the North Star?
- It shows where the answer is blocked. Often the hardest elements arrive as narrative text, outside records, or manual spreadsheets, which is where AI can do real work.
An adoption model, scored together
Before recommending anything, we place your organization on a data and AI adoption model and score it, at each level, for both data readiness and AI readiness. You rate yourselves, we rate you, and we reconcile the differences together. That conversation is often one of the most useful in the engagement. Below is the Community Impact Analytics Adoption Model, our adaptation of the public-domain Healthcare Analytics Adoption Model for mission-driven organizations. When we work together, we create your own custom adoption model based on your vision and needs.
The pattern we find most often: top-heavy
The model is progressive. The lower levels rarely make it onto the organizational agenda. Either there is an assumption that everything is working or leadership is tempted by the most challenging top-level use cases without understanding what is required underneath. Talented analysts produce genuinely good work at Level 5, and leadership concludes the data program is healthy. Often it isn't. Each of those wins is hand-built, hard to repeat, and more expensive than it looks. Naming that pattern, with evidence, is usually what unlocks funding for the less visible work at Levels 2 through 4.
AI makes this more visible. Pilots work well on curated extracts and then stall on the way to production, because production requires the governance, lineage, and access control that were skipped.
Four phases
The work is developed in partnership with executive sponsors and stakeholders. We set the schedule with you at the outset, around your calendar and the availability of the people we need to talk to. Phases can overlap.
Initiate
- Identify the executive sponsor, point of contact, and stakeholder set
- Set the meeting cadence
- Draft and ratify the Chief Concern and the strategy vision
- Finalize the plan and schedule interviews
Inspect & Interpret
- Review org structures, roadmaps, and the current data environment
- 30–45 minute stakeholder interviews across levels and functions, including an inventory of the AI tools staff already use, sanctioned and unsanctioned, and which knowledge lives in documents
- Score data and AI readiness on the adoption model together
- Deliver spot training on AI tools as real workflows surface
- Mid-engagement checkpoint and interim report
Integrate
- Synthesize themes into gaps tied to the North Star
- Draft recommendations and rank candidate AI use cases, then review with the sponsor
- Iterate, prioritize, and finalize
Inform
- Finalize the written report and executive presentation
- Present, or support your presentation of, the findings
- Run a short stakeholder survey on the strategy and priorities
- Deliver an addendum capturing the feedback
What the report contains
The engagement produces a written report and an executive presentation. You receive a full and irrevocable license to both. These are the sections it includes.
Chief Concern & Goals
One paragraph naming the most important data and AI problem you face, plus the specific outcomes this work must produce. Agreeing on this first is how we avoid solving the wrong problem well.
Data-AI Strategy Vision
A concise five-year statement of where data and AI take the organization, written to be ambitious enough to shift how people think and specific enough to guide real decisions.
Synthesis of Organizational Themes
What we heard in the interviews, organized into the patterns behind it: the recurring issues across people, process, and platform.
Adoption Model Assessment
Your scored position, for both data readiness and AI readiness, on an adoption model adapted to your sector, with the rationale behind each score and a summary figure you can present to leadership.
North Star Use Case
The unifying use case, written out, with the 5–10 core data elements it depends on and the reasoning behind it.
Gaps
Concrete gaps in data content, quality, acquisition, integration, governance, infrastructure, and cross-functional execution, plus the AI-specific ones: unstructured knowledge, AI governance and consent, evaluation, and skills. Each is tied to the outcome it is blocking.
Prioritized Recommendations, AI Use Cases, Tactical Steps, and Spot Training
Specific steps: what, by whom, in what timeframe, ranked by impact and feasibility, each traced back to the North Star. They span technology, organization, process, projects, and skills. They include a ranked portfolio of AI use cases, including customer-facing ideas such as chatbots, each scored on value, data readiness, and risk, with guidance on where to start and whether to build or buy. Alongside the multi-year recommendations we surface tactical moves you can make in the first 90 days, and deliver two to three short, hands-on AI sessions built around the real workflows we encounter during interviews: drafting from prior documents, plain-language summaries, training materials, reviewing narrative reports. The recommendations address the next several years. The spot training is meant to be useful immediately.
Where this has been applied
We have run this process across healthcare delivery, clinical research, and mission-driven organizations. Two anonymized examples, from opposite ends of data maturity:
Aligning a nascent data function on executive goals
Growing partner data-sharing demands and new systems had produced wide variation in data practice. The strategy drew on thirteen stakeholder interviews, from CEO to data specialist, which surfaced consistent themes around trust, access, and ownership. An adoption assessment showed strong analytic talent resting on thin governance and infrastructure, a North Star tied fundraising, public investment, and program outcomes into a single sentence, and sequenced recommendations turned both into a plan.
Outcome: the strategy became the basis for prioritizing and funding data initiatives internally. It has also guided strategic partnerships around data, both with the consumers of the data and with the partners helping to build out the infrastructure.
Giving a mature data organization a shared vision
The data organization was struggling with alignment. The roadmap was unclear to stakeholders, who did not understand which questions the data resource was meant to answer and were frustrated when they could not ask the questions they felt they should be able to ask. The engagement supplied the missing piece: a shared vision, the alignment of the data organization to it, and a structured, prioritized approach to completing it.
Outcome: the data team was redirected to the roadmap outlined in the strategy, and stakeholder engagement rose sharply because people saw their needs represented on it. In a live poll during the findings presentation, 84% of the 32 respondents said the North Star use case was exactly the focus the organization needs, and none thought it was in the wrong direction.
- A large cancer data aggregator
- A national non-profit research organization
Different starting points, the same result: a data organization aligned on executive goals, with a clear roadmap and investment to follow.
Pragmatic, actionable strategy
Grounded in your reality
Strategic advice that ignores your actual people, systems, and budget is common. We have run data operations, built platforms, and carried a P&L. Our recommendations account for where you actually are.
Executive partnership
We know the pressure that keeps executives from strategic thinking. Part of this work is being a trusted sounding board and turning an executive's instinct into direction the organization can act on.
Listening first
Success with technology requires careful listening. We take time to understand the current state: the details of the technical environment and the experience of the people working in it.
Let's talk about your data and AI strategy
Every engagement starts with a conversation about what you are trying to accomplish with data and AI and what is getting in the way. We will tell you honestly whether this engagement is the right fit.
Start the conversationStrategy work often pairs with our privacy-first AI training for the teams who will carry the roadmap. Implementation work (AI development, role definition, hiring, chartering and mentoring projects) is scoped separately.