<?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[Service Design Toronto - Medium]]></title>
        <description><![CDATA[Community updates, event recaps and service design related content from Service Design Toronto - Medium]]></description>
        <link>https://medium.com/service-design-toronto?source=rss----942b6d7df20b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Service Design Toronto - Medium</title>
            <link>https://medium.com/service-design-toronto?source=rss----942b6d7df20b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:26:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/service-design-toronto" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Recap: SDTO Book Club Event 9 with Jim Kalbach]]></title>
            <link>https://medium.com/service-design-toronto/recap-sdto-book-club-event-9-with-jim-kalbach-ba20dda12090?source=rss----942b6d7df20b---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba20dda12090</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Elena Glebkovskaya]]></dc:creator>
            <pubDate>Tue, 19 Oct 2021 22:31:23 GMT</pubDate>
            <atom:updated>2021-10-19T22:31:23.200Z</atom:updated>
            <content:encoded><![CDATA[<p>For the online SDTO Book Club #9 event, we had the amazing <a href="https://www.linkedin.com/in/kalbach/"><strong>Jim Kalbach</strong></a>, Chief Evangelist at <a href="https://www.mural.co/">Mural</a>, who joined us to talk about his book <a href="https://rosenfeldmedia.com/books/jobs-to-be-done-book/"><em>The Jobs To Be Done Playbook — Align Your Markets, Organization, and Strategy Around Customer Needs</em></a><em> </em>and answer our questions.</p><figure><img alt="Book cover for The Jobs To Be Done Playbook by Jim Kalbach" src="https://cdn-images-1.medium.com/max/616/0*h-972ZXY3cL0kmcp" /><figcaption>Image from <a href="https://rosenfeldmedia.com/books/jobs-to-be-done-book/">Rosenfeld Media</a></figcaption></figure><p>Jim introduced JTBD with the following quote:</p><p><strong>“People don’t want a quarter-inch drill, they want a quarter-inch hole” — Theodore Levitt</strong></p><p>This type of thinking about the outcome people want illustrates what JTBD is all about.</p><p>The ways to do something and the technology behind is changing through time, but the Job stays the same — like we always want to listen to music, and we keep inviting new ways of doing it. This makes JTBD approach future proof.</p><figure><img alt="A diagram showing 3 intersecting cycles — Job Performer, Target Job and Process that leads to Outcomes and it all is grouped as Circumstances." src="https://cdn-images-1.medium.com/max/1024/0*lbGUWNpP1XmbL49u" /><figcaption><strong>Image credit: The JTBD playbook — Jim Kalbach</strong></figcaption></figure><p>Jim mentioned that there are many JTBD techniques and shared the rules of creating <strong>Job Statements</strong>:</p><p><strong>DON’Ts</strong></p><ul><li>Reference technology, solution or methods</li><li>Don’t use AND or OR</li></ul><p><strong>DO’s</strong></p><ul><li>Start with a strong verb</li><li>Separate objectives from outcomes</li><li>Represent individual’s perspective</li></ul><p>Jim shared an example of identifying needs and job steps from research insights.</p><figure><img alt="An example tables with 3 columns: Insights, Objective that equals job step and Outcome that equals need." src="https://cdn-images-1.medium.com/max/1024/0*UheL8xcd9D5J7M7v" /><figcaption><strong>Image credit: Mural — SDTO book club event with Jim Kalbach</strong></figcaption></figure><p>Together in very interactive activity we went through some examples of creating a Job Statement and Jim shared with us <strong>JTBD steps</strong> to follow:</p><ol><li><strong>Scope Your Target Job </strong>(Where do you want to innovate?)</li><li><strong>Conduct Interviews </strong>(How do job performers understand the job?)</li><li><strong>Map the Target Job</strong> (What is the process of getting the job done?)</li><li><strong>Prioritize Opportunities</strong> (What are the key problems you can solve?)</li></ol><p>The attendees had lots of questions that Jim was very kind to answer and we are happy to share here.</p><p><strong>💡Q&amp;A with Jim Kalbach</strong></p><p><strong>(Q)</strong> I’m currently beginning a JTBD analysis on my team. As our first step, we’ve identified our core functional job. When we tried to identify our core job performer, we found there really are multiple 2 core job performers. Do you suggest we really just focus on 1 going forward? If so, how do we avoid neglecting the other necessary role completely?</p><p><strong>(A)</strong> You can focus on one. But when it’s B2B it might be many jobs and many job performances. So map and list them all out, decide where you start first, then maybe come back to others.</p><p><strong>(Q) </strong>How might you connect the job mapping activity with a storyboarding exercise to design the experience we believe users want? (I’m working with a team who has never done user flows before)</p><p><strong>(A)</strong> Before going to the scenario, we create a model and there might be a lot of solutions for this problem. You could create a job story that summarizes, creates a lot of focus, and becomes your proxy. You could also write a little scenario and do brainstorming.</p><p><strong>(Q) </strong>How might you imagine someone using a Job Map together with a Journey Map?</p><p><strong>(A)</strong> Job map is not a Customer Journey Map, because in CJM you see them as your customer. But Job map is what they try to do independently from you. Then after you have your solution — you’d have a CJM to continue with the process.</p><p><strong>(Q)</strong> At the start of a JTBD analysis when you’re defining your core/target job, how can you tell that the job is at the correct level of granularity? (to avoid being too high-level or too low-level)</p><p><strong>(A)</strong> There are no right or wrong answers here — you can innovate at any level. It depends where the team is, where the product is, where you are as an organization.</p><p><strong>(Q)</strong> Can JTBD be used in evaluative research? If yes, can you please provide an example of how we might use it in evaluative research without talking about the product/technology?</p><p><strong>(A)</strong> Yes, I think so, and the metric here could come from human needs.</p><p><strong>(Q)</strong> Can you please tell us more about your experience with JTBD within the B2B sphere? What special considerations need to be made in your experience? (I work in enterprise products, so I am very curious!)</p><p><strong>(A) </strong>You would need to look at all jobs that need to be done, the concept of related jobs. You will have many of them and you’ll need to map all them out. This can be very heavy, but once you do it once it is usually static. Then choose where you’re going to start and go from there.</p><p><strong>(Q)</strong> As UX researchers we choose research methods and methodologies based on research questions and the stage of the product, among other factors. Can you please mention if JTBD is for any specific types of research questions or for particular stages of the product?</p><p><strong>(A)</strong> We don’t care about the product in JTBD, we want to understand the job, the emotions. For this, we usually use a discussion guide.</p><p><strong>(Q) </strong>Do you only suggest doing interviews for collecting user data or we can use other methods such as observation where we do not have “quotes” from the participants?</p><p><strong>(A)</strong> I believe it can be done, but I think you do need to have some interviews there even during observation to understand the Job better.</p><p><strong>(Q)</strong> Are there any other things you wish you could add to or change about your book?</p><p><strong>(A) </strong>I would change the word ‘need’ to ‘outcomes’, and ‘main jobs’ to ‘target jobs’. I also might be more explicit about specific recipes.</p><p>We encourage everyone to read Jim’s amazing book to learn about JTBD in more detail and definitely try it out in your work!</p><p>Let us know how it goes!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba20dda12090" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-toronto/recap-sdto-book-club-event-9-with-jim-kalbach-ba20dda12090">📓Recap: SDTO Book Club Event 9 with Jim Kalbach</a> was originally published in <a href="https://medium.com/service-design-toronto">Service Design Toronto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recap: SDTO Book Club Event #2 with Marc Fonteijn]]></title>
            <link>https://medium.com/service-design-toronto/recap-sdto-book-club-event-2-with-marc-fonteijn-a45d685c329f?source=rss----942b6d7df20b---4</link>
            <guid isPermaLink="false">https://medium.com/p/a45d685c329f</guid>
            <category><![CDATA[toronto]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Arun Joseph Martin]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 12:32:09 GMT</pubDate>
            <atom:updated>2019-06-03T12:32:09.354Z</atom:updated>
            <content:encoded><![CDATA[<p>Due to stormy and unpredictable Toronto weather, after a few false starts we ended up running this year’s first Service Design Toronto (SDTO) book club event as online on February 12th!</p><p>Our second SDTO event featured guest <a href="https://www.linkedin.com/in/marcfonteijn/"><strong>Marc Fonteijn</strong></a><strong>,</strong> of the hugely popular <a href="https://www.youtube.com/c/servicedesignshow">Service Design Show</a> (YouTube channel and podcast). He is also the founding partner of <a href="http://www.31volts.com/">31Volts</a>, a leading service design agency in the Netherlands.</p><p>Marc answered the questions from the attendees in a recorded Q/A earlier to the event, which was shared with the attendees.</p><p>During the event, we read chapters from two different books and also had a conversation on few questions shared below.</p><p><strong>Book 1</strong>: <a href="https://learning.oreilly.com/library/view/the-knowing-doing-gap/9781422163528/KnowingDoing_chap-8.html">The Knowing-Doing Gap: How Smart Companies Turn Knowledge into Action</a> <br>Chapter 8: Turning Knowledge into Action</p><p><strong>Book 2</strong>: <a href="https://learning.oreilly.com/library/view/meeting-design/9781492068792/">Meeting Design: For Managers, Makers, and Everyone</a></p><h3>Why should you read The Knowing-Doing Gap: How Smart Companies Turn Knowledge into Action<strong>?</strong></h3><p><strong>Marc</strong>: As service designers, we often work in big organizations where we struggle to get ideas into reality. This book explains why organizations experience the <em>knowledge-doing gap</em> (when organizations “know” that the should do something yet they don’t do it). The book makes the case for how Service Designers can bridge the gap between insights and actions. It’s a cornerstone book that anyone interested in Service Design should read.</p><p>How might we help people new to the ‘learn-by-doing’ style of working that is inherent in service design? It’s a difficult transition for people and organizations accustomed to a ‘knowing-before-doing’ style. <em>— Jason King</em></p><blockquote><strong>Marc</strong>: Measure what matters, and in ways that connect ‘means’ to ‘ends.’ If we want to gain and sustain momentum, we need to choose metrics that answer two questions: <br>1) How do we know (and prove) that we’re making real progress? <br>2) How does this contribute to our organization’s priorities?</blockquote><p>How do you help people “get out of their own way”? Often, organizations are fixed in their ways and reluctant to innovate because it means changing “the way it’s always been done”. How can we overcome this?</p><blockquote><strong>Marc: </strong>As the saying goes, “we expect our colleagues to change instead of changing ourselves”. Perhaps Service Designers need to change by doing two things:</blockquote><p><strong>1) Empathize with the feared consequences of ‘failing fast’ or ‘failing forward.’ <br></strong>Someone steeped in a ‘knowing-before-doing’ environment will have real fears of rapid prototyping. <br>- What happens for them when (not if) one of their prototypes doesn’t go as well as they hoped?<br>- What consequences do they fear from their leaders and peers? <br>Once we understand this, we can find ways to encourage a sense of safety for them.</p><p><strong>2) Understand how teams are rewarded to get buy-in for new initiatives<br></strong>To get buy-in for new initiatives in organizations, teams should understand how the other teams measured and rewarded. Without this understanding, you can’t articulate what is in it for them, and without that, the new idea will not gain traction.</p><h3>Why should you read <strong>Meeting Design: For Managers, Makers, and Everyone?</strong></h3><blockquote><strong>Marc</strong>: Service Designers have to create design materials that allow our solutions to get into reality. One of the design materials that we work with are meetings. Meetings are a key element of the organization and mastering meetings is necessary to have organizational impact.</blockquote><p><strong>What are the possible ways to design “pre-meetings” before the official meeting?<br>Marc: </strong>Let’s not be naïve, as the adage goes, “the meeting starts before the meeting”. In any organization, there will be “pre-meetings” — these come in many forms, including in the calendar invite framing the purpose of the meeting, the two attendees who always take lunch together, another totally unrelated project that happens to also draw on the same attendee list.</p><p>Rather than fight this reality, accept it and work with it. As Service Designers, we have the ability to look at things as a holistic journey.</p><blockquote><strong>Understand that there are Three Acts of the meeting, “pre-meeting”, “meeting”, and “post-meeting” and flex your facilitation skills during all Three Acts.</strong></blockquote><p>Looking to continue to level-up your Service Design game? Need motivation to dig into the abundant Service Design literature? Look no further than the SDTO book club! <a href="https://twitter.com/servicedesignto">Service Design Toronto (SDTO)</a> is a bi-monthly book club event organized in Toronto. The next <a href="https://www.eventbrite.ca/e/sdto-bookclub-4-with-jess-mcmullin-tickets-62290625939">event</a> is on 20 June, 2019.</p><p><em>Thanks to </em><a href="https://www.linkedin.com/in/jasonnoelking/"><em>Jason King</em></a><em> and </em><a href="https://www.linkedin.com/in/ken-kongkatong-55941980/"><em>Ken Kongkatong</em></a><em> for sharing their takeaways. A big thank you to the volunteers: </em><a href="https://www.linkedin.com/in/elena-glebkovskaya-98474223/"><em>Elena Glebkovskaya</em></a><em> and Ken Kongkatong for crafting this article and a special thanks to </em><a href="https://medium.com/@kwtaylork"><em>Taylor Kim</em></a><em> for her editing expertise.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a45d685c329f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-toronto/recap-sdto-book-club-event-2-with-marc-fonteijn-a45d685c329f">Recap: SDTO Book Club Event #2 with Marc Fonteijn</a> was originally published in <a href="https://medium.com/service-design-toronto">Service Design Toronto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping a service design book club]]></title>
            <link>https://medium.com/service-design-toronto/prototyping-a-service-design-book-club-b54db78556fb?source=rss----942b6d7df20b---4</link>
            <guid isPermaLink="false">https://medium.com/p/b54db78556fb</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[toronto]]></category>
            <category><![CDATA[tisdd]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[sapscenes]]></category>
            <dc:creator><![CDATA[Haley Anderson]]></dc:creator>
            <pubDate>Fri, 11 Jan 2019 15:42:36 GMT</pubDate>
            <atom:updated>2019-01-11T15:42:36.145Z</atom:updated>
            <content:encoded><![CDATA[<p>Happy New Year service design book worms! 2018 was a year packed with amazing growth for our community here in Toronto and across Canada. Some highlights (full disclosure, I may be biased): <a href="http://sdcanada.ca/">Service Design Canada</a> (SDC) successfully hosted <a href="https://impact.sdcanada.ca/">IMPACT</a>, its 3rd annual conference in Montreal with a new two day format of workshops and talks offered in two languages (woah), Canada’s first ever <a href="https://twitter.com/SDNCanada/status/1012666997182746624">industry benchmark survey</a> was launched (get ready for some sweet sweet data), Service Design Toronto (<a href="https://twitter.com/servicedesignto">SDTO</a>) had a comeback with a talk from the kind folks at <a href="https://www.eventbrite.ca/e/sdto-impact-by-design-the-prosper-lab-tickets-49067966609#">The Prosper Lab</a> and added new events like our lovely book club. So much community ❤</p><p><strong>If all of this is news to you, here is some background.</strong></p><p>SDTO, is an organization co-founded in 2014 by <a href="https://medium.com/u/e1e418dbca90">Linn Vizard</a> that works hard to foster the service design community here in Toronto. SDTO creates opportunities to explore, connect and satisfy service design curiosities and addictions. In addition to a revived bi-monthly speaker series, we have started a book club!</p><p><strong>Our origin story goes like this:</strong></p><ul><li><a href="https://twitter.com/arunmartin">Arun J M</a> dreamed of a way to share his love of reading and service design long before he moved to Toronto from Bangalore, India.</li><li>Arun noticed that I was slack-ing (the tech platform, not lazing about here) frequently in the Canada channel of SDN’s network while I was repping Service Design Canada as the 2018 conference coordinator.</li><li>A couple of coffees later, we joined forces with Linn and SDTO!</li><li>With her support, we pitched the book club idea to the community at the Prosper Lab talk and circulated a mini survey which helped us start planning the first event.</li></ul><h3>Test early, test often.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JI_VLXFJr3Rdyg1bdf0aUg.png" /><figcaption>Chapter 7: Prototyping Cases, This Is Service Design Doing</figcaption></figure><p>Less than a week after the IMPACT conference in Nov. 2018, we hosted our first book club meet-up (which was crazy because most of us still hadn’t done our laundry or groceries since returning from Montreal). It was an intimate crew of 9 (both IRL and virtual) at the Toronto Reference Library, an appropriate inaugural venue for the book club!</p><p>We discussed the Prototyping chapter from <a href="https://medium.com/u/de70410513fa">This is Service Design Doing</a> (TISDD), an appropriate reading to pilot for our first meet-up. We set the bar quite high with this first one having two guest speakers join us from Germany!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5dHhfndtI4Y3wqlF" /></figure><p><a href="https://medium.com/u/731ce9d28951">Markus Edgar Hormeß</a>, one of the actual-real-life co-authors of TISDD joined us from Berlin (midnight his time, thank you!) for a group Q&amp;A. Having been a student of Markus’ during a TISDD bootcamp in Amsterdam, I knew we were in store for an in-depth (and generous) chat! Our club shared some questions with him in advance to help guide the conversation.</p><p><strong>We asked: </strong>How do you go about handling the challenge of prototyping a service that takes place over a longer time span?</p><blockquote>There are some nice variants of theatrical tools like investigative rehearsals you might want to look into here e.g. talk throughs. Desktop walkthroughs are also an option. Get inspiration from how movies show a storyline along an extended time frame. Of course, it always depends a bit on how your actual structure of the service is (e.g. many small interactions all the time, or, a few big ones every year). -Markus</blockquote><p><strong>Key take-aways from Markus:</strong></p><ul><li>It’s normal to have a love/hate relationship with prototypes.</li><li>Justify prototyping costs over the cost of staff developing the product without user feedback.</li><li>Service design is a new language to the organization and should be reframed from an organizational perspective.</li><li>Pay attention to the first question that colleagues ask when they see a prototype.</li><li>Don’t attend meetings without a prototype!</li></ul><p>Don’t forget to check out the<strong> </strong><a href="https://www.thisisservicedesigndoing.com/methods"><strong>#TISDD Method Library</strong></a> for free resources and templates!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tFPx07hO3bgs5YOg" /></figure><p>Following our in-depth Q&amp;A with Markus, Karen Detken joined us for a run down of storyboarding with <a href="https://experience.sap.com/designservices/approach/scenes">SAP Scenes</a>. She created SAP Scenes as a way for those who aren’t as comfortable with drawing to participate freely in storyboarding and desk top walk-throughs. They are a great way to put the focus back on <em>what is happening</em>, rather than drawing something perfect. You can <a href="https://experience.sap.com/designservices/approach/scenes">download</a> and print the open source library of elements for free! Thanks Karen!</p><p><strong>Key take-aways from Karen:</strong></p><ul><li>Before prototyping, start with a story and ideate.</li><li>In the story, identify how a hero solves a problem.</li><li>SAP Scenes is a storyboarding toolkit to quickly communicate a story rather than spending time creating characters.</li></ul><p>Now, we wouldn’t be service designers if we didn’t put our words into action would we!? Check out this amazing scene created by some of our new book club pals! Can you guess what the service system was?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zVIQR-S6TOQN75Le" /></figure><h3><strong>For our first time running the book club, I must say it was not such a sh*ty first draft!</strong></h3><p>We learned a lot just from hosting the event. Thanks to all of the attendees who were able to join us in the discussion and stick around for the activity. We welcome any feedback and input you may want to offer to help improve future events. If you took any notes and would like to contribute to this event summary please add a response!</p><p><strong>What we think worked well:</strong></p><ul><li>Leaders: We had two kick-a** service design leaders join us to share their work and discuss their perspectives and journey’s.</li><li>Community: What a lovely intimate group discussion we had. It was amazing to meet some new community members and to see some friends come out.</li><li>Food: Snacks, we had ‘em! Drinks, you bet! Brainstorming supplies, oh ya. Single-use plastic, nada! #BreakFreeFromPlastic</li></ul><p><strong>What we learned:</strong></p><ul><li>Location: We need better way-finding… It turns out the basement room at the Toronto Reference Library is fairly hidden. Next time we will be sure that you have no troubles finding us, no matter where we meet.</li><li>Agenda:<strong> </strong>Our first event was ambitious. We may have overbooked by having two speakers. However valuable their part was, it would have been nice not to rush either conversation and to give some more relaxed time for open discussion amongst ourselves.</li></ul><p>That’s all for now folks! If you are interested in joining the book-club, simply follow us on <a href="https://twitter.com/servicedesignTO">Twitter</a> and <a href="https://www.eventbrite.ca/o/service-design-toronto-3326592276">Eventbrite</a> to keep an eye out for the next meet-up! We are aiming for the <strong>next one to be at the end of January</strong> and will announce the next reading #soon! If you would like to add suggestions to the <a href="https://docs.google.com/spreadsheets/d/12j1kAxeAMhTO1klmTi7riCRJpcCVlYJ6PrHvIh63KYE/edit?usp=sharing">reading list</a> or browse it for some inspiration, please do!</p><p><a href="https://twitter.com/hashtag/SDTObookclub?src=hash">#sdtobookclub hashtag on Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b54db78556fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-toronto/prototyping-a-service-design-book-club-b54db78556fb">Prototyping a service design book club</a> was originally published in <a href="https://medium.com/service-design-toronto">Service Design Toronto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>