Author: jcdejong

Posted on

7 Differences between complex and complicated

Sonja Blignaut’s 7 Differences between complex and complicated sounds like a listicle, but is in fact an excellent primer on which is which, and why the difference matters. According to Blignaut, “as long as decision-makers believe they are dealing with complicated systems, they will assume they are able to control outcomes[…]” leading to decision making with a poor fit and a high cost, both monetary and in terms of human interaction.

With a nod to Dave Snowden’s Cynefin and Robert Poli’s article about the same topic, Blignaut looks at seven aspects of differences between complex and complicated systems and discusses their impact. Her discussion of linearity brings this almost off-the-cuff assertion: “small safe-to-fail experiments are more useful than large projects designed to be fail-safe.” 🔥 Great article to bookmark and to dive into with the right client.

Posted on

Retrospective: Do The Team Radar

Since it’s such a tried-and-true format, there are plenty of articles on the Team Radar, with advice and emphasis added based on the author’s position and involvement with teams. Christiaan Verwijs of The Liberators approaches the subject from a facilitation perspective with a Scrum Master-y stance in 2017’s Retrospective: Do the Team Radar, while Petra Wille’s 2019 article The Secret Weapon of Retrospectives – the Team Radar over on Mind the Product is clearly written from a product managerial perspective. Use the best of both for your team’s next (radar) retrospective.

Posted on

IDOARRT Meeting Design

IDOARRT is a simple tool to support you to lead an effective meeting or group process by setting out clear purpose, structure and goals at the very beginning. It aims to enable all participants to understand every aspect of the meeting or process, which creates the security of a common ground to start from. The acronym stands for Intention, Desired Outcome, Agenda, Rules, Roles and Responsibilities and Time.

Step 1:

Before the meeting/process, prepare a Flipchart / Slide outlining all the points of IDOARRT. See below:

Intention – What is the intention, or purpose, of the meeting? In other words, why have it?

Desired Outcome(s) – What specific outcomes should be achieved by the end of the meeting?

Agenda – What activities will the group go through, in what order, to move toward the desired outcome?

Roles – What roles or responsibilities need to be in place for the meeting to run smoothly? Who is facilitating, and who is participating? Who is documenting, and who is keeping track of the time? What do you expect of the participants?

Rules – What guidelines will be in place during the meeting? These could relate to agreed group norms. They could also relate to use of laptops/mobiles, or practical rules related to a space. Let the participants add rules to ensure that they have ownership of them.

Time – What is the expected time for the meeting, including breaks,and at what time will the meeting end?

Step 2:

At the beginning of the meeting, introduce the IDOARRT, going through point by point. Invite participants to ask questions or make suggestions for changes. Once the group is happy with the plan, go ahead with the rest of the meeting.

Posted on

Liberating Structures and (distributed) Scrum Events

For an upcoming meetup I’m preparing a session on how to use LS for Scrum Events and especially events where the participants are distributed and joining the event remotely.

Here’s a brief overview of some LS that can be used for the different Scrum events. I’ve marked all structures with an * that I’ve used myself in a distributed setting.

Refinement / Planning

Daily Scrum

Sprint Review

Sprint Retrospective

On the liberating Structures website you can find a design checklist for virtual meetings. Since the link is currently no longer working, you can find the document here:

DESIGN of LIBERATEDVIRTUALMEETINGS v2Download