Send to KindleBusiness processes are defined to streamline work efforts, lower costs, and improve customer delight. Some processes are standard and are expected to exist by customers. For example, if you mail a package, you expect to be able to track it. Some processes provide a competitive advantage via superior execution. For example, tight project management will differentiate professional services firms.
From time to time, customers and employees will ask for exceptions. Their reasons could be:
- “I am valuable therefore I deserve an exception.”
- “I am competent, please make an exception.”
- “Your process does not cover this boundary condition, please make an exception while you figure out policy and procedure changes.”
As always, some requests are reasonable, others are clearly a lack of discipline. A couple of common examples:
- Sales people don’t want to update CRM. They claim it takes time away from selling. The consequence is loss of intelligence on the buying/selling cycle for that prospect.
- Software developers don’t want to document their design or code. They assert it interferes with their deadlines. The consequence is higher costs when debugging or enhancing code.
- Business users don’t want to follow the governance model and want to rush their proposals into implementation. They worry that pointless objections will delay business benefits. The consequence is loss of trust and a power struggle.
Workarounds and exceptions make processes complex. Sensible managers pick their battles when granting or denying exceptions. It is never easy to decide whether an exception should be made, therefore mindfulness and wisdom, rather than logic is the best tie breaker.
