<?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 Kuldeep Salhan on Medium]]></title>
        <description><![CDATA[Stories by Kuldeep Salhan on Medium]]></description>
        <link>https://medium.com/@kuldeepsalhan_48955?source=rss-6ddd4102d8a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Kuldeep Salhan on Medium</title>
            <link>https://medium.com/@kuldeepsalhan_48955?source=rss-6ddd4102d8a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:30:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kuldeepsalhan_48955/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[Why do you need to run a workshop?]]></title>
            <link>https://medium.com/@kuldeepsalhan_48955/why-do-you-need-to-run-a-workshop-2ddaa4db1cf8?source=rss-6ddd4102d8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ddaa4db1cf8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[workshop]]></category>
            <dc:creator><![CDATA[Kuldeep Salhan]]></dc:creator>
            <pubDate>Fri, 01 May 2020 15:11:53 GMT</pubDate>
            <atom:updated>2020-05-01T15:11:53.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jQhtNNymxiA0H_SUsBpT-Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@halgatewood?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hal Gatewood</a> on <a href="https://unsplash.com/s/photos/prototype?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Workshops are very valuable and there are great reads on methods to run them. What I want to discuss here is the thinking and work that leads you to deciding on running one. Working across the product teams, the following are learnings /points to consider from the Farfetch Practice team…</p><ol><li><strong>What’s driving the need?</strong><br>- A need to accelerate or bypass an existing process<br>- To generate ideas more quickly to populate a backlog<br>- Alignment / creating a common understanding of an initiative<br>- Closer collaboration with engineers<br>Reflect on the current processes in your team which aren’t meeting this need</li><li><strong>Let’s do a workshop?</strong> Not everything needs to be a workshop.<br>- Workshops are expensive in getting lots of people together for +1 day, so <strong>be clear on return on value</strong><br>- How are you measuring success and the outcomes?<br>- Tracking the hours spent in pre-work and people involved to make them happen makes the investment in time more visible <br>👉 <a href="https://docs.google.com/spreadsheets/d/1jutECORACoSL_l7k5JPWIbt4qILEY3JSRRZopKqRLtk/edit?usp=sharing"><strong>Workshop tracker template</strong></a> 👈 by <a href="https://medium.com/@Pangramas">Pedro Sanjoa</a><br>- Would you arrive at the same answer through just working in your team in a concentrated/different way?<br>- Consider the wealth of previous workshops — are you covering old ground? The insights and ideas could be waiting for you</li><li><strong>Move from calling everything a ‘workshop’.</strong> What is a better term to use to describe the activity…<br>- Pre kick off/ kick off<br>- Stakeholder/Alignment<br>- Prioritisation<br>- Design sprint/exploration<br>- Spikes</li><li><strong>Structuring the activities</strong><br>- Not everything has to be fitted within the workshop day<br>- Think about having focussed activity on what matters in the workshop and think about what can be done ahead of time ie pre-reads/work<br>- Again, workshops are expensive, so does it really help getting heads and directors sketching? What do you need these groups to answer?<br>- You don’t have to follow text book activities — learn from the team around you. What has been the most effective activity for ‘x’ problem<br>- Ensure you have the right people in the room. Based on the problem and the area you are covering, its vital to connect the right people together to move things forward later</li></ol><p>It’s important to connect your ideation/exploration to your strategy — what are you trying to achieve and are the opportunities already there, either past or present. Make visible the time taken in workshop and view it as currency/a cost. Reflect on the value the outcomes may drive before getting the post-its and sharpies out =)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ddaa4db1cf8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus tactics]]></title>
            <link>https://medium.com/@kuldeepsalhan_48955/focus-tactics-1a1d0aad400b?source=rss-6ddd4102d8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a1d0aad400b</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Kuldeep Salhan]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 11:02:25 GMT</pubDate>
            <atom:updated>2020-04-24T11:43:31.782Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EA01CSvEzi6WagbYP4g_Qg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@yogidan2012?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniele Levis Pelusi</a> on <a href="https://unsplash.com/s/photos/confusion-abstract?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>During my time working with product teams at Farfetch, focus has been a topic which comes up a lot in conversations. In the current times, this has been amplified. The following are a few tactics which I have shared/learnt over time…</p><ol><li>Work with numbered lists rather than bullets<br>- You can only have one no1 priority. Force stack rank</li><li>What’s the highlight of the day and week<br>- Keep track of this. If you are not achieving your highlight on a regular basis then ask yourself why?<br>- It’s ok just to have one main thing to work on for a period of time. Spinning plates isn’t mandatory</li><li>Ensure you zoom out and understand the value you want to add in the day or week. What’s the key thing you need to be doing. It’s easy for this to get forgotten or pushed down in priority but refocus on your north star</li><li>Transparency and feedback loops are important. Use leadership to ensure you are moving in the right direction<br>- Its ok to course correct and let go things in order to focus on the <strong>right thing<br>- </strong>Who are the people that can give you this?</li><li>You drive your calendar. The calendar doesn’t drive you.<br>- Take ownership of it and ensure you have and make the time you need to do ‘x’. It’s an ongoing calibration of giving yourself the time in the right areas.</li><li>This might mean blocking out time but make this transparent to others in your calendar ie ‘No meetings or focus time’<br>- What’s the right % of time you need to block out to provide the focus you need?<br>- Share when you are and aren’t available. Set your own boundaries<br>- Reduce the time slot length when it makes sense to. Meetings don’t have to be 1hr by default<br>- Have clear agendas in meetings<br>- Use slack when it makes sense. Not everything needs a meeting</li><li>It’s ok to have a calendar which isn’t full. It’s not a tetris game</li><li>Think about where your time is going. Use the time thief and see where you are leaking time — assess this against your main goal. Are you investing in the right areas</li><li>What, So what, Now what<br>- There is a mirroring pattern in FF of seeing a problem and pointing to the problem and we loop around that. Ensure you have a <strong>now what. </strong>What’s the action or commitment?<br>- Getting stuff over the line is important. If you see this is not happening, reflect on why? Is the perceived value different to yours, what’s the blocker<br>- Circles and soup. What’s in your control, influence or out of your control? Where is your focus best placed?</li><li>Trust in others. You don’t have to be doing everything. Ensure you are building the muscle around you. You are creating superstars around you rather than being the superstar.<br>- Who is your successor? How can you be developing them and give yourself time to have more focus</li><li>Recognise the attention grabbers in your day ie slack, social notifications. what is pulling you away from your focus</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a1d0aad400b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sharing work at Farfetch]]></title>
            <link>https://medium.com/@kuldeepsalhan_48955/sharing-work-at-farfetch-5cc11738dd41?source=rss-6ddd4102d8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cc11738dd41</guid>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Kuldeep Salhan]]></dc:creator>
            <pubDate>Mon, 21 Oct 2019 16:23:47 GMT</pubDate>
            <atom:updated>2019-10-24T19:55:43.513Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8IlYMn8tmgBcQB3i0SfHg.png" /><figcaption>Credit <a href="https://www.linkedin.com/in/claraleandrofg/">Clara Leandro Fernandez Gil</a></figcaption></figure><p>The Practice team at Farfetch was set up at the start of 2019 to <strong>amplify </strong>and <strong>share</strong> practice across the consumer product teams. The focus being on <strong>how</strong> teams work. We look for <strong>leading indicators</strong> from the teams, signalling a need and then understanding if/how to support what’s not being served.</p><h4>The indicator</h4><p>There are many product teams at Farfetch with many rituals, where work is shared at a local level but nothing that cuts across the whole organisation and is global.</p><p>There was a growing need from exec, heads of product through to adjacent product teams, all wanting greater visibility on work in progress as well as what’s being shipped.</p><p>This lead us to set up <strong>Show and tell</strong> six months ago, as a platform for anyone (company wide) to share <strong>work in progress</strong>. Not a critique but a quick fire show of the work.</p><p>This is the journey we took and the learnings along the way…</p><h3><strong>How it works</strong></h3><h4>The format</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14IJMJpbtKxs6z5L6shHMw.jpeg" /><figcaption>Farfetch Porto office</figcaption></figure><ul><li>Fortnightly meeting</li><li>1 hour duration</li><li>10 slots</li><li>5 minutes per presenter</li><li>This is not a critique, so no questions from the room.</li><li>This is not a demo, its about sharing work in progress</li><li>It’s open for all — designers, PMs, engineers, marketing, data…</li></ul><h3><strong>Set up</strong></h3><p><strong>Map the future for your rituals</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdEDbE8QlssbNWB5EiBDGQ.png" /></figure><p>Map the existing rituals you have, the purpose, the value they drive and the audience. This will spotlight where there are overlaps and alignment with what already exists. <strong>You are adding a meeting — can you remove or combine existing ones?</strong></p><p>Think about the future rituals which support the sharing, feedback and learning culture you want to create. Create a roadmap and prioritise where to start. Start small — test &amp; learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91L5UgdkieCG4nUSCz7MQw.png" /></figure><p><strong>Run a Pilot</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSBR6vPUhhCxir_l4xqYlA.png" /></figure><p>Start with a one-off show and tell, with a smaller group. This is where you can get a sense of the right duration for the meeting and the number of slots you need — is the format working?</p><p>Run a survey to get feedback. Adapt based on the main emerging themes.</p><p>👉 Template: <a href="https://docs.google.com/forms/d/e/1FAIpQLSfMgA7cwtjECvSr7ovid6lxHnwXQavK36Cd0BW4krVmKzMhVA/viewform?usp=pp_url"><strong>Survey template</strong></a> 👈</p><p><strong>Choose a physical space<br></strong>Depending on the size of your team, pick an area in your office or room catered for large groups (shielded from office noise). Having it more visible to the general office helps promote the meeting to others. If not, try find a meeting room large enough to comfortably sit your audience size (as a recurring booking)</p><h3><strong>2 Weeks before</strong></h3><p><strong>Setting up the Slots for the meeting</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vIlZ1izHF60zBN7CbNYtGw.png" /></figure><p>👉 Template: <a href="https://docs.google.com/spreadsheets/d/1zYjPAN_w7u88_uF_w-NggEvs1imrp72BqYGBVBQe6cg/edit?usp=sharing"><strong>Running order</strong></a> 👈</p><ol><li>Set up a spreadsheet that teams can populate at the beginning of the 2 weeks.</li><li>Adding a tweet length description field helps to provide more context and a more meaningful running order for your audience to view</li><li>Device (PC laptop/Mac/Mobile) helps you understand what adaptors you will need on the day — you can always get caught out by that when setting up</li><li>Think about the running order. You may have presenters in different locations/time zones, so it will be easier to group them, to make handoff between locations less disruptive</li><li>Avoid having presenters from the same teams back to back</li><li>Have a closing date for the running order — 1 day before the day.</li></ol><p><strong>Presenter slides</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5oPux6b7aARwb_shvofbtw.png" /></figure><p>👉 Template: <a href="https://docs.google.com/presentation/d/1UI1vAZprqTuj5o2084wWXOwJQKXChsOzBySeEWs8Mwk/edit?usp=sharing"><strong>Presenter slides</strong></a> 👈</p><p>Get the presenters to complete the presenters slides prior to the day. This…</p><ol><li>Helps frame the subject they are presenting</li><li>Their name, role, team and the feature they are sharing helps the audience know more about the person presenting — remember they may not be in your team or area. This makes it easier, when they need to reach out to them (after the meeting).</li><li>‘Mission this feature contributes towards ‘ helps the audience to understand what the work (being shared) connects to</li></ol><p><strong>Slack channel</strong></p><p>For the team running the meeting, set up a slack channel, so you can discuss any technical gremlins on the day — ie audio, tv or screen sharing problems.</p><h3>Day before</h3><p><strong>Send out invite</strong></p><ol><li>DL invites don’t automatically get added to your calendar, so you need to make that clear in your email.</li><li>Send this out, the day before the meeting. There can be last minute changes of people changing order or pulling out, and keeping the email to the day allows you to catch this before pressing the send button.</li></ol><h3>On the day</h3><p><strong>Test setup 15mins before start</strong></p><ul><li>Get all offices to test the connections for audio and picture.</li><li>Depending on the conference tool you use, automatically set up muting of audio and disable joining notifications for people dialling in.</li><li>Get presenters to arrive 10–15mins before the meeting</li></ul><p><strong>Introduction deck</strong></p><p>1. At the start of the meeting, share an introduction deck which includes the running order, introducing the presenters and areas being presented on the day. 👉 Template: <a href="https://docs.google.com/presentation/d/1ffMsJiMppoYLYkn_poON9LW_o7kHYvbeSfJmxxTQAl8/edit?usp=sharing"><strong>Show and tell introduction</strong></a>👈</p><p>2. Repeat the message of what the meeting is intended for — purpose.</p><p><strong>Record the session and create a page for accessing it</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jhBiIBXjFH0TgueIkKaFA.png" /></figure><p><strong>Record the session</strong>.<br>Create a (confluence) page to be a single index of all show and tells. This is useful in comms in directing anyone that wants to know more, to one place.</p><p>Add the running order here. This will help anyone wanting to contact the presenters after the event.</p><p><strong>Time keeping<br></strong>Have a big timer, so the presenter knows how much time they have and you can give a nudge if things are going to overrun. It’s important not to have big overruns and you need to be strict on this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*dVnJVZMlWLoMJFjylryzww.png" /></figure><p><strong>Celebrate<br></strong>Ensure you are celebrating each presenter. We created button sized patches that you give out to each presenters and the more they do, they can add to their collection. This helps create wider visibility.</p><h3><strong>My takeaways from show and tells (6 months in)</strong></h3><p><strong>Taking ownership</strong></p><ul><li>Ownership needs to be driven down to the teams. Having someone to set up, own and run this meeting outside the product teams is all well and good but it becomes another ritual that teams just need to turn up too. If the teams own this, then it’s up to them to drive and see value.</li><li>Rotate the chair on the meeting.</li><li>Get sponsorship from senior leadership (Heads of, engineering managers, PMs and design leads) and advocates within other teams. They can help reinforce the sharing message, aswell as feedback on what could be better.</li></ul><p><strong>Too many rituals</strong></p><ul><li>Teams can get fatigued by all the rituals/meetings. By mapping what rituals are currently supporting your teams work, you can decide what to keep, combine or kill. If you add another meeting, you should also look to remove one. Categorising the types of meeting (team, WIP) can also help. <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> has a good example of this <a href="https://twitter.com/johncutlefish/status/1179058193382555649">here</a></li><li>You will need to sense if there is repetition of multiple shares of the same content across other meetings — are there too many meetings covering the same purpose?</li><li>There can be clashes in timing — negotiate what is possible with the teams cadence</li></ul><p><strong>Building the culture &amp; purpose</strong></p><p>Presenting work in progress can feel vulnerable for a number of reasons…</p><ul><li>You are opening yourself up to feedback — either crossovers or dependencies with other teams. It’s much easier to keep work shielded in your teams</li><li>Designers tend to present slick decks so it can feel intimidating for an engineer to talk about the work they have just started. Promote sharing of design/engineering at the most appropriate moments in the development cycle</li><li>A perception of lack of value in presenting WIP rather than completed work.</li><li>An invisible ‘quality bar’ of what is acceptable to share on a wider company platform. This needs unpacking by getting the teams to define the parameters of what they feel comfortable sharing and what they don’t.</li></ul><p>Repeatedly communicating what the meeting is intended for, aswell as <strong>not </strong>will establish purpose and value — Sharing stories/process and work in progress</p><ul><li>Teams work to different velocities. A two week period may not show much progress. Again get the teams to outline the parameters they will use to determined what they will be sharing. This may also be an indicator of the size of stories the teams are picking up and something to reflect on. Should they be broken down?</li><li>Creating a safe and trusting environment for each other. This is hard but it’s better to show rather than tell (find those advocates) and continue to reinforce the message. The value the teams feel from the meeting will drive the show and tells success.</li></ul><p><strong>Test &amp; Learn</strong></p><ul><li>Start small and test appetite with a few teams and slowly invite other areas of the business — marketing, data, analytics, creative and platform. This starts to give a much richer 360 of work in flight for the overall product</li><li>You may not always fill your allocated presenting slots and that’s ok. It just reflects what’s happening</li></ul><p>You may need to monitor the following:</p><ul><li>Too many shipped/demo presentations</li><li>The same person/discipline/teams presenting all the time</li></ul><p>In these scenarios, it’s a signal to work harder on the communication. What is it for, why you are doing it and what’s in it for them</p><ul><li>Keep iterating and adapt as the work and teams do</li><li>Be open to the fact this may not work — the teams need to see value in doing this. The attendance and participation will be key signals for you. Continue to get feedback and be prepared to adapt.</li></ul><p>I would love to hear your feedback.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cc11738dd41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making work visible at Farfetch]]></title>
            <link>https://medium.com/@kuldeepsalhan_48955/https-medium-com-kuldeepsalhan-making-work-visible-at-farfetch-476ddfcf10a9?source=rss-6ddd4102d8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/476ddfcf10a9</guid>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kuldeep Salhan]]></dc:creator>
            <pubDate>Fri, 13 Sep 2019 20:38:37 GMT</pubDate>
            <atom:updated>2019-09-19T16:28:47.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2FApbdlp9c502mczWfdPw.png" /><figcaption>Credit <a href="https://www.jakesharpe.co.uk/">Jake Sharpe</a></figcaption></figure><p>Practice was formed about 8 months ago within Consumer Product Design, acting as a horizontal function across the consumer product design org.</p><p><strong>Practice team </strong>purpose is to <strong>identify and amplify</strong> better ways of working and shares world class practice. We focus on the ‘<strong>how</strong> to…’ rather than ‘<strong>what</strong> to…’</p><p>I’d like to share an initiative <strong>Making Work Visible,</strong> taking you through what we did and my learnings.</p><h3><strong>Placing a Mirror up against the teams</strong></h3><p>In ‘<a href="https://www.amazon.co.uk/Making-Work-Visible-Exposing-Optimize/dp/1942788150">Making Work Visible</a>’ by Dominica DeGrandis (which I’ll reference throughout this post), she talked about creating high performing workflows by ‘<strong>making the work visible’. </strong>It’s powerful to place a “mirror” up against the teams, and reflect back the way in which they work. This creates time for teams to reflect and take ownership of what they are seeing.</p><h4><strong>The tactics we employed…</strong></h4><h3><strong>1. Creating maps on how teams work</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*foic2xVDKkSbw2qux_FDFA.png" /></figure><h4><strong>How it works</strong></h4><p>We start by speaking to the teams (designer, engineer, QA, PM, Head of) to understand how the teams work by asking them, <strong>‘What’s your process?’</strong></p><p>Do this with a cross section of team types — in this case co-located vs distributed, web vs native.</p><p>Create a visual map/single artefact that everyone can reference and build upon, through a series of interviews and white boarding/sketching. It’s important to be clear that you <strong>are not making any judgements</strong> or suggesting change but capturing the reality of today. This creates a safe space to work.</p><h4><strong>Takeaways from using it</strong></h4><ul><li>Teams tend to focus on what they are building/shipping but rarely think about how they do it</li><li>Having the multi-disciplinary teams do the exercise makes the teams reflect on how they work as<strong> a ‘team’ (designer, PM, engineer)</strong></li><li>Teams were very interested to compare how other teams work. There aren’t many rituals or platforms to discuss/share practice.</li><li>Platforms, time and space to reflect are easily overlooked</li></ul><h3><strong>2. Time thief</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-NMLbnpPCVKoFzT7IDT2Q.png" /></figure><p>This concept was inspired by two sources. The making work visible book and <a href="https://amplitude.com/blog/creating-flow-value-in-product-development">Creating Flow and Value in Product Development</a>, an article by <a href="https://medium.com/@johnpcutler">John Cutler</a>.<br>‘Consider a 40-hour work week. Let’s see where the time goes’</p><ul><li>You can start to build predictability, expectations and greater transparency<br>It becomes an early indicator on WIP and what’s stealing your time</li><li>It can cost the business when teams do not have visibility over when teams are unaware of mutually important information. This is especially true for distributed teams. The work tasks of the designer, PM and engineer can be invisible to each other.</li><li>Categorising the type of work — for example planned and unplanned can expose where the time is being stolen</li></ul><h4><strong>How it works</strong></h4><p><a href="https://docs.google.com/spreadsheets/d/1xmDAJaYcX6mBZ_sv6jQJLH7-t9iBFw3vl2idH1Uu-mw/edit?usp=sharing"><strong>Time thief</strong></a><strong> </strong>is an artefact that the team can use to visualise the work they are doing. A method of exposing the percentage of time physically spent working vs everything else.</p><p>Let the designer track his time over two weeks. Ensure the categories as default make sense or if iteration is required. Make sure this feels safe, as it’s easy to feel like their time keeping is being interrogated.</p><p>The follow-on question is then <strong><em>‘Does this feel right to you?’</em></strong></p><h4><strong>Takeaways from using it</strong></h4><ul><li>Especially with distributed teams, there were moments of ‘I didn’t know you were doing that?’ between team members</li><li>Syncing within and across your teams is valuable but actually seeing the amount of time taken is a moment of reflection. ‘Do I really need to be in all of these meetings?</li><li>Week to week — the time thief changes but you can use this artefact to check-in on the balance and when you might want to course correct.</li></ul><p>👉 Template: <a href="https://docs.google.com/spreadsheets/d/1xmDAJaYcX6mBZ_sv6jQJLH7-t9iBFw3vl2idH1Uu-mw/edit?usp=sharing"><strong>Time thief</strong></a> 👈</p><h3><strong>3. Cycle and shelf time</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2Rv7vkxLT14jOcoKCUg6Q.png" /></figure><p>There are always going to be delays in projects but we don’t tend to visualise them (combining design and engineering effort). Product teams are committed to getting value into our customers hands as quickly as possible in order to learn, but when we ask…</p><blockquote>How much time did we spend in design? <br>How long did it sit ‘on the shelf’? From build, significance to live?</blockquote><p>This can be invisible to teams</p><p>By visually your time you can start to understand patterns and predictability. It can start to expose things like …‘these types of projects tend to have longer design time’ Which then may lead to question ‘what is causing that? Is this what we expect as a team?</p><p>You may see patterns where design time is large but engineering effort is small. It may be the level of rigour is high in the design phase and it’s down-hill from there? Or design time is short but engineering effort is high. If this is happening often, what might be causing this?</p><h4><strong>How it works</strong></h4><ul><li>Work with the team to select a representative cross section of projects. Five should give you a good enough view</li><li>Get start and end dates of design tasks. Whether that’s in jira or trello having visibility of the design effort is a valuable data point.</li><li>Get the start and end dates from the engineering time and that will expose the shelf time.</li><li>Capture the impact and contributing factors of the shelf time. Having that conversation can be valuable to force the teams to reflect on when things haven’t gone to plan.</li></ul><h4><strong>Takeaways from using it</strong></h4><ul><li>Tracking design and engineering combined is essential to increase the visibility and pattern matching/predictability.</li><li>Reflecting on shelf time is important. The team becomes more conscious of shelf time and the <strong>cost</strong> associated — reworking, loss of context, the world is different</li><li>The action of some of the reflections: If there is low confidence or high complexity on a task, the team is reducing the level of fidelity of design required upfront — so it’s just enough to convey the idea and for engineering conversations to move ahead. These types of interventions only happen when you make the work visible.</li></ul><h3><strong>4. A combined backlog/WIP</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKaE1tGr0Q7sp_ELxdCqpA.png" /></figure><p>Having design working in trello and engineering working in jira creates a clear separation in <strong>team</strong> activity and reduces visibility and opportunity for early team collaboration.</p><p><strong>Questions to ask</strong><br>What/where is your backlog?<br>How does design discovery and build connect?<br>Where is the interaction happening?</p><h4><strong>How it works</strong></h4><ul><li>If your design and engineering backlogs are in jira, then generate a combined view of activity</li><li>If you don’t, then get the team together and compile a view and this can be as basic as a spreadsheet. You then have something to reflect on and if it makes sense for your team then look to create workflows to operationalise this — this could be moving design to jira workflow.</li></ul><h4><strong>Takeaways from using it</strong></h4><ul><li>Having all design in jira has the benefit of being able to track combined cycle and shelf time</li><li>Design and engineering are connecting design activity to epics and tasks. This creates a clear trail of work from design discovery to build.</li><li>Having a backlog of work visible for you and adjacent teams is vital in giving opportunity to share initiatives and spot dependencies/risks</li><li>Seeing Work in progress (WIP) across design and engineering can show the input and output impact and where bottlenecks appear</li></ul><h3><strong>5. Cumulative flow diagram</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v7ys_YkTU1EGqwVZ" /></figure><p>A view generated from jira showing the amount of WIP and items delivered over time</p><h4><strong>How it works</strong></h4><p>This makes visible how the teams are doing in terms of flow, what the risks are and improving predictability.</p><p>Metrics made visible…</p><ul><li><strong>Throughput</strong> : how many things are completed over a period of time, showing the rate of things coming in and out</li><li><strong>Flow time</strong> : how long it takes for items to move across the board</li></ul><h4><strong>Takeaways from using it</strong></h4><ul><li>The CFD is normally an engineering owned view but it’s just as useful for the whole team to review. Having design in jira makes the view of all work flowing in and out possible and the team can track what is working and what needs improvement</li><li>Grooming the backlog and removing stale or old tasks can be overlooked but it’s important to understand the real ‘ now, next and later’ of work</li></ul><h3><strong>6. Product Stages &amp; Players stage 1</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6zTqlSVnkb4KMdfBayJlw.png" /></figure><p>I went to a talk in May by Paul Adams at Intercom. Paul spoke about…</p><blockquote>‘Principles and Process enables us to leverage what we have learned to work and scale the company in predictable ways’</blockquote><h4><strong>How it works</strong></h4><p>Based on the maps that had been created (tactic 1), generate a visual representation of ‘product stages and players’ — an artefact which is shaped by the teams and reflects how they work, from an idea to a shippable increment.</p><p>The intent is to create something that the teams adopt. This allows a designer to onboard and understand the way we work and makes moving between teams easier as there is a commonality in approach.</p><h4><strong>Key points the artefact spotlights</strong></h4><blockquote>Where should the effort go across the end to end cycle?</blockquote><blockquote>Who should or could be involved?</blockquote><blockquote>What artefacts are being created/ what rituals or forcing functions are being used?</blockquote><p><strong>Takeaways from using it</strong></p><ul><li>Be clear about reality vs intent. It’s easy to capture ‘oh yes we want to do this’ but be clear about what you are showing</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sx2N3VYPMBocShwfqd415w.jpeg" /></figure><ul><li>Ensure you are including all teams in the creation of the stages (research, data, analytics, data science can be overlooked). We kept a printout on the wall and invited comments which exposed some blind spots. Invite people into the process with you.</li><li>Doing this also allows you to spot the gaps and potential for further deep dives.</li></ul><h3><strong>Product Stages &amp; Players stage 2 (deepdive)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e43C4YQuTnXLggpAhb8eaA.png" /></figure><p>As the Product stages and players artefact gets tighter the next question is…</p><blockquote>What’s actually happening in each stage?</blockquote><blockquote>What the mental checklist that the teams are following?</blockquote><blockquote>Is there any commonality?</blockquote><blockquote><strong>What’s the unique aspect about the activities that the teams have discovered/evolved — which makes it the Farfetch way?</strong> The ‘thing’ that you must know as a new starter?</blockquote><h4><strong>How it works</strong></h4><ul><li>Create an artefact where you can co-create. In this case a spreadsheet which reflects the product stages you have defined</li><li>Depending on the size of your team you can share this and invite them to complete. I find it more effective to set up a meeting, provide sufficient context and facilitate the conversation</li><li>Do this with each discipline — design, product, research, analytics. In this case we did this with each as separate meetings to keep the conversation focussed.</li></ul><h4><strong>Takeaways from using it</strong></h4><ul><li>Co-create using an artefact/document and keep building on the knowledge from the teams. Teams are time precious, so any upfront work you can do to get people engaged is important — sharing ahead of time, asking them to pick a target — something they may have an interest/expertise in</li><li>Connect with other guidelines to strengthen what is being asked at each. For instance principle or channel guidelines</li><li>Start to spot processes which are outliers, aswell as common. Call them out as discussion points</li><li>The process/practice you follow in itself can lead you in one direction over another. For example thinking caps vs Crazy8s will lead in different directions — when to use them will bias outcomes. What are the fundamental practices at each stage which work for you as a team?</li></ul><h3><strong>Creating a Playbook Index</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qKfK4C_kNH4glyR-" /></figure><h4><strong>How it works</strong></h4><p>From the data collected from the deepdive, start to chunk it up and create themes. This starts to create what you might see in your playbook index. The main task here is to identify what are the practices which really matter in your organisation.</p><p>Use this list to create a voting form (in google sheets) and get the teams to vote on what they believe is the must knows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wjl9qJQHIkDMMP-TT3ut3Q.png" /></figure><h4>My learnings from the whole process</h4><ul><li>Connecting the work to the team and day to day will begin to make the value of what you are doing real and ownership is with the team rather than a horizontal team</li><li>Spot your fellow change agents/advocates — they can help in your mission</li><li>Communication / when and who to, is so important. Understand your org and the layers to traverse to get the support you need</li><li>Co-create where possible. Invite others into the process rather than owning the change. This is not easy and show and not telling works better</li><li>Be clear on what you are and not focusing on — try and be ruthless in your focus</li><li>Be clear about your ask to others</li><li>Treat it as an experiment. Sense and respond as you go as things will evolve. Not everything is fully baked. Some things won’t work.</li><li>Create a safe space to work</li><li>Visibility of what you are doing. In horizontal teams the actual value of the work and impact on the teams can be invisible. It’s important to be as transparent as possible on</li><li>what you are committing to do</li><li>what you actually did</li><li>why it’s important for me</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PsCLKHeR36Wes3Go_6MHFQ.jpeg" /></figure><ul><li>Mission patches is one tactic to create a community around the work you are doing aswell as promoting the work/interest from others</li><li>Recognise the ‘thing’ that keeps you going when it gets hard.</li><li>Celebrate and share the progress.</li></ul><p>I would love to hear your feedback.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476ddfcf10a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>