Share this
Transform your team's behaviour with a working agreement or culture canvas
by Kirsten Eriksen on 01 May 2020
This article is republished from my original Transform your team's behaviour with a working agreement or culture post in LinkedIn.
Side note: I wrote this article just before New Zealand entered lockdown. In the weeks that have followed, I've been keeping in touch with the person whose situation I describe, and working remotely has, if anything, intensified the issues they are experiencing. I was going to wait to publish this till we were back in our offices again, but from what I've observed now more than ever, we need the structure the activities below describe.
The other day I was having a conversation with someone about issues they were struggling with in their team. As the conversation progressed, it sounded to me like they were dealing with issues of culture. It wasn't so much what they were doing but how they were doing it, how they interacted with each other and whether it was aligned with their "purpose".
I've always agreed with the adage: "culture is the behaviours you reward and punish". If people experience positive outcomes for a behaviour, it encourages it to continue. When people experience negative outcomes, they tend to avoid that behaviour in the future (as a side note, in my opinion, if you behave in a particular way and don't get any negative outcome, that counts as a positive outcome encouraging more of that behaviour, especially when the behaviour in question is sub optimal).
Issues they described
- People within the team were doing things because they were the things that got seen, and while not rewarded specifically, this behaviour didn't have any negative outcomes. As a result, the work that needed to get done but wasn't "seen" was falling to other team members.
- People were saying that they were able to do things that they couldn't, whether due to capability or because they were overloaded. This resulted in mistakes and work simply not getting done until others stepped in to clear up the situation.
- In sessions where new work was discussed, there was a pattern where certain team members would consistently jump in and claim work without allowing others to have opportunity.
- People within the team were undertaking work that didn't support their "why", their purpose for being, which was creating an expectation outside of the team about what work was done and whether it would be continued in the future.
- People within the team were encroaching on other team members explicit areas of responsibility, creating frustration, rework and expectations outside the team, that the team couldn't continue to support.
Canvases can help
The team has a recent new manager and a few new team members. This, coupled with the issues they were experiencing, prompted me to suggest that the team have open conversations and prepare an explicit agreement about how they will work together.
One way in which to do this is to work through a working agreement or culture canvas. Generally, these start with explicitly defining the "why" or purpose of the team and then focus on various factors such as values, roles and responsibilities, how the team will try new things, and what behaviours will be encouraged and what behaviours will be called out and discouraged.
There are many of these canvases online. One of my favourites for "normal" (non-agile) teams is http://theteamcanvas.com/, whereas for agile teams the Scruminc.com one works really well.
Some advice when using canvases
- Have an independent facilitator to run the session. This is really important, as personal biases and agendas will interfere with the team's ability to reach agreement. You’re looking for real agreement here, not lip service.
- When selecting a facilitator, choose someone who is familiar with the canvas method and is competent at running sessions like this. As a suggestion, an agile coach, scrum master or consultant should be familiar with both canvases and the concepts involved in facilitating this kind of session.
- The whole team should be involved as equal peers. Roles and hierarchy should be laid aside where possible, with everyone having equal voice in the discussion (another reason why an external facilitator is important, you can't facilitate and participate!).
- Have a think about the "problems" being experienced within the team. If the canvas you have selected doesn't address any of these issues, change it. There's no rulebook for what you need to include, and the elements of any canvas are suggestions rather than set in stone.
- Set aside adequate time for this activity. It may need multiple sessions. I've had teams get through this in a couple of hours and others that took much more time. This is something that will form the basis for your team culture, it is important and worth the time investment. Every team is different!
- Consider the impact the culture of your organisation has on your team. Its all very well for a team to agree that they’ll be honest and transparent with each other, yet if the wider organisation doesn't support the behaviour you're trying to encourage, it is less likely to be successful. Culture bubbles do occur; however, they usually only survive if not in direct contradiction with the organisational culture.
- Live the working agreement or canvas every day, nothing will change if the canvas is then simply put on the shelf. Leaders and team members must model the expected behaviour every time, and the full group will ultimately begin to follow the new norms.
- Don’t expect this activity to be a silver bullet. People take time to change and they must want to change (see my post on change). If you find things aren't changing, there may be multiple factors involved. Maybe you haven’t got the right things identified, or perhaps you don't have real agreement, or there may be something external impacting the team.
When you undertake an activity like this, and it works, the results are amazing and awesome. I've seen teams completely transform from the inside, where the team members are happier, more productive and more successful. Everybody wins in this situation.
If you'd like to have a chat about canvases, or anything else I've raised in the article, please do get in touch.
Kirsten Eriksen is a Senior Consultant specialising in business analysis and Agile coaching, based in Equinox IT’s Wellington, New Zealand office.
Share this
- Agile Development (153)
- Software Development (126)
- Agile (76)
- Scrum (66)
- Application Lifecycle Management (50)
- Capability Development (47)
- Business Analysis (46)
- DevOps (43)
- IT Professional (42)
- Equinox IT News (41)
- Agile Transformation (38)
- IT Consulting (38)
- Knowledge Sharing (36)
- Lean Software Development (35)
- Requirements (35)
- Strategic Planning (35)
- Solution Architecture (34)
- Digital Disruption (32)
- IT Project (31)
- International Leaders (31)
- Digital Transformation (26)
- Project Management (26)
- Cloud (25)
- Azure DevOps (23)
- Coaching (23)
- IT Governance (23)
- System Performance (23)
- Change Management (20)
- Innovation (20)
- MIT Sloan CISR (15)
- Client Briefing Events (13)
- Architecture (12)
- Working from Home (12)
- IT Services (10)
- Data Visualisation (9)
- Kanban (9)
- People (9)
- Business Architecture (8)
- Communities of Practice (8)
- Continuous Integration (7)
- Business Case (4)
- Enterprise Analysis (4)
- Angular UIs (3)
- Business Rules (3)
- GitHub (3)
- Java Development (3)
- Lean Startup (3)
- Satir Change Model (3)
- API (2)
- Automation (2)
- Scaling (2)
- Security (2)
- Toggles (2)
- .Net Core (1)
- AI (1)
- Diversity (1)
- Testing (1)
- ✨ (1)
- August 2024 (1)
- February 2024 (3)
- January 2024 (1)
- September 2023 (2)
- July 2023 (3)
- August 2022 (4)
- August 2021 (1)
- July 2021 (1)
- June 2021 (1)
- May 2021 (1)
- March 2021 (1)
- February 2021 (2)
- November 2020 (2)
- September 2020 (1)
- July 2020 (1)
- June 2020 (3)
- May 2020 (3)
- April 2020 (2)
- March 2020 (8)
- February 2020 (1)
- November 2019 (1)
- August 2019 (1)
- July 2019 (2)
- June 2019 (2)
- April 2019 (3)
- March 2019 (2)
- February 2019 (1)
- December 2018 (3)
- November 2018 (3)
- October 2018 (3)
- September 2018 (1)
- August 2018 (4)
- July 2018 (5)
- June 2018 (1)
- May 2018 (1)
- April 2018 (5)
- March 2018 (3)
- February 2018 (2)
- January 2018 (2)
- December 2017 (2)
- November 2017 (3)
- October 2017 (4)
- September 2017 (5)
- August 2017 (3)
- July 2017 (3)
- June 2017 (1)
- May 2017 (1)
- March 2017 (1)
- February 2017 (3)
- January 2017 (1)
- November 2016 (1)
- October 2016 (6)
- September 2016 (1)
- August 2016 (5)
- July 2016 (3)
- June 2016 (4)
- May 2016 (7)
- April 2016 (13)
- March 2016 (8)
- February 2016 (8)
- January 2016 (7)
- December 2015 (9)
- November 2015 (12)
- October 2015 (4)
- September 2015 (2)
- August 2015 (3)
- July 2015 (8)
- June 2015 (7)
- April 2015 (2)
- March 2015 (3)
- February 2015 (2)
- December 2014 (4)
- September 2014 (2)
- July 2014 (1)
- June 2014 (2)
- May 2014 (9)
- April 2014 (1)
- March 2014 (2)
- February 2014 (2)
- December 2013 (1)
- November 2013 (2)
- October 2013 (3)
- September 2013 (2)
- August 2013 (6)
- July 2013 (2)
- June 2013 (1)
- May 2013 (4)
- April 2013 (5)
- March 2013 (2)
- February 2013 (2)
- January 2013 (2)
- December 2012 (1)
- November 2012 (1)
- October 2012 (2)
- September 2012 (3)
- August 2012 (3)
- July 2012 (3)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- December 2011 (4)
- November 2011 (2)
- October 2011 (2)
- September 2011 (4)
- August 2011 (2)
- July 2011 (3)
- June 2011 (4)
- May 2011 (2)
- April 2011 (2)
- March 2011 (3)
- February 2011 (1)
- January 2011 (4)
- December 2010 (2)
- November 2010 (3)
- October 2010 (1)
- September 2010 (1)
- May 2010 (1)
- February 2010 (1)
- July 2009 (1)
- April 2009 (1)
- October 2008 (1)