Exploratory Data Analysis

Exploratory Data Analysis

Primary Category: Analytical Governance & Data Discovery

Secondary Focus: Data Quality Assessment, Pattern Identification, and Hypothesis Generation

Artifact Profile

Exploratory Data Analysis (EDA) is a governance artifact for examining new or uncertain datasets to understand structure, quality, distributions, relationships, and anomalies before deeper analysis begins.

Rather than jumping straight to conclusions or dashboards, this artifact structures exploration to surface patterns, data quality issues, emerging hypotheses, and the right next analytical questions.

Three Key Questions This Artifact Helps You Answer

- What is actually in this data, and what issues or gaps exist?

- What patterns, anomalies, or relationships are emerging?

- What questions or hypotheses should guide deeper analysis?

What This Framework Supports

This artifact supports organizations seeking:

- Structured examination of new or unfamiliar datasets before formal modeling

- Early identification of data quality gaps, anomalies, and structural issues

- Discovery of emerging patterns, distributions, and relationships

- Clear documentation of analytical questions and hypotheses for deeper investigation

How It Is Used

The artifact provides a structured data-governance framework that guides analysts, researchers, operations teams, and decision-makers through:

- Profiling data structure, completeness, and variable distributions

- Identifying anomalies, outliers, and unusual value patterns

- Exploring relationships and preliminary correlations

- Documenting limitations and defining next analytical steps

This enables organizations to understand what their data can and cannot support before committing to dashboards, models, or executive reporting.

What This Produces

• Structured observations about data quality and structure

• Identified patterns, anomalies, and unusual values

• Documented questions and hypotheses for further analysis

• Early warnings about limitations or data gaps

• A repeatable framework for exploratory data review

Common Use Cases

• Exploring a new or unfamiliar dataset

• Checking data quality, completeness, and anomalies

• Identifying patterns or relationships before formal modeling

• Forming hypotheses for deeper statistical or predictive analysis

• Determining whether additional data is needed

How This Artifact Is Different

Unlike formal analytics or reporting, this artifact does not aim to produce final conclusions. It governs the discovery phase, ensuring exploration is disciplined, transparent, and focused on learning what the data can truly support.

Related Framework Areas

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

- Evidence quality assessment and analytical rigor governance

- Decision quality scoring and reliability assessment

- Data lineage and traceability systems

- Executive storytelling and summary generation

Related Terms

Exploratory data analysis, data profiling, data discovery, data quality assessment, hypothesis generation, analytical readiness.

Framework Classification

This artifact is part of the SolveBoard library of structured decision and governance frameworks. It is designed as a repeatable data-exploration governance framework rather than a dashboard, predictive model, or final analytical report.

Exploratory Data Analysis

Discover patterns, anomalies, and questions before formal analysis

Definition

Exploratory data analysis (EDA) is the initial examination of data to understand its structure, quality, distributions, relationships, and anomalies. It is used to surface questions, hypotheses, and directions for deeper analysis.

When to Use

• When working with a new or unfamiliar dataset

• When data quality is uncertain

• When patterns or relationships are unknown

• When forming hypotheses for deeper analysis

When Not to Use

• When the analysis question is already fixed and validated

• When data has already been thoroughly profiled

• When only final metrics are required

Common Mistakes

• Jumping to conclusions from early patterns

• Overinterpreting small samples

• Skipping data quality checks

• Confusing exploration with confirmation

Purpose of Exploratory Data Analysis

The purpose of exploratory data analysis is to understand what the data can and cannot tell you before committing to formal analytical methods.

How to Apply

• Review dataset structure and fields

• Check completeness, ranges, and anomalies

• Explore distributions and basic summaries

• Examine relationships between key variables

• Document emerging questions and hypotheses

Example Scenario

Before analyzing supplier performance, an analyst explores lead time distributions, missing values, outliers, and correlations between volume and delay.

Boundaries

EDA informs analysis design but does not produce final conclusions. Findings must be validated through appropriate analytical methods.

What This Artifact Does

Structures exploratory data analysis to reveal data characteristics, issues, and analytical directions.

You Provide

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

• Dataset or data files

• Context and intended use

• Known constraints or definitions

• Initial questions or areas of interest

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

Core Question

What is in this data, and what questions does it raise?

Decision Logic

• If data quality issues appear → Address before deeper analysis

• If strong patterns emerge → Form hypotheses

• If gaps are found → Identify additional data needs

Do Not Use When

• The goal is to produce final metrics or conclusions

• Data has already been validated and analyzed

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 — Dataset Scope and Context

What This Input Represents

The dataset, domain, or business context being explored.

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

- Datasets

- Spreadsheets

- Database extracts

- Dashboards

Guiding Questions:

- What dataset is being explored?

- What business or analytical context does it represent?

- What questions or goals motivated this exploration?

Section 2 — Data Structure and Fields

What This Input Represents

The structure, schema, and fields contained within the dataset.

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

- Data dictionaries

- Schema documentation

Guiding Questions:

- What fields or variables exist in the dataset?

- What data types are present?

- Are any fields unclear, undocumented, or ambiguous?

Section 3 — Data Quality, Completeness, and Gaps

What This Input Represents

Observed issues related to missing data, inconsistencies, or errors.

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

- Quality notes

- Missing value reports

Guiding Questions:

- Are there missing, incomplete, or inconsistent values?

- Are ranges, formats, or values suspicious or unexpected?

- Where might additional data be needed?

Section 4 — Distributions, Patterns, and Summaries

What This Input Represents

Initial descriptive patterns, trends, or unusual distributions.

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

- Summary statistics

- Charts

- Exploratory visuals

Guiding Questions:

- What patterns or trends appear in the data?

- Are there skewed distributions or outliers?

- Which variables show interesting or unexpected behavior?

Section 5 — Relationships and Correlations

What This Input Represents

Connections or associations observed between variables.

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

- Correlation tables

- Scatter plots

- Cross tabulations

Guiding Questions:

- Are any variables strongly related?

- Do relationships suggest possible drivers or segments?

- Are there surprising or counterintuitive correlations?

Section 6 — Anomalies, Outliers, and Irregularities

What This Input Represents

Data points or behaviors that deviate from normal patterns.

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

- Outlier reports

- Exception lists

Guiding Questions:

- Where do anomalies or extreme values appear?

- Could anomalies indicate data errors or real-world events?

- Which irregularities warrant deeper investigation?

Section 7 — Emerging Questions and Hypotheses

What This Input Represents

New analytical questions or hypotheses generated through exploration.

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

- Hypothesis notes

- Exploration summaries

Guiding Questions:

- What new questions does the data raise?

- What hypotheses could be tested in deeper analysis?

- Which findings require validation before conclusions?

Section 8 — Constraints, Limitations, and Interpretation Risks

What This Input Represents

Limitations that affect what conclusions can be drawn.

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

- Known limitations

- Bias or coverage notes

Guiding Questions:

- What limitations constrain interpretation?

- Where could bias or misinterpretation occur?

- What findings should be treated as tentative rather than confirmed?

Section 9 — Supporting Context, Files, and References

What This Input Represents

Additional context, assumptions, constraints, or historical background relevant to exploratory analysis.

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

- Prior analytical work or benchmarks

- Known data caveats or warnings

- Strategic or organizational context

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 a structured Exploratory Data Analysis output that surfaces patterns, anomalies, data quality issues, and analytical questions to guide deeper investigation.

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

Explore provided data to understand structure, quality, patterns, and anomalies.

What This Bridge Answers

What does this data look like, and what should we analyze next?

Inputs (All Optional)

• Data files or datasets

• Context and intended use

• Definitions or 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

• Do not infer causation

• Explicitly note data quality issues

• Distinguish observations from conclusions

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

• Inspect structure and fields

• Review distributions and summaries

• Identify anomalies and gaps

• Document observations and questions

Output

• Data quality observations

• Key patterns and anomalies

• Questions and hypotheses for further analysis

Failure Conditions / Misuse

• Treating exploratory findings as final conclusions

• Ignoring data limitations

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 Exploratory 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