<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Simon Lawrence on Medium]]></title>
        <description><![CDATA[Stories by Simon Lawrence on Medium]]></description>
        <link>https://medium.com/@splawrence?source=rss-c5112fa2c587------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*O3debvnnzAjcyea0xov62A.jpeg</url>
            <title>Stories by Simon Lawrence on Medium</title>
            <link>https://medium.com/@splawrence?source=rss-c5112fa2c587------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:19:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@splawrence/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Threatening Behaviour]]></title>
            <link>https://medium.com/cambridge-agile-exchange/threatening-behaviour-5cf665ae2a0d?source=rss-c5112fa2c587------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cf665ae2a0d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Simon Lawrence]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 18:17:00 GMT</pubDate>
            <atom:updated>2018-06-07T18:17:00.887Z</atom:updated>
            <content:encoded><![CDATA[<h4>Do our meetings impact our abstract thinking?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IF_LU4-4XdaZxawWtmtUXg.png" /></figure><p>Most of us have too many meetings. I don’t think I’ve worked anywhere where someone has said “You know what we need? More meetings”. So, maybe the best thing to do is consider why you have those meetings in the first place and stop having them if they don’t add value, or if the same output could be gained by a conversation with a few people, a Slack discussion or even an email (as long as you don’t expect anyone to read it). For those that remain, how can we increase the richness of the communication and the overall value of the output?</p><p>This is probably a good point to admit that I am not a psychologist. Or a neuroscientist. Or a rocket scientist. Most of the concepts I’ll be describing below are the result of the research and study of others, primarily David Rock in his book ‘<a href="https://your-brain-at-work.com/">Your Brain at Work’</a>. All of my sources are listed in the end notes.</p><h3>What are you thinking?</h3><p>To answer this, we must look at the brain’s key principle — to minimise threat and maximise reward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*5HXhAi9s6Ih64AYN9h_-Eg.png" /></figure><p>This is an ancient motivator for humans and critical to the propagation of the species and so, as you might expect, we are better at detecting <strong><em>threat </em></strong>than we are <strong><em>reward</em></strong>. <a href="https://academic.oup.com/scan/article/10/2/153/1652379">A 2014 study</a> published in <em>Social Cognitive and Affective Neuroscience </em>showed that areas of the brain triggered when encountering physical threat were also activated when encountering social/emotional threat. So, for example, if we feel our status in a social group is at risk, we may experience similar sensations to being physically threatened. To understand why this is an issue, we should look at what is working inside our head.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XV1CKU62s7fAHiabq3brog.png" /></figure><p>The above diagram shows the Pre Frontal Cortex (PFC), the area of the brain in charge of high-bandwidth, abstract functions such as planning and outcome determination, decision making and the moderation of social behaviour. Basically, this is the bit of you that your employer pays you for — if they could keep this and not have to put up with all of the chaos and unpredictability, I’m sure they would.</p><p>Labelled in red is the Amygdala, housed within the Limbic system and, in evolutionary terms, fairly ancient, <a href="https://en.wikipedia.org/wiki/Limbic_system#Evolution">part of the intermediate or ‘old mammalian’ brain</a>. This is the component which deals with emotional response (fear, anger) and threat management. Both the PFC and the Amygdala deal with high bandwidth functions and processing power is high, so if our brain feels threatened we get an <strong><em>increase </em></strong>in the threat-avoidance response and a <strong><em>decrease </em></strong>in the creative and cognitively complex functions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xDl9GcrcqGOLu1jQdqGwA.png" /></figure><p>So, what are the components we need to consider in order to provide an environment conducive to creative thought? David Rock developed the SCARF model, which describes the drivers for social interaction.</p><p><strong>Status: </strong>Our relative importance to others</p><p><strong>Certainty: </strong>Our ability to predict the future</p><p><strong>Autonomy: </strong>Our sense of personal control</p><p><strong>Relatedness: </strong>Our perception of safety</p><p><strong>Fairness : </strong>Our sense of justice.</p><p>How does this apply to the working environment? Have you ever received an meeting invite with the subject header of ‘Chat’ or ‘Discussion’? No further context or detail, no agenda? This could mean anything, it could be something serious or completely innocuous, but without additional detail our sense of certainty may be impacted and we may walk into the meeting already in a defensive frame of mind.</p><p>Have you been in a meeting where the discussion is being monopolised by one person or a few people? Have you struggled to get your views heard? Or have your views been dismissed? All of these could result in an impact our sense or status, relatedness, fairness and autonomy and generate a threat-avoidance response.</p><p>So, here’s a technique that may work for you if you want to maximise the creative thought in your meeting.</p><h3>Thinking in Rounds</h3><p>The Thinking in Rounds technique works really well where you have a single question, problem statement or improvement item to focus on. Be sure to send your meeting invitation with a clear subject and agenda so that all attendees know why they’re being invited and the context, if any preparatory work is required, make this clear. Gather the team and re-iterate the agenda at the start of the meeting. Go clockwise around the team and ask everyone to provide an idea or response, allow people to talk as long as they need to but consider providing guidelines of a few minutes each. Ensure that only 1 person is speaking at a time and all other attendees are practising <strong><em>active listening</em></strong>. There are 2 rules to active listening:</p><ol><li>Don’t talk</li><li>Don’t think about talking</li></ol><p>You can continue this for 2–3 rounds and you may find that the thinking becomes deeper and the responses more insightful in the later rounds as our cognitive functions start firing and we begin to draw together multiple threads of thoughts and ideas.</p><h3>Takeaways</h3><p>How we behave, the things we say and how we say them affect the thinking of ourselves and of others. Consider the SCARF model and think of the last meeting you attended — did it flow with ideas? Was it ‘democratic’? Did all of the attendees speak or have the chance to speak?</p><p>Quality outcomes require quality thinking and it is within our power to create environments that allow people to perform at their best. As we take time to determine <strong><em>what</em></strong> outcomes we need, let’s also give some thought to <strong><em>how</em></strong> we might achieve them.</p><blockquote><strong>Sources</strong></blockquote><blockquote>‘Empathy for Social Exclusion Involves the Sensory-Discriminative Component of Pain: A Within-Subject fMRI Study’ by SISSA, published in Social Cognitive and Affective Neuroscience, April 2014</blockquote><blockquote>Your Brain at Work: Strategies for Overcoming Distraction, Regaining Focus, and Working Smarter All Day Long by David Rock, by HarperBusiness, October 2009</blockquote><blockquote>Neuroscience Online, <a href="https://nba.uth.tmc.edu/neuroscience/index.htm">https://nba.uth.tmc.edu/neuroscience/index.htm</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cf665ae2a0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cambridge-agile-exchange/threatening-behaviour-5cf665ae2a0d">Threatening Behaviour</a> was originally published in <a href="https://medium.com/cambridge-agile-exchange">Cambridge Agile Exchange</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting clean with feedback]]></title>
            <link>https://medium.com/cambridge-agile-exchange/getting-clean-with-feedback-877d5ad2aab5?source=rss-c5112fa2c587------2</link>
            <guid isPermaLink="false">https://medium.com/p/877d5ad2aab5</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Simon Lawrence]]></dc:creator>
            <pubDate>Tue, 22 May 2018 16:11:12 GMT</pubDate>
            <atom:updated>2018-05-22T16:11:12.694Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Feedback is a gift” — some people give terrible gifts…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3iCx9TEwdfuZeKDufGDdg.jpeg" /><figcaption>Photo by Gaelle Marcel on Unsplash</figcaption></figure><blockquote>The gifts we bring even in good faith maybe warp in our hands to implements, to manoeuvres</blockquote><blockquote>Margaret Atwood, Vision and Forms</blockquote><p>The word ‘gift’ originates from the 13th century and is generally held to mean ‘that which is given’, in some ancient Germanic languages the word can also mean ‘<a href="http://gift. (n.d.). Online Etymology Dictionary. Retrieved May 8, 2018 from Dictionary.com website http://www.dictionary.com/browse/gift">poison’</a>. Sometimes, both translations are valid.</p><p>In the Agile world, we rely greatly on interactions and collaboration so that our valuable solutions can emerge. We’re perpetually inspecting — our product as it evolves, our internal processes and practices and our interactions to ensure that they’re valuable and useful. We encourage our teams to highlight interactions and situations that are not helpful but how often do we give people the tools or resources to support this?</p><p>I came across the concept of <strong>Clean Feedback </strong>as a close cousin to Clean Language following a seminar run by Judy Rees and Olaf Lewitz last year and was immediately taken by the lightweight approach and obvious value it presented. The Clean Feedback framework suggests breaking feedback down into 3 components:</p><p>— <strong><em>Evidence</em></strong>: from an objective perspective, what happened? This should be verifiable by a 3rd party and not coloured with personal insight</p><p>— <strong><em>Perception</em></strong>: what is your own subjective interpretation of what you saw/heard?</p><p>— <strong><em>Impact</em></strong>: what was the effect on you as an individual or the situation?</p><p>The key thing for stages 2 and 3 above is that I talk only on behalf of myself — I can’t perceive on behalf of others.</p><p>Take a look at these 2 examples:</p><p>“Simon, in our team retrospective today, you were completely disengaged and disconnected from the discussion. You were not contributing in any way to what we were trying to achieve and it’s not on!”</p><p>So — straight to <strong><em>perception</em>. </strong>This is probably pretty common in humans, right? How about this?</p><p>“Simon, in the team retro today, I saw that you were sat with your head in your hands and you spoke a few times. My perception of this is that you were disconnected from the discussion and this could contribute negatively to the energetic atmosphere we’re trying to generate in these meetings. Also, it frustrates me personally as the team&#39;s Scrum Master and makes my life more difficult”</p><p>So here we have our get-out clause against mis-representation — we’ve stated the evidence and made it clear that the rest is personal perception and inference. Are there any other reasons that Simon has his head in his hands? Could he be thinking? Might he have a headache? In example 2 we do not assume intent on behalf of the other person, but describe our own perception with the view to opening up a discussion. Notice also how in the impact section, I can <strong><em>describe</em></strong> frustration without <strong><em>being </em></strong>frustrated during the conversation.</p><p>When using this approach, I’ve typically booked a session somewhere quiet and private and run through my pre-prepared Clean Feedback responses. I’ve suggested that the person receiving the feedback ask questions in order to gain understanding (not to defend/repel), think about it overnight, then we get back together to discuss and open up the conversation. For me, the Clean Feedback model is not a solution in itself, but a mechanism to frame a conversation — similar to many templates and frameworks used within Agile teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfqQzq2ote3mLK19FcdCKQ.jpeg" /><figcaption>Photo by Riccardo Annandale on Unsplash</figcaption></figure><p>It’s useful to include some self-reflection on the part of the <strong><em>reviewer </em></strong>as part of the conversation: Why did I perceive the event in this way? What am I hoping to gain in providing this feedback? Am I providing ‘weaponised’ feedback (i.e. feeding back in order to sell or set my own agenda)? Asking these questions out loud with your reviewee can provide transparency and build trust. I find it useful to keep this quote from <a href="http://www.coachingagileteams.com/publications/books/">Coaching Agile Teams</a> by Lyssa Adkins in mind.</p><blockquote>As you prepare to coach someone, check yourself. If you view the coachee as a problem to solve, you are in a barren place for coaching. All the coaching skills and agile experience in the world will fall flat if you coach from this perspective.</blockquote><p>I’ve found the Clean Feedback model particularly valuable in conversations where the stakes are high — where I’ve needed to provide personal feedback on behaviour and interactions that I see as negative or destructive; where a poorly thought-out word or comment on my behalf could have a significant impact on an individual and/or my relationship with the individual.</p><p>By governing our conversations in this way, we are not hiding behind platitudes, niceties or a fear of causing offence, we are opening up a real conversation, a conversation that is intense and based on honesty and transparency. And hopefully one that opens the path toward empathy for both parties.</p><p><em>This post is based on an interview given to Judy Rees as part of a YouTube series on the applications of Clean Language.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=877d5ad2aab5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cambridge-agile-exchange/getting-clean-with-feedback-877d5ad2aab5">Getting clean with feedback</a> was originally published in <a href="https://medium.com/cambridge-agile-exchange">Cambridge Agile Exchange</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning is fun: experiments with Hypothesis-Driven Development]]></title>
            <link>https://medium.com/cambridge-agile-exchange/learning-is-fun-experiments-with-hypothesis-driven-development-e3b7239516a5?source=rss-c5112fa2c587------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3b7239516a5</guid>
            <category><![CDATA[hypothesis]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Simon Lawrence]]></dc:creator>
            <pubDate>Fri, 04 May 2018 13:34:28 GMT</pubDate>
            <atom:updated>2019-01-18T15:09:31.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xEbQKjwCfs7YNWaY3OXbpg.jpeg" /><figcaption>Photo by Alex Iby on Unsplash</figcaption></figure><p>Often, we’re focused on delivering production-ready output when we should be centred on <strong><em>learning</em></strong>. <a href="http://www.drdobbs.com/architecture-and-design/hypothesis-driven-development/229000656">Hypothesis-driven development</a> is an approach designed to validate ideas rather than ship features.</p><h4>Learn</h4><p>Recently the team pivoted to the proposed design of a new protocol. The stakeholder wish was to build a prototype to prove the protocol would work and to generate a revised version of the original specification based on observations made during the prototyping phase. We met with our stakeholders to agree the <strong><em>value proposition statement</em></strong>, <strong><em>acceptance criteria</em> </strong>(using SMART as a reference point) and a <strong><em>Definition of Done</em></strong> for the feature.</p><p><em>As a &lt;user type&gt;</em></p><p><em>I want &lt;desired feature&gt;</em></p><p><em>So that &lt;value outcome&gt;</em></p><h4>Probe-Sense-Respond</h4><p>We realised that this work sat in the <a href="https://en.wikipedia.org/wiki/Cynefin_framework">Complex domain</a> (unknown unknowns)and extended periods of analysis, planning and the traditional user value-driven User Story format would not help us. We wanted a probe-sense-respond approach to help us experiment, feedback, review and navigate from Complex to Complicated.</p><p><a href="https://barryoreilly.com/2013/10/21/how-to-implement-hypothesis-driven-development/">Barry O’Reilly’s useful webpage</a> got us the start we needed. Hypothesis-driven development suggests using a hypothesis as the focal point and determining the capability and measurements needed to either prove or disprove — both of which classed as successful outcomes. The Hypothesis template looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQx5HbY5-KPCXV5_BxW2ug.jpeg" /></figure><p>Mike Burrows’ recently published <a href="https://www.agendashift.com/book">‘Agendashift’</a> book provides the example of Facebook’s ‘Dislike’ button using the Hypothesis-driven development format:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPMHJ5nXJKBYuhpORx-sCg.jpeg" /></figure><h4>Discover</h4><p>Our approach was to combine the Hypothesis template with a Discovery Kanban-style work board. The ‘backlog’ column was used to capture ideas; these ideas were relevant to the feature but as could be as wild and inventive as the team wanted, the ideas were prioritised by our stakeholders and the team then got together as a group to port the ideas into the Hypothesis template. At this stage some of the ideas that were agreed to be outside of the scope of the feature acceptance criteria or outside the realms of reality were dropped with the agreement of the team. The team demo’d each hypothesis, proven or disproven, to our stakeholders before moving to Done. We also used an <a href="https://cucumber.io/blog/2015/12/08/example-mapping-introduction">Example Mapping </a>approach for each hypothesis, resulting in a bunch of Friends-style ‘The one where…’ test scenarios.</p><p>Again, as we expected variance and unpredictability due to the complex nature of the work, we did not feel running Sprints would offer value. We focused instead on team convergence on intent, limiting the number of hypotheses in progress and directed our attention on the work remaining to deliver against the expected outcome.</p><h4>Adapt</h4><p>Something we learned early on is that the Hypothesis template places the capability at the top — we thought that this <strong><em>could </em></strong>lead to a <a href="https://en.wikipedia.org/wiki/Pro-innovation_bias">pro-innovation bias</a> where the technical implementation took precedent over the expected value outcome, so we flipped the 2 statements around.</p><p>We realised that we could use the Hypothesis templates as collateral for the feature rather than needing to create too much in the way of additional documentation, we added <strong><em>‘then we learned’</em></strong> and <strong><em>‘which is why’ </em></strong>statements to the reverse of the Hypothesis templates following the demo of each completed experiment.</p><h4>Measure</h4><p>So, lots of experiments, but how valuable was this approach?</p><p>A key learning was to keep the hypothesis template as high level as possible rather at functional implementation level — what is the overall outcome we are trying to achieve?</p><p>We flipped round the ‘Capability’ and ‘Outcome’ statements on the Hypothesis template. It’s not clear whether this was really necessary although it did steer the focus of the team conversations toward the expected outcomes as we created the Hypothesis templates.</p><p>The addition of the <strong><em>‘then we learned’</em></strong> and <strong><em>‘which is why’ </em></strong>statements to the reverse of the cards were a useful way of capturing the outcomes of our experiments and deciding on next steps. These outcomes could be captured on your wiki or preferred shared workspace if a more permanent record is needed.</p><h4>Takeaways</h4><p>The main benefit of this approach for me is that it converges the team and the stakeholders on the intent of the experiment, reducing the possibility of the team disappearing down a rabbit hole of implementation without keeping one eye on the intended outcome. The re-framing of the work from <strong><em>product</em></strong><em> </em>to <strong><em>discovery </em></strong>was an important and useful step, freeing the team to think wider and with greater freedom. Definitely an approach I’ll be suggesting in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3b7239516a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cambridge-agile-exchange/learning-is-fun-experiments-with-hypothesis-driven-development-e3b7239516a5">Learning is fun: experiments with Hypothesis-Driven Development</a> was originally published in <a href="https://medium.com/cambridge-agile-exchange">Cambridge Agile Exchange</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>