The Challenge of the "Unknown" in Research

In standard web development, the requirements are often clear: a user needs to log in, purchase an item, or fill out a form. In research communication, the requirements are frequently obscured by the data itself. You often don't know the story the data tells until you have cleaned, analyzed, and visualized it.

This fundamental uncertainty creates a friction with traditional project management. Research projects often start with missions that are beyond the currently possible, requiring solutions to emerge over time 1. When agencies apply rigid "waterfall" methodologies to this fluid process, the result is almost always scope creep.

The Cost of Misalignment

Scope creep—the uncontrolled expansion of project scope without adjustments to time, cost, or resources—is not merely an annoyance; it is a primary driver of project failure 3. For research organizations, the impact is threefold:

  1. Financial Loss: Poor scope management leads directly to budget overruns. When the complexity of data cleaning is underestimated, resources are burned on "data wrangling" rather than high-value design 4.
  2. Timeline Instability: Unchecked changes disrupt schedules, creating bottlenecks that delay critical policy interventions. In the policy world, missing a legislative window renders the research irrelevant, regardless of its quality.
  3. Quality Dilution: When teams are forced to accommodate unplanned work, the quality of the primary deliverables suffers 5. The team rushes the final interface to make up for time lost on undefined data tasks.

The "Iron Triangle" of project management dictates that you cannot fix Time, Cost, and Quality simultaneously without fixing the Scope 19. If the scope is fluid, quality or budget must break. Therefore, the goal of scoping is not to predict the future perfectly, but to build a structure that can withstand the unknowns of research.

Our Approach: The Strategic Necessity of "Discovery"

To mitigate these risks, we reject the idea that scoping is a one-time administrative task performed before the contract is signed. Instead, we position "Discovery" as a distinct, billable phase of the project. This is the primary risk mitigation tool for complex engagements.

Defining the "Central Curiosity"

Effective scoping begins by defining the purpose, not the deliverable. A common mistake is to scope a "dashboard" or a "report." These are formats, not solutions.

We follow the approach of defining the "Central Curiosity"—a concept championed by data visualization experts to identify the single, overarching question the visualization must answer 11. Scoping must bridge the gap between the "nice to know" and the "need to know" 12. By establishing the Central Curiosity during a "Product/UX Strategy" phase, we validate institutional objectives before a single pixel is designed 10.

For example, if the Central Curiosity is "How does water scarcity affect migration patterns?", the scope might require a narrative scrollytelling experience. If the question is "Which districts are most at risk right now?", the scope requires a searchable, real-time map. Scoping the format before the question is a recipe for misalignment.

Audience-Centric Boundaries

Scoping also defines the depth of complexity based on the audience. A policy brief for a government official requires brevity and clear recommendations, while a technical report for fellow researchers requires methodological depth.

  • The Policy Maker: Needs the "what" and the "so what." Scope emphasizes hierarchy and synthesis.
  • The Academic: Needs the "how" and the raw data. Scope emphasizes comprehensiveness and export capabilities.

By mapping these personas early, we avoid the costly mistake of building a tool that is too complex for a generalist or too shallow for a specialist 7.

Methodology: Phased Scoping and the "Eight Hats"

Complex research communication projects are rarely linear. They require a phased approach that allows for iteration. We utilize a stage-gate process (Strategy → Concept → Research → Design) that allows for re-evaluation at key milestones.

Managing Complexity with the "Eight Hats"

One of the hardest parts of scoping research communication is estimating the sheer variety of skills required. Data visualization is not just design; it is a multidisciplinary field.

We utilize the "Eight Hats of Data Visualization" model to ensure every aspect of the project is accounted for 25. A realistic scope must allocate resources for:

  1. The Initiator: Defining the constraints and goals.
  2. The Data Scientist: Mining, acquiring, and cleaning the data.
  3. The Journalist: finding the narrative within the dataset.
  4. The Computer Scientist: coding the interactive experience.
  5. The Designer: handling typography, color, and layout.
  6. The Cognitive Scientist: ensuring the visualization is understandable.
  7. The Communicator: managing the launch and dissemination.
  8. The Project Manager: keeping the tracks aligned.

If an agency provides a scope that only accounts for "Design" and "Development," they have ignored the Data Scientist and Journalist roles. This is where projects fail. The scope must explicitly answer: Who is cleaning the data? Who is writing the narrative? Who is vetting the statistical accuracy?

The "Goldilocks" Framework

Finding the right level of depth is critical. We apply a "Goldilocks Scope Framework" to balance rigor with feasibility 22. We assess the "Level of Evidence" required—does this need to be peer-review grade, or is it directional for a broader audience? This decision dramatically impacts the scope of data verification and visualization complexity.

For high-end, custom data art—similar to the layered storytelling approaches used by firms like Accurat—the scope must allow for significant "exploratory" time that may not yield immediate deliverables but is crucial for the final quality 35.

The Power of "Negative Scope" (Defining What We Won't Do)

Perhaps the most mature aspect of a rigorous scoping methodology is the use of "Negative Scope," or Project Exclusions 9.

Evaluators should look for a section in the Scope of Work (SOW) that explicitly lists what is not included. This is not about being difficult; it is about protecting the project's health by eliminating "grey areas" 17.

Why Negative Scope Matters

In research communication, assumptions are dangerous. A client might assume that "visualizing the data" includes "cleaning and restructuring the dataset." If this is not explicitly excluded (or included as a separate line item), it becomes a point of conflict that drains the budget.

Common examples of Negative Scope in our field include:

  • "We will visualize the provided dataset, but we will not perform primary statistical analysis."
  • "We will design the policy brief layout, but we will not copyedit the academic text."
  • "We will build the dashboard for desktop and tablet, but we will not support mobile responsiveness for complex scatterplots."

By defining these boundaries upfront, we prevent the slow erosion of the project's focus. This is particularly vital for formats like Policy Briefs, where a specific structure limits scope creep by forcing adherence to concise issue definitions and policy options 29.

What This Means for Your Evaluation

As you evaluate potential partners for your next research communication initiative, look past the portfolio of pretty images. Scrutinize the methodology. The way a partner scopes a project is a direct reflection of their operational maturity and their understanding of your sector.

The Evaluator's Checklist:

  1. Is there a Discovery Phase? Does the proposal allocate time and budget for strategy and data exploration before design begins? 10.
  2. Are exclusions explicit? Does the SOW include a "Negative Scope" section to prevent assumption-based conflict? 9.
  3. Are the "Eight Hats" accounted for? Is it clear who is handling data cleaning, narrative development, and QA? 25.
  4. Is the process phased? Does the methodology allow for "gates" where scope can be re-evaluated based on initial data findings? 2.

Strategic alignment occurs when the scope reflects the true complexity of the research. When you choose a partner who scopes with rigor, you are not just buying a website or a report; you are investing in a process that protects your budget, your timeline, and the integrity of your research.

Footnotes

1 Scopilot.ai, "Understanding Agency Scoping: A Practical Guide," 2024. Link Confidence: Medium

2 ResearchGate, "Lost Roots: How Project Management Settled on the Phased Approach and Compromised its Ability to Lead Change in Modern Enterprises," 2010. Link Confidence: Medium

3 Epicflow, "All About Scope Creep: Causes, Consequences, and Tips on Preventing It," 2024. Link Confidence: Medium

4 Dart, "Impact of scope creep: How it derails project success," n.d. Link Confidence: Medium

5 Research Publish, "Managing Scope Creep in Project Management," 2024. Link Confidence: Medium

7 Digis Corp, "Discovery Phase," n.d. Link Confidence: Medium

9 Teamdeck, "Project Management Statement of Work. Should You Create it for Your Projects?," n.d. Link Confidence: Medium

10 CCM Design, "Product & UX Strategy," n.d. Link Confidence: Medium

11 Medium, "Data Visualization Design Process: A 4-Step Journey Presented by Andy Kirk," 2024. Link Confidence: Medium

12 MRA Research, "How to Set the Scope of a Market Research Project," 2019. Link Confidence: Medium

17 PM Partners, "7 scoping strategies for successful projects," 2022. Link Confidence: Medium

19 Wikipedia, "Project management," n.d. Link Confidence: Medium

22 dscout, "Common Research Mistakes (and How to Fix Them)," 2025. Link Confidence: Medium

25 UX Collective, "How to figure out the scope of your visualizations quickly," 2021. Link Confidence: Medium

29 FiscalNote, "Your Step-by-Step Guide to Writing a Winning Policy Brief," n.d. Link Confidence: Medium

35 Medium, "The Architecture of a Data Visualization," n.d. Link Confidence: Medium