Skip to main content

Business Processes and Rules

Sometimes we sell a product to businesses that improves their efficiency. Improved efficiency can help the business achieve:
  1. Increased production or sales volume.
  2. Lower production and operational costs.
There is a discipline called "business process improvement" (BPI) dedicated to the subject of improving operational efficiency. Companies like Dell spend a great deal of time on BPI projects to determine how they can make different aspects of their business more efficient.

Key concepts in BPI include business processes and business rules.

Business processes are the steps a business executes to achieve their objectives. Accepting and processing orders, doing payroll, and hiring and firing employees are all examples of business processes.

Business rules are rules the company follows as it executes its business processes. An example is a pricing rule that states the minimum price or margin a sales person is allowed to negotiate with a customer. You can also view the steps within an established business process as rules; i.e. the rule is that the employees follow those steps.

When we are developing a product for sale to businesses, it's important to understand the business processes and rules of the businesses we are targeting. That way we can understand how best to deliver value - a product that will improve the businesses' operating efficiency.

In my next entry, I will explore the relationship between product requirements and business processes/rules.

Comments

rodgert said…
Hi Roger,

I recently when for an interview where I was asked

Explain the difference between a business requirement and a business rule?
Roger L. Cauvin said…
My next entry addresses the question you were asked in your interview.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the