An organisation chart tells you who reports to whom. It may tell you much less about how a customer actually receives a product. Following one order from enquiry to aftercare reveals the handovers that make the company work—and the gaps that a department-by-department description can hide.
Choose a representative order rather than the most unusual one. If the business sells several very different services, make separate maps. A single crowded diagram can conceal more than it explains.
Begin with the customer’s requested outcome
For an illustrative furniture business, the outcome might be a correctly sized desk delivered on an agreed day. Work backwards through quotation, measurement confirmation, materials, production, quality checks, transport and support. Include the information each stage needs, not only the physical item.
OpenStax describes the value chain as the activities through which a firm creates a product or service. Your order map is a practical way to explore those activities; it is not a complete financial valuation of the company.
Mark the handovers
At each transition, ask who receives the work, what confirms readiness and what happens when information is missing. A drawing approved by sales but never sent to production can matter more than a slow machine.
Use a different mark for external suppliers and partners. Outsourcing an activity changes who performs it, but the customer may still hold the seller responsible for the overall experience. Record the dependency explicitly.
Separate working time from waiting time
An order can spend two hours being worked on and several days waiting for a decision. Do not assume the longest visible task is the main delay. Ask for actual records where available and label estimates as estimates.
A useful table contains stage, owner, required input, completion signal and common exception. Avoid adding decorative complexity before you can explain those five things in ordinary language.
Test the map with the people doing the work
Walk through a completed order with staff from more than one stage. Ask where the official process differs from everyday practice. A workaround may reveal missing information, a system limitation or a responsibility nobody formally owns.
Finish by selecting one handover to improve and a measure that would show whether it helped. For example, track how often production receives a complete specification on the first attempt. The map becomes useful when it changes a specific question or action, rather than remaining a diagram displayed in a meeting room.
Another practical question: When One Supplier Matters Too Much: Questions for a Business Review.