Skip to main content

Facilitating Appreciative Inquiry - Mapping user feedback to business goal

A part of my responsibility as a Business Principal also involves facilitating conversations on end user feedback and how it maps to business goals.

There are several tools to map end user feedback to business goals. However, the intent is to understand how users perceive a business goal. 

We designed a more engaging exercise that can lead to more detailed inquiry on how the business goal impacts the end users. This post is a quick experience report on facilitating an exercise Appreciative Inquiry that helped us in this intent.






Some Context

Our operations team has been rolling out several initiatives to help with building capability in an office. Of several initiatives, one of the most critical is that of goal setting and individual self reviews.

The initiatives around capability are critical since we are a consulting company that prides on working on cutting edge techniques that help our clients with their business challenges and business journey in the future.

After 2 years of having launched a new initiative, it was time to collect feedback in a more determined manner that will help us gauge its effectiveness and work on the next set of bets and initiatives.

Choosing the right facilitation technique

The key challenge was understanding what outcomes we wanted. After an initial conversation with the business stakeholders - in this case the operations team , we decided that the conversation and inquiry was important among the users.

While there are several traditional feedback techniques or retrospective techniques, none of them look at the journey or engage the users beyond the transactional nature of these initiatives.

With the outcome defined, we decided on the Appreciative Inquiry technique for the following reasons:
  • Appreciative Inquiry works on the current strengths of the process
  • It helps the users build on the strengths to dream about a future state
  • It also generates more questions that will help with Inquiry

The workshop 

Planning for the workshop

The workshop was planned in 2 phases to accommodate more engaging conversations.

The workshop started with context setting around what we expect the users to contribute throughout the exercise. We emphasised on the Appreciative Inquiry process.

We started with a quick check-in. 

For this purpose, we designed a light weight checkin process. Each team member was asked to come up with an adjective for how they relate to the capability initiative.

We split the participants into 3 teams

Workshop - Phase 1 - Discover

We nudged the participants to come up with one strength that they can personally relate to.

As a part of their group, we asked them to discuss these strengths and ask them to come up with one strength that the team agrees on.

This helped in the inquiry on how they can come up with a common strength of the initiative.

Workshop - Phase 2 - Dream

We then asked the participants to work with the common strength the group came up with. This time, we asked them to come up with more strengths that they would like to see in an ideal initiative.

As a part of the journey, we also realised that the participants started coming up with a lot of questions that they have had . The inquiry process helped them discuss some of these as they were coming up with a new dream initiative.

They also came up with the set of strengths and ideas that they can use for the ideal initiative.

Workshop - Phase 3 - Design

This time , before we started the next phase of the workshop, we switches the groups to work on a set of questions and ideas that another group came up with.

This forced the groups to interpret the ideas and questions that the other group came up with. There was also cross group communication that forced more inquiry as the design needs to be based on ideas that the other groups came up with.

Outcomes

The groups were pretty engaged with the list of questions, ideas and new initiative approach. 

The ask from the groups was to carry out the inquiry outside the workshop as well so that this can continue.

A common critique of the workshop was that there was not enough time to complete some of these tasks. 

The next step is to have a different forum to address some of these questions and look at some of these ideas as we go forward with this initiative.

Conclusions on the approach

This approach was very inclusive and engaging and helped us achieve the outcomes we designed it for.






Comments

Popular posts from this blog

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It is a very valua

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here:  https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/