U02B — The six-stage analyst workflow
U02B — The six-stage analyst workflow
The repeatable map from a vague business request to an actionable answer — including people and scoping steps, not only charts.
Unit U02 · Part B
~16 min read
+ built-in quiz (5 Q)
Level: Beginner
Before this: Pass U02A. Next: U02C — scenarios & deliverables.
By the end of U02B, you will be able to:
- Name all six stages of the analyst workflow in order.
- State typical inputs and outputs at each stage.
- Know what to do first when a manager gives a vague request.
- Spot common mistakes (e.g. charting before clarifying).
- Contrast this workflow with U01B’s four technical phases.
1. Why a workflow?
Without a workflow, analysts jump straight to spreadsheets and charts. That feels productive but often answers the wrong question. The six stages add business and people steps around the technical work U01B described (collect → clean → analyze → explain).
2. The six stages (with examples)
1Receive & clarify — Stakeholder says “sales are bad.” You ask: bad vs what? Which region? Which time period? What decision will this drive?
2Scope the question — Turn the conversation into one measurable question: “Did North region revenue drop more than 10% vs last quarter?” List data you need.
3Find & assess data — Locate CRM export, POS file, or BI table. Check: complete dates? Missing stores? Trustworthy source?
4Explore & analyze — Calculate totals, compare periods, rank products, flag outliers. Draft findings in notes.
5Visualize & explain — One clear chart or table + 3–5 bullets in plain language. Headline = the “so what.”
6Review & hand off — Present, capture feedback, agree on action owner and optional follow-up date (“recheck in 30 days”).
3. Inputs and outputs per stage
| Stage | Typical input | Typical output |
|---|---|---|
| 1 Clarify | Vague request, email, meeting note | Written question + who decides + deadline |
| 2 Scope | Clarified business goal | One focused question + list of datasets needed |
| 3 Find data | Data catalog, access, export links | Working dataset you trust (or gap report) |
| 4 Analyze | Working dataset | Numbers, comparisons, draft findings |
| 5 Explain | Draft findings | Chart/slide + executive summary bullets |
| 6 Hand off | Presentation or short report | Decision recorded + action owner + follow-up plan |
4. Common mistakes by stage
- Stage 1 skipped: Building a dashboard before anyone defines “bad” or “success.”
- Stage 2 skipped: Trying to answer five questions in one analysis — scope creep.
- Stage 3 skipped: Analyzing incomplete exports (missing last week of sales).
- Stage 5 weak: Pretty chart with no headline recommendation.
- Stage 6 skipped: Sending a file with no meeting — stakeholders misinterpret numbers.
5. Six stages vs U01B four phases
| U01B (technical) | U02B (full analyst workflow) |
|---|---|
| Collect data | Stages 1–3 include clarify, scope, find — not only download |
| Clean data | Part of stage 3 (assess) and early stage 4 |
| Analyze | Stage 4 |
| Explain | Stages 5–6 include stakeholder review and hand off |
Rule of thumb: If you cannot write the scoped question in one sentence, you are not ready for stage 4.
Ready? Take the U02B quiz on this page
5 questions · 100% correct required
When you pass → U02C1 — Strong deliverables & marketing scenario
Rating
0
0
There are no comments for now.
1.
A manager says "sales are bad." What should you do FIRST in the workflow?
2.
At which workflow stage do you check if data is complete and trustworthy?
3.
What is the typical OUTPUT of the "Scope the question" stage?
4.
Jumping straight to charts before clarifying the request is a mistake at which stage?
5.
How do the six U02B stages differ from U01B's four technical phases?