Brainstorm – How to get best outcome

Brainstorm sessions are sometimes perceived as the fallback action. Meaning, we don’t know what else to do. Which highlights key strengths, Brainstorming opens new perspectives and gets people insights through participation.

Usefulness

Before listing out use cases, let’s look at the steps that a Brainstorm session goes through. The starting point is a question. To get more then Yes/No, it must be an open question that will trigger participants thoughts and imagination. It requires a team of participants. They will contribute to the brainstorm by submitting as many ideas as possible. When this is completed, the ideas are sorted into groups or categories. Although these resulting groups lead into the following step, we’ll consider this the end of the brainstorm.

In meeting room: Useful but not ideal

To understand the usefulness of brainstorming, let’s loop back on the above:

  • It enables to get insight into a question or problem.
  • It enables, if not already done, to identify stakeholders. Best results are obtained when participants have a diverse perspective.  That includes experts and novices. That can also be different roles such as users, operators, testers, managers, suppliers, customers or others. Eventually, an outsider, with no knowledge of the area, could think out of the box.
  • It’s an opportunity to have some fun while working. After all a good laugh brings people closer. A good way to fit in some team building with generating new ideas.
  • While organizing the many ideas that were put forward, the participants dialog to build knowledge. They will gain clarification on several points. Each individual will learn about other’s perspective. They will build an overall understanding. And, most importantly, they will provide potential answers to the question.

Getting to use cases, there is the obvious general domain of Creative problem Solving. It is a method to gain insight or clarification on a problem statement, a project scope. I can be used to build lists such as influencing factors, requirements, potential solutions, criteria or constraints. In the earlier stages of a project, the safe zone contributes to building a closer team, and increasing participants acceptance.

Brainstorm Ground rules

Osborn had two principles that contribute to idea generation efficiency: Defer judgement, Reach for quantity. From these principals, four ground rules are deducted:

  • Aim for QuantityQuality comes in later
  • Withhold criticismThe evaluation is later
  • Welcome wild ideas – Wild ideas are new ones
  • Combine and improve ideas – Expand to generate new ideas

You can extend these ground rules if you see a need. For example, everyone must find a gazillion ideas. Simply bare in mind, too many or strict rules will influence creativity.

Brainstorm Pitfalls and Advice

There are many pitfalls and opportunities to get the most out of a Brainstorm session. Here is a shortlist of the most meaningful ones:

Trying to address multiple questions at a time

A Y/N question and a broad question are two extremes to avoid. By aiming to get too tackle too much, the result will also be broader. And, you might not answer anything at all. While preparing and presenting the question to participant, the SMART technique (i.e. Simple Measurable Achievable Relevant Timely) can be helpful to refine the question. No need to aim for perfection, it is about setting a direction versus dictating an outcome. That would hinder the creativity. For the team to start, it is important that the challenge is generally understood and accepted. This can be achieved through open discussion and adjustments.

Team with single perspective

If we looked at stars for the first time without any scientific knowledge. We’d probably all describe bright spots moving in the night sky. Through history, people with different ideas and perspective have influenced that initial perception. When identifying participants, the team should ideally cover all perspective of the object. There are likely to be constraints such as sizes, availability, interest. Look for a compromise then avoids the single sided view.

Intimidated participants

A common example is a manager in the room. Some people may hesite to express themselves freely. There are the ground rules of criticism, participation and respect. Creating a safe environment is essential. The brainstorming in Goal Nabber uses anonymity to minimize that effect. Also, it allows for wild out of the box ideas to come out. The chat room offers the possibility to ask questions (with respect). Breaching barriers should be a way to generate new ideas.

Monopoly of speech time

If a person is capturing what others are saying, there are a few inconveniences. Firstly, ideas can only come one at a time. Secondly, speech time could be monopolized. Third, a new line of thought and ideas may be cut off. Brain writing can be effective for such situation. The limitation is that participants still need to pay attention to new ideas in order to build on them. To balance the collective and individual contribution, Goal Nabber shows the question and image with a word map of the collective ideas. The word map changes real time with newly submitted ideas. Participants are using their own device to submit their ideas. They are also able to scroll the submitted ideas freely.

Bias

Bias has several causes. Our information is usually partial because of availability or sampling. Our objectives and people that we want to please (e.g. boss, customer) are influencing our actions. And, there are many more factors that can influence our perception and reasoning. Nothing will beat seeing it with your own eyes. Gemba’s, or Go See sessions, play an important role in Lean Six Sigma. In a meeting room or conference call, you will rely on memory. That’s not ideal. Actual observation is the best approach. By using Goal Nabber on a mobile device, the participants can observe “out in the field” and submit ideas/notes live. Ideas are closer to reality. And, the inputs are collected together immediately with no extra effort.

Apply best practices

Try Goal Nabber

To conclude, the above advice applies even if you’re not using Goal Nabber. Goal Nabber makes it easier to apply. That way, you can focus on the more important aspects, and the desired results. If you’re not already using Goal Nabber, you can begin with a free trial:

Force Field Analysis (New Feature)

One of the recent additions to Goal Nabber is the Force Field Analysis. It was described as a Change Management technique by Kurt Lewin (1940s) to analyze competing forces. The same principals were described by Benjamin Franklin to balance pros and cons in a Decisional Balance sheet. Thus, two situations where this can be used are decision making and evaluating a desired change.

It is a simple and practical way to list and visualize opposite factors. The approach is the following:

  1. Define the situation to evaluate.
  2. Identify influencing factors distinguishing driving and retraining ones. This can be done separately. However, it often happens that they are identified simultaneously.
  3. Score their intensity based on greater or lesser influence.
  4. Analyze the result. Equal opposing forces and factors point to a status quo. For change to occur, the equilibrium must be disrupted. That can be done either by strengthening the driving factors, or by weakening the retraining factors.
Force field Analysis captured as highlight in Goal Nabber

There are potential weaknesses to be aware of. This is a subjective approach both while identifying and scoring factors. To overcome this, the team involved should be representative of all stakeholders. Stakeholders can be subject matter experts, manager, operators, support agents, change agents, suppliers and customers. Too small a team will not be representative of all perspectives. And, too many (e.g. over 10) will become inefficient. A representative team will provide a better insight to identify the different factors. And in absence of quantified information, it will also result in a richer discussion to determine the influence of the factors. By mitigating the weaknesses, the outcome of the force field analysis will give a better insight into the strongest factors and ones that can be changed.

Voice of Customer

For companies and projects, a critical success factor is to know the customer expectations. First reason is 95% of companies are reaching out to customers. Second reason is best in class VOC perform better. They have a 55% higher retention rate. Their customer support cost decreases 23% year to year. And, they have a greater employee engagement. And, it cost 25 times more to attract new customers then to retain them. In most cases, the objective is to implement changes or improvements that will increase customer satisfaction. Because it is crucial to project success, it is one of Goal Nabber features.

Where and When

VOC is used to understands the customer’s want, needs and requirements. Otherwise, the probability of meeting expectation is greatly diminished. It should be part of the first steps of any project or initiative. It avoids dissatisfaction and wasted effort. During the project, it is a reference for decision making and validating outcomes. Even in “sure” cases, it allows to confirm the alignment with the sponsors, customers and the team.

Customers

There are usually many customers. One distinction is external (e.g. end customers, users, leads, prospects), and internal (e.g. sponsors, business stakeholders, management). When looking at a process, a SIPOC is a good way to ensure that customers have been identified. Before beginning to collect information, check the list of customers. It should have the stakeholders that have influence or are impacted.

Collecting needs and expectations

With the customers identified, the next step is to obtain useful information with the least effort. There are several methods available to gather customer inputs. Interviews, Focus groups, Surveys, Observation, Online reviews are possible methods. Each have their strength and weaknesses. They all need preparation starting with having an idea of the information to gather. One place to start is confirming that the customer has something to gain from the project objective. A combination of open and close questions to understand the why’s and the what’s. While gathering information, keep an open mind. Save statistics and trends for the analysis. Avoid too many, changing or wrong questions. Take negative feedback as an opportunity to improve. Most of all show the customers that you are listening constructively to their feedback.

Customer needs through VOC in Goal Nabber

Analyze

The analysis will depend on the amount and type of information available. It will likely involve different information sources, sorting Needs & Wants, figuring out the reasons. This is about translating verbatim comments and other data into customer requirements. To demonstrate active listening, the outcome should be shared to get acknowledgement or adjustment. This also gains buy in from the stakeholders.

Action

One pitfall that happens too often is to not action the VOC. There is no need to wait for later. It can define criteria the decision making. Objectives can be aligned with customer expectations. Trigger new improvements initiatives and projects. Making these actions visible to the customer will increase their interest and fidelity.