Mapping workflows is about making invisible work visible. It helps a team understand how work actually flows from start to finish — not how people think it flows, but how it really happens in everyday life. For beginners, it’s one of the most eye‑opening parts of Agile because it reveals delays, confusion, and hidden steps that slow teams down.

What a Workflow Is

A workflow is simply the series of steps something goes through before it is finished. In normal life, you already use workflows without realising it.

For example, cooking jollof rice has a workflow: Buy ingredients → Prep → Cook → Taste → Serve.

The same idea applies to digital work, service delivery, and team projects.

Mapping a workflow means drawing these steps out so everyone can see them clearly.

Why Mapping Workflows Matters

When a team maps a workflow, they can:

• See where work gets stuck
• Spot unnecessary steps
• Understand who does what
• Improve speed and quality
• Reduce stress and confusion

It’s like looking at a bus route map in a new city. Once you see the stops, the journey suddenly makes sense.

How Workflows Look in Real Organisations

In the NHS A workflow might show how a patient books an appointment, from clicking the website to receiving confirmation.

In a council A workflow might map how a resident reports a pothole and how the request moves through different teams.

In a charity A workflow might show how donations are processed or how volunteers are onboarded.

In a tech startup or big tech company A workflow might map how a new feature moves from idea → design → development → testing → release.

Every organisation has workflows — Agile teams simply make them visible.

Common Workflow Steps

Most workflows include steps like:

• Request — someone asks for something
• Review — the team checks what’s needed
• Do the work — the main activity
• Check the work — testing or quality checks
• Deliver — handover to the user or customer

Once mapped, these steps help the team understand where improvements are needed.

What You Discover When You Map a Workflow

Beginners are often surprised by what they find:

• Steps that no one realised existed
• Work waiting in queues
• People doing duplicate tasks
• Bottlenecks where everything slows down
• Handoffs that cause confusion
• Missing information that delays progress

Mapping the workflow doesn’t blame anyone — it simply shines a light on reality so the team can improve together.

Practical Application (Walk‑Through Together)

Let’s imagine a simple everyday workflow: ordering a takeaway in a new UK city.

Step 1: List the steps as they happen

• Open the food app
• Browse restaurants
• Choose a meal
• Place the order
• Restaurant prepares the food
• Driver picks it up
• Food arrives
• You check the order

This is your initial workflow.

Step 2: Look for delays or pain points

• The app loads slowly
• Delivery takes longer on weekends
• Sometimes the driver can’t find your flat

These are your bottlenecks — places where the workflow slows down.

Step 3: Think about improvements

• Save your favourite restaurants
• Add clear delivery instructions
• Order earlier on busy days

You’ve just mapped a workflow and identified improvements — exactly what Agile teams do in NHS digital, councils, charities, and tech companies.

Your Turn (Activity)

Choose a small process in your life — maybe preparing for work, applying for a job, or organising your bills.

1. Write down each step from start to finish.
2. Circle any steps that cause delays or stress.
3. Identify one improvement you could make today.
4. Keep the workflow visible — this is your personal process map.

You’ve just practised real Agile workflow mapping.

One Thing to Remember

A workflow map turns confusion into clarity — it shows how work truly flows so the team can improve it together.