I'm a bit of a process-driven person. I believe strongly that any action or interaction can have macro-level implications and that when sentient entities (people or machine) operate in isolation - self-interestedly - that may be counter to any macro-level goals intended by entities with broader goals. Two examples:
Look at a bar/restaurant.
Primary Use Case: Customer dines
The Use Case begins when a Customer decides to dine at a restaurant. There are many process steps that follow and actions taken by some entities in isolation (Customer chooses what restaurant they want to experience without 'polling' any restaurant actors [they may look at menus online, walk by the restaurant, whatever]). Some of the important process steps:
- Customer makes reservation (optional, depending on type of restaurant). They typically interact with a host(ess) or maitre d', whose job it is to manage restaurant capacity, show a good face, seat customers, etc
- Customer is seated with a menu(host/hostess), given water (bus boy) and awaits their server
- Server takes Customer's order
- Order is fulfilled - Drinks (bartender), appetizers (expo)
- Server delivers order
- Customer asks for check and pays
Without going into details (naming names, etc), order fulfillment models in Enterprise-scale businesses should operate similarly. Too many of them are metrics-driven in only one or more sub-function. Sales/Service Delivery/Billing Operations are all acting self-interestedly and are quick to 'push-back' because they cannot process something that has entered their processing queue for x, y or z reason. Without sufficient, HOLISTIC, process management, the Customer experience is negative.
Whatever the industry, strive to understand why you are doing what you are doing and in support of what greater goal. Doing that, you'll never fail to meet or exceed Customer expectations
No comments:
Post a Comment