<?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 Isobel on Medium]]></title>
        <description><![CDATA[Stories by Isobel on Medium]]></description>
        <link>https://medium.com/@isobel-59565?source=rss-48f3843fdb17------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Cciay_ibYeYDnYpg.jpg</url>
            <title>Stories by Isobel on Medium</title>
            <link>https://medium.com/@isobel-59565?source=rss-48f3843fdb17------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:51:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isobel-59565/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[Digital Strategy Design — sprint notes 3–4]]></title>
            <link>https://medium.com/wethecatalysts/digital-strategy-design-sprint-note-3-4-a4c8ef747473?source=rss-48f3843fdb17------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4c8ef747473</guid>
            <dc:creator><![CDATA[Isobel]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 15:59:33 GMT</pubDate>
            <atom:updated>2021-04-19T12:53:43.096Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Digital Strategy Design — sprint notes 3-4</strong></h3><p>There are 4 charities in dxw’s cohort and we’re focussed on designing digital strategies.</p><h4><strong>Sprints 3 and 4</strong></h4><p>This sprint note covers sprint 3 and 4 on the Strategy Design cohort. We’ve combined this note as we did work that crossed both sprints.</p><p>The focus for sprint 3 and 4 was to design the things each charity had identified to focus on in the earlier sprints.</p><p>One charity chose to focus on designing a digital strategy, two charities decided they didn’t need a digital strategy and would like to focus on a new service instead, and the fourth charity focussed on both — a strategy and a service.</p><h4><strong>A mini sprint</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4xMKVat0wLhoED8Q5bwHg.jpeg" /></figure><p>We embarked on a mini sprint (at the end of sprint 3 and start of sprint 4) over 5 days. The mini sprint was based on the concept of a design sprint, but bespoke to the programme and what each charity is working to achieve.</p><p>A design sprint is a time constrained, phased process that’s focussed on designing something. On our sprint we used design thinking as a method, which describes a process that places users at the centre and solves problems in creative ways. On our sprint creative didn’t need to be visual ideas, it could be words.</p><p>The benefit of the design sprint was continuity and momentum, and the opportunity it provided to collaborate.</p><p>The charities had templates in Miro to work from. They also utilised existing research and techniques we’d practiced on the programme so far.</p><p>We got together each day for an hour in the morning. Everyone worked in an open and collaborative way, whilst focussing on different things. Here is what we did on each day:</p><ul><li>Day 1 was set-up day. We made sure everyone had what they needed to make start, and understand how to use the templates.</li><li>Day 2 was design day! This was when each charity focussed on designing their strategy or service. At the end of the day the dxw team reviewed the designs and provided feedback, to be reflected on the next day.</li><li>On day 3 the charities reviewed their feedback, and incorporated this into their designs which they continued to work on.</li><li>On day 4 the charities reviewed one another’s work and provided feedback. They then progressed their designs as far as they could before stopping.</li><li>On the final day the charities brought along a colleague to the session that hadn’t been involved in the project. The colleagues reviewed the ideas and shared feedback.</li></ul><p>We’re now on our 5th and final sprint. Each charity is focussing on completing what they started during the mini sprint. We’ll be sharing the outputs at the project show and tell on 26 April. If you’d like to come along let me know.</p><p><em>Rather than a sprint note for the final sprint we’ll be writing a blog collaboratively as a cohort.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4c8ef747473" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wethecatalysts/digital-strategy-design-sprint-note-3-4-a4c8ef747473">Digital Strategy Design — sprint notes 3–4</a> was originally published in <a href="https://medium.com/wethecatalysts">Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Strategy Design — sprint note 1]]></title>
            <link>https://medium.com/wethecatalysts/digital-strategy-design-sprint-note-1-3be6a5363c43?source=rss-48f3843fdb17------2</link>
            <guid isPermaLink="false">https://medium.com/p/3be6a5363c43</guid>
            <category><![CDATA[definition-programme]]></category>
            <category><![CDATA[digital-strategy]]></category>
            <category><![CDATA[dxw]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[sprint-notes]]></category>
            <dc:creator><![CDATA[Isobel]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 14:52:37 GMT</pubDate>
            <atom:updated>2021-03-05T15:49:19.058Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Digital Strategy Design — sprint note 1</strong></h3><h4>By dxw, Strategy Design group lead, Definition programme</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Av4eIAc--dpDFR42JRdTMA.jpeg" /></figure><p>There are 4 charities in DXW’s cohort and we’re focussed on designing digital strategies.</p><p><strong>Getting started</strong></p><p>We’re working in sprints - two weekly phases of work that start with planning and end in reflection. Sprints help us deliver work in a fluid and iterative way and keep track of what we’re doing. We completed sprint 1 of 5 at the beginning of the week.</p><p>We kicked off the project with an inception workshop. At <a href="https://www.dxw.com/">dxw</a> we often start projects with an inception. Inception is when you bring together the project stakeholders, with the purpose of identifying what you’re working towards, identify goals and start to form a plan. It’s an opportunity to make sure we all start with the same information and understanding.</p><p>In our inception we started by sharing hopes and fears for the project. We identified what we’re seeking to change, explored what we mean by certain terms such as engagement, and identified where the charities are on their digital transformation journey. We started to form a project roadmap for each charity. Roadmap is the term we use to describe a plan that is focussed around a shared goal. We identified shared activities and outcomes for the project.</p><p><strong>Working in the open</strong></p><p>In our kick-off meeting prior to inception we agreed the tools we’ll be using during the project and picked Slack as our main communication tool, accompanied by a regular project stand-up. We also have a living deck, which is a place to capture what we’re doing as we progress.</p><p>We had a conversation with our Editor at dxw to discuss our approach to publishing week notes. We decided on sprint notes, of which this is the first and the charities will follow for future sprints. We thought about the audience of the sprint notes and where the best place to publish them was. We decided here!</p><p>We agreed it was important to share what we’re learning in the sprint note, not just what we’re doing. We decided to write a case study in collaboration at the end of the project. This is something we’ll publish on the dxw blog too.</p><p><strong>Sprint one</strong></p><p>The first sprint focussed on set-up and planning, and the main aims of the sprint were to: agree what each charity is working towards and learn how to form a research plan.</p><p>We took the project roadmaps we began forming in inception, reviewed and refined these. After looking at these it became clear that they were very broad. As a first step, it was possible to identify a high-level goal for each charity to reflect what they want to achieve from the project. This is our starting point, and we may come back to the roadmaps later in the project, if they are a useful output for the charities to take forward to guide the work they go on to do.</p><p><strong>A few initial learnings</strong></p><ul><li>what is needed in terms of a strategy can be defined in different ways. We suggest this isn’t a bad thing, as a strategy can be applied at different levels</li><li>research is something people see happening at the start of a project. We suggest it happens throughout a project and it evolves as you progress</li><li>understanding what to deliver can be hard. We suggest to start with the needs of people in receipt of what you’re delivering to guide what you do</li></ul><p><strong>Things that have been hard</strong></p><ul><li>how do we learn from one another when we’re at different stages and seeking to achieve different things? We’ve decided to follow the same process as much as we can - but not seeking the same outcomes from it</li><li>being available at the same time isn’t always possible. We’ve decided to change our daily stand-up, to less regular but longer catch-ups</li></ul><p><strong>Learnings from one of our charities</strong></p><ul><li>what went well: “we’ve been able to set out clearly our expectations from this project and ourselves, which has allowed the project to get off to a good start”</li><li>what was hard: “planning our time and the logistics of this project for the next sprint - as a small organisation with research that needs to involve our wider team, it has been tricky to make sure we can get the most out of this project within our limited capacity”</li><li>what we want to learn next: “as we move into research, I’d like to learn how we can most effectively analyse our research findings to construct our strategy”</li></ul><p><strong>Sprint two</strong></p><p>We’ve started sprint 2. The focus of this sprint is to understand who we’re doing the work for, and what we currently do for these people. We’ve decided to prioritise our activities for this sprint as we complete them. The first prioritised activity is to create a research plan. Some of the charities would like to undertake primary research whereas some would like to use their existing research. The research we do in this sprint will be helpful to direct what we do in the later sprints.</p><p>We’re also undertaking 3 team sessions this sprint, focussed on:</p><ul><li>understanding the people we’re doing the work for</li><li>understanding the things we currently do/the services we deliver</li><li>identify where there is opportunity for change and improve what we do</li></ul><p><strong>Our first project show and tell is on 16 March. Please come along!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3be6a5363c43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wethecatalysts/digital-strategy-design-sprint-note-1-3be6a5363c43">Digital Strategy Design — sprint note 1</a> was originally published in <a href="https://medium.com/wethecatalysts">Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>