Sunday, June 3, 2018

Six Tips to make Story Mapping more effective


Story Mapping is a practice that helps you experience a customer or user journey. You would first capture the end-to-end customer experience by asking what would a user do? This includes establish a backbone, steps, and options.  
The story mapping process promotes the team to think through elements of what the customer finds as valuable from a process perspective. It moves away thinking of functionality first and instead advocates thinking about the customer experience first.  Then you would use an incremental approach of building, inspecting, and adapting for the next increment. What might be some tips to help you more effective work through a story mapping session? 
Tip #1 – Craft your Persona (aka, customer)
Draft the persona that will be taking the customer or user journey.  Place the persona at the top or head of the story map. This provides empathy for the user and inspiration for those that are attempting to craft the journey through the eyes of the user (via the story mapping practice).  Learn more about personas at Personas - Getting to really know your Customer 
Tip #2 – Everyone stands up around the story map
As simple as it sounds, have everyone working on the story map session stand-up and around the story map as they are creating it. This keeps everyone engaged on crafting the story map.  
Tip #3 – Everyone writes options
When it comes time to imagine options for each step along the customer journey, provide everyone with a post-it pack and marker.  Ensure everyone knows that they should put up the option ideas as they think of them.  This gets lots of options up quickly. This also reduces any single threaded thinking where only one person is doing the writing.  
Tip #4 – Promote lots of chatter during Affinity of options
After a number of options are written by a number of people, it is time to determine if there are affinities.  This is a good opportunity to promote conversation for understanding the customer journey together as each option is discussed.
Tip #5 – Ask owners of options if they are similar
If two options are similar, ask the owner of each to determine if they form an affinity.  Often times when there are similar options on post-its, those that didn’t write them speak up to discuss if they are indeed related. Instead, those that wrote them should determine the affinity (or not) as they would know better.  
Tip #6 – Use verb/noun
Use short verb/noun phrases to capture the backbones, steps, and activities (e.g. capture my address, view my order status, receive invoice). This helps with understanding the expected action for each step of the user journey. 

You can learn details of executing a story mapping session at Story Telling with Story Mapping.

Sunday, April 22, 2018

Importance of Treating Psychological Safety as a Journey

Amy Edmondson defines psychology safety as “a belief that one will not be punished for speaking up with ideas, questions, concerns, or mistakes.” The benefit is that this can lead to high performing teams and innovative ideas.  To align with a shared belief at a team or organization level, it explicitly requires a change in the way a culture works and this will take time. 

More specifically, a culture shift that must occur in the following areas: openness to asking questions instead of staying quiet for fear of looking ignorant; admitting mistakes instead of hiding them for fear of looking incompetent; offering ideas instead of holding on to them for fear of looking intrusive; and challenging norms instead of sitting back for fear of sounding negative. 

As it can take time to shift to a culture of psychological safety, I have seen great benefits in treating this as a journey.  I encourage this as my experience has shown that attaining psychological safety requires several components that work together.  With that in mind, I’ve created, tested, and applied what I dub the Psychological Safety Roadmap.  This roadmap is meant to be adaptive as your starting point and the dynamic as each organization is different.  The journey and practices therein are meant to be spaced-out and applied over months as building psychological safety takes time.  As you proceed with your journey, you may also add or adapt the components of the roadmap.  
The components or metaphorically the cities along the journey to psychological safety include: Get to know one anotherEstablish Safety NormsShow Vulnerability; and Practice Safety via Feedback.  Within each city, there are a lot games and practices you can visit or try, each supporting the city you are in.  It is important to understand that the roadmap is not meant to be sequential and instead, several cities may be visited concurrently.  The only exception is you should visit the city of Getting to know one another before visiting the city of Showing Vulnerability.  My experience has shown that it is easier to show vulnerability after you get to know someone. 

Now let’s visit each city on the roadmap.  The city of Get to know one another includes practices and games where team members will, well, get to know one another.  The intent is if we know about each other, conversations tend to be safer and easier. This includes practices and games such as “Who am I?”, “If I were an animal, what would I be?”, “How do we educate ourselves”, and “Checking-in”.  

The second city on the roadmap is Establish Safety Norms.  The intent here is to make meetings a safe space to encourage speaking up with ideas, questions, and concerns.  This includes practices and games such as “All voices will be heard”, “Learn to repeat”, and encourage such attributes as being curious and non-judgmental. 

The next city is Show Vulnerability with the intent that being open and showing vulnerability helps build trust and creates a safe space within a team.  This includes practices and games such as “Circle of Vulnerability”, “I Feel Safer When”, and “Three Before Me”. 

The fourth city on the roadmap is Practice Safety via Feedback. The intent is giving feedback with good intent helps build trust and create strong relationships.  This includes practices and games such as "Appreciative feedback", "Differentiating feedback", and "Reflection for improvement".  

As you approach the Psychological Safety Roadmap, remind yourself that it is not meant to be a sequential journey nor are the games and practices a definitive list of what can be applied along the journey.  You (or your team) are meant to visit several cities (and practices and games therein) sometimes concurrently and it will take many months to achieve psychological safety.  Enjoy the journey and remember that your goal is to create a safe environment for people to speak up with ideas, questions, concerns, or mistakes.  This can lead to high performing teams and innovative ideas. 

To learn the basics of psychological safety, consider reading: Psychological Safety leads to High-Performing Teams.

Sunday, March 18, 2018

Can Agile Games help you build Psychological Safety?

What are the advantages of attending an Agile Games conference? Let's look at Agile Games 2018 (in Boston) as an example.  This particular Agile Games focused on psychological safety.  The primary advantage of bringing the latest psychological safety and agile related concepts and practice back to your company, helps you lead to higher performing teams and greater company success.

First, what is Psychological Safety?

Google's Project Aristotle showed that team performance is indicated by one primary attribute: Psychological Safety. This is the degree to which team members can speak up without fear of retribution. Amy Edmondson has shown that psychological safety and accountability create the most productive teams. 

Second, what are the advantages of Agile Games?  

This 3-day conference (
in the greater Boston area - Burlington, MA on April 9-11) explored ways to use serious interactive games to significantly improve team performance by increasing psychological safety and other key attributes. It focused on using games, collaborative activities and interactive exercises to support the values, principles and practices of lean and agile. What are some of the topics being covered?

Third, who are some of the Speakers and their Topics?   

When approaching Psychological Safety games, how do you balance uncomfortable situations, harmless triggering of the impostor syndrome while getting to the real essence of safety that can lead to high performance?  How do we steer between frivolity and personal risk? Tim Ottinger explored guidelines for safely sharing games that teach. 

In achieving psychological safety, how can you use games to “Stop the fear pandemic” where you encounter endless meetings, employees’ disengagement, blame and a lack of trust?
 Dana Pylayeva introduced agile games designed to increase empathy, build connections and practice risk taking in a "safe to fail" setting. 

Experience interactive games for building Psychological Safety. Craft team norms for a psychologically safe environment. Practice constructive non-judgmental feedback to strengthen your relationships. Mario Moreira 
will work you through this and you will leave with a Psychological Safety Roadmap that can be adapted to your company. 

-->

Sunday, March 4, 2018

Woven Together - A Practice to Build Authentic Connection and Psychological Safety


By Jody Gold with Mario Moreira

The game is changing.
 Hierarchies are flattening out. Companies are re-organizing to profit from the agility and collective intelligence of smart, flexible teams.  The concept of “leadership” itself is changing—from individual leadership that devises strategy and drives troops into battle, to relational leadership that catalyzes the creativity and commitment of all team members.

The good news is that there are constructive frameworks from the isolation, frustration, and disengagement that reduce collective learning and performance, to fully engaged, highly coordinated, innovative and agile teams that increase learning and performance. One such framework is the Matrix Leadership Networks that helps you successfully navigate this transformation.

Woven Together is an early practice and part of Matrix Leadership that helps strengthen the fabric of your team. Icebreakers and team-building exercises are often fun but their value fades.  Woven Together builds authentic connection, curiosity, and care among team members that last. People who’ve worked on teams together for years often rarely know about each other as people.  They may not know that John has a baby girl, and fills up with love when he talks about her getting her first tooth, or that Jennifer gets lit up by the smells, sounds, and tastes of street food when she is in another country. 
Woven Together raises energy in the room and can be used as a stand-alone activity.  It’s a tangible introduction to core Matrix concepts like seeing relationships as first class entities that Mario Moreira describes in his article (part 1 of this series) and the entire network of relationships within a team as the relational infrastructure that Jody Gold describes in part 2 of the series.  You can practice Woven Together with your team, right now.

Set-up

The ingredients include your team, a ball of yarn, 20-30 minutes depending on the size of your team, and enough space to stand in a comfortable circle.

Determine if each person in the circle will say just their name or their name, role, years in role, years at company, years doing agile.  This will depend on how well the facilitator and team members know each other.

You are person A.  You will explain the activity and model the two most important components: 1) forming a connection with one person—person B—and speaking to that person only, instead of scanning from person to person as we’ve all learned to do, and 2) telling person Bsomething that lights you up’ in a way that is genuine and concise.

Steps 
  1. Person A wraps the end of yarn around a forefinger and loosens enough yard equal to the distance between person A and B.  Person A throws the ball of yarn to BA speaks directly and only to B.
  2. Person A says their Name.  Person B says their Name. 
  3. Person A shares, “Something that lights me up is…”
  4. B responds in a few words to complete the connection, “Cool. Thanks for telling me that. I want to know more about that. Etc.”
  5. Person B chooses person C.  Repeat steps 1-5 (figure 1)
  6. C chooses D and repeats steps 1-5.  Iterate until all people steps 1-5 and the ball of yarn is back at A  (figure 2).
  7. After the yarn is back at person A, ask people to share what the experience was like and how things feel different now than before the activity.  

Final Thoughts

If Woven Together is used to introduce other Matrix practices, you may invite observations about the structure itself and its capacities.  Participants will name many characteristics of distributed leadership before they’ve learned about them formally.

Woven Together almost runs itself.  It’s amazing how much authentic connection, trust, and psychological safety arise from sharing ‘What Lights You Up.’  As the one leading the activity, be prepared for someone to say that speaking to only one person feels rude, exclusive, or uncomfortable.  Of course it may—scanning from person to person is a deep cultural norm.  Others may describe a sense of ease staying in connection with one person, like talking one-on-one with a friend.

Woven Together is also a good way for everyone to hear everyone else’s name a couple of times, and to quickly know who’s in what role and for how long, and/or how long they’ve been on the team or in the company.  It’s a great activity for a new team, a team whose membership has changed, or a new cross-functional project.

You have everything you need right now to turn thirty minutes into gold.  If you would like more information, consider contacting Jody Gold to discuss Woven Together or to learn more how the Matrix framework equips teams to accurately sense and effectively respond to complex and chaotic challenges leading to higher performing teams.  

---------------
Read Part 1 & 2 of the Matrix Leadership series:
(Part 1) Importance of treating Relationships as First Class Entities 
(Part 2) Strengthening the Relational Infrastructure to Build High-Performing Teams