AddThis Social Bookmark Button

Common Mistakes Made By Business Analysts Playing the Role of Facilitator

In Agile projects, the business analyst can elicit the business requirements more effectively by facilitating the meeting rather than interviewing stakeholders individually. Here are some of the common problems that a BA can encounter.

Problems in the Meeting

Failure to Relate to Participants: This is the most commonly mistake made by the facilitator and is usually caused when the facilitator has not prepared for the meeting by reviewing the background of the participants and categorizing them. Each participant has a different background and different characteristics. The facilitator cannot treat the participants the same or as a generic person.

Failure to focus on the Meeting Content: When too much information is being exchanged during the dialogue of the group, it becomes difficult to direct the participants to focus on the key point of the discussion. The facilitator must identify key words for each point as a summary of the content to help visualize the discussion. If this is not done the team may become frustrated, especially if the discussion is going around and around resulting in a state of confusion. The facilitator must identify each point, capture it, organize it, synthesize it and clearly document it. People expect the meeting process to be well managed and these steps will help meet that expectation.

Failure to Use Group Memory: People can only tolerate so much pure discussion without having something written down. If the facilitator encourages discussion and listening without writing anything down, participants may begin to feel that this is a just an informal discussion. Facilitators must create or reference visual memory at least every fifteen minutes. As the meeting proceeds, the amount of written documentation will continue to grow. It is also important to make use of any support materials before, during or after the meeting. Remember that written words, and diagrams, are more memorable than spoken words.

Problems with Participants

There may be minor problems with some of the participants during a session. However, there may be some serious problems with an individual participant that can impact the entire team. So let me explain what I have encountered.

Blue-Sky: Blue-Sky participants are progressive and optimistic people who believe they can accomplish complex tasks. They tend to view their objective as part of the group as a mission to seek out new information, to discover new ways of doing business and to venture where no other team has ventured before. This type of person wants to take on as much as possible, to change as much as possible and to totally re‑engineer the business often using new and advanced technology. The problem is that the organization may not be ready for such drastic changes. The intent of this type of participants is good but the facilitator must rein in this person by directing questions to all of the other participants. The facilitator should determine if the ideas in the discussion are realistic and achievable within the boundaries and the budget of the project scope. The facilitator should involve the team in determining the direction of the conversation rather than trying to cut off the discussion point.

Snowball: This type of participants likes to continually add one more item to the discussion. They usually say, "While we are doing that, let's also do this..." The difference between a blue sky and a snow ball participant is that the blue sky participant will talk about doing everything at once, while the snow ball participant adds one thing at a time. This technique can add quite a bit to the discussion points over the course of the meeting. The facilitator needs to recognize that the added item identified in this manner is not directly part of the effort. The facilitator should validate with the group if the discussion point is within the team's scope and a part of the team's objectives.

Wanderers: This type of participant likes to meander during their discussion point or talk about something that is not related to the topic nor follows the dialogue that was in progress. Wanderers enjoy tangents and digressions. They tend to begin to speak before they have thought out their ideas. The facilitator must stop the wanderer before too much time has been wasted and/or as soon as the facilitator recognizes that the discussion point is not relevant to the topic. The facilitator should consider if it is a digression or not in order to get back to the topic. Often these points can be put on a "parking lot" to stop the discussion and return to the points at hand.

Philosophers: This type of participant likes to inject academics into each discussion topic. This person's language skills are advanced and often speak using a large vocabulary of difficult and often unrecognizable words. Participants who are more practical will find it difficult to work with the philosopher. The facilitator will need to rephrase, or summarize, what the philosopher has said in order for all the participants to comprehend the discussion point. The facilitator needs to verify with the group if the ideas expressed in the discussion point are practical and feasible for the organization. The facilitator must not allow the philosopher to carry‑on without the idea being documented in the group memory.

Conversers: These participants are usually more social and tend to seek out other participants who share the same characteristics. Most of the ideas they express are not related directly to the topic, although it may appear that way as they begin their discussion. They are similar to the wanderer, who also like tangents and digressions. However, they are not as far off from the topics as the wanderers are. The facilitator needs to listen to the converser's idea, assess if it relates to the topic and limit that person's time to speak. The facilitator should determine their ideas are a part of the topic or relate to something else. The facilitator must monitor this person's contributions more closely than others in order to keep the other participants from becoming frustrated with what appears to be unnecessary and time wasting discussions.

Devil's Advocates: This person is always negative when expressing their ideas. They tend to state that things will never work, that things can't be done or that the technology is too complex. These pessimistic people can become a real downer to the other participants because they will be viewed as being against the rest of the team. The facilitator must request that this person keeps an open mind to the ideas that are expressed and only when there is a negative aspect that others haven't identified, should they point this aspect out. This type of person can become very harmful to the overall team's motivation. Too much negativism can turn the meeting process into a frustrating experience for all participants.

Followers: These people like to follow the lead of the others, especially others from their own department. They always align themselves with their manager or an influential person in the group. They are always in agreement with that person and are reluctant to express their personal view. This may be due to previous experiences when having been in meetings with their manager or this influential person. The facilitator needs to recognize that this person is continually repeating what others have said and should try to ask a specific question that will enable them to express what they really feel about the topic. The facilitator may need to stand between the follower and his/her manager to block his/her view.

I have only listed a few problems that I have experienced for this article and I would be interested in some the problems that you had endured - so please feel free to leave your comments or contact me directly.

Don't forget to leave your comments below.


Steve Blash is an experienced IT professional consultant providing business and technology leadership, mentoring and vision. His areas of experience include business process improvement, business analysis, business intelligence, data analytics, project and IT management.
Comments (13)Add Comment
...
written by Allen Pitts, June 14, 2011
Excellent article.
Two other problems I have run into when facilitating JADS or requirements elicitation sesions.
First, there is almost always an alpha personality who has an agenda and an axe to grind along with a huge ego has no problem with steering the meeting where he or she wants it to go. Then there are subject matter experts who may be clerks, accountants, or business process owners who are less vocal but who have carry with tme a wealth of system and process information. Tuning down the alpha types and bringing out the non vocal SMEs can be a challenge. When this gets too bad a time out to do a DISC assessment can defuse the situation . http://en.wikipedia.org/wiki/DISC_assessment

Second, and this may seem so mundane that it would seem to be easy to solve but has been and continues to be a challenge. If one is following the agenda, and keeping the session out of the weeds and toning down the alphas and elicitating the non-vocal SMEs
and has two or three other faciltation balls in the air the facilitator does not have time to take notes. Good notes means good meeting output. Bad meeting output is a huge and expensive waste of time and effort. One can appoint a scribe, especially if the appointment is made before the meeting and therfor prepared but beware the scribe must be skilled in the vocabulary and concepts of the knowledge domain or the notes could be worthless. This writer struggled with this aspect of session facilitation and stubbed his toes several times in the devlopment of a solution. Once the entire JAD (joint application development) session, all sixteen hours was recorded using a Sony mini-disc recorder.
It then took two weeks at three to four hours a night to transcribe the the sixteen hours into seventy pages. One does not ususally have two weeks to produce the meeting output. The solution which is used to day is to appoint an SME scribe who uses a text edititor like Word on a laptop to project the notes as they are being created. This works great because the stakeholders can see what the ouptput will be in real time and can say
"No! Thats not what I meant!" if that is the case. The meeting participants have a feeling of being contributors ato the meeting results and therfore have a feeling of buy-in.
These are two of the biggest problems. There are many more such as scheduling and action items.


...
written by Farrukh Shaikh, June 15, 2011
Very Good Article, this article can help both fresh and experience Business Analysts to take the guidance in their career.
...
written by Mahesh, June 16, 2011
Hi All,

This is very helpful. Please try to post some more problems which you might have faced in your career.

Thanks

Mahesh
...
written by Snehil, June 28, 2011
Hi Pitts,

You must go for a stakeholder analysis and power interest diagram before any meeting. This wya you can only invite the required people.

...
written by Manji Sekhon, July 05, 2011
When facilitating, i always write this on my whiteboard. It sets the tone of the meeting correctly and people start speaking carefully.

I know that you believe you understand what you think I said,
but I'm not sure you realize that what you heard is not what I meant ...
...
written by Cecilie Hoffman, July 05, 2011
Great article - a "bookmark" for personal use and to give to fellow practitioners.
...
written by Deepthi Nayana , July 22, 2011
Good read for professionals unsure on how to deal with people of different mentalities.

It is a good idea to think and refine the required attendeeslist before setting up JAD/ Working sessions rather then bluntly inviting every and any one part of a project. This will ensure proactive use of time/resources without ignoring crucial SMEs whose inputs are most valuable.
...
written by Bhavna, July 22, 2011
It is a great article indeed...
...
written by Martin Brunk, July 23, 2011
In response to Allen Pitts: excellent comment! When it comes to capturing requirements even live "recorded" text can still be ambiguous and even worse you loose people's attention because it doesn't relate to their day-to-day live and doesn't visualize the problem or solution. People want to see and "touch" things. Ever tried interactive visualization; simulations like those you can build with iRise? Beauty is it can all happen while you are still in the JAD session and you can apply immediate feedback. The wow factor is huge!
...
written by Devon Johnston, July 26, 2011
Thanks for not just identifying them but giving us solutions. Good job.
...
written by Charu, July 26, 2011
This is a great article and lovely realistic comments!

We also have to acknowledge that, time and again, Business Analysts come across SMEs (or other very knowledgeable people) who either do not attend the JAD session (after repeated invites) or who attend but do not disclose much of the information.

When information is withheld by a SME due to issues that the SME may have on the imprtance of their role in the project or in the organisation itself, it may be easy to identify this ........and but very difficult to correct the situation.

Sometimes, the situation can be tackled by approaching the SME on a personal basis if the relationship between the Business Analyst and the SME is good, even though the SME would like to continue to behave that way in a group workshop (for whatever reasons). Hence this situation can somehow be resolved even though there is time wasted in identifying it and taking the different approach.

But when the situation cannot be tackled even this way, identifiying the situation and escalation of this needs a lot of tactics ......as the escalation may make the situation worse. Another SME may be identified for the project which may make the situation worse with the first SME and this can be an obstacle that may remain throughout the lifespan of the project.

The above situation is definitely a pain .........hopefully does not arise at all ......but when it does, lot of effort is required. It can only be solved on a case by case basis without any generalistic solution.

Ideas are welcome on this.........and may be by sharing their experiences, useful suggestions may come out.
...
written by Stepan P. N., July 27, 2011
Interview of a group of people (all stakeholders) had not been discovered by the Agile method. Conversely, it is a technique used by qualified analysts regardless which project management method is used. It is also one of the strong method described by the BABOK that has nothing common with the Agile phenomenon.
Therewithal, types of people and their approach to the discussion is described clearly. Let me just mention that for many people their attitude to the meeting topic is not driven by their nature but buy their interest about the topic and impacts of prepared changes to their own work / competency / environment. A consultant should work with that but mostly has no power influence the consequences which are managed by managers.
...
written by Neosure Dolma, July 31, 2011
Does Lotus Notes Meeting Agenda help? A Questionnaire type form could be linked with the Outlook or Lotus Notes where 3 or 4 important questions are asked beforehand, as an agenda to the meeting, when the meeting goes off-track the facilitator can highlight that current discussion still does not answer the question posed in the agenda. Finally, before concluding - a summary of to-do list could be repeated so that everyone in the meeting could agree that the Facilitator has captured the essence of that particular facilitation session. Please comment on my opinions.

This is an excellent article. Please post more like these.

Write comment
We love to see comments! However, please do not market or sell any products. Your comment will be removed immediately!
smaller | bigger

busy