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!

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 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 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. Note: Goods may not always be provided for every Service Offe

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search