Map the Workflow Before You Build Custom Business Software

c
ceofounder
17 min read 38 views
Map the Workflow Before You Build Custom Business Software
Process Mapping

Map the Workflow Before You Build Custom Business Software

Software can make a clear process easier to follow, but it can also make a confusing process faster and harder to correct. Map the work before deciding what to build.

A business may ask for a dashboard, booking app or inventory system when the real problem is that nobody has agreed who confirms a booking, when stock should be reserved or who can approve an exception.

Choose one workflow with a visible pain point

Start with an important process that happens often, such as handling a new enquiry, processing an order, approving a service request or closing a job. Keep the first mapping exercise narrow enough to finish.

  • Point 1Trigger
  • Point 2Responsible person
  • Point 3Information required
  • Point 4Decisions
  • Point 5Hand-offs
  • Point 6Final outcome

Describe what really happens

Ask the people who do the work to walk through a recent example. Include exceptions: missing information, a customer changing a request, a payment needing confirmation, an absent approver or a record that needs correction.

The official process and the real process are often different. Both need to be understood before scope is agreed.

Identify waste and control points

Look for duplicate data entry, waiting, repeated questions, ambiguous ownership and decisions that nobody can explain. Also identify controls that protect customers or the business, such as approvals, verification, reconciliations or review steps.

✕ Waste
  • Duplicate data entry
  • Waiting between steps
  • Repeated questions
  • Ambiguous ownership
  • Decisions nobody can explain
✓ Necessary control
  • Approvals before commitment
  • Verification of details
  • Reconciliations
  • Review steps
  • Protection of customers
Not every manual step is waste. Some exist for a valid reason.

Write requirements as observable behaviour

Instead of describing a feeling, describe something that can actually be seen and tested. Clear requirements make testing and quotations more meaningful.

Rewrite the requirement

From vague wish to observable behaviour

Before “The system should be user friendly.”
↓
After “A coordinator can view all open requests, identify the person responsible and see the next required action.”
Before “Automate billing.”
↓
After “Specify what triggers an invoice, what data it contains, who reviews it and how corrections are handled.”

Clear requirements make testing and quotations more meaningful.

Define what will not be built yet

Separate must have launch capabilities from future improvements. Record dependencies such as data clean up, staff training, existing software, email or payment integrations.

A staged scope helps the business validate the process before investing in every possible feature.

Interview people across the hand off

The person who starts a process may not see the delay created for the person who finishes it. Speak to the people who receive, approve, perform and report on the work. Compare how they describe the same record or status.

Interview 1 Who receives the work
Interview 2 Who approves it
Interview 3 Who performs it
Interview 4 Who reports on it
Differences often reveal missing definitions that must be resolved before the system can usefully enforce the workflow.

Quantify pain without inventing savings

Where practical, observe task duration, rework frequency, waiting time and the number of hand offs. Use a few representative cases and record the assumptions.

Do not promise a percentage reduction before the process has been tested. A baseline gives the team a way to evaluate improvement later and helps distinguish high cost problems from minor annoyances.

Write tests from the requirements

For each important requirement, define a scenario and expected result. A requirement about approvals should include an ordinary approval, a rejected request, a missing approver and an attempted action by an unauthorised role.

Test the approval rule

Four scenarios to write down

1An ordinary approval works
2A rejected request is handled clearly
3A missing approver does not stall silently
4An unauthorised role cannot approve

These scenarios help the developer and the business agree what working software means before a deadline arrives.

Decide when to stop adding scope

New ideas will emerge during discovery. Keep them in a prioritised backlog and ask whether they solve the core problem, depend on another feature or can wait.

First release
  • Completes one workflow end to end
  • Handles the agreed exceptions
  • Has a test for each key requirement
  • Can be used consistently by staff
Later backlog
  • Nice to have features
  • Reports nobody has asked for yet
  • Extra integrations
  • Ideas that depend on other work
A small system used consistently can provide a better foundation than a broad system that has too many unfinished paths.

Turn the process map into a buildable brief

1

Observe a real example of the current workflow and record the trigger, people, information, decisions, hand offs and exceptions. Include the employees who receive and finish the work, not only the manager who requested automation.

2

Identify unnecessary duplication and necessary controls. Write requirements as observable behaviour and define what the system should do when information is missing or an approval is rejected. Estimate the current time or rework where practical so improvement can be evaluated honestly.

3

Agree which requirements belong in the first release and write a test for each important one. Keep future ideas in a separate backlog. Use the discovery findings to compare proposals and prevent new features from being added without a clear business reason.

Keep business rules separate from technical assumptions

A proposed screen or database field is not itself a requirement. Ask what decision the field supports, who maintains it and what should happen if it is blank or disputed. Record assumptions that need confirmation from finance, operations or leadership.

Assumption register

Resolve these before the team treats behaviour as final

DecisionWhat decision the field supports
OwnerWho maintains the value
EdgeWhat happens when it is blank or disputed

This prevents the development team from embedding unapproved business policy into software simply because an early conversation suggested it. A short assumption register can be reviewed during discovery and resolved before the team treats the behaviour as final.

Example

A repair business may initially request a customer portal. Mapping the current job lifecycle could reveal something different.

Requested A customer portal.
Revealed Missing job cards and uncertain technician assignments.
Better fit A simple internal job workflow might deliver more value than a portal customers will rarely use.

Frequently asked questions

How long should process mapping take?

Start with one high value workflow and map enough detail to agree hand offs, exceptions and acceptance criteria.

Should software automate every step?

No. Some controls or human decisions are necessary; automate only when it improves the agreed process.

Action checklist

  • One workflow and its owner are defined.
  • Normal cases and exceptions are mapped.
  • Controls are distinguished from unnecessary duplication.
  • Requirements describe observable behaviour.
  • Launch scope and future improvements are separated.

Final thought

The quality of custom software depends heavily on the quality of the problem definition. Document the work, involve the people doing it and use concrete acceptance criteria before approving scope.

Ready to map before you build?

Stonehenge Digital KE starts its Business Management System service with a discovery process to understand how the business operates.

Explore the Business Management System Service →
Share Written by ceofounder

Interested in Business Management System?

Let's build this for your business

Replace spreadsheets, paper records, and WhatsApp chaos with a custom system built for exactly how your business works.

Leave a Comment

Share Your Thoughts