A business process is the flow from the event that starts a piece of work to the result that ends it: who does what, in what order, with which inputs and outputs. The basic way to improve it is to map the process as it is done today, then find the steps where time leaks away (retyping, waiting, missed deadlines) and eliminate, combine or automate them.
What is a business process?
A business process is a set of connected steps that produce one result. For example, "take a customer order, deliver it and get paid" is one process that runs through quoting, order entry, shipping, delivery, invoicing and collection.
When you document a process, writing down the six elements below keeps anything from being left out.
| Element | Meaning | Order-to-cash example |
|---|---|---|
| Trigger | The event that starts the process | A customer's quote request email |
| Steps (activities) | The work to be done, written briefly as verb + object | Prepare quote, check purchase order |
| Owner | The person or team responsible for the step | Sales, production, accounting |
| Inputs and outputs | Documents or data that come into a step and the result it produces | Purchase order → one row in the order log |
| Rules | Deadlines, approvals, quality conditions | Reply within 3 days, manager approval for discounts |
| End | The state at which the process counts as finished | Payment received |
How do a process, a procedure and a manual differ?
| Term | Scope | Example |
|---|---|---|
| Business process | The overall flow of work across people and teams | From quote to payment |
| Procedure | The order and rules followed within one step | When a PO arrives, check items, quantities and delivery date, then log it |
| Work manual | Instructions detailed enough to follow, including screens and forms | How to enter rows in the Excel order log |
It is usually most efficient to agree on the overall process first, then write detailed procedures and manuals only for the steps where problems often occur.
How do you draw a process map?
A process map (flowchart) is a picture of the process. Rather than opening a tool right away, writing each step on a sticky note and arranging them is a fast way to start.
- Define the start and endSet the scope first, for example "starts when a quote request email arrives, ends when payment is confirmed." If the scope is too broad, the map never gets finished.
- List the steps in orderWrite each step briefly as a verb and an object, such as "Prepare quote" or "Check purchase order."
- Split lanes by ownerDraw a horizontal lane (swimlane) for each owner such as sales, production and accounting. You can then see where work passes between people, which is where most waiting and dropped items happen.
- Mark decisions and documentsShow decisions such as "Is it in stock?" as diamonds and documents that move between steps with the document symbol.
- Note the time each step takesRecording working time and waiting time for each step gives you evidence later when choosing what to improve.
| Symbol | Shape | Used for |
|---|---|---|
| Start/End | Rounded rectangle | Beginning and end of the process |
| Process | Rectangle | Work done by a person or system |
| Decision | Diamond | A point that splits into yes or no |
| Document | Rectangle with a wavy bottom edge | Documents such as quotes and purchase orders |
| Flow | Arrow | Direction to the next step |
These are common flowchart symbols. For more precise models, such as for system development, use BPMN notation.
What goes into a process definition document?
If the process map is the picture, the process definition is the same content written as a table. Put the items below as columns on one Excel sheet and write one row per step.
| Item | What to write |
|---|---|
| Process name and purpose | What the work is for (e.g., deliver ordered products on time and get paid) |
| Scope | The trigger and the end state |
| Steps and owners | Step names and the person or team responsible |
| Inputs and outputs | Documents that come into each step and the result it produces |
| Rules | Deadlines, approval conditions, checkpoints |
| Tools | Systems or files used (email, Excel, ERP, etc.) |
| Metrics | Numbers that show whether it is working (time to reply, number of missed items, etc.) |
A free process definition Excel template built on these items is available. Write one row per step and a swimlane process map is drawn automatically; an order-to-cash example is included.
Example: an order-to-cash process that starts with email
Here is the order process of a manufacturer or distributor that receives quote requests and purchase orders by email. The highlighted steps are ones where retyping or chasing can be handed to a tool.
- SalesReceive quote requestEmail → quote logAuto-logged
- SalesPrepare and send quoteQuote file → reply in original threadReply with attachment
- SalesReceive purchase orderPO PDF → order logAuto-logged
- Production · LogisticsProduction and shipping prepOrder log → work order
- LogisticsDelivery and delivery noteDelivery note → delivery note logAuto-logged
- AccountingInvoice and collect paymentInvoice → due date, balanceDue date alerts
The flow of an example company. Steps and owners differ by company.
Common problems at each step, and how to change them, are summarized below.
| Step | Common problem | What to change |
|---|---|---|
| Receive quote request | Requests arrive at several addresses and it is unclear who replies | Collect them in one list (quote log) and put reply deadlines on the calendar |
| Receive purchase order | Typos while copying from the PDF into the order log | Have POs read and logged as rows; people only check them |
| Production and shipping prep | Delivery dates live only in the log and get missed | Put delivery dates on a calendar to see what is coming |
| Delivery and delivery note | Received delivery notes are retyped into the purchase log | Read delivery notes and log them automatically |
| Invoice and collection | Balances on partial payments are calculated separately | Enter payments and let the balance and status be calculated |
Where do you start improving a business process?
Improvement starts with mapping the current process (As-Is) exactly as it is. If you start by drawing the ideal process, it is easy to miss where time is actually lost.
- Map the current processAsk the people doing the work what they actually do and draw it that way. Include exceptions and the things that "aren't supposed to happen but often do."
- Find wasteMark places where the same data is entered twice, where people wait on someone else, where questions go back and forth, and where deadlines depend on memory.
- Apply ECRSAsk in turn whether a step can be Eliminated, Combined, Rearranged or Simplified. Automation is one way to simplify.
- Update the process definitionWrite the improved process (To-Be) into the process definition and map, and share it with the people involved.
- Check with metricsCompare time to reply, time spent retyping, and the number of missed or late items before and after the change.
Which steps should you automate first?
Automation pays off most for steps that repeat often, receive documents in a similar form, and involve people retyping content. Steps that need judgment, such as setting prices, handling exceptions and talking to customers, stay with people, and tools gather and present the information they need.
- Good candidates for automation: copying purchase orders, delivery notes and invoices from email into logs, putting due dates on a calendar, replying with a set file attached
- Steps for people: quote prices and delivery commitments, complaints, approving exceptions
- RPA vs. AI: RPA repeats fixed clicks and keystrokes on fixed screens, so it tends to stop when a document format changes. AI reads the content and finds the values, so different formats end up in the same columns. Either way, it is safer to flag low-confidence items for a person to check.
See the parts manufacturer use case for what automated order processing from email looks like, and the demo for the actual screens.
Frequently asked questions
Is a business process the same as a workflow?
The terms are used similarly. A business process usually means the overall flow of the company's work, while a workflow often means the sequence that runs that flow inside a tool, such as approvals and notifications.
What tool should I use to draw a process map?
PowerPoint or Excel shapes or a free diagramming tool is enough. At first, moving sticky notes around on a whiteboard is often faster.
Does a small company need to document its processes?
Yes, if you want work to keep moving when someone changes roles or is away. Start with one page each for the two or three tasks you do most often.
Where can I see examples of process improvement?
See the use cases by industry, based on quote, purchase order, delivery note and invoice emails. They are illustrative examples built on the demo, not real customer stories.
Will it work with your inbox?
Tell us which email service and document formats you use, and we will show you how it fits.