Data Analysis

Data Analysis

Primary Category: Decision Governance & Analytical Reasoning

Secondary Focus: Data Interpretation, Analytical Rigor, and Evidence-Based Decision Support

Artifact Profile

Data Analysis is a governance artifact for examining data to uncover patterns, trends, relationships, and insights that support decision-making. It ensures analysis is driven by clear questions, appropriate methods, and contextual interpretation.

Rather than exploring data aimlessly or producing disconnected charts, this artifact structures analysis with decision alignment, data validation, analytical rigor, and explicit interpretation so insights lead to action.

Three Key Questions This Artifact Helps You Answer

• What does the data reveal that matters for this decision?

• What patterns, trends, or relationships meaningfully influence outcomes?

• What limits, assumptions, or uncertainties should inform interpretation?

What This Framework Supports

This artifact supports organizations seeking:

- Decision-aligned data analysis driven by clear questions and objectives

- Identification of meaningful patterns, trends, and relationships that influence outcomes

- Explicit treatment of assumptions, limitations, and uncertainty in interpretation

- Analytical outputs that inform action rather than producing disconnected insights

How It Is Used

The artifact provides a structured analysis governance framework that guides analysts and decision-makers through:

- Defining the decision context and analytical question

- Validating data sources, quality, and relevance

- Selecting appropriate analytical methods and techniques

- Interpreting findings with stated limits and implications for action

This enables organizations to convert data into defensible insights that directly support prioritization, performance improvement, and informed decision-making.

What This Produces

• Decision-aligned analytical findings

• Validated data interpretations with stated limitations

• Descriptive, diagnostic, predictive, or prescriptive insights

• Clear summaries of implications for action

• A repeatable framework for structured data analysis

Common Use Cases

• Supporting decisions with evidence and data-driven insight

• Identifying trends, performance gaps, or operational bottlenecks

• Comparing options using quantitative analysis

• Forecasting outcomes or risks using historical data

• Evaluating performance and monitoring key metrics

How This Artifact Is Different

Unlike exploratory reporting or ad-hoc dashboards, this artifact treats data analysis as a governed decision-support process. It ensures analytical work answers the right question, uses appropriate methods, and produces insights that inform action rather than noise.

Related Framework Areas

This artifact is commonly used alongside other SolveBoard frameworks focused on:

- Decision support and evidence-based governance

- Performance measurement and monitoring

- Business intelligence and analytical design

- Risk-informed and data-driven strategy

Related Terms

Decision-support analytics, evidence-based decision making, data interpretation, analytical rigor, business intelligence, performance analysis, quantitative analysis, insight generation.

Framework Classification

This artifact is part of the SolveBoard library of structured decision and governance frameworks. It is designed as a repeatable data analysis governance framework rather than exploratory reporting, ad-hoc charting, or intuition-driven interpretation.

Data Analysis: Extract insights from data to inform decisions and action

Definition

Data analysis is the structured examination of data to identify patterns, relationships, trends, and insights that support judgment, decision-making, and execution.

When to Use

• When decisions depend on evidence

• When patterns or trends must be identified

• When performance must be understood

• When options must be compared using data

When Not to Use

• When the question is purely conceptual

• When data quality is insufficient

• When analysis would not change the decision

Common Mistakes

• Analyzing without a clear question

• Confusing correlation with causation

• Overcomplicating analysis

• Ignoring data limitations

Purpose of Data Analysis

The purpose of data analysis is to reduce uncertainty and improve decision quality by grounding judgment in evidence.

How to Apply

• Define the decision question

• Identify relevant data

• Validate and prepare data

• Apply appropriate analysis

• Interpret results in context

Example Scenario

An operations team analyzes cycle time data to identify bottlenecks and prioritize improvements.

Boundaries

Data analysis supports judgment but does not replace it.

What This Artifact Does

Structures data analysis to produce actionable insights aligned to decisions.

You Provide

(You may provide some, all, or none of the items below. Partial inputs are valid.)

• Decision question or objective

• Data sources or files

• Context and constraints

• Assumptions

• Text, links, documents, PDFs, spreadsheets, images, or uploads

Core Question

What does the data reveal that matters for this decision?

Decision Logic

• Descriptive → summarize

• Diagnostic → explain

• Predictive → forecast

• Prescriptive → recommend

You do not need to complete every section below. Provide only the information you have available or wish to provide. The AI will generate output using only the inputs you supply and will not assume or infer missing information.

Section 1 — Decision Question or Objective

What This Input Represents

The decision, problem, or question that the analysis is intended to support.

If You Have Materials, You May Provide (List file names here in your input document):

- Decision statements

- Business questions

Guiding Questions:

- What decision or question should the data inform?

- What outcome would make this analysis useful?

- What scope or boundaries apply to the decision?

Section 2 — Data Sources and Availability

What This Input Represents

The datasets, systems, or reports available for analysis.

If You Have Materials, You May Provide (List file names here in your input document):

- Spreadsheets

- Databases

- Dashboards

- Raw datasets

Guiding Questions:

- What data sources are available?

- How current, complete, and reliable is the data?

- Are there known gaps or limitations?

Section 3 — Definitions, Metrics, and Assumptions

What This Input Represents

How key metrics, fields, and assumptions should be interpreted.

If You Have Materials, You May Provide (List file names here in your input document):

- Metric definitions

- Data dictionaries

Guiding Questions:

- How are key metrics defined?

- What assumptions should guide interpretation?

- Are there risks of misinterpretation?

Section 4 — Context, Constraints, and Business Environment

What This Input Represents

Operational or strategic context that shapes analysis meaning.

If You Have Materials, You May Provide (List file names here in your input document):

- Business context

- Operational constraints

Guiding Questions:

- What contextual factors influence the data?

- What constraints limit analysis or conclusions?

- Are there external factors that must be considered?

Section 5 — Analytical Focus and Depth

What This Input Represents

The type and depth of analysis desired.

If You Have Materials, You May Provide (List file names here in your input document):

- Analysis plans

- Stakeholder priorities

Guiding Questions:

- Is the analysis descriptive, diagnostic, predictive, or prescriptive?

- What level of depth or rigor is required?

- Are there priority areas or segments to emphasize?

Section 6 — Stakeholder Expectations and Use

What This Input Represents

How insights will be consumed or applied.

If You Have Materials, You May Provide (List file names here in your input document):

- Stakeholder requirements

- Decision timelines

Guiding Questions:

- Who will use the analysis results?

- How will insights influence decisions or actions?

- What format or clarity level is expected?

Section 7 — Known Risks, Biases, or Data Limitations

What This Input Represents

Potential sources of bias, noise, or misinterpretation.

If You Have Materials, You May Provide (List file names here in your input document):

- Quality notes

- Prior analysis concerns

Guiding Questions:

- Where might bias or data quality issues exist?

- What limitations should be disclosed?

- How could misleading conclusions be avoided?

Section 8 — Desired Outputs and Decision Implications

What This Input Represents

What outputs are expected and how they should guide decisions.

If You Have Materials, You May Provide (List file names here in your input document):

- Report expectations

- Decision criteria

Guiding Questions:

- What outputs are needed (charts, tables, summaries)?

- What decisions should the analysis enable?

- What level of confidence or certainty is required?

Section 9 — Supporting Context, Files, and References

What This Input Represents

Additional information, datasets, constraints, or historical insights that influence interpretation.

You May Include (List file names here in your input document):

- Additional datasets or sources

- Historical trends or benchmarks

- Strategic or regulatory considerations

Additional Instructions (Optional)

You may add extra instructions to further shape the output, including:

Requesting PDF or other output formats
Limiting page length or response size
Layout preferences (section order, headings, structure, templates)
Specifying tone, style, or format (executive, concise, detailed, formal, etc.)
Output consistency preferences (fixed structure, standardized phrasing, strict formatting)
Prioritization or scoring preferences (how gaps, risks, or actions should be ranked)
Desired mode behavior as outlined in the section below
Any other constraints, rules, or priorities relevant to your use case

If included, the AI will follow these instructions when they do not conflict with the bridge’s execution rules. More specific instructions generally produce more consistent, repeatable, and targeted outputs.

Desired Mode Behavior

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

What This Enables

Based on your prepared inputs, this artifact produces structured data analysis that extracts insights, highlights patterns and trends, and supports evidence based decision making.

Canonical Input Rule (For All SolveBoard Artifacts)

Documents are optional. Sections may be partially completed or left blank. Structured answers to any subset of guiding questions constitute valid input. The AI will evaluate only provided information and will not infer missing content.

AI Execution Instructions

You are operating in Bridge Execution Mode. Follow these rules exactly. Do not reinterpret, summarize, optimize, or override them. Do not introduce external knowledge, assumptions, or inferred content. Evaluate only user-provided inputs. If required information is missing or ambiguous, flag it rather than guessing. Output must follow the defined Output section exactly.

Users may provide some, all, or none of the input sections. Process only what is explicitly provided. Treat empty sections as intentionally omitted.

Purpose

Analyze provided data to generate decision-relevant insights.

What This Bridge Answers

What insights does the data provide for this decision?

Inputs (All Optional)

• Decision question

• Data files or datasets

• Definitions and assumptions

• Constraints

• Supporting materials (text, links, files, PDFs, spreadsheets, images, uploads)

Note: Output Quality and specificity scale with input completeness. The user has been informed of this via the input sheet.

Processing Rules

• Align analysis to the stated question

• Use appropriate methods for data quality

• Explicitly state limitations

When inputs are sparse:

• Produce the most complete output possible with available data

• Explicitly flag what's missing and how additional inputs would enhance the analysis

• Do not infer or assume missing information

Execution Steps

• Review the question

• Assess data quality

• Analyze data

• Summarize insights and implications

Output

• Key findings

• Implications for decision

Failure Conditions / Misuse

• Analysis answers the wrong question

• Results lack context

Mode Behavior (From Input Sheet)

Strict Mode

• Maximize determinism and repeatability
• Minimize wording variation, structure changes, and interpretive flexibility
• Do not extend beyond explicit user inputs

Balanced Mode (Default)

• Maintain structure and discipline
• Allow limited analytical judgment where inputs are incomplete
• Do not introduce external assumptions

Exploratory Mode

• Expand hypothesis space and analytical angles
• Surface alternative interpretations and scenario paths
• Still grounded only in user-provided inputs

If no mode is specified, default to Balanced Mode.

Additional Instruction Governance

User-provided additional instructions must be followed exactly unless they conflict with core Bridge Execution Rules. If a conflict exists, Bridge Execution Rules take priority.

Additional instructions may control format, tone, structure, length, or ordering, but must not introduce inferred content, external knowledge, or speculative assumptions.

If instructions are ambiguous, flag ambiguity rather than guessing.

Additional Instructions Execution Rule

If the user provides instructions in the Additional Instructions field, they are binding execution constraints.

Failure to follow them constitutes a Bridge Execution Failure.

Reminder to AI: If a format is requested (e.g., PDF, DOCX), the final output MUST be delivered in that format.

Artifact Instructions

This guide explains what information the Data Analysis artifact requires and how to prepare your inputs.

How to Prepare Your Input Document (Required Format)

Create a new Word (or similar) document.
Copy all text from the Input Sheet tab into the document.
Save it — this is now your Input Document.
Answer the guiding questions directly in the Input Document and reference any supporting files there.
Save the completed Input Document (Word, PDF, etc.).
Copy all text from the Bridge AI Prompt tab and paste it into the prompt field.
Attach the completed Input Document and any referenced files when submitting the prompt.

No Supporting Files? No Problem.

You can proceed without uploading any supporting documents, spreadsheets, dashboards, reports, or other attachments.

The Input Document is still required, but it may contain only plain-text answers to the guiding questions.

Written responses alone are sufficient for the AI to generate output.

Supporting files, links, and pasted materials are always optional.

Missing Inputs Are OK

You do not need to complete every section.
You do not need supporting files.

The AI will still run. It will:

Use only the inputs you provide
Skip or flag missing sections
Never fail due to incomplete information

Output quality scales with input depth — but execution never breaks.

Submitting Files

If you upload files, list each file name under the relevant “If You Have Materials” section in your Input Document. This ensures each file is clearly tied to its intended use.

What to Expect From This AI Bridge

This bridge generates a structured, high-value starting point, not a guaranteed final deliverable. Output quality improves as inputs become clearer, deeper, and more complete.

This artifact supports iteration. Users are encouraged to refine inputs, test variations, and rerun the bridge to improve results.

The AI organizes complexity and accelerates insight — but final judgment and decisions remain with the user.

In Short

Stronger inputs → stronger outputs
Iteration improves results
Cross-artifact testing can reveal new perspectives
This artifact enables progress, not perfection