Skip to main content

Brainstorming Techniques for a Business Analyst

Brainstorming is my favorite and in my opinion the most productive method or the technique one can try out when it comes to analysis or trying to solution a problem.



It’s a very simple method and I will point out some techniques which you can use during your session.

1. Be very thoughtful when you are selecting people 💡
You have to get the most productive, solution oriented and technical people into this. In my work I usually invite,
  • The product owner or BA - Who knows in and out of the product from customer point of view
  • The architect or the tech lead - They know the functionality of the system and the technical aspect of it 
  • Solution architect or engineers – So we can have many solutions on the table 
  • QA – Because they think in different angles 

2. Do your homework and be pro-active

Since you are going to be the organizer of the session you have to know what the problem you are going to discuss, give them a background as to why we need to have the change, present them few possible solutions (this is not a must since the goal of the session is to come up with a solution) 
Always keep in mind to plan the session 3,4 days in advance so that they also can prepare for this when they are walking into the session.

3. Plan your resources 
Find a bigger meeting room –Since people are going to sit and discuss about problems and solution they should not feel packed. Need to have space to walk and talk. I would personally recommend if all the attendees can be in the same place physically. But if it’s not possible try to get them in a video conference so that everybody feels connected.

Materials – A place where you can draw (white-board, canvases) marker pens with different colors, sticky notes etc. (Once you are in the meeting you cannot run here and there to find things you need to draw and write. So make sure you have everything you need.

4. Make everyone feel comfortable

We have different personalities in our working environment. Some people can be very straight forward whereas some can be really shy. But again we need to hear what they have to say. Don’t be so formal when it comes to a session like this. Make a joke or a two and feel them comfortable. If they are not talking then ask questions and make them talk. If they have a problem of speaking the language don’t hesitate to change the language you speak in the middle without noticing that you are doing it on purpose.

5. Draw and write
Trust me this works! 👌
Just don’t talk and talk during the entire session. Draw diagrams, write down the points, and make use of all the materials you got. Something we don’t get the problem or the solution by speaking about it. But if we can draw a diagram then it can be more productive.

6. Plan your time
Don’t plan any long sessions. Keep it to maximum 2 hrs and have breaks in between. Have a cup of tea or eat a piece of cake. These simple things can directs us to a great solution at the end.

7. Summarize
At the end of the session always summarize what you discussed. This is where all your diagrams and note are coming in handy. In the very first session we might not have a solution and its fine. Plan then next session this time itself. Inform the attendees so that they also can do their homework.

Try doing these few techniques when you are planning for your next session and see what has improved 😊


Comments

Post a Comment

Popular posts from this blog

What is a User Story and Tips of Writing an Effective User Story

What is a User Story ? We can define a user story as the short and simple description of a functionality used in Agile practice. Basically they are written to capture the requirement from the customer or the end user perspective. It will simply say What type of users, What they want and Why they want it. The user stories should be written in a language where it is clear to both the customer and the development/QA teams as to what the customer wants and why he wants it and what kind of customer wants it.  Development team should understand the customers need and they should take care of how to cater the requirement from technical perspective. There is a simple structure to a user story. As a <<CUSTOMER TYPE>> I want <<WHAT CUSTOMER WANTS>> So that <<WHY CUSTOMER WANTS IT>>  Let me elaborate more on this taking an example.  Assume a tutor wants to publish his/her tutor services for students online for...

Best Agile Practices to Follow

Like I mentioned in my previous blog post I will be elaborating more on what are the best practices we can use when we're working in an Agile environment. I hope you all are familiar with the term Agile and we can easily put it as building a software incrementally from the start of the project, instead of trying to deliver it all at once near the end.That's simply what Agile means.  Scrum is one of the subsets of the agile methodology and the most widely used framework process in agile development. (A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. (For example, the Scrum process framework requires the use of development cycles called Sprints)  I am purely writing this blog post based on my professional experience which I gathered when working with an agile environment.  Plan your Sprint at least a week prior  As business analyst you have to work closely with the s...