<?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 Aaron Percival on Medium]]></title>
        <description><![CDATA[Stories by Aaron Percival on Medium]]></description>
        <link>https://medium.com/@am_percival?source=rss-9386cf987b88------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*EqGwBuAoSLB5MCX-.</url>
            <title>Stories by Aaron Percival on Medium</title>
            <link>https://medium.com/@am_percival?source=rss-9386cf987b88------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:23:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@am_percival/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[Service design in action: Improving the experience for youth]]></title>
            <link>https://medium.com/series/service-design-in-action-improving-the-experience-for-youth-35e58342a163?source=rss-9386cf987b88------2</link>
            <guid isPermaLink="false">https://medium.com/p/35e58342a163</guid>
            <dc:creator><![CDATA[Aaron Percival]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 14:41:04 GMT</pubDate>
            <atom:updated>2019-01-11T18:44:22.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’re jamming with a room full of youth stakeholders over two days.</h4><h4>We want to create a great experience for young people who access government services for help with employment, skills, and learning.</h4><h4>We are working together to understand how our current offerings can be mapped to what young people need at different times in their journey to a successful career.</h4><h3>Day 2</h3><blockquote>Today is focused on taking the goals and tasks for our audience segments and understanding how our existing resources help achieve goals.</blockquote><h3>We started they day by cleaning up our goals and tasks. Then we made sure that we didn’t miss any of our users in our segments.</h3><h3>Where did we get after two days?</h3><h3>Now what?</h3><blockquote>Over the next few weeks we will validate the work done to create this list and match each resource to how they help specific audience segments with their goals and tasks.</blockquote><h4>The result will allow us to create a tailored experience for users that is simple and easy to use and will enable them to find what they need when they need it quickly.</h4><h3>All of this work is to support our Minimum Viable Product…</h3><h3>It’s only the start of something big</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35e58342a163" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the makeup of project teams using three lenses]]></title>
            <link>https://medium.com/@am_percival/understanding-the-makeup-of-project-teams-using-three-lenses-296115d4c903?source=rss-9386cf987b88------2</link>
            <guid isPermaLink="false">https://medium.com/p/296115d4c903</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Aaron Percival]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 14:37:32 GMT</pubDate>
            <atom:updated>2018-07-16T15:34:18.125Z</atom:updated>
            <content:encoded><![CDATA[<h4>An activity to identify focus, level of involvement, and the deciders.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x8MjORy1r6pT0zCv" /><figcaption><a href="https://unsplash.com/@scottwebb?utm_source=medium&amp;utm_medium=referral">Scott Webb</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’d like to share an activity that I’ve had a lot of success doing to help create empathy among projects team that consists of people with different focuses, priorities, levels of engagement, and authorities.</p><p>As someone who works in the User Experience (UX) and Service Design world in the Government, it’s essential that I understand entirely why the project has specific constraints, motivators, and success criteria. It’s all about understanding why I hear things like,</p><blockquote>You can’t do that because…<br>We need to do it this way…<br>I want this solution…<br>We need to have this done by…<br>We can’t talk to so and so…<br>We can’t use that system…<br>…</blockquote><p>The activity that I’ve created helps me to understand three important attributes of the project team:</p><ol><li>What everyone’s primary focus? Is it Users, the Business (Organization), or Process (policy, laws, procedure…).</li><li>How are involved is everyone? Are they part of the core team, or will we engage them periodically, or do we need to communicate what we’re doing to them?</li><li>Who makes decisions about what?</li></ol><blockquote>As a first step, I run this activity with the entire project team as a group to create a shared understanding and to identify gaps any gaps we might have from the start.</blockquote><h3>Context</h3><p>My journey as a <a href="https://gccollab.ca/profile/Agents">“Free Agent” for the Government of Canada Free</a> currently finds me working on the Service Innovation Team in the Digital Services Directorate at Transport Canada.</p><p>The Service Innovation Team is primarily a product and service design shop. We use a User-Centred Design (UCD) framework with a Design Thinking approach to help projects explore problems, frame them in the right way, conduct research, and develop concepts of potential solutions.</p><p>Depending on the project and the scope we, use methodologies like User Interaction Design (UI), User Experience Design (UX), and Service Design to provide more evidence for funding decisions.</p><p>Our context is the same as similar teams across government: we work outside of the core project team and provide <em>design as a service</em>. We don’t own project or money; we’re brought in to help, and we work collaboratively with the project.</p><h3>Step one: understand who we’re working with</h3><p>Our team, the way we work, and how we fit into the life of a project is new to the department. Because of the design as a service model, we’re also coming into the project from the <em>outside. C</em>onsequently, as a <strong>first step,</strong> we must</p><ol><li>effectively express what we do and how we fit into the project; and,</li><li>understand how everyone else fits in, so we know how to work effectively <em>with </em>the team.</li></ol><blockquote>Our goal is to be collaborators, not adversaries.</blockquote><p>Mostly, I need to know three things: focus, level of involvement, and who decides on what:</p><h4>Focus</h4><p>The Service Innovation Team’s primary focus is making sure the project is producing outputs that are desirable, useful, and usable. The reality, that’s not everyone’s concern.</p><blockquote><strong>That’s completely fine.</strong></blockquote><p>Some people will be focused on budget and timelines. Some people will be on rules, process, policy, regulation. Some people will be focused on departmental priorities and the five-year strategy. Some people will be focused on how we implement the thing.</p><p><strong>We all need to understand where everyone is coming from so that we can work collaboratively toward a solution that works for everyone.</strong></p><h4>Level of Involvement</h4><p>Who is part of the day-to-day team? Who is creating and implementing the plan for getting GSD (getting sh… stuff done)? Who do I need to work with so that I can make sure that my research and design activities are given enough weight and time to produces the results that I need them to? Who do we need to engage from time to time? Who do we need to keep informed?</p><h4>Decision Makers</h4><p>Who can make day-to-day decisions about what? Who has the overall authority for this project?</p><h3>The Activity — Team Roles Canvas</h3><p>I’ve created this canvas and activity to help answer these questions. I bring everyone together at the start of a project (or at least when I join a project) so that we start off with some empathy and understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oGxQfrAUZonAhNX1fZwmDg.jpeg" /><figcaption>My Team Roles Canvas</figcaption></figure><p>The canvas is inspired by the Team Roles activity in Nesta’s <a href="https://www.nesta.org.uk/toolkit/designing-for-public-services-a-practical-guide/"><strong>Designing for Public Services: a practical guide</strong></a>, which I’ve modified and added more detail that I find necessary.</p><p>I’ve included the pdf of the canvas along with my facilitation instructions. The pdf itself is in 11x17 format, which works well as a placemat that people can use individually.</p><p>I suggest also printing a large format version. I’ve had mine printed on 36&quot; wide role which produces a canvas that’s about 36&quot; x 55&quot; and works well.</p><h4>Instructions</h4><ol><li>Have everyone write their name and role on a sticky note (or notes) and place them in the approriate places on the canvas.</li><li>Go over the canvas with the group; make it a discussion. Ask why people see themselves in different lenses and what’s important to them about the project.</li><li>Have the group try to identify gaps: who isn’t in the room that might be touched by this project.</li><li>After the session, make sure that everyone gets a copy of the canvas and if you can, hang it in a communal place for all to see.</li></ol><p>I explain each part in detail below.</p><ul><li><a href="https://drive.google.com/file/d/1T1neZDvLdIEEzg11Pw2pm3ydOK5DUX5Y/view?usp=sharing">Team Roles - Canvas (v1.0).pdf</a></li><li><a href="https://drive.google.com/file/d/1CLyjCI8nSNSzTFH6-2DU1mNKGuYGjfEg/view?usp=sharing">Team Roles - Canvas (Facilitation Instructions).pdf</a></li></ul><h3>1. The Design Triforce</h3><p>In the government context, I’ve found it very useful to segment people’s primary focus into three <strong>lenses</strong>: User Lens, Business Lens, and Process Lens. Together I call this the <strong>Design Triforce</strong>.</p><blockquote>Only where the lenses intersect, do we have something that’s desirable, viable, and feasible (i.e. we have a good thing and can actually make it).</blockquote><h4>The User Lens: Desirable</h4><p><em>What is desirable, useful, and usable for users and stakeholders?</em></p><p>These are people are <strong>primarily </strong>focused on the needs of end users and stakeholders. They are interested in things like,</p><ul><li>a user’s experience with the product or service;</li><li>engaging with users;</li><li>user needs, pains, and gains; and,</li><li>user requirements.</li></ul><h4>The Business Lens: Viable</h4><p><em>What is viable for the organization?</em></p><p>These people are <strong>primarily </strong>focused on the needs of the organization. They are interested in things like,</p><ul><li>the organization vision and goals;</li><li>the organizations short- and long-term strategy;</li><li>business requirements and outcomes; and,</li><li>budgets and timelines.</li></ul><h4>The Process Lens: Feasible</h4><p><em>What is feasible to implement?</em></p><p>These people are <strong>primarily </strong>focused on factors that make the thing feasible to implement. They are interested in things like,</p><ul><li>developing and implementing the thing (e.g. coding the final thing);</li><li>regulations, laws, and policies;</li><li>politics; and</li><li>privacy, security, and safety.</li></ul><h3>2. The Team</h3><h4>Core Team: Actively involved</h4><p><strong>What they do:</strong><br>The core team is the heart of the project. These people are actively involved in the day-to-day activities. They own the project plan, implement it, and ensure it stays on track.</p><p><strong>Key project roles:</strong></p><ul><li>The people who are accountable for the outputs of the project.</li><li>Owners of the design process.</li><li>Liaise with the Extended Team when necessary</li><li>Communicate and seek approvals from the Leadership Team when necessary.</li></ul><h4>Extended Team: Engaged</h4><p><strong>What they do:<br></strong>These are typically people identified as subject matter experts and could come from the policy space and/or delivery space. They contribute their expertise to the challenge but are not actively involved on a daily basis; they contribute when prompted.</p><p><strong>Key project roles</strong>:</p><ul><li>Providing subject matter expertise.</li><li>Can also act as reviewers of the core team’s work.</li></ul><h4>Leadership Team: Informed</h4><p><strong>What they do:</strong><br>These are the final decision makers and have control over the different governance processes that the project needs to go through. It’s vital that these people are kept informed along the way so that they can contribute to the strategic direction.</p><p><strong>Don’t forget about these people!</strong></p><p>They are invested in the outcome and will support (or not) the work horizontally across the organization.</p><p><strong>Key project roles:</strong></p><ul><li>High-level decision-making and approval.</li><li>Cover for the core team from higher levels of authority so that the Core Team can do the work they need to do.</li></ul><h3>3. The Deciders</h3><h4><strong>Sponsors</strong></h4><p>Sponsors are in leadership and management positions at the unit and above level. They are invested in the success of the project and its impact on the organization.</p><p>Sponsors shouldn’t be actively involved in the day-to-day. However, they approve major project decisions. They can also provide support through resources and processes to the core team.</p><p>They may attend a few key activities and project checkpoints.</p><h3>Leads</h3><p>Leads are usually part of the core team. They bring in content knowledge and stay connected around the organization. They are responsible for steering different aspects of the project forward and are invested in success.</p><p>Leads are often supported by a team member to coordinate schedules, communication and logistics.</p><p><strong>It’s important to define what each lead can decide on. </strong>This way, the Project Team knows who to approach about different issues that arise.</p><p>If you liked this post, please consider giving it some clap love — claps make me feel good and let me know that you appreciate my work.</p><h4>About me</h4><p>I’m one of <a href="https://gccollab.ca/profile/Agents">Canada’s Free Agents</a>. It’s a fascinating job where I’m able to work anywhere in Canada’s Public Service on projects that I choose.</p><p>In my past life, I was a physicist with <a href="http://www.drdc-rddc.gc.ca/en/index.page">Defence Research and Development Canada</a>. Since moving on, I’ve leveraged my extensive academic science research experience on Service Design and User Experience Design in the Government of Canada by helping to build design programs and better things across the Public Service.</p><p><strong>Connect with me on Twitter</strong></p><p><a href="https://twitter.com/am_percival">Aaron Percival 🇨🇦 (@am_percival) | Twitter</a></p><p><strong>Find me on LinkedIn</strong></p><p><a href="https://www.linkedin.com/in/ampercival/">Aaron Percival - Free Agent - Canada&amp;#39;s Free Agents | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=296115d4c903" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An adaptive challenge — finding the gap]]></title>
            <link>https://medium.com/@am_percival/an-adaptive-challenge-finding-the-gap-b25cda425bbc?source=rss-9386cf987b88------2</link>
            <guid isPermaLink="false">https://medium.com/p/b25cda425bbc</guid>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Aaron Percival]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 12:55:16 GMT</pubDate>
            <atom:updated>2017-10-18T14:00:42.099Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMNcd1wT7fnmbMo3EH3nXA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/3GWOlKitAMY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Josh Wilburne</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>An adaptive challenge — finding the gap</h3><h4>How can we be better at creating for our <strong>clients</strong> and make it less about us?</h4><p>I’m taking a self-directed online course from Acumen on <a href="http://www.plusacumen.org/courses/adaptive-leadership">Adaptive Leadership: Mobilizing for Change and Disrupting the Status Quo</a>. Over four weeks, the course will cover these topics:</p><ol><li>Identify Your Leadership Challenge;</li><li>Think Politically to Mobilize Support;</li><li>Distinguish Technical and Adaptive Problems; and</li><li>Adaptive Experience</li></ol><p>These topics are essential to my current work because my team is trying to change the way that our organisation develops products and services for our clients.</p><p>This effort requires a significant change in the way we think — by ‘we’ I don’t mean only my organisation but the entire enterprise. I’m talking about changing the culture.</p><p>I’ve completed the first module, which focuses on finding a gap between current reality and my aspirations. It introduces the concept of the Dance Floor and the Balcony:</p><blockquote><strong>The Dance Floor<br></strong>Where the day-to-day work gets done; full of action, to-dos, noise, and deadlines.</blockquote><blockquote><strong>The Balcony</strong><br>Where you see the big picture; get perspective in the midst of action.</blockquote><p>It emphasised the importance of getting on the balcony to find a gap:</p><blockquote>The gap is a leadership opportunity, a tension to be held creatively, rather than something to be relieved or ‘solved’.</blockquote><p>The module asked me to observe from the balcony and look for a gap between my current reality and my aspirations. This gap will be my focus for the rest of the course.</p><p>The gap I’ve chosen is the difference between what we say about how we should be developing products, services, and policies and my experience.</p><p>This week I had to write a 300-word description of my gap addressing these points:</p><ol><li>Who am I;</li><li>What is my aspiration;</li><li>Why it matters; and</li><li>What the current reality is</li></ol><p>My submission is below.</p><h3><strong>Who am I</strong></h3><p>I am a public servant working in the innovation space. I am currently leading a team tasked with ensuring my organisation delivers products and services that offer our clients the best possible experience.</p><h3><strong>My aspiration</strong></h3><p>I want to create an open and transparent culture that embraces experimentation and smart failures. I believe we should engage our clients throughout the entire process. We should start with ideas that will be useful and desirable to the people we’re creating for. Only then should we bring in other constraints to ensure that we’re making things that are viable and feasible.</p><h3><strong>Why it matters</strong></h3><p>We can’t pretend to know everything that our clients want or need. We shouldn’t speak or act on their behalf. It’s crucial that we take more time to understand the real root of a problem. Doing this means we do a lot more asking and a lot more listening. It involves trying things, setting measurable goals, exposing ourselves a little, experimenting, and getting things wrong sometimes. It’s important that we fail, but that we fail in a smart way: small and adaptable so we can learn and try again — and maybe fail again.</p><h3><strong>The current reality</strong></h3><p>Although this might seem like common sense, the reality is that we often start by looking through a business less. We let the bureaucracy take control. We think about what will work for our business before we think about our clients. We walk too far down the development path before we try to understand what’s feasible regarding technology, politics, policies and all of the other no machines. This process culminates in us forcing our solutions onto our clients and then we go ¯\_(ツ)_/¯.</p><p><strong>If you like this post, please consider adding a few claps. This helps other people find it and lets me see that you enjoyed it too.</strong></p><p><strong>I’d love to continue the discussion.</strong></p><p><strong>You can find me on twitter </strong><a href="https://twitter.com/am_percival"><strong>@am_percival</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b25cda425bbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>