Basic Business Requirements Workshop Facilitation

Ok, so you’ve decided to use the Nimblex Platform for your next digitisation or process automation project.

But you are unsure about the high-level requirements, scope, the buy-in of the rest of your team, cost and many more issues which can muddy the water for you.

If this sounds like your situation, then we can help you to save a lot of wasted effort and money down the line by the facilitation of a discovery workshop.

This type of discovery workshop allows everyone to meet and lay their cards on the table for example what frustrates them with the current application/process, queries they may have about Nimblex Platform, question about how the project will be run and most excitingly to contribute with their bright ideas on what is the high-level business and functional requirements to ensure success.

Who should be involved:

  • We recommend a small group of people that is highly knowledgeable about the problem you wish to solve.
  • No more than 5 on this stage and it needs to include the key sponsor.
  • Beside the Sponsor, the rest of the team should be representatives from the group of people who is going to use the new system i.e. future users.

Discovery Workshop Breakdown

The following is the typical topics which we will discuss during the workshop. These can vary from project to project, but the basic framework remains the same:

  1. Introduce everyone and communicate purpose of the workshop
  2. Agree on the workshop objectives and outcomes
  3. Explore the Problem Statement and Vision of the project
  4. Define the Scope of the project
  5. Define the ‘user profiles.’
  6. Create together a high-level process flow
  7. Explore the workflow requirements and notifications
  8. Understand the desired reports and dashboards needs
  9. Use the MoSCoW (Must, Should, Could, Won’t) method of prioritisation to:
    1. High-level business requirements
    2. Formulate the ‘features’ that need to be included
    3. Non-functional requirements
  10. Determine roles and responsibilities and next steps

The workshop tends to enhance the scoping phase of the project.



Now is the perfect time to get everyone involved in the project by means of a discovery workshop. It will help you to

  • Kickstart your project as needed
  • extract information and ideas from your stakeholders about the problem you wish to fix
  • define what success will look like
  • gain clarity on the next steps

What Comes After the Discovery Workshop?

The discovery workshop enables both you and eBMS to gain clarity about your various requirements.

Following the workshop, eBMS will produce some of the following documents:

  • Notes of the meeting
  • High level business requirements document e.g. objectives, vision, problem statement, etc.
  • High level functional requirements document e.g. lists the requirements of the application from the perspective of the users, demonstrating the ‘why’ and ‘what’, rather than the technical 'how'
  • High level functional requirements e.g. expectations around hosting, security, etc.
  • High level transition requirements e.g. training needs, data transfer, etc.
  • A project Plan
  • Firm proposal

The above will give you all the necessary information to get off to a great start.