<?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 Chris Smith on Medium]]></title>
        <description><![CDATA[Stories by Chris Smith on Medium]]></description>
        <link>https://medium.com/@chrissmithagile?source=rss-371191894233------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gQHTk6QjskI28YHeifC8Og.jpeg</url>
            <title>Stories by Chris Smith on Medium</title>
            <link>https://medium.com/@chrissmithagile?source=rss-371191894233------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:48:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrissmithagile/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[Evolving annual reteaming at Redgate]]></title>
            <link>https://medium.com/ingeniouslysimple/evolving-annual-reteaming-at-redgate-8c7526be267f?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c7526be267f</guid>
            <category><![CDATA[reteaming]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[redgate]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 16:32:32 GMT</pubDate>
            <atom:updated>2025-03-26T17:07:00.665Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How we’ve adapted our approach to reteaming to be more dynamic and efficient, and retained the good stuff</strong></h4><p><strong>Our journey so far with reteaming</strong></p><p>Since 2018, Redgate has applied a process we call “reteaming” to shape our groups and teams, responding to Redgate’s strategic aims and investment decisions for the coming year. The fundamental idea behind reteaming is that we should change our team structure in collaboration with the folks that work in those teams, enabling them to have influence over which team they work in. The process has enabled responsiveness to business needs while providing individuals with the opportunity to change teams to work in areas that align with their interests or support their professional development.</p><p>Why do we give people a strong influence over which team they work in? After all, it’s significantly more effort for us to create the environment, share the information, and manage the process that allows people to guide which team they work in. However, we gladly invest that time and effort because we believe doing so aligns with our principle that people will be most engaged and motivated in their work if they have <a href="https://en.wikipedia.org/wiki/Drive:_The_Surprising_Truth_About_What_Motivates_Us">autonomy, mastery and purpose</a>. In the case of reteaming, that means autonomy over what work they do, the space to gain mastery or develop their skills, and to work in service of a clear purpose they understand and believe in.</p><p>We’ve also found that deliberately encouraging some movement between teams spreads knowledge, best practice, and innovation, as people joining a new team bring experience from their previous teams with them. Reteaming also helps spread social connections throughout the organisation and break down team silos.</p><p>You can read more about our journey with reteaming <a href="https://medium.com/ingeniouslysimple/reteaming/home">here</a>.</p><p><strong>What prompted us to evolve our approach this year?</strong></p><p>As we moved towards our latest attempt at reteaming, aimed at reconfiguring our teams to support Redgate’s 2025 product and technology strategies, we realised that the needs of our now larger organisation, and the improved processes of the business, meant that we needed to evolve our approach to reteaming. It was time to inspect and adapt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5j6GQf_9JmgAxSmudbx6A.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/stocksnap-894430/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2570705">StockSnap</a> from <a href="https://pixabay.com//?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=2570705">Pixabay</a></figcaption></figure><p>Firstly, we’re a much larger organisation than we were in 2018, making some of the reteaming processes we were using inefficient and time-consuming. For example, ever since our first attempt at the process the majority (around 2 in 3) of engineers have preferred to stay in their current team, and therefore did not move during reteaming. Collecting these common choices manually from everyone was becoming an increasing burden.</p><p>Secondly, our product groups had a greater range of strategies, users, and technology stacks — causing movement between teams in the same group to become more popular than movement into another group. We also recognised that novel technology choices for specific products could increase the impact of experts in that technology moving out of the team.</p><p>Thirdly, and perhaps most importantly, (<em>Ed: so, why do you mention it third then?!</em>) Redgate have been gradually moving to a more iterative (or evergreen) strategy process, rather that a having a bigger-bang re-plan at the end of each year. This might also mean the business wants to make more significant changes, such as creating a new team, throughout the year, when market or product opportunities occur, rather than saving most significant changes to the next January.</p><p>In summary, reteaming needed to become more agile, more efficient, and support varying needs of our product groups.</p><p><strong>What we changed this year</strong></p><p>The key changes we made for 2025’s reteaming were:</p><ol><li><strong>Using an new internal opportunities board to share open and new roles throughout the year. </strong>If an engineer wanted to move teams during this reteaming, they did that by interacting with this internal job board and registering interest in a specific team. This streamlined the process of asking for a team move and will allow us to be more transparent about open roles in our teams throughout the year.</li><li><strong>Creating an “evergreen” Information Hub for team information and insights. </strong>Previously this information has been captured in ephemeral “team charters” prepared specifically for the reteaming process. In addition to avoiding one-off costs of building these canvases, the Hub is useful for Redgaters inside and outside of Engineering to explore the purpose, aims, responsibilities, and objective progress of each of our teams throughout the year.</li><li><strong>By default we now assume people want to stay in the team they are in.</strong> In previous years, most team members opted to stay in their current teams. Nonetheless, we encouraged everyone to also express their interests in other teams, both for personal development and to provide leadership with more options when forming new teams. For some, this created additional anxiety about reteaming due to uncertainty about possibly leaving a preferred team. This year, we decided to relax that requirement and assume that if individuals did not indicate an interest in another team, they wished to remain in their current team. However, to support this change and be transparent with participants, we called out that we may approach Engineers to suggest a team move if we believe their skills and experience could significantly benefit another team’s success. Interestingly, when we did that in a handful of cases, engineers were generally very open to moving towards work that had been identified as a great fit for them.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ysasusOXiyXa5ZbQd9JhCQ.png" /><figcaption>The new Opportunities Board, where participants registered an interest in joining another team</figcaption></figure><p>On reflection, these changes may have moved our approach closer to something what would meet the needs of other tech organisations — rather than the, perhaps idiosyncratic, requirements of our fairly rigid annual strategy process. I’ll leave that to you to decide.</p><p>This year our intention was to observe how these modifications would affect an already effective process for the Engineering organization. There was a concern that not requiring everyone to share team interests might limit leadership’s ability to create appropriate teams, due to having fewer team preferences to consider. However, it was anticipated that this year there would be fewer changes in product strategy and team investments compared to previous Januarys (for example, at the beginning of 2024, four new teams were created within the engineering organization) due to our more iterative strategy process.</p><p><strong>So, what was the outcome?</strong></p><p>The headline is that the evolved reteaming process allowed us to create a roster of teams aligned with the aims and investments of our product and system strategies 🎉. In terms of the outcomes for engineers, 95% of folks are in a team they sought to be in, and we were able to support team moves for 11 engineers (most of those moving teams within a product group).</p><p>The below graph shows that 11 engineers moving teams represents the lowest team movement percentage since we started applying a reteaming approach. Given that there were relatively few changes in product strategy and team investments that is not surprising. Nevertheless, this may still feel like a retrograde step in terms of supporting personal development aims and breaking down team silos. However, it’s worth noting that only around 10% of engineers registered an interest in moving teams, so there was not a great deal of demand for changes. This year also returned the highest ever percentage of folks that have ended up in their preferred team, which indicates we are still supporting the self-determination principle central to our approach to reteaming.</p><figure><img alt="A graph showing the scale of change in teams during each annual reteaming process" src="https://cdn-images-1.medium.com/max/1024/1*gEHslOuHcFQCOHpiR1-8CQ.png" /><figcaption>How 2025’s reteaming process compared to previous iterations</figcaption></figure><p><strong>2025 Redgate reteaming by the numbers</strong></p><ul><li><strong>9.1% </strong>engineers moved team</li><li><strong>94.5%</strong> engineers are in a team they sought to be in</li><li><strong>91%</strong> of engineers are in their 1st preference team (the vast majority of these preferring to stay in their current team)</li><li><strong>4</strong> <strong>hours </strong>was the approximate time individual engineers spent on reteaming activities over the month the process was playing out</li></ul><p><strong>What did participants think of the process this year?</strong></p><p>As we do with every reteaming, we surveyed participants to see how it worked for them and identify where we could improve next time. On this occasion, we also wanted to see how the changes we had made felt for those involved. Here are the highlights of what participants told us:</p><ul><li><strong>89%</strong> of respondents felt comfortable with the outcome of the reteaming process. This is an increase of 7.5% on last year’s process</li><li><strong>92%</strong> of respondents were happy with their personal outcome from reteaming, 1.7 % of respondents were unhappy. This is the same as last year’s process</li><li><strong>93%</strong> of respondents felt their team gelled quickly or continued unaffected following reteaming. This is the same as last year’s process</li><li><strong>92%</strong> of respondents were satisfied with the shape of their team following reteaming (5% increase on last year)</li><li><strong>13.5%</strong> of respondents felt anxious at some point during reteaming (a reduction of 6% over last year)</li><li><strong>0%</strong> (!) of respondents do not support Redgate’s approach to reteaming</li></ul><p>From these measures it seems that reteaming was a positive experience for the majority of those involved. Respondents apprieciated the default assumption that people wanted to stay in their team, the new Engineering Hub and the communication &amp; smooth process as highlights of this year’s process.</p><p>However, there were areas to improve. Respondents lamented the reduction in people deliberately thinking about possible team moves, and called out the uncertainty over how team moves might work at other times of the year. We’ll look to address these issues.</p><p><strong>We mentioned supporting team moves throughout the year, how might that work?</strong></p><p>With the changes to reteaming this year, we had aimed to put the mechanisms in place to support team moves at other times of the year. Those changes might be in service of mid-year strategy and investment changes, or personal development opportunities, where in-year promotions or leavers in engineering teams are of interest to folks in other teams.</p><p>To support this aim, we’ll be using the new Engineering team opportunities board to share open role in our teams and, if the need arises, any new teams that Redgate decides to spin up mid-year. We also have the new Engineering Hub, which we will keep up to date with the latest goals, team roster, working approach, objectives, and progress throughout the year — so engineers will easily be able to find out more about a team they might be interested in.</p><p>We are also considering running a mid-year “transfer window” where we ask Engineers to share any speculative interest they have in other teams. For a two-week period we’ll be on the lookout for people sharing interest in moves for personal development and seeing which of those we can support immediately or arrange for the future.</p><p><strong>Thank you! 💐</strong></p><p>Finally, I’d like to thank all the Redgaters involved in reteaming during December 2024 and January 2025 for engaging with, shaping, and delivering the activity. It was a team effort: Engineering Managers handled change management, team leaders invested their time in their information pages, engineers gave their options some deep thought, folks interested in moves made requests backed with clear rationale, and everyone supported the process of kicking off the new year and welcome new teammates. Thank you, all!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c7526be267f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/evolving-annual-reteaming-at-redgate-8c7526be267f">Evolving annual reteaming at Redgate</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do participants feel about annual reteaming?]]></title>
            <link>https://medium.com/ingeniouslysimple/how-do-participants-feel-about-annual-reteaming-7bfded98bd1f?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bfded98bd1f</guid>
            <category><![CDATA[reteaming]]></category>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Mon, 19 Apr 2021 13:45:15 GMT</pubDate>
            <atom:updated>2021-04-19T13:45:15.657Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>We’ve found that people appreciate having a strong influence on their destination during team reorganizations and that self-selection reteaming places people into teams they are happy to be part of. But there are difficulties to be aware of and, as with everything, there’s always room for improvement.</strong></p><p>In January 2021 we completed our 3rd annual reteaming process at Redgate. In previous posts I have described <a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">the principles of our approach to reteaming</a> — to give our staff a strong influence over the team they are part of and the work they do — and <a href="https://medium.com/ingeniouslysimple/how-redgate-ran-its-first-team-self-selection-process-4bfac721ae2">detailed the process we apply</a>. In this post I’ll talk about how participants have experienced the process.</p><p>After each Annual Reteaming we asked our development team members for their feedback. What they’ve told us has been broadly positive each time but has also highlighted areas for improvement that we’ve been able focus on in subsequent years. We’ve tuned the process to make it as smooth and timely as possible for the organization but also as comfortable as possible for our people. For instance, our first reteaming happened during December which many people found difficult because they had a decent about of holiday booked during that month, so they missed some of the context for decision-making and felt a bit rushed. For each year since, reteaming has taken place in January when virtually everyone is back at work and can fully engage in the activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A0KMQCha29aTjFERdHn8wQ.jpeg" /><figcaption>Feedback from our first annual reteaming in 2019</figcaption></figure><p>What is absolutely clear from feedback each year is that people far prefer being consulted and involved in these kind of team reorganizations than being moved around by an <em>arbitrary people moving machine </em>(see the below feedback from our first reteaming)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*kdjTQ7JAQ9TMOFolsfjZ9g.jpeg" /><figcaption>A close up of the <em>arbitrary people moving machine </em>feedback</figcaption></figure><p>Our latest reteaming was our first fully-remote process, so feedback via post-it notes and a whiteboard was not possible! Instead we used an internal survey to gather peoples experiences and observations on the activity.</p><p>Here are some of the key results (summarizing the responses from <a href="https://en.wikipedia.org/wiki/Likert_scale">Likert scale</a> questions):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*CIZhZ9h7H-Okzz9odIDigQ.png" /></figure><p>The above shows that:</p><ul><li>The vast majority of survey respondents were happy with their personal outcome from reteaming (87% agree, 13% neutral, 0% disagree)</li><li>Respondents were comfortable with the shape of their team and feel they have gelled quickly</li><li>Respondents felt they had the information and support they needed during the process</li><li>As a group, we think taking this approach of giving people a strong influence over where they work is a good thing</li><li>A significant proportion of people (39%) felt anxious about the reteaming process at some point.</li></ul><p>That’s mostly good news, but we were obviously drawn to the insight that reteaming can cause anxiety and stress for our people. That’s even though <a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">we have always been very mindful of the anxiety caused by organisational changes</a> and why we offer a 1–2–1 coaching conversation for every single person that is part of the reteaming process. It’s our way of ensuring participants have a supportive thinking partner while they consider their team preferences and personal development aims. We also broadly follow the <a href="https://www.prosci.com/adkar">ADKAR </a>change management model to help people become more comfortable with reteaming by explaining the reasons for why we do it, giving them as much information as possible about the process and the teams they can be part of, working with them to shape the team changes, supporting their decision-making process and helping them segue smoothly into their new teams.</p><p>A sympathetic solution to the anxiety reported to some might be to say, “Ok, we’ll stop annual reteaming then”, but that wouldn’t be in service of a central principle we hold dear in product development at Redgate — the ambition to give people autonomy, mastery and purpose. It also would not reflect the reality that reteaming, the changing and forming of teams, will always be necessary. People will leave teams, join teams &amp; move teams, and organizations will look to change the shape of their team structure to meet emerging needs. As <a href="https://www.heidihelfand.com/">Heidi Helfand</a> says in her book <a href="https://www.amazon.co.uk/dp/1492061298/ref=cm_sw_r_tw_dp_4G8EFSQXYSXF5XPQ8E3D?_encoding=UTF8&amp;psc=1">Dynamic Reteaming</a>, “team change in inevitable, so we might as well get good at it”.</p><p>Cancelling deliberate reteaming would also not help break down team silos, create personal development opportunities or spread good practice. No, self-selection reteaming is here to stay, but we should minimize the level of unnecessary anxiety (or dis-stress) caused by a reorganization process like reteaming. For instance, this year we suspect it would have helped if we’d been clearer that people who were happy where they are, and wanted to stay in their current team, would be able to do so. This was actually a principle from the team-forming process lead by our development managers, so in the end everyone who wanted to stay on in a team did just that. But next time we’ll be sure to explicitly call this aim out.</p><p>The key point is that, as with any reorganization process, self-selection reteaming can still generate anxiety for participants. It’s therefore paramount that leaders have a deep empathy for their people throughout, and are considerate of the uncertainty and worry that may be being created for some. While the team changes may be necessary, dis-stress is not, and we should do everything we can to ameliorate people’s concerns and reduce discomfort.</p><p>If you have any more questions about reteaming at Redgate then check out my FAQ post <a href="https://medium.com/ingeniouslysimple/reteaming-faq-and-an-offer-to-help-8079a22dc990">here</a>.</p><p><em>This post was originally published on </em><a href="https://leadingagileteams.com/2021/03/08/how-do-the-participants-feel-about-annual-reteaming/"><em>Leading Agile Teams</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bfded98bd1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/how-do-participants-feel-about-annual-reteaming-7bfded98bd1f">How do participants feel about annual reteaming?</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reteaming FAQ and an offer to help]]></title>
            <link>https://medium.com/ingeniouslysimple/reteaming-faq-and-an-offer-to-help-8079a22dc990?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/8079a22dc990</guid>
            <category><![CDATA[teams-and-teamwork]]></category>
            <category><![CDATA[agile-software-teams]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[reteaming]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Tue, 09 Mar 2021 13:31:42 GMT</pubDate>
            <atom:updated>2021-03-09T13:47:37.589Z</atom:updated>
            <content:encoded><![CDATA[<h4>Questions we’re commonly asked about self-selection reteaming at Redgate and an offer to help you plan your own process</h4><p>In January we completed our 3rd annual reteaming process at Redgate. I’ve written a couple of posts about <a href="https://medium.com/ingeniouslysimple/how-did-our-first-remote-annual-reteaming-go-d5b26ed7276c">how that went</a> on this site and shared a tour through a key event in our approach —<a href="https://youtu.be/G5xcKB8lNhI"> the team charter expo</a>.</p><p>In response to that video I’ve had several people from different organizations make contact with me to ask about reteaming. They were curious about similar aspects of the process, so I thought I’d share my answers here, in case it’s useful for anyone else.</p><p>If you like videos for this kind of thing, I cover some of the questions in the recording below on a walk around my local countryside (while I self-consciously wrestle with a selfie stick):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_sI6VHLBSDo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_sI6VHLBSDo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_sI6VHLBSDo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/500f7dff1e1a1a3bbbd28fbfb5c202f2/href">https://medium.com/media/500f7dff1e1a1a3bbbd28fbfb5c202f2/href</a></iframe><p>But if you like you blog posts to actually have words and sentences and stuff, please read on:</p><h3>Reteaming Frequently Asked Questions</h3><h4><strong>Q: What prompted you to start deliberately reteaming at Redgate?</strong></h4><p>Firstly, some context: At Redgate we have called out a central principle of our approach to software development that “we believe the best way to make software is by engaging teams empowered with a clear purpose, freedom to act and a drive to learn”. We have that Guiding Star because we’ve seen teams that have those things succeed and be special places to work, but we were also inspired by Dan Pink’s book <a href="https://www.amazon.co.uk/dp/184767769X/ref=cm_sw_r_tw_dp_U_x_GaFmDbSJB3M56">Drive: The surprising truth about what motivates us</a> (read more about what we took from the book <a href="https://medium.com/ingeniouslysimple/last-week-i-was-put-together-a-reading-list-for-an-interview-candidate-recommending-some-of-the-d6fa314b1577">here</a>).</p><p>Three years ago we decided we wanted to make a significant change to how we organize and direct our development teams. You can read more detail about that <a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">here</a>, but to summarize the changes we were making; we wanted to change what some teams worked on, create one new team, explicitly explore some new product areas and group teams by life cycle stage. A complex change to undertake, but one that would correspondingly create many new personal development opportunities for our people to take on.</p><p>Around that time we’d been inspired by <a href="https://medium.com/u/317014acd998">Heidi Helfand</a>’s popular conference keynotes about “dynamic reteaming” and drawn to the idea of giving our people more freedom and influence over the work the do. After all, if we were really serious about that central principle of giving people autonomy, mastery and purpose — then surely when faced with such a change and the variety of work available across our product portfolio, we had to give people a say over which team they would like to be part of!?</p><p>Furthermore, we’d seen some drawbacks of having long-lived, very stable teams with fewer internal moves between groups. Teams became naturally siloed; common tasks were often duplicated, knowledge was tacit rather than explicit, team approaches were prone to ossification and experts became deeply entrenched in their teams, unable to move for fear of leaving a team unable to operate without them.</p><p>All that together lead to our first attempt at deliberate, self-selection reteaming. Fortunately, Redgate is a progressive and people-first organization who trusted my team and I to <em>go for it</em>!</p><h4><strong>Q: Why (on earth) do you do this every year?</strong></h4><p>Well, we refresh our portfolio and product strategies at the end of each year at Redgate, and that can prompt a change of mission for some teams or create entirely new areas of work where we need to build a team to undertake. So we follow-up that strategy process with reteaming to give our people an opportunity to get involved in the upcoming work they are most motivated by or interested in.</p><p>Worth noting that while we’ve always been open for people to move between teams at Redgate — but people seldom asked for one before we started deliberately reteaming. Making the process regular (if infrequent) occurrence has normalized team moves, helped reduce team silos and driven us to get better at forming new teams quickly.</p><h4><strong>Q: </strong>Do you end up with no one wanting to be on certain teams?</h4><p>Prior to our first attempt at the process I was certainly concerned that some teams, perhaps those doing less glamourous work supporting legacy products or alike, would be unpopular destinations for people and so left with no team members following reteaming! But we have not found that to be the case. We’ve reteamed 3 times, and while we’ve had oversubscribed teams and undersubscribed teams, we’ve always been able to create a full roster of functional teams. That happened predominately because people’s preferences allowed for it naturally, with folks favoring a range of types of work — from early stage, lean product exploration to on-going maintenance and scaling of our most popular, established products. It seems you really do need <em>different strokes for different folks</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atkg140mQeBh_0syskS0dQ.jpeg" /><figcaption>Rey was uncomfortable with the outcome of this year’s reteaming process</figcaption></figure><p>We take care to highlight the mission of a team when providing people with information on what each team will be like. People don’t just join a team for the whizzy programming language or the market stage of the product, they care if they can have an impact on users’ lives and the success of the business. So while a product team might be dealing with gnarly code or an unfashionable tech stack, their product might be crucial to a cohort of users’ working lives. That speaks to the purpose that people need to be engaged and motivated in their work, as called out in Drive.</p><h4><strong>Q: Does everyone move teams during reteaming?</strong></h4><p>No. Many people have chosen not to move during each iteration of our reteaming process. In fact, each reteaming has seen ‘only’ around a third of our software development staff join new teams. The majority of people were happy in their current team, still committed to their mission, comfortable building skills on a familiar technology or simply did not have the appetite for a significant change at the moment. And that is absolutely fine.</p><p>Annual reteaming is not about disbanding all our stable teams and starting again from scratch. It’s about giving everyone the opportunity to move towards the work that best speaks to their aspirations and motivations. Those needs can often be served by staying put.</p><h4><strong>Q: What happens when you need to change things mid-year?</strong></h4><p>Despite having a predicable, regular cadence for reteaming, we are still able to create new teams or have people move between teams throughout the year. After all, we need to be a responsive, agile organization no matter the time of year — so we must be able to spin-up work at short notice to take advantage of an opportunity or tackle an emerging challenge. Similarly, there is no point making someone stay in a team until the next reteaming event if their work no longer motivates them or they can see an internal personal opportunity elsewhere.</p><p>When we change mid-year, we apply the same principles as we do during reteaming . We give people a strong influence over where they work, make new team opportunities visible &amp; open and work with people to smoothly manage their transition into a new role.</p><p>Having said all that, it is fair to say that the vast majority of team changes do happen during our reteaming process (which happens in response to our annual product strategy review). So things do tend to be fairly stable during the rest of the year.</p><h3>Can we help you try self-selection reteaming?</h3><p>Giving people more autonomy over their work, the space to gain mastery and a motivating purpose is something we are really passionate about at Redgate. We see self-selection reteaming to be in direct service of that principle and we’d love to help other organizations try it too. So, if you have any other questions about reteaming, would like to know more about how to run a process (remote or physical) or how we build great teams at Redgate following reteaming, let us know in the comments, on twitter at <a href="https://twitter.com/cj_smithy">@cj_smithy</a> or by emailing chris.smith@red-gate.com.</p><p><em>This post was originally posted on </em><a href="https://leadingagileteams.com/2021/03/08/annual-reteaming-faq/"><em>Leading Agile Teams</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8079a22dc990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/reteaming-faq-and-an-offer-to-help-8079a22dc990">Reteaming FAQ and an offer to help</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How did our first remote annual reteaming go?]]></title>
            <link>https://medium.com/ingeniouslysimple/how-did-our-first-remote-annual-reteaming-go-d5b26ed7276c?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5b26ed7276c</guid>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[reteaming]]></category>
            <category><![CDATA[redgate]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Wed, 27 Jan 2021 22:12:13 GMT</pubDate>
            <atom:updated>2021-03-09T13:38:40.118Z</atom:updated>
            <content:encoded><![CDATA[<p>This month Redgate’s Product Development organisation embarked on <a href="https://medium.com/ingeniouslysimple/product-development-reteaming-at-redgate-b094e71b45e6">our annual “reteaming” process</a> to reconfigure how our teams are assigned to reflect the company’s 2021 strategy and plans. For the last 3 years, our approach to these team changes has been to allow people to strongly influence where in the new team structure they will work, encouraging them to move towards the work they find most engaging. This year, for the first time, we had to run reteaming as a fully-remote process.</p><p>As I described in more detail in <a href="https://medium.com/ingeniouslysimple/product-development-reteaming-at-redgate-b094e71b45e6">my previous post</a>, our reteaming process involves asking people in product development to tell us their preferences for their team in 2021 and the reasoning behind those preferences. We then look to balance those preferences with the needs of the development teams and Redgate, forming a new team structure that could deliver against Redgate’s strategy but also give as many people as possible the kind of work they were most keen on. This post aims to share the results of reteaming and how we had to adapt the activity during a national lockdown.</p><h4>The team changes we were aiming to make during reteaming</h4><p>Before describing what happened, let’s focus on the desired outcome of of this year’s reteaming. We were looking to reorganise into 11 well-balanced, cross-functional development teams (that’s 10 stream-aligned teams and one platform team, <a href="https://teamtopologies.com/">Team Topologies</a> fans). This included combining the remit of two teams into a single team and doubling the size of another team. Every team was to have an updated or brand new mission, reflecting our product portfolio strategy for the new year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuYX2i0LbH_d0BEgYTt_KQ.jpeg" /><figcaption>We’d like 11 teams, please</figcaption></figure><p>In addition to these changes, we had several team leaders who wanted to move to work on different products and a newly promoted technical lead looking forward to kicking-off their first team leadership role. We also have a number of open software engineer roles that we will wanted to distribute across the team structure, ready for us to fill them as soon as possible in 2021. In related news, <a href="https://www.red-gate.com/our-company/careers/current-opportunities/">we’re hiring </a>— you should come work with us ;)</p><h4>How we build our new teams</h4><p>It is significantly more effort for us to create the environment, share the information and manage the process that allows people to have a strong influence over which team they work in. We gladly invest that time and effort because we believe doing so reflects our principles of autonomy, mastery and purpose, spreads best practices and creates personal development opportunities across the development organisation (find out more about why we use a self-selection process for reteaming <a href="https://medium.com/ingeniouslysimple/product-development-reteaming-at-redgate-b094e71b45e6">in this post</a>).</p><p>Our Development Managers and Coaches owned the task of gathering people’s team preferences via one-on-one conversations via Zoom. We then went about building a new team structure that would best meet the needs of Redgate’s product strategies for 2021 while meeting as many people’s preferences as possible.</p><p>We used the following principles to help guide our decision-making:</p><ul><li>Our goal is to have 11 healthy teams. We’ll put the overall health of the development organisation before the needs of the teams we are directly responsible for as development managers.</li><li>We should strive to respect the constraints and needs for team membership &amp; skills called out by our team leadership groups.</li><li>We should consider the balance of each teams, especially regarding development experience and existing product experience.</li><li>We want to meet as many people’s team preferences as possible and strongly consider the reasoning behind their preferences when assessing team options.</li><li>We favour keeping people where they are if their 1st preference is to stay in their current team. We don’t want to move people who are content and settled in their team.</li><li>We should spread the open roles across the division as much as possible, rather than having a few very small teams.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e9w29ke0I3-s19txrdOjBQ.png" /><figcaption>We used a Mural canvas to help us guide the process and visualise people’s preferences against our desired team structure</figcaption></figure><p>These guidelines really helped us objectively turn 50+ preferences into a coherent team structure in a little under 3 hours. We ran the proposed structure past our team leadership groups to ensure they were comfortable with it and we had a conversation with everyone who did not get their first team preference to explain why. Worth noting we had to ask a handful of people to delay their moves for a little while to ensure they don’t leave their current teams in the lurch before new joiners have had chance to get up-to-speed with their new context. In every case, those people were very understanding and were happy to remain where they are for a little while longer.</p><h4>How much movement was there and how much say did people really have?</h4><p>The final team structure we assembled saw <strong>37% of the people working in or with our product development teams join new teams or product areas</strong>. That’s slightly more movement than we had in our previous reteaming efforts, when around 33% of people moved. Our teams coped well with that disruption and the benefits of the moves vastly outweighing the drawbacks. So, I’m confident we’ll segue into our new team structure really well.</p><p><strong>We were able to meet the 1st team preference for 83% of the people involved in the reteaming process</strong>. Which just goes to show that different people genuinely favour and are motivated by different kinds of work. Furthermore, <strong>98% of people involved in reteaming will be in a team that they specified a 1st, 2nd or 3rd preference for</strong>. For the people that missed out on a preference, I’m pleased to report we were still able to find them a team that met the personal development objectives they were looking to serve.</p><p>I’d like to thank everyone in Product Development who engaged in the process, thought deeply about where they would like to work in 2021 and had open &amp; honest conversations with dev/tech leads to explore their options.</p><h4>How did we cope with reteaming while fully remote?</h4><p>Organisers and participants alike seemed to handle it really well! Our experience working remotely over much of the last year stood us in good stead for running this process away from the Office. We flexed between asynchronous and synchronous styles of interaction and made good use of the tools that have helped us work effectively at home.</p><p><a href="https://www.mural.co/">Mural </a>and <a href="https://www.atlassian.com/software/confluence">Confluence</a> allowed us to share all the content relating to what our teams will be like in 2021 for people to consume at a time that best suited them. <a href="https://spatial.chat/">SpatialChat</a>, a virtual meeting space platform, and <a href="https://zoom.us/">Zoom</a> made it possible for us to collaborate effectively face-to-face to explore, gather and fit-together people’s preferences.</p><p>Much of the context around our team’s plans were presented in lightweight team charter canvases, which our team leadership groups put together for the process. This year we converted our large physical A1 team charter posters from previous reteamings to a Mural template, which you can see below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHpTy3Eb4BF0MiNiMEFxYA.png" /><figcaption>Our team charter template in Mural-form</figcaption></figure><p>These were prepared right at the start of the reteaming process and people were able to review them asynchronously to delve into the details and prepare questions to ask the team leaders at our 2021 team “expo”. You can also get a peek inside that open event, which allowed people to explore what our teams will be like in 2021 in the below video on our Ingeniously Simple YouTube channel:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FG5xcKB8lNhI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DG5xcKB8lNhI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FG5xcKB8lNhI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2edc29c98c3a980dc19f006056a19e6/href">https://medium.com/media/d2edc29c98c3a980dc19f006056a19e6/href</a></iframe><p>In the video I take a tour through the expo, explain how the event fits into the overall process, see what goes into a team charter and interview a few team leaders to find out how the event was for them.</p><p>All-in-all, I can honestly say that our remote reteaming process seemed to run more smoothly than our previous physical attempts! If you have questions about our approach to reteaming, then checkout <a href="https://medium.com/ingeniouslysimple/reteaming-faq-and-an-offer-to-help-8079a22dc990">my FAQ post </a>here.</p><p>You can also read about how <a href="https://medium.com/ingeniouslysimple/reteaming-in-a-remote-world-95eb3a7de06f">Redgate’s CORE department</a> (our internal engineering, operations and critical infrastructure teams) applied the lessons from our reteaming process to restructure and reform their group over the last few months. There’s lots of great ideas in there about how to encourage people to engage and get involved in wider restructures — even when many of us are working from home. Check out <a href="https://medium.com/u/6f41031b1a2">Damon Witherick</a>’s post <a href="https://medium.com/ingeniouslysimple/reteaming-in-a-remote-world-95eb3a7de06f">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5b26ed7276c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/how-did-our-first-remote-annual-reteaming-go-d5b26ed7276c">How did our first remote annual reteaming go?</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What was the impact of Level Up Week 2020?]]></title>
            <link>https://medium.com/ingeniouslysimple/what-was-the-impact-of-level-up-week-2020-ade1f3728d82?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/ade1f3728d82</guid>
            <category><![CDATA[redgate]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[levelupconf]]></category>
            <category><![CDATA[internal-conference]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Tue, 15 Dec 2020 17:31:03 GMT</pubDate>
            <atom:updated>2020-12-16T14:38:43.759Z</atom:updated>
            <content:encoded><![CDATA[<p>Level Up Week 2020 was Redgate’s first ever global event focused on learning and personal development. It encouraged us to share skills, knowledge, and ideas with other Redgaters and give each other opportunities to grow and improve. Originally envisaged as a physical conference, Level Up Week also became our first company-wide remote event, delivering content at a sustainable pace and in a format we thought people could really engage with while they’re working from home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TsmQkL8CkjImbKsdfgea8Q.png" /></figure><p>This post continues the story of how Redgate pivoted its internal tech conference to be a company global virtual conference in September 2020. If you’d like to hear the whole story of how we planned &amp; delivered the event, discovering some unexpected advantages of a remote conference, you can <a href="https://medium.com/ingeniouslysimple/level-up-week-2020-how-we-evolved-our-internal-tech-conference-for-our-remote-first-world-e1fcd6eec95a">read that here</a>.</p><p>Here we consider whether Level Up Week 2020 was objectively a success, focussing on if it delivered the outcomes and had the impact we aimed for.</p><h3>The post-event survey</h3><p>It’s fair to say the Level Up Week Organising Team were completely blown away by the engagement during the week from across Redgate, the strength of support and appreciation that Redgaters gave our speakers, and the sense of reconnection with the wider company. It certainly <em>felt</em> to us like things had gone well but, to be honest, the team and I are a bit biased! We really wanted to step back and get a more objective view of whether the event had met the aims we set out at the start of the planning process. Afterall, putting on the event was a lot of effort and we only wanted to do it again in the future if that effort was well placed.</p><p>Thanks to the 104 wonderful Redgaters who took the time to fill in our post-event survey, we developed a clearer sense of whether Level Up Week did what it was meant to do and how people felt about the event itself.</p><p>We’ll start by sharing the ratings survey respondents gave Level Up Week’s sessions, organisation, communication and social events, plus the overall rating for the event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*3RRYwBTzBUzDjJoxThXNdQ.png" /></figure><p>We’re delighted with these scores. They compare favourably with the results of a similar survey for the development-focused Level Up conferences in <a href="https://medium.com/ingeniouslysimple/level-up-2018-survey-results-be9aa2b114fd">2018 </a>and <a href="https://medium.com/ingeniouslysimple/level-up-2019-attendees-survey-results-2d38a8cfa89e">2019</a>. This is remarkable given that those were physical events able to focus more tightly on the L&amp;D needs of a smaller group of people.</p><p>Focusing on the quality of sessions rating, 98% of respondents rated Level Up Week’s sessions as 4 or 5 out of 5. A lovely quote from the survey was, “Every talk or workshop I attended was of a quality that I would hope to get from any paid external conference”, and respondents shared the following themes regarding why they scored the quality of sessions so highly:</p><ol><li>Many attendees said they learned something in every session they attended</li><li>Sessions were considered to be well prepared and high-quality</li><li>In general, session content was clear, informative and engaging</li><li>Workshops and interactive sessions were engaging and valuable</li><li>There were a wide range of talks from across the business on a variety of topics</li><li>Every speaker was a Redgater, and it was good to see a mix of public speaking experience on show</li></ol><p>A conference lives and dies on the quality of its sessions, and clearly this is where our 42 speakers (all Redgaters) excelled — thank you so much to every one of those brave souls who stepped in front of their webcam to present their skills and ideas to their colleagues.</p><h4>What did people takeaway from Level Up Week?</h4><p>Rather than just rely on survey respondents telling us a score for the usefulness of the sessions (in which they would probably be quite optimistic and kind) we decided to ask respondents to tell us what their key lessons were from Level Up Week.</p><p>Redgaters called out a huge variety of takeaways from the sessions during the week. Here are a few of our most common lessons:</p><ul><li>There’s a really high level of talent at Redgate and an enormous wealth of skills and experience that we can share with each other.</li><li>It’s important to set time aside to invest in personal development and embrace a growth mindset when faced with difficult work or new opportunities.</li><li>We can do more on diversity and inclusion and we have a large group of Redgaters who are passionate about addressing this.</li><li>We learned presentation skills and about the mindset we need to step forward to do more public speaking. New speakers also learned that they really can give a talk and their fellow Redgaters will be really supportive of them.</li><li>We learned how to level up our writing skills and how we can put them into practice.</li><li>Sketchnoting is a fun and valuable skill to learn — but its something that we can all pick up and put into practice.</li><li>Software accessibility is something we can and should think more about.</li><li>We learned a lot about career progression, paths and opportunities from the Exec session.</li><li>We learned about how different functions within Redgate work and that there is real interest from Redgaters in other parts of the business.</li><li>The Imposter Syndrome is something many of us suffer with and many of us have the same worries about our work. We’re all in the same boat and we that’s comforting to know.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XhoSkc7rpSaz1Z7XzivUbw.jpeg" /><figcaption>Sketchnoting with Chris Spalton</figcaption></figure><p>In addition to lessons, we asked people what they were already doing differently as a result of Level Up Week. It was wonderful to hear that Redgaters are investing more in personal development. From reading new books, blogging and sketchnoting to practicing intent-based leadership and delegating to grow others.</p><p>For some rigorous scientific analysis of what respondents told us in this category, here’s a pretty word cloud emphasizing the common words from those responses:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTJPfoZhEGzJ25lX1JURDQ.png" /></figure><p>More learn, indeed.</p><h4>Bringing Redgate together</h4><p>One of the biggest successes people reflected on in the survey was how Level Up Week brought Redgate together and increased our feelings of “connectedness” with the wider company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OY0GX6nXNDkZE1oacfLy6g.png" /></figure><p>91% of respondents who attended the event agreed that they feel more connected to Redgate as a result of Level Up Week. For context, there was no strong consensus that Level Up Week increased connection within our teams. That lead us to wonder whether a future Level Up event could look to catalyse some shared learning within our normal working groups.</p><h3>Did Level Up Week meet its objectives?</h3><p>While the results of the survey are heartening, the Level Up Week Organizing team were keen to review whether the event had the impact we were hoping for. At the start of the initiative we used <a href="https://en.wikipedia.org/wiki/OKR">Objectives and Key Results</a> (OKRs) to set out and measure the outcomes we wanted the event to deliver.</p><p>Ultimately, we believe learning &amp; personal development is vital to increase the capability of the organisation, staff engagement and the company’s performance. The aim of Level Up Week was to invest in people’s learning and personal development, encouraging Redgaters to share the skills, knowledge and ideas we need for a successful Redgate and for Redgaters’ growth.</p><h4>Level Up Week’s OKR:</h4><p><strong>Objective </strong>(what change are we trying to encourage): Increase engagement with learning &amp; personal development for Redgaters by delivering an engaging and valuable ‘theme week event’.</p><p><strong>Key Results</strong> (how we know we’re succeeding with that objective):</p><ul><li>We wanted high engagement from Redgaters. Despite being an optional activity, 74% of Redgaters engaged with a session or activity during the week. Our target was 60% of Redgaters, so the event exceeded our expectations. This figure does not include people who could only catch-up on video content during the week.</li><li>We wanted the event to be valuable for people’s personal development. Only 2% of respondents reported learning nothing or not very much from the event. Our aim was to that 90% of event attendees believe the event was valuable for their personal development.</li><li>We wanted people to be able to apply what they have learnt in the role. 64% of survey respondents named something new they were trying or going to try themselves or in their team. We aimed for 50% of people who engage with the event to be able to name something they have taken away to try themselves or with their team.</li><li>We wanted to see visible impact of the event at Redgate. We have been able to gather stories of change from across the company on the back of Level Up Week. For example, many Redgaters have offered to share their skills in workshops on the our new #level-up Slack channel, people are practicing and sharing their sketchnoting efforts and a Redgater in Marketing committed to organizing a book club having heard about the practice in Product Development.</li></ul><p>In summary, Level Up Week did have the impact we had hoped for, exceeding each of our key result targets.</p><h3>What next for Level Up?</h3><p>Well, it seems Level Up Week 2020 — Redgate’s first ever global event focused on learning and personal development — was a success from a variety of perspectives. It encouraged us to share skills, knowledge, and ideas with other Redgaters and give each other opportunities to grow and improve.</p><p>For the hybrid/remote-first working future many of us expect to become the norm (some work in an office, some work at home — but aiming for equality of experience wherever you are) and to improve our connectedness with our global offices, it’s likely that we’ll continue with a week-long remote learning &amp; development event in 2021 and beyond.</p><p>If you’d like to know more about Level Up Week 2020 or how to evolve your company conference into a virtual event, please do let me know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ade1f3728d82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/what-was-the-impact-of-level-up-week-2020-ade1f3728d82">What was the impact of Level Up Week 2020?</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Level Up Week 2020: How we evolved our internal tech conference for our remote-first world]]></title>
            <link>https://medium.com/ingeniouslysimple/level-up-week-2020-how-we-evolved-our-internal-tech-conference-for-our-remote-first-world-e1fcd6eec95a?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1fcd6eec95a</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[virtual-events]]></category>
            <category><![CDATA[levelupconf]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Tue, 08 Dec 2020 17:58:00 GMT</pubDate>
            <atom:updated>2020-12-16T14:33:27.054Z</atom:updated>
            <content:encoded><![CDATA[<p>Since 2018 Redgate’s Product Development organisation have run an internal conference to inspire people to engage in their personal development, build capability across our teams and bring people together to learn, share and collaborate. The conference — which we called <a href="https://medium.com/ingeniouslysimple/levelup/home">Level Up </a>— got us out of our usual working environments to learn from other Redgaters working on different things and gather fresh insights &amp; opinions.</p><p>In 2018 our first Level Up conference had 80 attendees with around 20 people speaking to deliver sessions. Last year, Level Up 2019 had 120 attendees and almost 40 speakers. Both conferences were a big success, garnering great feedback from attendees and speakers alike, and enabling some tangible improvements in our teams.</p><p>If you want to know more about our previous Level Up conferences, check out <a href="https://medium.com/ingeniouslysimple/level-up-2019-has-landed-f5c16c9f8ce3">this blog post</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Udw65uKSyv-SSiL6-0zTrQ.jpeg" /><figcaption>A scene from Level Up 2019 Conference</figcaption></figure><p>At the start of this year, we had big plans for this year’s event — the Level Up 2020 Conference. Our CEO was keen to build on the success of the product development focused event and widen the scope to include the whole company in a day of learning and personal development. This would mean expanding the conference to include every UK-based Redgater (250+ people) and expand the programme content, so it provided engaging and valuable sessions for everyone — from sales representatives and finance controllers to software engineers and our HR advisors. Quite a challenge, but the Level Up Organising Team and I gladly accepted it, then went about planning the event. We booked a magnificent venue, set some OKRs, worked out the scope of the programme and even created some brilliant branding.</p><h4>Enter Global Pandemic</h4><p>Then, of course, the COVID-19 pandemic happened, and it became very clear that we were not going to be able to put 250 employees in a conference centre together any time soon.</p><p>Following that realisation, the organising team almost gave up on having an event this year. Our full focus rightly became our day jobs and our home lives; segueing our teams and business to be effective working from home and looking after our nearest and dearest. The same as everyone else, I guess. Due to the clunky nature of our remote working in those early days and the attrition of never-ending Zoom meetings, we struggled to get as excited about a remote Level Up as we had been about our physical event.</p><p>Eventually though, once we got over the first few months of lockdown, we saw that we needed to get back to doing more than just surviving remote work, and the team gradually got our collective heads around running a remote learning &amp; development conference. Initially, we started thinking about a straight switch into a single day remote conference, but we just couldn’t shake the feeling that wasn’t something people were going to be able to get excited about or comfortably engage in.</p><p>We decide to do some research and spoke to people across Redgate to see what they thought — they seemed to agree. Those who had already attended remote conferences, workshops, and training sessions during lockdown told us it was difficult to make the most of them. Audience engagement, where many people get the most value from these events, really suffered and concentrating on your screen for too long was a huge challenge. Plus, the flexibility required to balance home commitments — such as home schooling — was not compatible with a solid day spent at an online event.</p><p>We took a step back, deciding to look at the subject from another angle by asking ourselves “what would a remote conference allow us to do, that a physical conference does not”. We soon realised a virtual event might give us some important advantages. This insight gave us the nudge we needed to get past out disappointment of our lost physical event and get excited about what we could achieve with a virtual conference.</p><h4>The benefits of a remote company conference</h4><p>Here are the advantages we felt a virtual event would allow us to achieve:</p><p><strong>1. We could deliver the conference content at a more sustainable pace</strong></p><p>Rather than one intense day of talks and workshops, we decided the virtual format meant we could run a week-long event, spreading the exciting content we would have had at a conference over 5 days. That did not mean MORE sessions for us to schedule; it’s the same number of sessions but spread out to leave gaps in the timetable. We felt that would allow people to take a break from their screens, look after things at home and do some ‘normal’ work.</p><p>You could never do this with a physical conference at an external venue — it would mean shipping the event’s attendees out to a lecture theatre for 2 hours a day for 5 days in a row!</p><p>As a result, the Level Up 2020 Conference became Level Up Week 2020.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZPy8j-v7-QMAAvu5YxBlQ.png" /><figcaption>One quick rebrand later</figcaption></figure><p><strong>2. We could open the event up for our global Redgaters</strong></p><p>Redgate has it’s HQ in Cambridge, UK, but has offices around the world in the US, Australia and Germany. We were always keen to make our L&amp;D focussed conference accessible for folks in Redgate’s global offices not just our Cambridge-based people, but we didn’t think this was possible for a physical event. A virtual event is a much better choice for people across the world to engage with, providing we schedule sessions times at sympathetic times of the day.</p><p><strong>3. We could record everything to allow people to catch-up at a time that works best for them</strong></p><p>With the virtual event we would naturally be able to record every single session and build up a library of awesome content to be watched or re-watched at a later time. While this is possible with a physical event, it logistically tricky for a multi-track event that takes place on that single conference day. A remote event makes this task so easy.</p><p>We could plan to add sessions to a full library of content within hours of the live presentation. The valuable sessions that we would spend time, effort and skill preparing for Level Up Week would be preserved for years to come, ensuring we get as much value and insights as possible from that energy.</p><p><strong>4. We could provide something to suit a wider variety of learning styles</strong></p><p>Some people like in-depth talks to learn all they can about a subject, some people want a quick introduction to a topic for inspiration to explore on their own. Some find they retain lessons from getting their hands dirty in interactive workshops and others would rather not have to collaborate with other people while they get to grips with something new. Some find they need a deadline of a live talk in order to actually watch a session, others want to watch a session when it suits their timetable and they have some flow time. Some want to dip in and out of sessions as fits their day, some campers want to sit down for 3 hours and watch EVERYTHING. Some people want to debate what they have just seen straight-away, others really don’t.</p><p>A physical conference would have allowed us to provide something to suit most of those preferences but a virtual event allowed us to hit all of them — and that was important in order to make it as easy as possible for as many people as possible to invest in their learning and development.</p><p><strong>5. We could bring Redgaters together at a time when we really needed it</strong></p><p>In mid-March 2020 Redgaters, like many people around the world, found themselves to unexpectedly to be full-time remote workers. This wasn’t a situation most of us would have chosen and we certainly not something we were well prepared for.</p><p>In our teams we scrambled to transform our practices, processes and attitudes to make distributed groups work — and we were pretty successful with that. What we were less attentive to, was our relationship with the wider company, our connectedness to other teams in adjoining areas of the business and our social relationships with people we <em>know</em> from across Redgate.</p><p>The global pandemic, lockdown, stress and the isolation of home working took its toll on many of us. And while many of us closely connected with, and well supported by, their immediate colleagues, we were losing touch with what it felt like to be part of a bigger community.</p><p>A big cross-company event like Level Up Week would give us an opportunity to reconnect with the company and see friends from across the company that we have not bumped into since March.</p><h4>Level Up Week takes shape</h4><p>In June, we announced our plans to evolve the Level Up conference into a format that better suited a fully online event; in September we would be running a week-long event, Level Up Week 2020. The aim of the event remained the same — to invest in people’s learning and personal development, encouraging us to share the skills, knowledge and ideas we need for a successful Redgate and for Redgaters’ personal growth. We also decided on a theme that we believed the whole company could come together behind — The Growth Mindset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ijyomr1C8nZf17JgqP_lRw.png" /><figcaption>Our theme for the programme</figcaption></figure><p>The aim of the theme was to set people’s expectations for the type of content that would be available during Level Up Week, and to help potential speakers decide which topics are appropriate. The theme also needed to reflect the Learning &amp; Development mission of Level Up Week but shouldn’t be too restrictive in terms of what people could share at the event.</p><p>A growth mindset is the belief that people can develop their talents through hard work, good strategies and input from others. The concept comes from <a href="https://en.wikipedia.org/wiki/Carol_Dweck">Carol Dweck</a>’s 2006 book Mindset.</p><p>A fixed mindset tells us that if something new is difficult or effort-intensive, we are inadequate. A growth mindset tells us that if something is hard, it means we’re in the process of growing new capabilities.</p><p>Equipped with our programme theme and with a date to aim for, we went about creating the event.</p><h4>The Big Event</h4><p>On 7th September 2020 Redgate kicked off it’s first ever global learning and development conference — Level Up Week 2020. By the time the week was over, we’d collectively seen 14 talks, 21 lightning talks, 10 hours of workshops, 11 hours of video content and 42 Redgate speakers sharing their skills &amp; ideas. In the final count, more than 275 Redgaters had attended at least one session during the event; that’s 75% of all Redgaters globally.</p><p>We were blown away about the level of engagement with the event from our remote workforce and the sheer quality and influence of the sessions people ran for their fellow Redgaters.</p><p>But what about those remote event advantages we were hoping for?</p><p><strong>1. We said we could deliver the conference content at a more sustainable pace.</strong></p><p>Feedback on the pace of the event schedule was excellent, with people reflecting that they found it manageable to fit sessions into their day and that they could absorb the lessons without being worn out. Here’s a few of the comments we received; “Just a brilliant week. You could’ve fitted everything on the same day but that would’ve been awful — just like online conferences are at the moment where it’s exhausting!”, “Excellent, much prefer a week rather than trying to cram it all into one or two days, we should do this again”. Whoop!</p><p><strong>2. We said we could open the event up for our global offices.</strong></p><p>Going virtual really did open-up Level Up Week as an event for all Redgate, and it was great to see folks based out of US offices attend sessions and take a full part in the discussion around talks. A highlight for me was the closing session at the end of the week, where we could all scan across pages and pages of Redgaters from across the world coming together to review a week of learning and reconnection with the wider company (I took a snap of just one of the multiple Zoom screens full of Redgaters, below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TsmQkL8CkjImbKsdfgea8Q.png" /><figcaption>A sample of the scene in Zoom, as Redgate came together for Level Up Week</figcaption></figure><p>However, the conference schedule and participation was still skewed towards the majority of Redgaters based in the UK — so we could have done more to make it easier for international folks to engage. We hope to improve this next time by involving our global offices more deeply in the preparation of the week and rethinking our scheduling.</p><p><strong>3. We said we could record everything to allow people to catch-up at a time that works best for them.</strong></p><p>During the week we were indeed able to add sessions to a library of content within hours of the live presentation and people often watched sessions within a day or two of them being broadcast. We even have Redgaters who have joined the company since the event watch and get value from the recorded sessions on Microsoft Stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*JZt2m_4b5HQUYRH_c3S3UA.png" /><figcaption>Our Level Up Week Stream channel, bursting with Redgaters sharing their skills and ideas</figcaption></figure><p><strong>4. We said we could provide something to suit a wider variety of learning styles</strong></p><p>Our programme had 30-minute presentations, collections of 8-minute long Lightning Talks, 2.5 hour in-depth workshops, group panel sessions, networking and social events and, of course, the aforementioned recordings of everything for consumption on-demand.</p><p>All these session styles garnered positive feedback as people selected the type of session that suited their learning style, the busyness of their day or how they were feeling. For instance, some people really loved the networking event but many passed on something that interactive, favouring to catch-up on a talk recorded earlier in the day. I think most people found something that worked well for them, which was the aim.</p><p>Here’s a peek at the overall schedule (captured after the event, so showing links to recordings and slides):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*k92QdBgiUjpYFaH8E022Ww.png" /></figure><p><strong>5. We said we could bring Redgaters together at a time when we really needed it</strong></p><p>One of the most surprising things about Level Up Week, for me at least, was the palpable sense of reconnection with the wider company and our more distant colleagues. I can’t explain how lovely it was to log into the first session of the event, and scan across the pages and pages of Redgaters, smiling and ready to take part in Level Up Week together.</p><p>Our approach connected individuals from across the company. One attendee told me that in the past when they have attended a physical conference they spent their time outside sessions chatting with people they work with every day, but during our virtual event they interacted with people from across the company in the Level Up Week Slack channel and our interactive sessions.</p><p>Had we cancelled our company conference, and not challenged ourselves to do something virtually, we’d have missed that opportunity to help each other feel part of something bigger and help folks when they really needed a boost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYRktP3ezPnSOjEMZgDnag.png" /><figcaption>Together again!</figcaption></figure><h4>Was it actually worth it?</h4><p>As I’ve just explained, there were plenty of good signs that things went well during the week. There was a great buzz in the company’s communication channels, the logistics of the event were smooth and the sessions were well presented. But the Level Up Week organising team and I really wanted to understand if the event had had the impact we wanted — that we had encouraged people to invest in their learning &amp; personal development, both during the week and afterwards. The event took a lot of time and effort to prepare and deliver — by the organising team, our speakers, our IT team and many others across the company, not to mention the 275 people who attended at least one session live. It was important we understood if that effort was well directed.</p><p>To do that we surveyed our attendees and revisited the objectives we drew up in February 2020. This is a long post already, so if you want to find out whether Level Up Week actually delivered the outcomes we wanted, then take a look at my follow-up post — <a href="https://medium.com/ingeniouslysimple/what-was-the-impact-of-level-up-week-2020-ade1f3728d82">What was the impact of Level Up Week 2020?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1fcd6eec95a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/level-up-week-2020-how-we-evolved-our-internal-tech-conference-for-our-remote-first-world-e1fcd6eec95a">Level Up Week 2020: How we evolved our internal tech conference for our remote-first world</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Development Reteaming at Redgate]]></title>
            <link>https://medium.com/ingeniouslysimple/product-development-reteaming-at-redgate-b094e71b45e6?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/b094e71b45e6</guid>
            <category><![CDATA[reteaming]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Fri, 20 Nov 2020 17:57:22 GMT</pubDate>
            <atom:updated>2020-11-26T09:49:25.987Z</atom:updated>
            <content:encoded><![CDATA[<p>In January 2021 Redgate’s product development organisation will undertake a “reteaming” process to reconfigure how our teams are assigned to reflect the company’s strategy for 2021. Our approach to these team changes will allow people to strongly influence where in the new team structure they will work, encouraging them to move towards the work they find most engaging.</p><p>We’ve applied a team self-selection process for the last two years in preparation for changes to development team assignments in <a href="https://medium.com/ingeniouslysimple/how-redgate-ran-its-first-team-self-selection-process-4bfac721ae2">2019</a> and 2020. Overall, the process has garnered good feedback from team members, team leaders and divisional leadership. Although we are still able to flex our team structure part way through the year, our reteaming in January has in the main successfully shaped how are teams are organised for the following 12 months.</p><p>At the start of this year, our 2020 reteaming process resulted in everyone in the division sitting in their new teams and working in service of our 2020 product strategies by 27th January. 34% of people in the division moved teams or roles, with almost every team having team members leave or new team members join. 97% of people in the division ended up in a team they expressed a first or second preference for and 83% were in a team that was their first preference. Our new or significantly changed teams all hit the ground running; they gelled quickly, new missions were enacted, and valuable software delivered to our users without missing a beat. A testament to the attitude and engagement of everyone involved in the process.</p><p>This week I have given everyone in Product Development a heads-up that we’ll be running a reteaming process again in January 2021. We’ll be taking a similar approach, but this time we’ll be doing everything remotely (more on that later). There’s no need for any of our people to do anything just yet, but we’re giving them a heads-up so they can wrap their heads around what is coming. We’ll explicitly kick off the process when we have enough information from our strategy and planning process to be able to create 2021 team charters for our development teams. A Team Charter is a document that defines a team’s purpose, what they are responsible for and what we expect work to be like in the team — you can see the template for our charters, below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oj8-pmY7GY8OmSNAdSxTgA.png" /><figcaption>The Team Charter template from our reteaming in January 2020</figcaption></figure><p>We won’t have all this information for our teams in 2021 until nearer the end of this year. In the meantime, Redgaters may want to chat with their line manager in the coming weeks to explore their personal development aims in preparation for reteaming. At Redgate, we have a large portfolio of products, written in a variety of languages, structured in a variety of ways and that exist at various stages of the product life cycle. That’s a lot of variety, and people may favour some combinations over others. They may also see a change of combinations, moving to work in an area that is brand new to them, as an opportunity for personal growth. It’s also entirely reasonable for them to decide they want to stay in their current team and, in fact, we’ll need many people to do that in order to provide continuous support and delivery of our existing products and solutions.</p><h4>Why we use a self-selection style “reteaming” technique</h4><p>It is significantly more effort for us to create the environment, share the information and manage the process that allows people to have a strong influence over which team they work in. However, we gladly invest that time and effort because we believe doing so aligns with our principle that people will be most engaged and motivated in their work if they have <a href="https://en.wikipedia.org/wiki/Drive:_The_Surprising_Truth_About_What_Motivates_Us">autonomy, mastery and purpose</a>. In the case of reteaming that means autonomy over what work they do, the space to gain mastery or develop their skills and to work in service of a clear purpose they understand and believe in.</p><p>We have also found that deliberate reteaming spreads knowledge, best practice and innovation throughout our teams, as people joining a new team bring techniques, skills and insights from their previous team with them. It also spreads social connections throughout the organisation and helps break down team silos. While there is theoretically a hit to team efficacy and cohesion when team members change, we’ve found that by improving our reteaming techniques and setting reasonable expectations of handover, if there is a hit at all it is very short-term. Put simply, we’ve found the benefits to teams outweigh the drawbacks.</p><p>We have seen that moves can also enable people to level up and encourage personal development. In the last two years, many Redgaters have moved teams to place themselves where they can gain new skills and build their capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnt6DZ2V4KkIbkE0AzcxGA.jpeg" /><figcaption>The excellent Dynamic Reteaming (2nd Edition) by Heidi Helfand. Now with extra Redgate!</figcaption></figure><p>Furthermore, self-selection reteaming is championed by leading figures in the software development community, like Dan North and <a href="https://medium.com/u/317014acd998">Heidi Helfand</a>. This collaborative, team member-driven approach to building teams is an increasingly common characteristic of high performing software development organisations. In fact, earlier this year, we were very pleased to learn that Redgate and our approach to reteaming was featured in the 2nd edition of Heidi’s book, <a href="https://www.amazon.co.uk/dp/1492061298/ref=cm_sw_r_tw_dp_x_n7QSFbWHEPC4S">Dynamic Reteaming</a>. In the book we are recognised as a progressive organisation and that we’re doing self-selection reteaming as well as anyone else in the industry right now. Which is something we are pretty proud of.</p><h4>How reteaming at Redgate works</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXdB8cpqeUcgV3BvdjZW6w.png" /><figcaption>Our reteaming process (with a break for Christmas holidays)</figcaption></figure><p>Our approach to reteaming in January 2021 will be broadly the same as it was last time. We’ll:</p><ul><li>Share the overall 2021 plans for product development, including where each team’s purpose will remain the same and where it will change</li><li>Confirm leadership roles around our teams first (many of which will not change from 2020 teams)</li><li>Build team charters to define what life will be like in each team in 2021</li><li>Run an open session for people to explore team charters, chat to product leadership groups and explore their options in depth</li><li>Gather individual’s preferences for which team they would like to be part of in 2021</li><li>Assemble a team structure that meets as many people’s preferences as possible while ensuring we have teams that can meet the needs of product strategies</li><li>Organise new team member start dates and handover with an aim for new team structure to be in place by late January 2021</li><li>Facilitate team-building activities to help new groups form</li></ul><p>As before, we’ll be looking to balance people’s individual preferences with the needs of the development teams and Redgate. We’ll ask people to tell us their first and second preferences for their team and the reasoning behind those preferences, but we won’t be able to make guarantees we can meet those as we’ll need to take a step back to see how people’s preferences line up with the big picture we needed to support. For the last two years around a third of people moved teams and I’m sure we will be able to support that level of movement again in the New Year.</p><p>Throughout, we’ll endeavour to be open and transparent about the process and highly considerate of people’s preference and concerns. My development managers team and I make ourselves available at any time during the process to chat with people one-on-one about reteaming and their preferences.</p><h4>What we’ll do differently this time</h4><p>This time all activities for reteaming will take place virtually. Regardless of national lockdown measures, no one will need to come into the office to take part in the reteaming process. Overall strategy presentations will be streamed, Team Charters will be created electronically (I’m looking at you, <a href="https://www.mural.co/">Mural</a>), the collaborate open session will be hosted online (checkout <a href="https://spatial.chat/">SpatialChat </a>for a tool that can help with these kind of events) and we’ll be supporting individuals to consider their team options via one-on-one Zoom calls.</p><h4>Want to know more?</h4><p>There are a couple of blog posts available that describe our first reteaming process in detail, explaining in more detail why we wanted to run a self-selection process and how we did it. They may be of particular interest to leaders keen to increase the transparency of their team changes processes and give people more influence over what they work on:</p><ul><li><a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">Team self-selection (without the anxiety)</a></li><li><a href="https://medium.com/ingeniouslysimple/how-redgate-ran-its-first-team-self-selection-process-4bfac721ae2">How Redgate ran its first team self-selection process</a></li></ul><p>If anyone has any comments or questions, please do reach out and let me know at <a href="/service/mailto:chris.smith@red-gate.com">chris.smith@red-gate.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b094e71b45e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/product-development-reteaming-at-redgate-b094e71b45e6">Product Development Reteaming at Redgate</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wellbeing and cohesion hacks from our newly remote teams]]></title>
            <link>https://medium.com/ingeniouslysimple/wellbeing-and-cohesion-hacks-from-our-newly-remote-teams-fbc4b1a04eba?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbc4b1a04eba</guid>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cohesion]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 12:14:09 GMT</pubDate>
            <atom:updated>2020-04-28T12:15:48.515Z</atom:updated>
            <content:encoded><![CDATA[<p>During social distancing measures, with all our teams working remotely and with differing work patterns, we should be especially attentive to the wellbeing of our teammates and how we collaborate with each other. Last week I got together with a group of our engineers, designers and technical leads to explore what practices and behaviours were making a difference in their teams, as they look to nurture wellbeing and stay connected &amp; collaborating with their teammates.</p><p>We ran a simple virtual post-it sharing session using the online collaboration tool <a href="https://www.mural.co/">Mural </a>(there’s your first tip — Mural is excellent!) and here’s a picture of what we came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8RF4dbcAnUeEbOcUduyPQ.png" /><figcaption>The output of our collaborative session sharing team wellbeing and cohesion hacks</figcaption></figure><p>These are the ideas, hacks and practices that are helping our twelve development teams, right now. Some are tailored to the needs of a specific team (some teams may not feel the need for virtual beers or always-on video calls), but many are useful for any team hoping to look after each other and coordinate during these strange times.</p><p>I thought I’d call out a couple of the key lessons taken from the session:</p><p><strong>Use stand-ups for team connectedness</strong><br>Morning “stand-up” meetings (where, I imagine, no one actually stands up anymore) have become even more vital for team connectedness than they are for coordination and progress sharing. Our teams have reshaped those synchronisation points to include more informal chat, raise wellbeing concerns or segue into some retrospection (or gaming sessions).</p><p><strong>Talk about how you are</strong><br>Several of our teams (including my team of development managers) are finding a daily wellbeing traffic light status check encourages us to openly share how we are feeling and making it <em>ok to say we are not ok</em>. Once we know how our teammates are feeling, we can offer help &amp; support, or simply show more empathy for how they are feeling. But we have to know how they feel first — hence the explicit check. Our DB DevOps team discovered that idea from <a href="https://open.buffer.com/mental-health-at-work/">this blog post</a> (under the title “5. We Communicate Vulnerably”) and the practice has spread naturally through development.</p><p><strong>Model self-care</strong><br>Team members are setting an example by being open about their availability for work (for instance, sharing on Slack that they have to look after the kids during part of a given day), going out for their daily exercise or playing a game. We could hide these things if we were worried about receiving criticism, or even punishment, for taking time during core hours for these vital activities. But I’m so pleased to hear we’re not hiding that stuff and instead sharing openly. Hopefully, this openness will make it safe for others to do the same.</p><p>The Development Managers team have taken this a step further by creating a weekly Wellbeing Challenge. We’ve drawn up a list of activities that provide a boost to wellbeing, from going for a 15 minute walk to rearranging a Zoom meeting so it does not run back-to-back with another! All these activities are awarded wellbeing points, and we celebrate on Mondays who has topped the rankings for the previous week. You can see the latest leaderboard <a href="http://keepthescore.co/board/pgalptudzbr/">here</a>!</p><p><strong>Keep up the collaboration through online tooling</strong><br>Our developments teams are big on pair programming and, in recent years, mob programming to build our software collaboratively and, well, better. Remote working has not put a stop to all that. In fact it’s become even more important to keep technical work in the team’s collective consciousness. Our teams are using standard video conferencing software like Zoom, plus dedicated tooling like <a href="http://mobster.cc/">Mobster</a>.</p><p>For collaboration and ideation, we’re making a heavy use of online tools like <a href="https://www.mural.co/">Mural</a>, <a href="https://miro.com/index/">Miro </a>and countless others (I hear a new one mentioned every day)! All these are working well, and using them has the valuable side effect that they produce human-readable and easily shareable records of the discussions they have supported (like the one at the top of this post!).</p><p><strong>Say “hello” and “goodbye” to mark your workday</strong><br>Many team members are being explicit about the times they are available for work during the day, updating Outlook and Slack availability to reflect this. This makes expectations clearer and the task of booking any team meetings that little bit easier.</p><p>Another valuable practice called out was team members adding a “good morning” note on their team’s Slack channel at the start of the day and a corresponding “goodbye” at the end of the day. This helps eliminate the grey area between home and work time, but also reminds people that they are working with a community of people who <em>notice</em> when they are around. Also, people get to use their favourite silly gifs to brighten the mood first thing in the morning. <a href="https://gph.is/g/4V66Q0g">Here’s one of mine</a>.</p><p><strong>Be a team that plays together, to stay together</strong><br>Social gaming is popular and valuable in technical teams, providing some light relief and informal connection during the day. The <a href="https://www.jackboxgames.com/party-pack/">Jackbox Party Pack </a>games, easily able to support remote groups via Zoom, were widely appreciated (Ben Wood wrote a <a href="https://medium.com/ingeniouslysimple/making-working-from-home-just-that-little-bit-better-c1e071703076">great post on those games</a> last month), as were free online drawing games like <a href="https://skribbl.io/">Skribbl </a>and <a href="https://www.drawasaurus.org/">Drawasaurus</a>. But there are a wide range of games in use, tailored to the norms and gaming experience of the team. Redgate made the call early on during lockdown to make funds available to teams to purchase games for this very purpose, and I think we can see that this was a valuable investment.</p><p>These are just a few of the ideas and innovations that people are applying to make sure our teams are supportive and healthy communities, putting themselves in the position to do effective and valuable work for our customers. If, over the coming weeks, your team discovers a new hack then please do share it. We’d love to hear about it in the comments on this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbc4b1a04eba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/wellbeing-and-cohesion-hacks-from-our-newly-remote-teams-fbc4b1a04eba">Wellbeing and cohesion hacks from our newly remote teams</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forget dumb productivity measures & focus on software delivery performance with Four Key Metrics]]></title>
            <link>https://medium.com/ingeniouslysimple/forget-dumb-productivity-measures-focus-on-software-delivery-performance-with-the-four-key-3ad0e045e5b8?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ad0e045e5b8</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[accelerate]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Wed, 08 Apr 2020 15:28:57 GMT</pubDate>
            <atom:updated>2021-08-27T08:54:20.500Z</atom:updated>
            <content:encoded><![CDATA[<h3>Forget dumb productivity measures and focus on software delivery performance with Accelerate’s Four Key Metrics</h3><p>The book <a href="https://www.amazon.co.uk/dp/1942788339/ref=cm_sw_r_tw_dp_U_x_gaFmDbPZ0XMA7"><em>Accelerate — The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations</em></a><em> by Nicole Forsgren PhD, Jez Humble and Gene Kim </em>has been really important for Redgate over the past 12 months. It’s helped us find a software delivery terminology that teams and the wider company understand and buy into, and allowed us to compare how we’re performing against the best in the business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9nMIvBLRuH6N0nx4-ZPgQ.jpeg" /><figcaption><em>Accelerate — The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations</em></figcaption></figure><p>Over the years my fellow Redgaters and I have become resistant to “productivity” measures like velocity, lines of code, code coverage and time spent on tasks, and related techniques like story points and time estimates. We’ve used practices like that in the past but have found their usefulness is outweighed by their drawbacks. Those metrics have been used to give teams (and the company) a false sense of certainty or been unconsciously used to measure the performance of teams and individuals. Therefore, before <em>Accelerate</em> some Redgate development teams settled on using cycle or flow time to gauge how well they were delivering. And some teams didn’t use a measure for this at all, focussing squarely on outcome metrics instead — like feature usage. We never felt either approach provided the full picture of software delivery performance, though. For a start, it ignored quality and stability.</p><p>Then about a year ago <a href="https://medium.com/u/b443ec63ce29">Jeff Foster</a>, Redgate’s Head of Product Engineering, discovered <em>Accelerate</em> and shoved a copy into my hands. We both immediately saw the importance of the <em>Four Key Software Delivery Metrics</em> it champions and how they could help move the organisation in a positive direction.</p><p>To kick off that initiative we really pushed to engage the dev organisation with the content of book in the hope people saw this positively rather than as a suspicious measurement activity by management. We ran a book club, talked about the underlying State of DevOps report and called out the positive methodologies &amp; cultural characteristics the results supported. People seemed to ‘get it’. In fact, they were impatient to get started.</p><p>As a result of the lessons in the book, we’ve implemented the Four Key Metrics across all our product development teams. Thanks to the tenacity and skills of <a href="https://medium.com/u/edd7ee127ad6">Gareth Bragg</a>, one of Redgate’s Technical Coaches, each team has clear graphs available to track the measures. From there our Development Managers provided a little encouragement to get all the teams to put the graphs up on each team’s large dashboard screens and referenced in day-to-day work. You can see an example below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnL4lBAQEIuJTaJ98oX4TQ.png" /><figcaption>A dashboard showing the Four Key Metrics for one of our products</figcaption></figure><p>I thought we’d have to nudge much more to see improvement in the measures but, it turns out, as our teams already have a principle of continuous improvement and are really keen to do great work, they have naturally taken action to push the accelerate metrics in the right direction. Sure, sometimes Development Managers have had to do a little coaching and introduce some agile/lean techniques to inexperienced teams, and you can see the results of one of those engagements in the above image (down and to the right on the graphs is great). But in most cases the teams have driven improvements themselves. I guess it’s the old <a href="https://en.wikipedia.org/wiki/Peter_Drucker">Peter Drucker</a> adage; what gets measured, gets done!</p><p>In addition to the benefits for teams, I’ve found that the metrics have finally given the development organisation a language to describe the performance of our software delivery engine to the wider business in terms we are all comfortable with…</p><p>In development we don’t have the impactful commercial measures of revenue, invoices raised or leads that our friends in Sales and Marketing can report on. Other product-focussed measures like active users, retention and churn are affected by forces outside of the influence of the development teams. Previously we might have had to rely on reporting the number of releases we had shipped or deadlines we’d met, both fairly numbskulled measures of productivity that ignore (at least) three maxims of agile product development:</p><ol><li>Focus on outcomes not output,</li><li>Maximise the amount of work not done,</li><li>Learn fast, learn often.</li></ol><p>All of these are underpinned by one key idea; that you don’t really know, for certain, what is going to be a success in your product. You might have a really good idea that your new feature will be well received by users, you might have a super smart Product Manager who bets her reputation on it working in the market or you might have an insightful Sales organisation telling you exactly what customers are asking for. You might have all that, but you don’t have absolute certainty. You don’t know that what you build is going to work for people. You might have misread the market, mis-implemented the feature or mistaken a user <em>want</em> for a user <em>need</em>. You might have done nothing wrong at all, and still nobody buys the thing you made.</p><p>To channel <a href="https://en.wikipedia.org/wiki/Cynefin_framework">Cynefin</a>, your users, product, market and the wider economic environment are a complex system, not a complicated one. It is unpredictable. Unknowable. If you accept that then you’ll realise your strategy should be to take an experimental approach — to <em>probe, sense and respond </em>as Cynefin would put it<em> — </em>and that productivity measures are folly. Measuring the output of your plans, releases and deadlines, no matter how carefully created, would be pretending the problem you have is a predictable one and your predictions were 100% “right” from the start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n7K6VyxlFS0cEieiWK6Nbg.png" /><figcaption>Learn fast, learn often</figcaption></figure><p>We now measure and report to the business on the Four Key Metrics; Lead Time — how long it takes for use to get something done &amp; released so we can learn from it, Deployment Frequency — how often we deliver something to our users, Change Failure Rate — how often we break something where users lose the ability to use our product, and Mean Time To Restore Service — how quickly we restore users’ ability to use the product. Aside from the obvious benefits of improving the performance of the organisation in these areas, thanks to the State of DevOps Report, we can also compare ourselves to other software organisations, sharing where were are in the Elite — High — Mid — Low performer spectrum. Equipped with that understanding we can drive further improvements.</p><h4>Further information</h4><p>As I mentioned before, <a href="https://medium.com/u/edd7ee127ad6">Gareth Bragg</a> played a big part in getting these metrics measured and embedded in our teams. If you’d like to know about our first lessons from the metrics and how actually we track them in our teams, he’s written a couple of great blog posts below:</p><ul><li><a href="https://medium.com/ingeniouslysimple/learning-from-the-accelerate-four-key-metrics-91725675e30a">Learning from the Accelerate “Four Key Metrics”</a></li><li><a href="https://medium.com/ingeniouslysimple/sharing-our-approach-to-tracking-the-accelerate-four-key-metrics-bbb1a615d7bb">Sharing our approach to tracking the Accelerate “Four Key Metrics”</a></li></ul><p>You should obviously read the book, if you have not already, and check out the <a href="https://cloud.google.com/devops/state-of-devops/">2019 State of DevOps Report</a> itself.</p><p>If you have any more questions about Accelerate, the Four Key Measures or how we use them at Redgate, give me a shout at chris.smith@red-gate.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad0e045e5b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/forget-dumb-productivity-measures-focus-on-software-delivery-performance-with-the-four-key-3ad0e045e5b8">Forget dumb productivity measures &amp; focus on software delivery performance with Four Key Metrics</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Redgate ran it’s first team self-selection process]]></title>
            <link>https://medium.com/ingeniouslysimple/how-redgate-ran-its-first-team-self-selection-process-4bfac721ae2?source=rss-371191894233------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bfac721ae2</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[reteaming]]></category>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[self-selection]]></category>
            <dc:creator><![CDATA[Chris Smith]]></dc:creator>
            <pubDate>Sun, 22 Sep 2019 13:01:01 GMT</pubDate>
            <atom:updated>2019-10-23T13:58:08.196Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Redgate ran its first team self-selection process</h3><p>In <a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">my previous post</a> I explained why, at the end of 2018, Redgate wanted to give people a strong influence over what team they worked on, our concerns about short team self-selection events and how we decided to approach the idea. I also covered what feedback we received immediately after the changes and reflected on the results nine months later.</p><p>This post explains in much more detail exactly how we that first formal team self-selection process, in the hope someone outside the company might find it useful.</p><h4>A recap of the changes we wanted to make to our team structure</h4><p>Our aim was to keep to the principles of self-determination but to try to make it as fair and low-pressure for everyone. As a function of the process we were looking to make the following changes to the shape and remit of our eleven product development teams:</p><ul><li>Change the responsibilities of a number of our teams,</li><li>Create one brand new team and disband another,</li><li>Explore some new product areas,</li><li>Group teams by life cycle stage and reset expectations as a result.</li></ul><p>This was a complex change to undertake, but one that was important for Redgate’s plans for 2019 and one that would correspondingly create many new personal development opportunities for our people to take on.</p><p>So, here’s exactly how we did it:</p><h4>1. We explained the big picture to team leadership roles, including the reasoning behind the changes.</h4><p>At the very start of the process, we (the development organisation’s leadership team) gathered people responsible for leading our teams (our Technical Leads, Product Designers and Product Managers) together to share our ideas. We wanted their help to shape and improve our plans and then join us in rolling out the changes more widely.</p><p>We presented the changing needs of the business in 2019 and outlined our ideas for grouping teams by life cycle stage. We were careful to explain the reasons behind these changes — the all important Why — and made a commitment to get their feedback on what we’d presented. We also shared the high-level plan for the process (see below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YaVz-tAVCu2F3NSB" /><figcaption>Our timetable for the process</figcaption></figure><h4>2. We engaged leaders in shaping the plans, getting their advice on how to improve our ideas and the next steps.</h4><p>Following the presentation we ran a workshop (centred around Liberating Structures’s <a href="http://www.liberatingstructures.com/18-users-experience-fishbowl/">Fishbowl</a> activity, facilitation fans) with the team leaders to answer their many questions and gather their feedback on what they had heard. That feedback was absolutely vital in helping us improve our plans, removing some elements of the team groupings that did not make sense, clarifying points around key concerns and reframing some of the messaging behind decisions.</p><p>What was clear at this point was that the leaders had just as much anxiety about where they might work in the new setup as anyone else. So we needed to get that decided first.</p><h4>3. We got the leaders for each team in place in the new structure first.</h4><p>Having explored and helped improve our plans, we gave leaders a few days to mull over where they wanted to work themselves. In that time they had depth chats with their line managers and considered their options.</p><p>To be honest, given the importance we place on our lead roles, it would have been difficult for us to support a high number of them moving from their established teams and still ensure the organisation maintain knowledge in key areas. But giving them the option to ask for a move if they want to was the right thing to do and, as it turned out, most of them wanted to continue to work with the team they currently lead.</p><h4>4. We shared our plans, reasoning and expectations with everyone.</h4><p>We were then in a great position to clearly explain the changes and the process to everyone in product development. We had an all hands meeting where we stepped through the plans for 2019 and how we wanted people to have a strong influence over what they worked on in the new year.</p><p>The most important thing we did in the session was to be very clear about the timetable for the changes and what people could expect from the process. We provided an array of avenues for people to ask their (many) questions about the changes — they could talk to their now up-to-speed team leads, contact us on Slack/Email or attend a number of drop-in sessions with the development organisation’s leadership team. Our people made use of all of these, raising fair questions and concerns — most of which we were able to answer well because of the initial feedback phase we took with the team leaders.</p><h4>5. We asked leaders to provide more details on what life would be like in their teams in 2019.</h4><p>Broadly, the plan from here was for people to explore their options at an open session two days after the all hands meeting, where team leaders would be on hand to explain their mission, plans and the shape of the team they would need for 2019. This meant we needed the team leaders to really engage in the task of providing a vision and plan for their team and it’s work in the next year.</p><p>As a thinking and presentation tool, we drew up a Team Charter template (below). This encouraged leaders to think about the why the teams will exist, what they will own, what impact they are going to aim for, how they will do their work, and so on. Our team leaders spent time discussing and honing their charters ready to chat them through with prospective new team mates at the upcoming workshop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*yXKsTlalMHPM-QT0" /><figcaption>Our team charter template</figcaption></figure><h4>6. We ran an open session for people to explore their options in depth.</h4><p>Our team leaders then set-up in our largest collaborative space (our canteen, the brilliantly named “SQL Servery”) to run an open information sharing session, armed with their Team Charters and the narrative behind its content. We invited everyone in development to drop in and out of the session, challenging them to “explore what life will be like on your team and the other teams in 2019” and “consider whether you would prefer to stay with your team or you have a preference for a move to another team”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rZITYYgXLfjumlOecYEDgg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kr_RoMIqyvi2DNGPW6ouVw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9Az2peON2yyfGe_KzQ16w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REQvqXZV6BDq7rL03vohkQ.jpeg" /><figcaption>The open session for people to explore our 2019 team charters and chat to team leaders</figcaption></figure><p>The session was a great success thanks to our brilliant team leaders and the engagement and professionalism of the entire development organisation. People explored the charters carefully and formed a clearer picture of what might be motivational for them.</p><h4>7. We provided coaching and support for people 1-on-1 to help them explore options and decide.</h4><p>Gathering all that information at the open session was invaluable, but the key step was to derive insight and preferences from it. We needed to help people answer questions about what kind of work they wanted to do? Whether they were best placed learning about this tech or that? Which team will give them the opportunities they need to progress their career aspirations. It is these deeply personal questions that can be missed or go unanswered during a “shut everyone in a room and only let them out when the new teams are decided” team self-selection approach.</p><p>Instead, we took a collective step back following the team charters workshop and made sure every single person in our development teams had a one-on-one session with their manager or leadership person to explore their thoughts and aims. That was a big time investment for our leaders, but it was worth every second.</p><h4>8. We asked for team preferences and reasoning, but made no promises.</h4><p>To draw that exploration to a close, we asked everyone to communicate their thoughts about where they’d like to work. We requested the following information:</p><ul><li>Their first preference for their team for 2019. This could be a preference to stay with their current team.</li><li>Their second preference for their team for 2019. This could not be the same as their first preference.</li><li>The reasons behind those preferences — “The Why”.</li></ul><p>Throughout this process we were keen to emphasise to everyone that, although we would do our best, we could not make guarantees to meet people’s preferences. We needed to balance what was best for individuals, our teams and Redgate. It would be brilliant if we could give everyone their first preference, but it was improbable that everything would land that way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1UU1b7DDpkdXGOO_E9anMg.jpeg" /></figure><p>An explanation of the “Why” behind people’s preferences was perhaps the most important thing we asked for from our people. We heard that people wanted to move for a variety of reasons, such as getting to grips with web technologies, working on a product earlier in its lifecycle or doing something new after many years working in the same area. Those key insights helped us see where we could create options, ensuring people had their needs met but in ways they had not envisaged.</p><h4>9. We took a step back to see if we were close to what we needed.</h4><p>At this point, my team of development managers and I then had so see how people’s preferences lined up with the big picture. So, we set up camp in a meeting room, drew the final shape of the organisation up on a whiteboard wall, represented people’s preferences with post-it notes, and started to piece together the puzzle. We had a single <em>Elephant in the Room</em> question to answer — was this actually going to work?</p><p>And guess what? It did work! But it was <em>tricky</em>.</p><p>To make what I think is a key aspect of this success clear, our development teams are purposefully constrained to be a consistent size and shape — one technical lead, five developers and a designer. We could flex that a little, but only by +/- one developer. Furthermore, part of each team’s chartering process was to call out the balance of skills and experience they ideally needed in the team, such as “at least two people with prior web dev experience” or “three people who have worked on SQL Monitor before”. I think it was these constraints around the final picture that meant we understood what the solved puzzle should look like and allowed us to make best use of people’s first and second preferences to shape our answer.</p><p>Unsurprisingly, once we had assembled a picture using everyone’s first preferences, we had a few significantly over-populated teams and a few under-populated. We were then able to use second preferences, coupled with each person’s Why behind their preferences, to almost entirely complete the puzzle!</p><p>There were, of course, a couple of people for whom we could not juggle things in order to accommodate their preferences. However, we were able to examine the reasoning behind their preferences to identify another team option that might be a good fit for them. As with the best puzzles, creating those options necessitated knock-on changes — such as the odd person having to fall back to their second preference.</p><p>I have no doubt this step was key to the success of the process, but I do recognise this stage looks most like the “managers go into a locked room and decide <em>all the things</em>” approach we were keen to avoid. I can only assure the reader that we did this objectively, carefully considering the bigger picture but with our duty of service to the people in the organisation always in mind.</p><h4>10. We validated the new structure with team leaders and worked with people that did not get their preferred team.</h4><p>Once we had a solution to the puzzle we went back to the leaders of the teams to give them a chance to influence and commit to the shape of the team they were inheriting from the process. I’m pleased to say that the proposed teams met with universal approval. I think this was primarily down to conversations had at the open charter session and everyone’s confidence that each team was populated with people who were clearly motivated to take on their upcoming work.</p><p>We went back to talk, one on one, with everyone that had not got their first preference. This was a relatively small group of people. We took special care to talk in detail to people for whom we had not been able to meet either of their preferences, instead relying on their “Why”. While not exactly happy with the outcome, I am thankful that those folks agreed to give the teams we suggested a try (and I can say now, over 9 months down the line, that those teams have proved to be a great fit). It’s worth calling out that it was just two people in that situation — moving to a team they had not identified as a preference — out of a development organisation of ~75 people.</p><p>After all these discussions, the solution to the great team puzzle was agreed and everyone knew where they were going to be working at the start of 2019.</p><h4>11. We made the team moves happen, ensuring teams were set up to start well.</h4><p>The final step was to make those team moves happen. All at pretty much the same time, ready for a new start on the first week back at work after our Christmas break. And then to ensure that all those new and changed teams were able to hit the ground running, nurturing a healthy team culture and embarking on their new missions.</p><p>The answer to this was simple. Set the target that we wanted the new teams to be in place on January 2nd 2019, empower the team leaders to organise who in their new teams can move when (and to treat the target date pragmatically, if they needed to) and provide a set of common team building and direction setting tools that the teams could all make use of to set themselves up for success.</p><h4>Happy New Year</h4><p>By the end of our team self-selection process over 33% of people in the development organisation had moved teams, with every team having had team members leave or new team members join. We had teams working on three new product areas, reduced investment in a couple of other areas and refreshed the mission for every single group. We achieved this change in 20 working days (excluding the days between Christmas and New Year, when most people were out the office), from initial sharing of the plan to people literally sat in their new teams on 2nd January 2019.</p><p>If you want to find out more about how people in the teams found the process or whether the resultant teams were healthy, <a href="https://medium.com/ingeniouslysimple/team-self-selection-without-the-anxiety-be5a1478c484">check out my previous post</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bfac721ae2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ingeniouslysimple/how-redgate-ran-its-first-team-self-selection-process-4bfac721ae2">How Redgate ran it’s first team self-selection process</a> was originally published in <a href="https://medium.com/ingeniouslysimple">Ingeniously Simple</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>