Connect the business question to the data.
Turn business questions into agreed definitions, useful analysis, and decisions that teams can act on.
The context behind the work.
You translate a business need into a question that data and delivery teams can act on. Context includes the current process, the decision-maker, agreed definitions, and what would make the answer useful enough to change the work.
A stakeholder asks for a new report
Start by asking which decision the report should support. Agree the definitions and source requirements with the data team, then validate a representative output with the person who will use it.
A process change needs analytical evidence
Describe the expected outcome and a fair comparison. Work with an analyst to examine the result, document important limitations, and turn the conclusion into an owned process decision.
A practical path from task to outcome.
Turn a business requirement into a clear analytical task and acceptance criteria.
- 01
Discover governed context
Describe the decision, current process, participants, and the question that needs an answer.
- 02
Assess needs and evidence
Work with the data owner to agree definitions, source availability, and access requirements.
- 03
Publish trusted outputs
Review an analysis or prototype with the intended users and check it against the acceptance criteria.
- 04
Brief decision owners
Document the decision, process change, and remaining questions so delivery teams have a clear next step.
A validated requirement, agreed definitions, and an actionable decision brief.
Less repeated effort. More useful work.
Explore the habits and platform connections that can make this role easier, more consistent, and easier to collaborate with.
Requirements written without a shared definition
Agree business terms and metric meaning before implementation.
Repeated clarification between business and data teams
Keep the question, source context, and acceptance criteria in one review.
Reports delivered without an operational decision
Connect the analytical output to an owned business action.
Measure your own improvement
Choose a baseline before you begin. Review these signals with your team; results depend on your data, process, and implementation.
- Requirements returned for clarification
- Time from a business question to agreed acceptance criteria
Build confidence with a first task.
Turn a business requirement into a clear analytical task and acceptance criteria.
Use AI with judgment
Use AI to organize interview notes and draft requirements; validate business meaning with the people doing the work.
Your practice checklist
0 / 4 completeThe right surfaces. The right people.
Continue into the product, deepen your knowledge, or follow the next role in the handoff.
Go deeper
Technical workbookDocumentationTechnical workbooks are maintained in English. Workspace access and available capabilities depend on your deployment and permissions.
Bring your own workflow.
Explore how these practices could fit your team, your data, and your operating requirements.