Most software projects that go wrong do not fail because of the technology. They fail because the process was never written down, so each person imagined something slightly different. Spending a few hours mapping how work really flows is the cheapest insurance you can buy. It makes vendor quotes comparable, shortens discovery and gives your team a say in the design. This guide shows a method that works for owners and managers, with no special tools.

Start from one outcome, not the whole company

Pick a single end-to-end flow that matters, for example enquiry to quotation, order to delivery, purchase to payment or hire to payroll. State where it starts, where it ends and what success looks like. A flow with a clear start and end can be described on one or two pages. Mapping the entire company at once is how mapping projects stall.

The five questions to answer for each step

QuestionExample answer
Who does it?Sales coordinator, then the finance manager approves
What triggers it?A signed quotation arrives by email or WhatsApp
What information is used?Customer, items, price list, payment terms, VAT treatment
What is produced?Sales order, delivery note, invoice
Where does it wait or go wrong?Waiting for approval; stock figure out of date; invoice retyped

Draw it as lanes

On a large sheet or whiteboard, write each role as a horizontal lane and the steps as boxes in the lane of the person who does them. Draw arrows between steps. Where an arrow crosses from one lane to another, that is a hand-off, and hand-offs are where delay, error and lost information live. Mark them. Take a photo and type it up as a simple numbered list so it can be shared.

Capture the exceptions, not only the happy path

  • What happens when the customer changes the order after approval?
  • What if an item is out of stock, or a price differs from the list?
  • Who can override a rule, and how is it recorded?
  • What is done for a VIP customer, a government customer or an export order?
  • How are returns, credit notes and cancellations handled?

Ask the people who do the work, not only their managers. The exceptions are usually where the real rules are hidden, and they are what a generic package handles worst.

Add numbers

  • How many of these flows happen in a normal week, and in the busiest week?
  • How long does each step take, and how long does the item wait between steps?
  • How many users take part, in how many locations?
  • Which documents are produced, in which language, and who receives them?

List the data and the systems it touches

Write the main records involved, such as customers, items, suppliers, contracts and staff, and where each one lives today. Note which other systems the flow must connect to: accounting, WhatsApp, payment, delivery or government portals. This single page tells a vendor more than a long feature list.

Turn the map into a requirements pack

  1. The one-page process map with lanes and hand-offs
  2. A list of exceptions and special rules
  3. Volumes, users and locations
  4. The documents and reports you need
  5. The systems to connect and the data to bring across
  6. Three outcomes you will measure after go-live

With this pack in hand, a vendor can quote precisely, you can compare proposals fairly, and your team will recognise their own work in the design. See also our guides on the software project brief template and the demo scorecard for comparing vendors. If you would like help mapping a process, contact our team.