The DI Squared Data Strategy Framework: Discover, Map, Navigate, Adjust
Most data strategies fail in the same places: discovery gets short-circuited, the strategy document never gets adopted, the roadmap survives only until the first re-org, and nobody owns the adjustment cadence. Our four-stage data strategy framework, refined across 200+ engagements since 2008, is built to prevent those four failures. This is the canonical deep-dive on how the framework works.
Qlik Solution Partner of the Year, ’13, ’17, ’19
Our framework runs in four stages.
- Discover diagnoses current state across people, process, platform, and governance.
- Map consolidates findings into a strategy document the team and the CFO can both work from.
- Navigate identifies what to build first and partners through implementation.
- Adjust revisits the strategy as priorities evolve so it stays useful.
What is a data strategy framework?
A data strategy framework is a repeatable methodology that turns business objectives into a documented, governed, executable data plan. The DI Squared framework has four stages, each driven by a single question. The questions are deliberately simple, because the work underneath them is not.
Discover asks: What are you trying to achieve with your data? Map asks: How do you begin to document the strategy? Navigate asks: What comes first? Adjust asks: What comes next? These four questions structure the engagement and the strategy that comes out of it.
The framework is not waterfall. The stages overlap. Discovery never fully ends. Mapping continues as facts emerge. Navigation begins before the strategy document is fully signed off. Adjustment is a permanent function. The stages are a way to know which work belongs where, not a strict sequence.
- Four stages: Discover, Map, Navigate, Adjust.
- Each stage is anchored by a single question and produces specific deliverables.
- Applied across 200+ engagements since 2008.
- Used for full enterprise strategies, departmental data plans, and platform modernization roadmaps.
- Designed to survive re-orgs, budget cycles, and executive turnover.
What are you trying to achieve with your data?
Discover is the diagnostic stage. We are not trying to build the answer yet. We are trying to understand the situation honestly, including the things the organization is not saying out loud.
We interview executives and operators across the functions that will rely on the strategy: finance, operations, supply chain, marketing, IT, and any product or revenue function with data exposure. We use our 47-question Stakeholder Interview Guide as the spine, adapted to the engagement. We profile the data environment: source systems, current warehouse or lake, ingestion patterns, BI tools, governance practices, and the gap between documented process and actual behavior.
We also assess capability honestly. What does the team know how to do today, what does it pretend to know how to do, and what does it not know how to do at all. This is uncomfortable and it is essential. Strategies that overestimate capability are the most common cause of failed implementation.
The output of Discover is a current-state assessment, a risk register, a stakeholder map with priorities and conflicts, and a defensible articulation of what the business is actually trying to achieve.
How do you begin to document the strategy?
Map is where the strategy document takes shape. We consolidate the Discover findings into a single, written, governable strategy that the operations team and the CFO can both work from. Different audiences, one document, same language.
The Map stage produces the components that define a real strategy: business outcomes and the metrics that prove them, the data and capability inventory required to deliver those outcomes, the platform and tooling decisions (warehouse, BI, ingestion, orchestration, governance), the operating model and governance structure, and the phased roadmap with budget ranges and dependencies.
We are vendor-neutral here, but fluent in the platforms that matter. Snowflake or Databricks for the warehouse layer, Qlik or Power BI or Tableau for analytics, dbt and Fivetran for engineering, Collibra for governance, AWS or Azure or GCP for cloud. Recommendations are framed against fit, not partner quota.
The output of Map is the strategy document itself, a target-state architecture, a governance charter, and a prioritized roadmap with explicit assumptions and decision points.
What comes first?
Navigate is execution. The strategy is real only when it changes what gets built and in what order. We identify the highest-value first moves and partner with the client through implementation, change management, and ongoing monitoring.
What comes first is rarely the most exciting capability. It is usually the dependency that everything else needs: a trustworthy customer master, a clean financial data layer, a working ingestion pattern, a basic governance discipline. We start with what unblocks the next three things on the roadmap.
We also embed the change management work that most strategies skip. New tools require new behaviors. New behaviors require new training, new incentives, and new accountability. Navigate covers all three, not just the technology install.
The output of Navigate is a working first capability (or set of capabilities), a documented runbook for repeating the pattern, and a measurement model that shows whether the strategy is producing the outcomes it promised.
What comes next?
Adjust is the stage most consultancies skip and most strategies need most. Budgets change. Leadership changes. Acquisitions happen. Regulation changes. A strategy that cannot adapt becomes a constraint instead of a guide.
Adjust is a recurring engagement model, not a one-time deliverable. We revisit the strategy on a defined cadence (often quarterly check-ins and an annual refresh), reassess priorities against the original outcomes, retire capabilities that no longer earn their keep, and identify the next sequenced moves.
This is also where we help the internal strategy owner build the muscle to maintain the document without us. A good engagement ends with the client running the framework, not depending on us to run it.
How the four stages connect: a How To summary
Discover.
Discover the current state across people, process, platform, and governance. Interview stakeholders, profile systems, surface honest capability gaps. Deliverable: current-state assessment.
Map.
Map the strategy by consolidating findings into a written document with business outcomes, capability inventory, platform decisions, governance model, and a phased roadmap. Deliverable: the strategy document.
Navigate.
Navigate by identifying the highest-value first moves and partnering through implementation, change management, and measurement. Deliverable: a working first capability and a repeatable runbook.
Adjust.
Adjust on a defined cadence as priorities, budgets, and leadership evolve. Deliverable: a strategy that continues to produce decisions year over year.
Data Strategy Framework, answered.
Q: How is the DI Squared framework different from other data strategy frameworks?
A: Most frameworks stop at Map. They produce a strategy document and walk away. Ours is built on the premise that a strategy is only useful if it survives execution and adapts over time, so Navigate and Adjust are first-class stages, not afterthoughts. The framework also reflects 200+ delivery engagements, so the stage definitions are grounded in what actually happens, not what should.
Q: Can you apply the framework to just one part of our data environment?
A: Yes. We use the same four stages for full enterprise strategies, departmental analytics plans, platform modernizations, and migration efforts. The depth scales. The stages do not.
Q: How long does each stage take?
A: Discover typically runs four to eight weeks. Map runs four to eight weeks, often overlapping with the back half of Discover. Navigate is a multi-month implementation engagement sized to the first capability. Adjust is ongoing, usually a lightweight quarterly cadence with an annual refresh.
Q: Who from our team needs to be involved?
A: Discover requires access to executives, line-of-business operators, and the data and IT teams. Map requires a smaller working group, usually six to ten people. Navigate requires the implementation team and an empowered product owner. Adjust requires the named internal strategy owner plus an annual executive review.
Q: Does the framework work for companies with no current data strategy?
A: Yes. Most of our engagements start in exactly that situation. Discover takes longer in those cases, because there is no existing baseline to react against. The other stages are unchanged.
Q: What if our priorities change mid-engagement?
A: That is what Adjust exists for. The framework expects change and is structured to absorb it. We re-map affected sections of the strategy rather than restarting the whole engagement.
Want to see what Discover would surface in your environment?
The first conversation runs about an hour. We bring the framework. You bring the situation. By the end you know whether a full engagement is the right next move.