Updated: Jul 23, 2020
We have successfully wrapped up Perspective 3 around process and now it’s time to tackle the topic of business rules. As you look through these different perspectives and start to uncover how the organization in which you work operates, you have come across business rules along the way. Whether you knew it or not, you have probably identified some as you discuss the customer experience, and as you mapped/modeled processes. We have definitely talked about why it is not a good practice to process map/model business rules. It will add some complexity to the process map/model that will make it very hard for the audience consuming the document to follow. However, business rules are very important to capture and can tell you a lot about your operations.
So, what is this thing called a business rule? In its simplest definition it’s a rule that defines, or constrains some part of the business operations. The outcome of the rule should either be true or false. Business rules are extremely important to capture, and understand in your business as many of these rules can help organizations stay compliant with policies or regulations that may govern their organization.
Let’s go a little deeper and look at how to identify, write, and store business rules.
1. How to identify business rules
As stated above, a business rule is a rule that defines, or constrains, some part of the business operations. Business rules are typically owned by the business, unless of course the organization in which you work is set up in a hybrid function with business and technology mixed, but typically the rule should be owned by the business. Business rules tend be static, and not change much over time. However, that doesn’t mean they do not, or will not, change.
One way to identify a business rule is if the business owner needs to make a decision. This is not always the case because not all business rules are decisions, b