The design discipline that should happen before the first query — and why skipping it breaks everything downstream.
Most analytics failures aren't tool failures. They're design failures that happened weeks or months before anyone wrote a query, built a dashboard, or selected a platform.
The tool worked. The data was clean. And the output sat unused — or got bypassed by a bad PowerPoint that someone made that morning.
If you've felt that, you've felt the absence of something. Not a harder skill. An earlier one.
The Intentional Analyst™ is a framework for designing analytics systems that actually work — before a tool is ever selected. It begins with the questions that should have been asked first: what decisions the system is supposed to inform, who the real decision-makers are, what governance logic is embedded in how the organization actually operates, and what architecture serves that governance before a platform is ever evaluated.
The series is where to start. The work goes deeper from there.
The framework draws from three decades of designing analytics systems for organizations where the stakes were real — from global military health systems to civic market ecosystems to crisis reporting environments where numbers moved up a chain to the highest levels of government.
The method is transferable. The stakes don't have to be federal to feel the pattern.
A one-page field reference for the work that should happen before any tool is opened. Five questions, in order, with the reasoning behind each one.
Keep it close. It's the design stage most analytics projects skip.
Justin Sweetman has spent three decades designing analytics systems for organizations where getting it wrong had real consequences — healthcare for people who served, crisis reporting in environments that didn't allow for do-overs, market ecosystems built to support genuine community.
The Intentional Analyst™ is the discipline he's practiced across all of it, and is now naming.