Skip to main content

Effective Brainstorming Session

There are several problem analysis techniques which are discussed in the V3 Service Operation book, including brainstorming. I have used brainstorming sessions often in my career. Brainstorming is used throughout the problem solving process whenever the team needs to generate ideas quickly and effectively. Some sessions have been very valuable, others not so much. What was the difference? Basically, we need some structure around the sessions and some rules of engagement.

Let’s begin by defining brainstorming. This is a technique used to quickly generate a list of ideas by a team to solve problems or issues. The relevant people must be gathered together either physically and/or electronically to increase creativity and idea generation in a very short amount of time.

Here are 3 different types of brainstorming methods: 
  • Free Wheeling Brainstorming
    • Participants call out their ideas when they occur to them and in no particular order. A recorder posts all ideas for everyone to see as they are presented.
  • Round Robin Brainstorming
    • Each team member is asked, in turn, for an idea. Members may pass on any round as the session continues until all members have passed during the current round.
  • Slip Method of Brainstorming
    • Each individual writes down their ideas on small slips of paper or index cards. The slips are then collected and organized by the group

 The typical brainstorming session consists of three phases:  
  • Idea Generation
    • Team Leader presents the problem. It should be stated in specific, precise terms and known to all participants. Leader makes sure all understand the problem, the session objective and the brainstorming method. All ideas are recorded on a flip chart, only one person talks at a time to ensure that all ideas are recorded. Team begins generating ideas using the method selected for the session. Do not stop until all ideas are exhausted.
  • Idea Clarification
    • Review the list for understanding and duplication. Do not discuss the ideas now. Testing and evaluation will occur later. Clarification and/or modification of an idea is only done with the approval of the idea originator.
  • Idea Evaluation
    • Review the list to eliminate irrelevancies or issues that are not related to the predetermined purpose of the session. Idea evaluation is often performed in conjunction with other analytical tools. It may take place outside the team meeting itself.

 Here are some Brainstorming Rules to guide your session: 
  • Clearly state the purpose of the brainstorming session.
  • Record ideas where they are visible to the whole group. Recorder writes down the words of the idea presenter unless the presenter agrees on an acceptable paraphrase of their idea.
  • Build on the ideas of others (leapfrog).
  • Strive for quantity (not quality) of ideas.
  • Do not evaluate ideas; there is no right or wrong idea.
  • Encourage presentation of wild or even impossible ideas.
  • Never criticize ideas. Remember the goal is quantity not quality.
  • Everyone contributes.
Brainstorming sessions can be very innovative and constructive. It is crucial that the Problem Manager documents the outcome and any agreed resulting actions. The Problem Manager needs to control the session using the above guidelines. Best of luck, with these simple tips, the effectiveness of your next session should improve!

 

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...