Skip to main content

From a Business Request to Reviewed Requirements: A Learning Path

Business Analysis, Change & TransformationLearning Paths

By Jefferson Otonbara Imgbi

Published
8 October 2026
Last reviewed
8 October 2026
Turn a fictional business request into a reviewed set of requirements and a change-impact note. Follow five ordered resources with practical outputs and review questions.
Image
A magnifying glass, interview notes and requirement cards leading towards a small prototype.

Goal and audience

Turn a fictional business request into a reviewed set of requirements and a change-impact note.

This self-directed practice path is for learners who want an organised way to use existing Digest resources. It is not an enrolled course, a qualification or a certificate programme.

Before you start

A simple fictional service request and a document editor. No access to customer or employee data is needed.

As an RDE planning estimate, allow around 30 to 60 minutes for each step, or roughly 2.5 to 5 hours in total. Your pace and prior experience will affect the time needed. Pause and repeat a step when its review question remains unanswered.

How to use the path

Follow the steps in order. Each resource opens in a new tab; keep this path open and return here for the activity and review question. Previous and next links move between steps on this page. Record your own notes and outputs privately. This page does not track, save or certify completion; account-based progress tracking is deferred.

Step 1 of 5: Frame the problem

Open resource: Define the Problem Before Choosing the Solution Opens in a new tab.

Practice

Use a fictional request such as a new attendance dashboard. Describe the current situation, the affected people and the decision or task that needs support before naming a solution.

Produce

A problem statement and three uncertainties.

Review before moving on

Have you described a problem that can be investigated without assuming a dashboard is the answer?

Step 2 of 5: Investigate user needs

Open resource: A Practical Guide to Discovering User Needs Opens in a new tab.

Practice

Follow the guide with a fictional administrator. Record the request, the underlying task and what evidence would help you understand the need. Label invented observations as fictional.

Produce

A needs note with observations, assumptions and open questions.

Review before moving on

Can you distinguish what the user needs to achieve from the feature they requested?

Step 3 of 5: Prepare a stakeholder conversation

Open resource: Plan a Useful Stakeholder Conversation: A Practical Workbook Opens in a new tab.

Practice

Use the workbook to plan questions for one affected role and one decision maker. Choose questions that explore current work and constraints without pushing your preferred solution.

Produce

A conversation plan and an evidence-recording approach.

Review before moving on

Which question could challenge your initial understanding rather than merely confirm it?

Step 4 of 5: Review a small requirement set

Open resource: Requirements Quality Review Checklist Opens in a new tab.

Practice

Draft three requirements for the fictional case. Use the checklist to identify ambiguity, missing context and a practical way to check each requirement. Keep a record of amendments.

Produce

Three reviewed requirements and a review log.

Review before moving on

Could a reviewer tell what would satisfy each requirement and what still needs a decision?

Step 5 of 5: Assess the likely change impact

Open resource: Change Impact Assessment: A Practical Planning Template Opens in a new tab.

Practice

Use the template to identify affected roles, process steps, information and support needs. Mark unconfirmed impacts and assign a question or review action for each.

Produce

A change-impact note with owners to consult.

Review before moving on

Have you identified who needs to confirm the impact instead of presenting guesses as agreed facts?

Review your practice pack

Bring the five outputs together. For each, record the date, what you produced, the evidence you checked and the next amendment. Ask a trusted reviewer for specific feedback where possible. Completing the sequence means you have attempted these practice activities; it does not establish job readiness, professional competence or accreditation.

  1. A problem statement and three uncertainties. Record: attempted, reviewed or needs further work.
  2. A needs note with observations, assumptions and open questions. Record: attempted, reviewed or needs further work.
  3. A conversation plan and an evidence-recording approach. Record: attempted, reviewed or needs further work.
  4. Three reviewed requirements and a review log. Record: attempted, reviewed or needs further work.
  5. A change-impact note with owners to consult. Record: attempted, reviewed or needs further work.

Select one improvement and set a realistic review date. Return to the relevant step when your evidence or understanding changes.

Return to step 1

Related resources

Explore related RDE learning