Client Q & A - Building a Business Requirement document

Well…hear I am New Years Day morning dealing with another client question. Everyone is still asleep so I thought I would catch up with some work.

The client question I am dealing with in this article came from a meeting I had last week. They asked a good question which we continually deal with about the creation of a Business Requirements document, the critical first step when beginning a new project.

This client has never put together a document like this before and asked for guidance.

Below is my reply:

The level of detail to provide for the Business Requirements document is up to you and your model, the more detail the better. In some instances we are provided Business Plans to work from; however we spend time distilling all the non relevant information which costs the client.

Your Business requirements document should focus on the following:

1. Key business functions you are creating which provides point of difference.

2. Business functions which are key to your operational effectiveness.

3. Key process work flows around your relationships with your customers. How do you want to interact with customers? How you would like to sell to them and what are the key selling techniques your model utilises to sell to new and existing customers currently. For example do you have a loyalty rewards system which is working effectively? If so, document.

4. Key process work flows around your relationships with your suppliers you will be partnering with. How do you want to interact with your suppliers? How will your supply chain be supporting you in the delivery of your products and services? What type of SLA (Service Level Agreement) is set up with your supply chain to ensure customer levels remain to a high standard. What information do you want sent to your suppliers (if any)?

5. Processes you will be managing manually to begin with and make a point of describing how in the future you will want to automate.

6. How third party software applications (i.e. inventory system, Accounting system) will be utilised to support your model. What are your philosophies around Inventory management? Will you accept orders for stock you do not have, if so then how will you manage back orders?

The best advice I can give you is do not focus on technology when putting this together!  Do not let your knowledge of technology influence your model.

Our job is to configure technology to compliment the model, not the other way around.  Never let technology influence your decision making on how your business should be conducted.  The establishment of business processes comes first because it supports business strengths, business philosophy, and business requirements. Once a business has defined the rules and steps, only then can the selection of technology take place.

This is a common trap many businesses (big and small) fall into, especially these days when complex eCommerce technology is now so readily available.

If the information can be presented in a way where it answers all of the above, we can create a Functionality Requirements document which can clearly identify how technology can be configured to align to your business, and meet all your business needs.

Good luck.

**Its important to note, even though Exceed can and does build Business Requirement documents, it is highly recommended clients put this together. It is your business, your strategy; you know your business better than we do.