How to blueprint a business process that keeps getting stuck
Sales confirms an order on WhatsApp. Dispatch sees the message, but waits for someone to confirm the delivery date. The founder steps in, the order moves, and the same problem comes back next week. If this sounds familiar, start by drawing the handoff.
1. Name the capability and its outcome. Call the capability Order Intake. Define its outcome as “Dispatch receives a complete order it can act on.” Start when Sales confirms an order and stop when Dispatch accepts it. That boundary makes the first blueprint small enough to validate with the people who do the work.
2. Draw what happens today. Pick three recent orders that got stuck. For each, note which role held the work, which record carried it, what information was missing, and when the order moved again. In USRP terms, Sales, Dispatch and the order record are elements. “Sales hands off the order to Dispatch” is a relationship. The confirmed delivery date is a property of the order record. Draw the handoff as it actually happens, including any workaround.
3. Test one explanation. Suppose two orders waited because the delivery date was missing. Check with Dispatch whether that explains the delay, and ask what blocked the third order. Missing information, insufficient dispatch capacity and unclear decision rights call for different fixes. CABOOM uses the capability as the unit of diagnosis and change.
4. Add a rule and measure the effect. If the missing date was the cause, agree that Sales records the confirmed date before handing off. Have Dispatch record returns and their reasons. For one week, compare the share of orders accepted on the first handoff against the previous week using the same definition. Review a few exceptions before deciding whether to keep or revise the rule.
Try it today. Draw three boxes for the sending role, the shared record and the receiving role. Under the diagram, write the acceptance rule and one measure. Ask both roles to walk through a real order with you. You can use paper or, in AAIBOS, keep the model, rule document and order tracker in the same Operating Space.
This is an illustrative example. The blueprint clarifies the information, responsibilities and exceptions a tool or AI assistant would need to work with later.




Comments