<?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 CJ Hostetter on Medium]]></title>
        <description><![CDATA[Stories by CJ Hostetter on Medium]]></description>
        <link>https://medium.com/@chostett?source=rss-746a6c06f3fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_QeF3_3y6i7PLejr9UTQrw.png</url>
            <title>Stories by CJ Hostetter on Medium</title>
            <link>https://medium.com/@chostett?source=rss-746a6c06f3fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:21:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chostett/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[Design Matters Tokyo 2024: Sketchnote Edition]]></title>
            <link>https://medium.com/@chostett/design-matters-tokyo-2024-sketchnote-edition-3eb25f610793?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eb25f610793</guid>
            <category><![CDATA[sketchnote]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[graphic-recording]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 07:28:39 GMT</pubDate>
            <atom:updated>2024-08-28T07:28:39.193Z</atom:updated>
            <content:encoded><![CDATA[<p>In June, I attended <a href="https://designmatters.jp/">Design Matters Tokyo</a>. It was my first design conference in a while and I was happy to get back to sketchnoting talks throughout the day. Here’s three previews of talks I sketchnoted from from the event.</p><p>Many thanks to <a href="https://medium.com/u/6a548ce6f6c5">Leecy Li</a>, Yumiko Tanaka, and <a href="https://medium.com/u/b9caef738df0">James Reichelt</a> for sharing your insights.</p><figure><img alt="A sketch of a woman with red highlights in her hair. She is Leecy Li. A quote is next to her that reads, Every pixel is an opportunity to delight. She begins the talk, ‘I went from Motorola in China to Parsons in New York. Thinking about exhibition design in museums (my former job prior to Motorola) got me thinking about user centered design. I started working at Google. I went from everything being colorful…’ Image of people of varying shapes and sizes looking at a wall, ‘to boxes." src="https://cdn-images-1.medium.com/max/800/1*UWpg0NnEtVaogqcBJSDkxg.png" /></figure><figure><img alt="A handdrawn sketch of a Japanese woman wearing glasses. Text reads, ‘Vision Design: Four Steps of Future Foresight. First, researching the present. Then, formulating the hypothesis about the near future. Then verifying in the farther future. Last, creating a vision for the future. These are the steps Koel Design has taken in their recent design projects.’ Yumiko says." src="https://cdn-images-1.medium.com/max/800/1*syPPkpX4vpYJ00WPjB81kg.png" /></figure><figure><img alt="A sketch of a man wearing square glasses. He has a beard and his hair is tied into a bun. He starts, ‘This is a talk on inclusive design. I work at Smartbox. We create software and services that give disabled people a voice. Our platform is Grid. It is an alternative access method of voice generation linked to inputs that can be controlled through keyboards and eye trackers.’ There is a sketch of a grid device — a square touch panel with different types of icons on various buttons." src="https://cdn-images-1.medium.com/max/800/1*iDHygxWmVUFxuiEvFikzEw.png" /></figure><p>The full notes and more are available on <a href="https://chostett.com/blog/posts/2024-08-27-Design-Matters.html">my personal blog, chostett.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eb25f610793" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding a Home on the Internet]]></title>
            <link>https://medium.com/@chostett/finding-a-home-on-the-internet-9a27732da993?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a27732da993</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[capitalism]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[enshittification]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 03:25:32 GMT</pubDate>
            <atom:updated>2023-07-21T03:25:32.340Z</atom:updated>
            <content:encoded><![CDATA[<p>I was eleven when I made my first Angelfire site.</p><p>It’s still live on the archived internet. I’ll never tell you the URL, because my cringey middle school self, whom I love and cherish, does not need to bear the scrutiny of the modern public.</p><p>The site has the feel of a kid’s room; nothing matches and the only theme binding them together is, “CJ likes this.” It has images from TV shows and musicals I was into and pictures of my friends’ art, who I liked to hype.</p><p>It also has a “QUOTES ZONE.” I, like most teenagers, went through a phase where I found edgy or cool quotes in school reading, online sites, or inside jokes with my friends and thought, “ah, this <em>defines my essence,</em>.” Into the QUOTES ZONE they went.</p><figure><img alt="A pixellated screenshot of an Angelfire site." src="https://cdn-images-1.medium.com/max/800/1*O_FD3t9OBoffsHOEXF6CPw.png" /><figcaption>Not many people were brave enough to make their entire background chartreuse.</figcaption></figure><p>Over twenty years later, those quotes may not define me, but they symbolize a freeness to write down what I liked, even if it was weird, and what kind of people I idolized, even if it was a little cringey.</p><p>Overall, it was a personal place to me. Something that wasn’t <em>tailored to me,</em> but something I made my own.</p><h3>“They just don’t make ’em like they used to”</h3><p><em>“They just don’t make ’em like they used to,”</em> a research participant says. He’s sitting across from me in his car. I am interviewing him; I am asking him about his car and why he bought it. “I remember customizing my car with my dad. We made those cars to fit our dreams. There wasn’t anything on the market that was exactly what we wanted.”</p><p>I nod. His comment resonates with me. I’m a tinkerer, too. I don’t like “out of the box” things unless I’ve done a few modifications on them first. I can’t use a website template without digging into the code and adding in something unique.</p><p>“With these electric components I don’t do as much custom work. I break them, I void the warranty,” he continued. “I don’t really own that car, the maker does. I used to think affording a new car was my end goal, but nowadays…an older car I feel comfortable repairing is fine by me.”</p><p>Most online spaces like Instagram, Twitter, Medium and Tumblr feel like I’m renting, not owning. For the price of convenience and visibility, I’m giving up my rights to full customization and am restricted by their, and their hardware’s, Terms of Service. I am free to make myself at home…as long I abide by the contract rules and I don’t put holes in the wall.</p><h3>What changed?</h3><p>In the mid 00’s, I was happy to do just that. The online spaces made themselves welcoming, so I followed. But over time, the customization became meaningless, and the things I was writing or posting about to make my space feel like home became “content” and I became a “content creator.”</p><p>My friends became “my audience” and once-thoughtful comments were replaced with emoji reactions. I would try harder to get “engagement,” i.e. thoughtful comments by making more “content.” I can’t blame my friends for not reacting, though. When everyone’s a content creator, the world becomes a sea of things to react to. You get tired. You don’t have enough time. And Facebook built a convenient “like” button.</p><p>It wasn’t until recently that I realized platforms were trying to solve for issues they’d created themselves. If they put too much information in front of people, they would become overwhelmed and not comment. But people like comments, so they made a button that is an <em>easy comment</em> — a react. Most landlords’ end goals are not to help their tenants own a house; it’s for them to keep renting so that they will receive money.</p><p>And in this case, money is data, created by people but never owned by them.</p><p>Social media platforms like Facebook, Instagram, and Twitter made it easy for me to sign a contract. They encouraged me to “make a home” on the web, but just like renting, there is almost never a future where my home on social media can truly be <em>mine.</em></p><p>I wanted to reclaim that.</p><p>So I stopped updating my Twitter. I stopped using Medium. I started retreating to Discord, <a href="https://cohost.org/illuminesce">Cohost</a>, and recently, my personal blog.</p><p>It’s been strange having the code editor up instead of the post editor. And true, I’ve encountered much more friction in making my own spaces; it’s not as smooth or as easy a setup, but the end product is something that I feel proud of.</p><p>And I don’t feel pressured to post as much. It’s nice to not have that anxiety in the back of my head; that I <em>need</em> to capture the moment to show it. If I do snap a photo, I share it on Discord, or Slack, or LINE, or one of the many direct messaging channels I have now.</p><p>I still keep a presence on <a href="https://twitter.com/playterranova/">Twitter for Terranova</a>, and check my personal/professional Twitter from time to time, but mostly for direct messages.</p><p>This space may not be 100% mine — it still is hosted on neocities’ and GitHub’s servers, but it feels more like my home on the internet many years ago — moreso than it ever has.</p><p>That is what is most important to me right now; to feel like I am making a space, not having the space tailored to me. My desire for ownership now outweighs my desire for convenience.</p><h3>Twitter is my local mall</h3><p>Watching people leave Twitter has been, for me, like watching my local mall shut down. I spent my days in that mall and ran into a lot of people I knew or became friends with, despite the mall’s purpose being commerce. I feel sad to let that go.</p><p>When I was a teenager, I was part of the mall rats that would hang out in the mall for hours and hours; not buying anything but hanging out in the Sharper Image until they told us to leave. Somehow, us kids were able to squeeze out our own meaning from a place that wasn’t meant for us, and that itself was meaningful.</p><p>But it <em>was</em> a shopping mall. And Twitter <em>is</em> a platform whose survival depends on monetization. A shopping mall, and Twitter by extension, isn’t defined by the amount of new friends and connections made there, it’s whether or not businesses survive. And if they don’t, the mall dies. This was always true, but for a while we fooled ourselves into thinking we owned the mall.</p><figure><img alt="An image of a concrete building in front of a parking lot. The signs are faded and there is a signboard that says, “For Lease.”" src="https://cdn-images-1.medium.com/max/800/1*auBJzJUKX_bnSr4gFpfBqQ.png" /><figcaption>What my local mall looks like now. (via commercialcafe.com)</figcaption></figure><h3>Public libraries of the internet</h3><p>Rather than saying “good riddance” or mourning the loss of large-scale platforms on the internet, this is a moment for me to reflect on how sustainable it really is to build spaces on the internet that are commerce-first, people-second.</p><p>Commerce-first spaces, like malls, ensure that the space will only survive as long as the businesses survive. If community meetups are happening here, their presence are precariously balanced on the decisions of the mall executives. If the execs make a mistake in putting unprofitable businesses in the mall, then the mall will fail and the place the community had dissolves.</p><p>Libraries are a great example of people-first spaces. Most of the time they are funded by the government, for use by the public. Their survival is dependent on donations from the community and the community <em>coming to</em> and <em>making use of</em> their public services.</p><p>The good news is, there are a few people-first spaces already on the web, and they’re mainly non-profits, not government. <a href="https://www.wikipedia.org/">Wikipedia,</a> <a href="https://archive.org/">The Internet Archive,</a> and <a href="https://www.transformativeworks.org/">The Organization for Transformative Works</a> continues to break ground in this space.</p><p>Another option is for for-profit places on the internet to be run by small, sustainable teams and their business models to be transparent to users so it is clear what will and will not allow the business to succeed. I’m personally biased towards <a href="https://cohost.org/">cohost,</a> which has been initially self-funded and is using a subscription model. Or <a href="https://www.dreamwidth.org/">Dreamwidth,</a> which has been run by a small crew of people for many, many years. Denise, one of the founders of Dreamwidth, has <a href="https://synecdochic.dreamwidth.org/786741.html">some of the most helpful reading</a> on understanding Terms of Service agreements on modern websites.</p><p>I have a lot more to learn in this area. I’ve been looking to people who have been in the guts of the Internet far longer than me for information on how to reclaim my own home, and also to marginalized communities, who are concerned with the <em>usability</em> and <em>personal safety</em> of a site over, say, the ability to appear smart or hacker-ly.</p><p>It’s been an interesting journey to venture from my old, mismatched Web 1.0 site, into the shiny high-rises of Web 2.0 to settle into a home of my own. I once was a kid who spent hours in the library. As a young adult, I thought I’d grown out of the library. But I’ve returned, now older and bolder.</p><p>I want a happy ending to this story, but the future is still so uncertain. For now, I’ve been enjoying myself. I used to think having a sleek, modern website was a goal, but nowadays…what I feel comfortable I can repair is fine with me.</p><p><em>The original is </em><a href="https://chostett.com/blog/posts/2023-07-01-Finding-a-Home-on-the-Internet"><em>on my personal blog for free.</em></a><em> If you like the stuff I write, consider </em><a href="https://ko-fi.com/illuminesce"><em>buying me a coffee.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a27732da993" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I left work to take a sabbatical.]]></title>
            <link>https://medium.com/@chostett/i-left-work-to-take-a-sabbatical-3280ed24ae25?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/3280ed24ae25</guid>
            <category><![CDATA[sabbatical]]></category>
            <category><![CDATA[hustle-culture]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Mon, 23 Jan 2023 23:02:33 GMT</pubDate>
            <atom:updated>2023-01-23T23:02:33.527Z</atom:updated>
            <content:encoded><![CDATA[<p>Starting at the end of this month, I’ll be leaving my job.</p><p>I have a hard time saying out loud I’m taking a break. I find myself thinking <em>“if I loved my job, I wouldn’t need it. If I take a break, it means I’m changing careers, or spinning up a new money-making venture.”</em> Younger folks and non-Americans tend to have less of this productivity-imposed guilt. They believe it’s better to live practically and sustainably than to be submerged underneath sinking systems that already need tearing down.</p><p>“Hustle” was what defined and drove my early career; it pushed me through school, and made me ambitious and bold. It’s hard for me to let it go; it’s an old friend of mine. I’ve experienced so much, good and bad, from “hustling” — from working hard past my limits.</p><p>I’m comfortable with the hustle.</p><p>Five years ago, I was sitting across from my partner, whom I had married less than two years ago. He was shaking his head. “This is crazy,” he mumbled. “There’s no reason we should move to Japan.”</p><p>“Are we happy here?” I asked.</p><p>“We have friends and family here.”</p><p>“So we’re <em>comfortable.</em> Is that happiness for you?”</p><p>He thought for a long while. And then he said the second most important “yes” in our relationship.</p><figure><img alt="Passport next to a cream cheese and salmon sushi roll." src="https://cdn-images-1.medium.com/max/650/0*z7QKsVkLvkPIv4vr.png" /><figcaption>Our last meal before we left. No cream cheese sushi in Japan.</figcaption></figure><p>Five years later. We miss our people back home dearly. But we don’t miss the day-to-day of living in the States. We have warm dinners and new recipes, international friendships, new communities, and a house we never thought we’d be able to own.</p><p>We even <em>look</em> like different people. We’re happier, healthier, and more confident. And we aren’t “comfortable” — at least, in the stagnant sense of the word. We’re always moving, always experiencing new things; always able to step into our comfort zone as we need it. The bold risk we took made our lives exponentially better — moreso that we thought it would.</p><p>Two years ago, I was having coffee with a colleague of mine. They asked me what it’s like working for my current company.</p><p>“It’s nice,” I say, “My coworkers are great.” I pause. They looked earnestly at me.</p><p>“And…?” They sensed there was something more I wanted to say.</p><p>There it was again. The feeling of <em>comfort.</em> It wasn’t a bad feeling, but it didn’t feel good, either. After we finished our coffee I wandered back to the train station and thought about that pause.</p><p>I could change jobs, but would have the same issue; the skills I want to stretch are sometimes aligned with my career, but sometimes they aren’t. I realize I’ve settled, once again, into a valley of comfort. Am I happy?</p><p>Can I <em>be</em> happy with comfort?</p><p>For some people I know and respect, it is enough. My aunt lives in the same town she was born in and has family living nearby. She’s happy with how things turned out. I’ve dated, and subsequently broke up with, people before who find comfort to be, well, <em>comforting.</em> If I’m honest, I envy them — they cultivate deep roots and can talk about the history of their hometown like an anthropologist because they’ve directly experienced it all.</p><p>But their happiness isn’t my own. I enjoy “shaking things up,” and my long-standing friends and family are, without fail, in for the ride with me.</p><p>From the outside looking in, my partner is a reserved man. To me, he’s quick-witted, bold and crazy like me. Which is why when I told him about this <em>feeling</em> I had, he threw my words back in my face.</p><p>“Are you happy there?”</p><p>“It’s crazy,” I said. “My coworkers are great. I love design — I love my career.”</p><p>“But are you happy?”</p><p>“I’ve only known hustle. I’ve never taken a sabbatical before.”</p><p>“Sounds like you need a change.”</p><p>And so the student became the master, and the master the student. I’m deeply grateful to him for his support. It is the greatest gift we can give each other — time to rest, reflect, learn and grow.</p><p>I’m starting off with a deep dive into <a href="https://www.renpy.org/">Ren’Py</a>, a visual novel maker. I’ve created prototypes before, but I’m looking to make something with a bit more polish and love than my previous games. Will it be marketable? I don’t know. Will it be fun? Absolutely.</p><p>I’ve also <a href="https://www.instagram.com/p/ClXmOLcJIM_/">slowly built up skill as a glassblower since mid-2021</a>, and I’ve gained enough confidence to create more complex pieces. I’m looking to grow more and make things that are intricate and beautiful.</p><p>As far as work is concerned, I’m putting it on hold to pursue other things. I won’t be considering active contracts until July.</p><p>I’ll be using my <a href="https://chostett.com/">personal site</a> and <a href="https://illuminesce.cohost.org/">cohost</a> to document my learnings. I hope it serves as a moment I, and other folks can look back on fondly. I have a general direction on where I’m going but the route I’m taking is winding and unknown. I can only hope that something good will come from it.</p><p>Ah, hustle, my old friend. You’re whispering in my ear, asking me to close this entry with promises a Patreon or Substack, to <em>engage</em> my readers. But I don’t know where this experimentation will take me. I’m tired of the comforting pattern of making a thing marketable. I’m ready to experiment.</p><p>So here I am. Tired of comfort, a little crazy, a little bold, stepping off the cliff, scared of the height, hopeful it will lead to things I can’t otherwise imagine.</p><p><em>(Originally posted to my personal site, </em><a href="https://chostett.com/"><em>chostett.com</em></a><em>, which I’ll be moving to for writing.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3280ed24ae25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I made a design division within an agile company.]]></title>
            <link>https://medium.com/yamaneco/why-i-made-a-design-division-within-an-agile-company-8bf9a2e08d4e?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bf9a2e08d4e</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 07:29:09 GMT</pubDate>
            <atom:updated>2023-06-28T02:18:02.575Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is an English translation of the original Japanese talk, 「どうしてアジャイル会社でデザイン部が必要なのか？」presented at <a href="https://2022.scrumgatheringtokyo.org/">Regional Scrum Gathering Tokyo 2022</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UnvtEErsxJJbwX-5aXLDA.png" /><figcaption>Why I made a design div. within an agile company.</figcaption></figure><p>Good afternoon, everyone. Thank you for coming to my talk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nMN8oNMuHPSw3GdKUNuDA.png" /><figcaption>A photo of CJ. Previous work includes frog design, Goodpatch, and yamaneco.</figcaption></figure><p>Allow me to introduce myself. My name is CJ. I use they/them pronouns. I have been doing UX design for over nine years. I now work at <a href="https://www.yamaneco.co.jp/">yamaneco</a>, an agile startup as the Head of Design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIr4OR8eKsTEZfPgs27IIw.png" /><figcaption>Hobbies: glassblowing, indie game development, and taking photos of my cat.</figcaption></figure><p>I have a few hobbies. <em>(laughs)</em></p><p>I do glassblowing, and I’m making a visual novel called Terranova that will be releasing on Steam this year. I also like taking photos with my adorable black cat.</p><p>You probably can tell just by looking at me, but I’m from the U.S. Japanese is not my native language. I’m also not a scrum master or an agile coach — I’m a designer. So why am I here in front of you speaking Japanese?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crrOx_X1NhsFQLNQu0X6hw.png" /><figcaption>In order to bring the worlds of agile and design closer together, we must adopt a new language and new POVs.</figcaption></figure><p>Because I want others to do the same. Even if it’s difficult, even if we make mistakes, to bring the worlds of agile and design closer together, we need to change both our words and perspectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_6ejwu6fquS1o5mgF3kVQ.png" /><figcaption>“Agile and design will never get along.”</figcaption></figure><p>This is what I thought before I joined yamaneco. To understand how I got from those words to today, let me tell you a story. Previously, I worked at an international design agency by the name of frog. I used to harshly criticize high level executives’ software and products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G387wnWkW5fovUgYvjVkWg.png" /><figcaption>“Your product sucks.”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnZiVp1wItZbNntG_ar6GA.png" /><figcaption>“You need design to fix it.”</figcaption></figure><p>“Your product sucks,” I’d say, “You need design to fix it.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4qsH21IhGQfDZySQxZ87cg.png" /><figcaption>Scrum and Design: Backlogs versus the customer voice.</figcaption></figure><p>Every problem could be solved with design, I thought. Our clients looked to their backlogs for decision-making, not the customer’s voice or the product vision. Because I saw them say they wanted to improve their customer experience but give up because of tech restrictions, I also harshly criticized both scrum and agile.</p><p>From the outside, I mistook agile and scrum’s purpose as “just to make a backlog.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBuWQPMwqthZ7jv9jxpJ7g.png" /><figcaption>Why did I harshly criticize scrum and agile?</figcaption></figure><p>So, why did I so harshly criticize scrum and agile?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KR-T2HpZvLZ0Fw9HE-r_TA.png" /><figcaption>Photos of our product team. Emojis added to protect privacy.</figcaption></figure><p>In 2017, I jumped from outside of product development to inside. Where I previously viewed developers with coldness, I began to empathize with my team’s struggles and worries. I started to understand that scrum and agile were not the same thing, and their intrinsic value. I wanted to integrate the design process that I learned at frog with the scrum framework we were using as a team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJUrBZ6tMGkMeT1sECG5eA.png" /><figcaption>The design process and scrum events don’t agree on what is a team decision and what is an individual decision.</figcaption></figure><p>But there was one problem. The design process and scrum events don’t agree on what is a team and what is an individual decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v2KVSqyuWPRN2U04IwUk4Q.png" /><figcaption>The double diamond, a framework used by many designers.</figcaption></figure><p>I’d like to introduce the double diamond, a framework used by many designers. In order to make a product that solves users’ needs, we use the process of divergence and convergence to first understand the problem and then to find a solution. Because this is a framework, consider this similar to scrum, not agile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HeTvUXs5rdbKAeTk9bE5Iw.png" /><figcaption>Divergence in the double diamond.</figcaption></figure><p>In divergence, in order to generate new information and ideas, we take a few options and increase them. From this divergence, new ideas are born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiYiTQNSJCDvUVhenW9vtw.png" /><figcaption>Examples of divergence might include: customer research, persona creation, brainstorming ideas for new features, imagining what the product might look like in five years, etc.</figcaption></figure><p>An example might be drawing application screens on a whiteboard before developing a feature. Typically in scrum, this kind of divergence is done between the PO and the designer and then the result of the brainstorming is talked about in the sprint planning or the sprint demo. In scrum, the word “developer” is used to include both engineers and designers, but in the product world, there still remains the thinking that a developer’s role is “to write code” and a designer and PO’s role is “to create ideas.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfEeBULNmZEHPXNLpq7KvQ.png" /><figcaption>Divergence in the scrum team is done only between the designer and the PO; in the design process it is done with the whole team.</figcaption></figure><p>An example might be drawing application screens on a whiteboard before developing a feature. Typically in scrum, this kind of divergence is done between the PO and the designer and then the result of the brainstorming is talked about in the sprint planning or the sprint demo. In scrum, the word “developer” is used to include both engineers and designers, but in the product world, there still remains the thinking that a developer’s role is “to write code” and a designer and PO’s role is “to create ideas.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yBCbf5IkJhDI6DKN5zIZAg.png" /><figcaption>Convergence in the double diamond.</figcaption></figure><p>In convergence, in order to decide and prioritize, we take many options of ideas and information and reduce them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Yphz2l4TYFwcIrGgPTX5A.png" /><figcaption>Some examples of convergence include: user story mapping, backlog prioritization, and deciding on ideas for a new feature, etc.</figcaption></figure><p>For instance, when prioritizing the backlog, we collect user stories, and from those stories we pick up ones to focus on, and then decide what stories to work on in the next sprint. In teams that I have observed, everyone participates.</p><p>Why is that?</p><p>Well, one reason is because in order to converge on the right items, we need the estimation and the technical opinion of the developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ikg9_pgLd6kdVkr-bi7W-A.png" /><figcaption>In scrum teams, convergence is done as a team, whereas in design, convergence is done primarily alone or in pairs.</figcaption></figure><p>By the way, in order to make a strong design that has a consistent vision, has validated user needs and is easy to understand, designers diverge and converge many, many times. In order to do this, feedback and critique is necessary. It is best to have design critique either once per day or once per every two days. If the designer is receiving feedback once a week, or once every two weeks, from a design perspective, the process is moving too slowly.</p><p>In scrum, typically sprints are two weeks, where the team showcases their work in a sprint demo, but there isn’t much time to dive into thoughtful conversation. So, how do we make this kind of space?</p><p>These kinds of issues came up over and over again within our product team. Even if we tried to integrate, even if our scrum and our design’s vision was in agreement, if we could not agree on who decides what, we struggled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9P-A7CoGkuHm5atDgvQww.png" /><figcaption>Learnings from coaching design within agile teams.</figcaption></figure><p>Can I make a confession?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Oeirz4khdKsTnev68q9kQ.png" /><figcaption>Mostly, I complained about scrum.</figcaption></figure><p>Even though I was within the product team, I still didn’t know how to solve these issues. One day, an agile coach from a company called yamaneco came to our team. When they did, mostly I complained about scrum. We fought a lot.</p><p>When I quit the product team, yamaneco reached out again with a proposal for me to join them.</p><p>“Why would you ask me to join? All I did was fight with your agile coach…”</p><p>“That’s exactly the reason why we think you can integrate design and scrum.”</p><p>“What??”</p><p>So, the designer who thought integration was probably impossible joined yamaneco. I found that designers in agile teams also struggled with the same things I did. Next, I’ll share what I learned in working with and coaching these teams.</p><h3>Even though design is collaborative work, most product designers are alone.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOuNTnWGOjDQvwSW1mLO1w.png" /><figcaption>Even though design is collaborative work, most product designers are alone.</figcaption></figure><p>For the past two and a half years, I was yamaneco’s only designer. I did everything alone. Customer hearings, idea generation, decision-making — everything was done on my own. In most of the agile teams that I coached, there was only one designer on the team. Most designers I spoke to gave up long-term design work such as making pattern libraries to focus on short-term work like exporting assets for the team’s engineers. Just as technical debt accumulated, so did design debt grow larger and more unmanageable.</p><p>In order to balance the load of short-term and long-term design work, it is important for the team to collaborate together. Brainstorming, idea generation, and feedback on sketches and mockups is not just the PO’s responsibility, but the entire teams. As I mentioned before, it is best to have design critique either once per day or once per every two days. It is impossible for one designer to critique their own work with that frequency alone.</p><h3><strong>In order for conflict to safely occur, it is necessary to have psychological safety.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*prcwgfpVlZe1w7D-5bSfQw.png" /><figcaption>In order for conflict to safely occur, it is necessary to have psychological safety.</figcaption></figure><p>In order for convergence to happen, the team must be able to safely have conflict, which means they need psychological safety. It is normal in convergence for ideas to clash and for debates to happen, and so, if the team does not have the necessary psychological safety to do that, the design will be blocked.</p><p>For instance, in one team that I coached, there was a lone designer who would always converge on decisions on his own. When a decision involving the design needed to be made, he would not involve the team. During sprint planning, he told the team he was blocked and needed to converge on an idea. However, the team didn’t trust him and didn’t want to be made to feel stupid, so no one offered up their opinion. The task was stalled, and because the designer was frustrated that no one spoke up, the team started to fight.</p><h3><strong>Throwing away everything to make a new framework is scary.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68Gx38WKu1-gPtl1oSA-ew.png" /><figcaption>Throwing away everything to make a new framework is scary.</figcaption></figure><p>When I first began coaching on design and scrum integration, one of my teams was having a conversation around “throwing away scrum.” They said they were scared to throw away the entire scrum process they had worked so hard to learn.</p><p>But what if we tried another framework rather than throwing everything away?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-qjmJU53ZO1VPBRHnocDZA.png" /><figcaption><a href="https://www.mobiusloop.com/">Mobius Loop</a>, a framework that integrates design thinking and agile principles.</figcaption></figure><p><a href="https://www.mobiusloop.com/">Mobius Loop</a> is a framework that combines both agile principles and design thinking. Discovery, Ideation, Picking Options, Measuring Impact, Learning — all of these phases are summarized in an easy-to-understand process. Mobius Loop looks at first blush like the double diamond, but also includes important points that the double diamond does not, such as integrating learnings into new, interesting ideas.</p><p>yamaneco proposed this framework to the team, and their initial fears turned into a lively conversation. They compared Mobius Loop to their current processes, and talked about what parts they wanted to add, what parts they wanted to improve, and what parts they wanted to throw away entirely. This is just an example of one such framework. You can make your own framework to meet the needs of your unique team!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_6ejwu6fquS1o5mgF3kVQ.png" /><figcaption>“Agile and design will never get along.”</figcaption></figure><p>I thought this once. And I am happy to say that I was wrong. I am thankful to both my coworkers at yamaneco, and for our wonderful clients for teaching me this.</p><p>Before, I harshly criticized scrum and agile because I didn’t understand it or the jobs engineers were doing.</p><p>But now I will criticize scrum and agile for the exact reason that I understand this world if only a little, and that I love it. In order to make a strong design, it is important to critique it. Up until now, conversations around integrating scrum and design have been about “how to integrate design without massively changing scrum” or “how to include scrum events in our pre-existing design process.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zqcqFQS0CnsCIQmTC3PHAQ.png" /><figcaption>So why did we make a design division within our agile company?</figcaption></figure><p>This, I think, is wrong.</p><p>Is anyone here married?</p><p>This year will be my seventh-year anniversary. <em>(applause)</em></p><p>Aw, thanks. <em>(laughs)</em></p><p>Before that, I perhaps thought, “I won’t have to change my lifestyle or my opinions, and my partner and I will always be lovey-dovey.” But we all know that’s not realistic, right? My partner and I are two different people. It’s normal for our opinions to clash or for us to have conflict. That’s why we create psychological safety around that conflict, try our best to understand each others’ feelings, and even if it is hard, or even if we are scared, we walk forward together, with our eyes open.</p><p>Scrum, agile and design can be married, too — but it’s not always going to be lovey-dovey. Conflict is naturally going to happen, so even if we’re scared, why not just do it?</p><p><a href="https://www.yamaneco.co.jp/design-at-yamaneco/">We do this kind of coaching in the design div at yamaneco.</a> And this is the reason why I created a design div within an agile company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Icpe5-txcwkaP8Bkh3NqQw.png" /><figcaption>yamaneco’s Twitter is <a href="https://twitter.com/yamaneco_agile">@yamaneco_agile</a>, and my Twitter is <a href="https://twitter.com/chostett">@chostett</a>.</figcaption></figure><p>If you listened to this talk and thought, “I want to try the Mobius Loop framework,” or if you are interested in design thinking in your own process — even better, interview a designer. Or if you want to throw everything away and make something new, do it.</p><p>Even if we fail, if we grow, we will be stronger — together.</p><p>Thank you very much.</p><p><em>If you’d like to work with yamaneco on bilingual (Japanese and English) design thinking and agile integration in your organization in Tokyo, get in touch </em><a href="/service/mailto:hello@yamaneco.io"><em>via email</em></a><em> or </em><a href="https://twitter.com/yamaneco_agile"><em>Twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bf9a2e08d4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/why-i-made-a-design-division-within-an-agile-company-8bf9a2e08d4e">Why I made a design division within an agile company.</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[どうしてアジャイル会社でデザイン部が必要なのか？]]></title>
            <link>https://medium.com/yamaneco/%E3%81%A9%E3%81%86%E3%81%97%E3%81%A6%E3%82%A2%E3%82%B8%E3%83%A3%E3%82%A4%E3%83%AB%E4%BC%9A%E7%A4%BE%E3%81%A7%E3%83%87%E3%82%B6%E3%82%A4%E3%83%B3%E9%83%A8%E3%81%8C%E5%BF%85%E8%A6%81%E3%81%AA%E3%81%AE%E3%81%8B-310bb8723754?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/310bb8723754</guid>
            <category><![CDATA[デザイン]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[アジャイル]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 07:28:45 GMT</pubDate>
            <atom:updated>2022-01-07T07:28:45.909Z</atom:updated>
            <content:encoded><![CDATA[<p><em>この記事は、</em><a href="https://2022.scrumgatheringtokyo.org/"><em>Regional Scrum Gathering 2022</em></a><em>のために私が行ったトークを参考にしています。</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LdgbzWKVlYA-copf-XTLg.png" /><figcaption>どうしてアジャイル会社でデザイン部が必要なのか？</figcaption></figure><p>こんにちは、皆さん。トークにお越しいただきありがとうございます。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nMN8oNMuHPSw3GdKUNuDA.png" /><figcaption>CJの写真。前職はfrog design, Goodpatch, yamaneco.</figcaption></figure><p>まずは自己紹介をさせていただきます。シージェと申します。9年以上UXデザインとして仕事をしています。今は、デザイン部長として<a href="https://www.yamaneco.co.jp/">yamaneco</a>と呼ばれるアジャイルスタートアップで働いています。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIr4OR8eKsTEZfPgs27IIw.png" /><figcaption>趣味：吹きガラス、インディーズゲームを開発したり、猫ちゃんと写真を撮る。</figcaption></figure><p>趣味は、色々ありますね。（笑）</p><p>吹きガラスをして、ビジュアルノベルを開発しています。今年でスチームにリリスしたいと思います。後は、私の可愛い猫と一緒に写真を撮るのは好きです。よろしくお願いします。見た目から分かると思いますが、私はアメリカ出身なので、日本語は母国語ではありません。そして、職業はスクラムマスターでもアジャイルコーチでもなく、デザイナーです。</p><p>なぜ、私は外国語を話すことにしたのでしょうか？</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZO7pP10QJh6povfLcTtSg.png" /><figcaption>アジャイルの世界とデザインの世界を近付かせるために、新しい視点と言語を取り入れてみたいのです。</figcaption></figure><p>それは、より多くの人に同じことをやってほしいからです。たとえ難しくても、間違えても、アジャイルの世界とデザインの世界を近付かせるために、新しい視点と言語を取り入れてみたいのです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1y5C0Z9mNSnz9TzaW6LreQ.png" /><figcaption>「アジャイルとデザインは絶対にうまくいかない。」</figcaption></figure><p>私がアジャイルスタートアップに入社する前にそう思っていたこと。その思いから今までどうやってここにたどり着いたかを理解するために、ストーリーを語ります。以前、frogと呼ばれる国際的なデザインエージェンシーで働いていました。私は、グレーのスーツが着ている社長のプロダクトを厳しく批判しました。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DApyjnvFV0tE30d3YotJqA.png" /><figcaption>「あなたのプロダクトは最悪だ。」</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7jvPYU8Uh9Z1F7JL6fV-MA.png" /><figcaption>「デザインの力が必要。」</figcaption></figure><p>“Your product sucks,” と言いました。 “You need design to fix it.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Al2jwbY3omlDMf6946lowA.png" /><figcaption>スクラムとデザイン：バックログvs.お客さんの声</figcaption></figure><p>全ての疑問は、デザインによって解決できると思いました。クライアントは顧客の声やビジョンではなく、バックログを意思決定の北極星として指さしました。顧客の体験を改善しようと思ったら、プロダクトの技術的な制限があり、諦めるので、スクラムもアジャイルも厳しく批判しました。</p><p>外から見ると、「スクラムとアジャイルの目的はただ機能のバックログを作ることだけだ」と誤解されていました。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dwwx3MgtKL9TPP81gy_g2Q.png" /><figcaption>なぜ、スクラムとアジャイルを厳しく批判したのか？</figcaption></figure><p>では、なぜスクラムとアジャイルを厳しく批判したのか？</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1L5isxO0RuYD1rTd2XDOHg.png" /><figcaption>プロダクト開発のチームの写真。プライバシー保護のため、絵文字を追加しました。</figcaption></figure><p>２０１７年、プロダクト開発の外から中へ飛び込んできました。以前冷たい目で見ていた私は開発者の苦労していること、不安を感じていることについて、共感し始めました。スクラムとアジャイルは違うと分かって来て、価値を理解し始めました。frogで学んだデザインプロセスや、開発者が使用しているスクラムを総合したいと思いました。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S5DAAjdDCMm9xHI8-YK6oQ.png" /><figcaption>何がチームで、何が個人の判断なのか、デザインプロセスとスクラムイベントは一致しないのです。</figcaption></figure><p>でも、一つの問題がありました。何がチームで、何が個人の判断なのか、デザインプロセスとスクラムイベントは一致しないのです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odl7oZGeHvaTLW4BvJD7FA.png" /><figcaption>デザイナーが主に使っているフレームワークのダブルダイヤモンド。</figcaption></figure><p>デザイナーが主に使っているフレームワークのダブルダイヤモンドを紹介したいと思います。ユーザーのニーズを解決するプロダクトを作るための疑問を理解し、疑問を解決するために必要な、発散と収束を表しています。</p><p>フレームワークですので、スクラムと同じように考えてみてください。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVQuimnEGIIm4f-l6QqT9Q.png" /><figcaption>ダブルダイヤモンドの発散。</figcaption></figure><p>発散とは、新しい情報を得て、新しいアイデアを作ることであり、いくつかのオプションを取り、さらに追加していくことです。そうすることで、新しい可能性を思い描くことができるのです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqNfkL0u0jLEef6w7xfQOQ.png" /><figcaption>発散の例：<strong> </strong>顧客との対話とペルソナ作成、新機能のためのブレインストーミングセッション、<strong>5</strong>年後の製品を想像する、等。</figcaption></figure><p>例えば、機能を実装する時に、ホワイトボードでいくつかのアプリ画面を書き出します。このような時に、発散はスクラムイベントの外でPOやデザイナーと一緒に考えられていて、スプリントデモやプラニングの結果について話します。スクラムの「開発者」の言葉は、エンジニアだけではなくて、デザインにも含まれてますが、プロダクト開発の世界の中では開発者の役割は「コードを書く」ということ、そしてPOとデザイナーの役割は「案を描き出す」という考え方があります。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfEeBULNmZEHPXNLpq7KvQ.png" /><figcaption>例：スクラムチームでは、発散は個人の判断、デザインプロセスではチームの判断。</figcaption></figure><p>そういう考え方をチャレンジしたいと思います。デザインはフィードバックに大きく依存しているので、デザイナーが一人しかいない場合、顧客や他のチームメンバーからのインプットがないと行き詰まってしまいます。発散は、異なる分野の人が複数参加することで、革新的なアイデアが生まれる可能性が高まるというメリットがあります。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zCmjCeBaEl_D6epQ7MByzA.png" /><figcaption>ダブルダイヤモンドの収束。</figcaption></figure><p>収束とは、意思決定と優先付けのことで、得たアイデアや情報など多くのオプションを取り込んで、減らしていくことです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0a6FqPRHErreDxRhF4kimQ.png" /><figcaption>発散の例：<strong> </strong>ユーザーストーリーマッピング、バックログの優先付け、新機能のアイデア決定、等。</figcaption></figure><p>例えば、バックログを優先付ける時に、ユーザーストーリーを収集し、その中から注目すべきものをピックアップし、スプリントに何か中心すべきなのかを決定する。私が観察したチームでは、全員参加します。なぜでしょうか？収束が必要な事象は、決める前に開発者の見積もりと意見を聞かせていただきたいからと言うことは一つの理由です。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ikg9_pgLd6kdVkr-bi7W-A.png" /><figcaption>例：スクラムチームでは、収束はチームの判断、デザインプロセスでは個人の判断。</figcaption></figure><p>しかし、デザインプロセスでは、デザイナーがチームにヒアリングして、一人か二人で収束することは多いです。なぜなら、デザインでは、チームの合意よりも、プロダクトに対する一致されているビジョンが評価されるからです。収束する時に、意見がぶつかり、難しい会話が必要になります。同意しない、討論する、そしてコンフリクトが行うまでするのは普通です。そうしないと、プロダクトの範囲が広がり、プロダクトビジョンが見えなくなってしまいます。収束に関わる人数が少なければ少ないほど、難しい会話は短くなるので、デザイナーが大部分を担当しています。</p><p>ちなみに、強いデザイン、つまり、プロダクトビジョンに一致している、ユーザーニーズに検証していた理解しやすいデザインを作るために、何回も何回も収束と発散をします。そのために、フィードバック、それと批評が必要になります。デザイン批評は、1日1回から2日に1回がベスト。もし1週間に1回、2週間スプリントが1回しかフィードバックを頂かなければ、デザイン的には遅いです。</p><p>スクラムでは、２週間スプリントに別れ、レビューに出来上がったものをデモしますが、あまり思いで深く話せる時間がありません。では、どうやって時間を作るのでしょうか？</p><p>入っていたプロダクトチームの中でこの問題が何回も出てきました。何回も統合してみても、スクラムとデザインのビジョンが合わせても、誰が何をするのかを一致しないと、困ります。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56uz1R7DeymkL4838A6akg.png" /><figcaption>アジャイルチームでデザインコーチングからの学び。</figcaption></figure><p>告白してもいいでしょうか？</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Oeirz4khdKsTnev68q9kQ.png" /><figcaption>以前、私は文句を言うばかりでした。</figcaption></figure><p>プロダクト開発チームで、私はまだどうやって解決するのか分かりませんでした。ある日、yamanecoと呼ばれる会社から来たアジャイルコーチが入ってくださりました。そのときに、私は文句を言うばかりでした。そのアジャイルコーチとよく喧嘩をしました。</p><p>プロダクトチームをやめた時に、yamanecoから「ジョインしてみないか」ということを提案されました。</p><p>「なぜ、私にお願いしているの？以前、アジャイルコーチと喧嘩したこともあるのに、、」</p><p>「だからこそ、あなたはデザインとスクラムを統合できると思います。」</p><p>「は？」</p><p>そして、統合するのは多分無理と思っていた私がyamanecoに入社しました。でも、他のアジャイルチームとデザイナーは私と同じようなことに困っていると理解しました。コーチングから来た学びを次に共有したいと思います。</p><h3><strong>デザインが協力的な仕事ですが、主にデザイナーは一人で働く。</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xOhftRGrTdKsnWdIgPctRw.png" /><figcaption>デザインが協力的な仕事ですが、主にデザイナーは一人で働く。</figcaption></figure><p>私は2年半の間、yamanecoの唯一のデザイナーでした。、何でも一人でやっていました。一人で顧客のヒアリング、案出し、決定。私が関わってきたアジャイルチームの大半は、デザイナーが一人しかいません。主なデザイナーはパターンライブラリを作るような長期的な仕事を諦めて、画像をエクスポートするような短期的な仕事が中心でした。そうすると技術的負債のような「デザイン負債」がだんだん増えて行きます。</p><p>短期的な仕事と長期的な仕事のバランスを保つため、チームの協力が必要です。ブレインストーミング、案を描き出す、デザイン画面を批評することは、POの責任だけではなくて、皆の責任です。先に言いましたが、デザイン批評は、1日1回から2日に1回がベスト。一人のデザイナーはその頻度で自分の作業を批評するのは無理です。</p><h3><strong>コンフリクトが安全に行うために、心理的な安全性が必要。</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*prcwgfpVlZe1w7D-5bSfQw.png" /><figcaption>コンフリクトが安全に行うために、心理的な安全性が必要。</figcaption></figure><p>収束をうまく行うために、チーム内で心理的安全性があれば安全なコンフリクトが行われます。案がぶつかったり、討論するのは普通ですので、心理的安全性がないチームでは、デザインが生き詰まります。</p><p>例えば、あるチームのデザイナーは、いつも勝手に一人で収束しました。彼はもちろん頭がいいのですが、何かを決定する時は、いつもチームが関わっていませんでした。スプリントプラニングで彼のタスクは行き詰まり、収束が必要になりました。ですが、皆さんは馬鹿にしたくないと思いましたので、誰も意見を出せませんでした。タスクはそのままで止まって、チーム内で喧嘩が始まりました。</p><h3><strong>全てを捨てて、新しいフレームワークを立ち上げられるのは怖い。</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68Gx38WKu1-gPtl1oSA-ew.png" /><figcaption>全てを捨てて、新しいフレームワークを立ち上げられるのは怖い。</figcaption></figure><p>私がデザインとスクラムを総合しようとコーチングを学び始めた頃、あるチームでは「スクラムを捨てる」という話が出ました。チームが、今までで学んできたスクラムプロセスを全部捨てるのは怖いと言いました。</p><p>でも、他のフレームワークを試してみるのはいかがでしょうか？</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-qjmJU53ZO1VPBRHnocDZA.png" /><figcaption><a href="https://www.mobiusloop.com/">Mobius Loop</a>は、デザイン思考とアジャイル原則を統合したフレームワークです。</figcaption></figure><p><a href="https://www.mobiusloop.com/">Mobius Loop</a>は、デザイン思考とアジャイル原則を統合したフレームワークです。発見、生成、選択、測定、学びというプロセスをわかりやすくまとめています。(日本語の説明は<a href="https://note.com/nttrtech/n/n7fdf08dfcf64">こちら。</a>）このフレームワークはダブルダイヤモンドのように見えますが、ダイヤモンドにはない重要な点、たとえば、学んだことを新しい案に統合することなどが含まれています。yamanecoは、これを不安を感じているスクラムチームに提案し、彼らは元気に会話をし始めました。Mobius Loopを自分のプロセスに比べて、どの部分を追加したい、改善したい、そして捨てたいと話しました。それを見て嬉しくなりました。このフレームワークだけではなくて、自分のチームに合わせたフレームワークを作成できます！</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1y5C0Z9mNSnz9TzaW6LreQ.png" /><figcaption>「アジャイルとデザインは絶対にうまくいかない。」</figcaption></figure><p>「アジャイルとデザインは絶対にうまくいかない」と思ったことがありました。嬉しいことに、私は間違っていたです。このような貴重（きちょう）な学びを与えてくれたyamanecoの同僚とクライアントにとても感謝しています。</p><p>以前に、私はスクラムとアジャイルと開発者の仕事を理解しなかったので、厳しく批判しました。</p><p>ですが、今ではスクラムとアジャイルの世界が少しだけ理解でき、好きだからこそ、厳しく批判しています。強いデザインを作るために、批評が必要です。今までで「デザインとスクラムをどうやって統合するのか」という話は、「スクラムを何も変えずデザインに入れてみたい」とか「ダブルダイヤモンドを変えず、スクラムイベントを入れてみたい」と言うことです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQfAZ1qfGNzAYBK8jQ5VlQ.png" /><figcaption>「どうしてアジャイル会社でデザイン部が必要なのか？</figcaption></figure><p>しかし、違うと思います。</p><p>結婚した方がいらっしゃいますか？</p><p>今年が７年の結婚記念になります。「拍手」</p><p>ありがとうございます。「笑」</p><p>「私の生活、意見は何も変わらずに、いつもパートナーとラブラブしまーす」と以前は思っていました。でも、それは現実的ではないと皆さんご存じだと思います。私とパートナーは別の人です。コンフリクトがあるのは普通でしょう。ですので、心理的安全性を作って、お互いの気持ちを理解し、話が難しくても、怖くても、目をさまして、前へ向かいます。</p><p>スクラム、アジャイル、デザインと結婚することはできますが、いつもラブラブしないですよ。コンフリクトが行うのは当然なので、怖くても、やってもいいんじゃないか？</p><p><a href="https://www.yamaneco.co.jp/design-at-yamaneco/">yamanecoのデザイン部は、そのようなコーチングをします。</a>だからこそ、アジャイル会社の中でデザイン部を立ち上げました。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Icpe5-txcwkaP8Bkh3NqQw.png" /><figcaption>yamanecoのTwitterは、<a href="https://twitter.com/yamaneco_agile">@yamaneco_agile</a>, 自分のTwitterは<a href="https://twitter.com/chostett">@chostett</a>.</figcaption></figure><p>この話を聞いて、「Mobius Loopを試してみたいな」と思えば、自分のプロセスに対して、デザイン思考に興味を持つかもっと言えば、あるいは全てを捨てて、新しいことを作りたくなったら、ぜひやってみてください！</p><p>たとえ失敗しても、一緒に成長すれば、もっと強くなれるはずです。</p><p>ありがとうございました。</p><p><em>もしあなたが東京の組織で、バイリンガル（日本語と英語）のデザイン思考とアジャイル統合についてyamanecoと一緒に仕事をしたいと思ったら、</em><a href="/service/mailto:hello@yamaneco.io"><em>メール</em></a><em>か</em><a href="https://twitter.com/yamaneco_agile"><em>Twitter</em></a><em>で連絡を取ってください。</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=310bb8723754" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/%E3%81%A9%E3%81%86%E3%81%97%E3%81%A6%E3%82%A2%E3%82%B8%E3%83%A3%E3%82%A4%E3%83%AB%E4%BC%9A%E7%A4%BE%E3%81%A7%E3%83%87%E3%82%B6%E3%82%A4%E3%83%B3%E9%83%A8%E3%81%8C%E5%BF%85%E8%A6%81%E3%81%AA%E3%81%AE%E3%81%8B-310bb8723754">どうしてアジャイル会社でデザイン部が必要なのか？</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s get to work.]]></title>
            <link>https://medium.com/yamaneco/lets-get-to-work-32279ecc649d?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/32279ecc649d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Wed, 24 Feb 2021 07:28:11 GMT</pubDate>
            <atom:updated>2021-02-24T07:28:11.747Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learnings from the interaction21 conference</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YpyXfDk5qmy-Mhjrt9D0tw.png" /><figcaption>interaction21: Design in Perilous Times. Let’s start.</figcaption></figure><p>Never did a conference have a more prophetic theme than interaction21 this year. “Design in Perilous Times” came on the heels of interaction20’s “A New Dawn,” which signifies a turning point in the way the design community perceives itself and how it will continue to grow going forward.</p><h4>What is interaction21?</h4><p><a href="https://interaction21.ixda.org/">interaction21</a> is an annual global design conference run by the <a href="https://ixda.org/">Interaction Design Association</a> (IXDA) that showcases the latest trends and future thinking in interaction design (known also under the broader name of UX design). Its members are a tight-knit community of professionals who share resources and help one another to grow. interaction is special because it is the only design conference where, when the speakers step off stage, they are an accessible and friendly part of the community rather than simply “sages on a stage.”</p><p>When we work as the solo designer in a team or an organization, we can feel cut off from the debate and idea exchange that excites our brains and inspires our work. interaction is a fire starter and an opportunity to meet and share ideas with people who you may not otherwise meet in your career. (I am biased: <a href="https://vimeo.com/161009416">I spoke at interaction16</a>, and since then have been lucky enough to attend almost every year since.)</p><p>In this post, I’ll be showcasing four interesting and inspiring talks that I attended over the three-day conference. Keep in mind these were talks from the ones I was able to attend and sketchnote which was only a fraction of the conference — if you have other ones you’d like to share, please comment below.</p><h4><strong>Mapping Hate: </strong><a href="https://www.linkedin.com/public-profile/in/erinkmalone"><strong>Erin Malone</strong></a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwhaVcw8jxjh5KInw3lc-w.gif" /><figcaption>Sketchnotes for Erin Malone’s talk: Mapping Hate.</figcaption></figure><p>In her work with the <a href="https://www.adl.org/">Anti-Defamation League</a>, Erin Malone presents her exhaustive research into the complex web of how hate speech and begins and is influenced by various methods and actors. In it, she talks about how hate is monetized through merchandise and subscriptions that enables people with a platform built on hate to continue fomenting hate as a business rather than a personal opinion.</p><p>She also speaks of intervention points, where educational institutions, family, and community members can intervene to help prevent a person from being radicalized. Her work is also an excellent case study into how to research and map complex, messy systems, as radicalization is not a linear path.</p><p>The big learning from her talk is that something as complex as “hate online” cannot be solved by a singular point alone—and we as designers can make a difference by attempting to understand and map the systems in which a problem is occurring, not just propose solutions on how to solve the problem itself. Understanding <em>when</em> to intervene is just as important as <em>how </em>to intervene.</p><h4>Designing for Trust in the Post-Truth Era: <a href="https://medium.com/u/2828926830c9">Jonathan H Brown</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6HOMYLBnZqHO9oN6W8bUQ.gif" /><figcaption>“Designing for Trust in the Post-Truth Era” by Jonathan H Brown.</figcaption></figure><p>As a natural pair to Erin Malone’s talk, Jonathan H Brown talks broadly of the metaphysical term for the “collective knowledge of humanity” called the <strong>noosphere</strong> coined by French philosopher De Chardin. His argument is that simply de-platforming hate speech apps like Parler only ensures that they re-establish themselves in other, harder-to-monitor spaces (<a href="https://techcrunch.com/2021/02/15/parler-crawls-back-online-empty-and-with-a-tea-party-ceo/">Parler has since come back online, hosted by a company called SkySilk</a>).</p><p>So how do we monitor our collective knowledge without de-platforming? He suggests that we use a rubric of testing the character of both the poster and the message by asking ourselves the following,</p><ul><li>“Is this person really who they say they are?”</li><li>“What is the intent of this message?”</li><li>“What is this person’s previous track record?”</li><li>“Is this topic in their area of expertise?”</li></ul><p>By asking ourselves these four critical questions we can understand whether a post is legitimate, fear-mongering or simply coming from an uninformed perspective. At the end of his talk, he presents a new experimental decentralized monitoring platform he’s working on called <a href="https://twitter.com/xpostfact">Noosphere</a>. I’m looking forward to seeing where this experimental platform goes.</p><h4>How Design Communities Can Address Social Inequities, Racism and Homophobia: <a href="https://medium.com/u/795f1ea3541b">Mitzi Okou</a>, <a href="https://medium.com/u/92fdfe715f6">Max Masure</a>, <a href="https://medium.com/u/d6ffc9a335ae">Rebecca Brooker</a>, <a href="https://medium.com/u/7f968435c6b9">Pablo Stanley</a>, and <a href="https://medium.com/u/ff15427fb9a7">Brenda Laurel</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6pP2dJtBXy-ftImpryt6UQ.gif" /><figcaption>How Design Communities Can Address Social Inequities, Racism and Homophobia: Mitzi Okou, Max Masure, Rebecca Brooker, Pablo Stanley and Brenda Laurel.</figcaption></figure><p>Five heavyweights in design, each who have cultivated and are supported diverse communities, talk about the challenges facing designers as a community. There were so many quotable moments in this talk that I can’t cover them in a short summary alone, and I will post the recording when it becomes available on Vimeo. Particularly Mitzi Okou’s closing comment struck a chord:</p><blockquote>“As designers, we are taught to critique, but we label black designers as ‘defensive’ if we point out gaslighting [in our community and in our designs].</blockquote><blockquote>White designers have the privilege to design anything [without worrying about how it will affect them and their communities]. I want for us to do the same. But black designers — we have to design for survival, because otherwise we are designing for our death.”</blockquote><p>If that quote made you feel as uncomfortable as it did me, good. The design community doesn’t often turn the spotlight on themselves <a href="https://www.theguardian.com/technology/2020/dec/04/timnit-gebru-google-ai-fired-diversity-ethics">as perpetrators of social inequity, racism and homophobia</a> as we see ourselves as open-minded, empathetic and compassionate people who practice “human-centered design.”</p><p>But just because it makes us uncomfortable doesn’t make it any less true, nor does it make us bad people to address it openly, take accountability and work to improve it. This talk was a refreshing <a href="https://www.nytimes.com/2020/11/19/style/loretta-ross-smith-college-cancel-culture.html">“calling in” </a>of the design community to take responsibility for what they can change and change it.</p><h4>Utopia for Designers: <a href="https://medium.com/u/3174047b99b3">Nina Krishnan</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ispJaCcV4FH-in2-f0Urhg.gif" /><figcaption>Nina Krishnan’s “Utopia for Designers.”</figcaption></figure><p>Nina’s main argument is that common utopian thinking (i.e. <em>“Don’t think about the present! Design for the future!”</em>) is unrealistic, static and is working towards a perfection that is unachievable. It is also done by designers who have the security of not worrying about the present (as Mitzi points out) and excludes historically marginalized communities.</p><p>Instead, she presents us with a compelling alternative framework from feminist activism—critiquing the existing system, imagining a brighter, realistic future together with impacted communities, and putting those futures together with continuous action. This, she says, is the brighter way forward—from “consultant” to “co-creator” and from “designing towards a utopian future” to “designing towards an equitable future.” She references Antionette D. Carroll’s talk on <a href="https://vimeo.com/427590444">Understanding Identity, Power, and Equity in Design Leadership</a> and Rutger Bregman’s book <a href="https://www.goodreads.com/book/show/40876575-utopia-for-realists">Utopia for Realists</a> which I recommend to those interested in digging in deeper into this topic.</p><h4>Personal impressions</h4><p>As a young designer, I studied the “greats” of design—Charles Eames, Walter Gropius, Dieter Rams—who were white, male-identified individuals. Context and framing influences all our design decisions and I’ve noticed that commonly “great design” is coded language for “design that white men do.” They are talented individuals, but it is also true they owe societal and actual institutions that validated their “greatness” in the design field.</p><p>For those of us who have been in design for a while, we, actively or inadvertently, have contributed to this system. Even in a relatively young field like interaction design, we still uphold traditional ways of critiquing design based on its usefulness to a singular person with little regard to how our work contributes to driving income inequality or reliance on privatized systems. It is my hope that we can, with the help of our fellow BIPOC, queer, neurodivergent and designers with disabilities, tear down old constructs, burn them, and like the phoenix, rise anew. It’s what we as designers do best, right? Make ideas, tear them up and craft them anew.</p><p>To do that, <strong>we will have to feel discomfort.</strong> We will have to grapple with ideas and values that we ourselves may not value, and be at peace with not always being the subject matter expert. I felt some of this energy at this interaction21, especially during Day 3, but I invite the IXDA organizers to push more to call out breakdowns in our community, call in our community members to grow and learn from one another, and empower diverse designers and leaders so we can reshape the face of what “great” design looks like.</p><h4>What’s next?</h4><p>A few call to actions came up in the conference:</p><ul><li><strong>Value systemic thinking and seek out your own blind spots. </strong>Read <a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems">Donnella Meadows</a>, <a href="https://www.goodreads.com/book/show/190560.Design_for_the_Real_World">Victor Papanek</a>, and <a href="https://www.goodreads.com/book/show/34762552-algorithms-of-oppression">Safiya Noble</a> to broaden your horizons and consider how technology contributes to the pre-existing destruction of our environmental and social systems. If you want to get more involved, there’s an active conversation happening on the <a href="https://ixda.slack.com/join/shared_invite/zt-l652eik7-2AAo6nuv1Wdx7~_cI~hUzA#/">IXDA Slack</a> in the <strong>#systems-thinking</strong> channel.</li><li><strong>Understand and practice inclusive design.</strong> Specifically — design that is not contributing to destructive cycles of social oppression. One of the speakers, <a href="https://medium.com/u/738654501896">Ariba Jahan</a> put together <a href="https://www.aribajahan.com/blog/cant-empathize-privilege">an excellent list of resources for learning about inclusive design.</a></li><li><strong>Join a community. <br></strong>In addition to the IXDA Slack, there are places where designers of traditionally underrepresented groups can find some solidarity:<br><a href="https://wherearetheblackdesigners.com/">Where are<strong> </strong>the black designers?</a> is a community for black designers for community, jobs and mentorship.<br><a href="https://www.latinxswhodesign.com/">Latinx Who Design</a> is a group for Latinx designers and creative leaders.<br><a href="https://queerdesign.club/">Queer Design Club</a> is a design community for queer-identified folx.</li><li><strong>Support your community. </strong>Via mentoring (I suggest <a href="https://www.pair-up.org/">Pair Up</a>), portfolio reviews, buying software licenses for designers who can’t afford it. Creative work is still a pay-to-play game, and oftentimes designers that can afford their own computer, software, and ability to take time off to go school/bootcamp are the ones who can successfully get into this industry. Give back and help the community grow.</li></ul><p>If you know of any good resources on any of the above, please comment or <a href="https://twitter.com/chostett">reach out to me on Twitter</a>. I want to share more resources, especially those created by underrepresented groups.</p><p>Thank you to everyone who organized, spoke and participated in this event. If I met you at the conference, it was wonderful to meet you—if I haven’t met you yet, I hope to see you at the next one.</p><p><em>I will post the respective video links to these talks once they become available on Vimeo.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32279ecc649d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/lets-get-to-work-32279ecc649d">Let’s get to work.</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Story of Love and Marriage: The Hidden Challenge of Outcomes]]></title>
            <link>https://medium.com/yamaneco/a-story-of-love-and-marriage-the-hidden-challenge-of-outcomes-ec71459f5e7b?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec71459f5e7b</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Wed, 28 Oct 2020 06:57:41 GMT</pubDate>
            <atom:updated>2020-10-28T06:59:38.374Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making organizational change means celebrating differences and sharing outcomes.</h4><p><em>(This article is adapted from an interactive session </em><a href="https://medium.com/u/c0826d58f919?source=post_page-----8639f913d516----------------------"><em>Davide Petrillo</em></a><em> and Chelsea Hostetter did at </em><a href="https://ridethelightning.doorkeeper.jp/events/102718"><em>Ride the Lightning</em></a><em> in January 2020. It is Part Three of a three-part series on intentionally integrating agile and design called “The Hidden Challenges of Design and Agile.”)</em></p><p>Welcome back. We’ve covered the hidden challenges of vocabulary and context in our previous articles and today, we’ll be tackling the third and final challenge of outcomes, or how to generate value without compromising the “spark” that makes agile methodology powerful and the design process innovative. If you have not already done so, we urge you to read <a href="https://medium.com/yamaneco/hidden-challenges-of-design-and-agile-pt1-8639f913d516">Part 1: The Vocabulary Challenge</a> and <a href="https://medium.com/yamaneco/the-hidden-challenge-of-context-in-design-and-agile-4d2cf3f1d828">Part 2: The Context Challenge</a> before you dive into outcomes.</p><p>This section was inspired by Joshua Seiden’s book <a href="https://www.senseandrespondpress.com/managing-outcomes">Outcomes over Output</a>. If you’ve read it, this article will provide a new lens with which to view his thoughts. If not, we’ll explain the essential concepts and add our twist on how to focus on outcomes when integrating agile and design.</p><p>But first — have you heard this story before?</p><p>Two people meet. They fall in love.</p><p>They marry.</p><p>Then — things change. Conversations that once were interesting become dull. The <em>“spark”</em> is gone.</p><p>Marriage is a good metaphor for what happens when people “integrate” — initially, the closeness feels good, but too much sameness over time becomes tedious. As we aim to better integrate design and agile, we must understand that when we do this, we too risk “losing the spark.” How do we keep what makes both agile and design individually revolutionary, but integrate the best parts of each? This chapter is about how to navigate the integration of what both agile and design needs to thrive — individual space and shared outcomes.</p><figure><img alt="Two wedding rings below the text, “The Outcome Challenge.”" src="https://cdn-images-1.medium.com/max/1024/0*x-W4n0AQaRqknMcy" /></figure><h3>What is an outcome?</h3><p>An <em>outcome</em> is a change that happens as a result of the team’s work. Imagine your team implemented an easy-to-access sign up button on the homepage that leads to an increase in customers signing up to your newsletter. In this example, the <em>sign up button</em> is an output (i.e. what the team made) and <em>an increase in customers signing up to your newsletter</em> is an outcome (i.e. the result of the team’s work). They are the <a href="https://uxdesign.cc/how-to-measure-progress-with-outcomes-985fb118fb56">“human behaviours that drive business results.”</a></p><p>Seiden observes that most teams focus on their resources, activities and output as opposed to their outcomes. If you’ve heard of the term “feature factory,” this is what we mean — teams that are so focused on the output and organizations that are so focused on results that they forget <em>why</em> and <em>for whom</em> they are building in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X5dGZk-Gvo-M3Glu" /><figcaption>Teams tend to focus on resources, activities, and outputs.</figcaption></figure><p>A new lens with which to consider this is that agile focuses on <em>delivery</em>: predictability, risk minimization, flexibility towards change. Design mindset focuses on <em>discovery</em>: understandability, delight, and a frictionless experience. Though the end output of both is a great product or service and happy customers, agile does this through constant iteration and making. Design mindset does this through talking to users directly and understanding their needs.</p><p>It’s easy to assume that the product is the shared outcome and agile and design are different ways to achieve it, but in reality, the product is an output, not an outcome. If you do not acknowledge this difference, you may inadvertently focus only on making the product. If this is the case, then <em>making</em>, rather than <em>understanding</em> will be valued. This can lead to teams who are jumping in and “just doing it” but struggle to think holistically or produce consistency. In companies where <em>making</em> is valued, the organization <em>must</em> consider design as a first-class citizen to make the leap from good to great.</p><p>Design, with its focus on user behaviours and needs, helps teams understand the “why” of what they are building. It grounds them in research and experimentation and prevents the team from becoming the dreaded “feature factory.”</p><p>So all we need to do is align together on a common goal and processes, and we should be fine, right? Theoretically, yes. But theory and practice are different things. Here are some friction points we’ve noticed in teams moving towards unified, outcome-focused goals.</p><h4><strong>Implementation of the “appearance” of agile or design but not the mindset.</strong></h4><p>Design is full of visuals such as screens, customer journey maps, and user flows. Likewise, agile teams have ceremonies in calendars, a backlog of (hopefully) user-focused stories and end-of-sprint reports. These tangible things from both agile and design are <em>outputs</em>.</p><p>In design, hours spent at a whiteboard brainstorming with the development team and customer research directly contributes to understanding and driving behaviour change in the product. In agile, the team thinking in sync and iterating with curiosity is how the agile mindset unlocks enhanced team collaboration and efficient delivery. These changes in both customer and team behaviour are <em>outcomes.</em></p><p>The tangible aspect of both agile and design is sometimes mistaken by the organization as “the end goal” and as such, only the appearance of both is implemented and not the actual mindset or thinking. This can lead to a “hollowness” where, on the surface the team <em>seems</em> agile or design-oriented, but below the surface is not.</p><h4><strong>Not involving designers in the development process increases the risk of becoming output-focused.</strong></h4><p>When Davide was working as a product manager he noticed that, when designers were not involved in a backlog creation activity or a sprint planning, user stories would easily lose their focus on actual needs and become feature requests. “The user needs a way to navigate our site,” easily turned into, “the user needs a hamburger-style menu in the application.” It was easier to understand from the development team’s perspective because they knew what to build, but they inadvertently skipped the step of <em>understanding</em> what needed to be built.</p><p>To return to our marriage metaphor, each individual person has their own goals and motivations for coming into a marriage. They also have shared ones, too. The trick to successful integration, in our opinion, is not to have <strong><em>all</em></strong> our goals be the same. It is to have <em>the top few shared goals be the same</em> and treat our different motivations as important as our own. The goal the outcome-driven team should share is to commit to creating something that benefits the user and <a href="https://dzone.com/articles/agree-to-disagree-vs-disagree-and-commit-how-to-di">disagreements are a natural part of this</a>. Integration means refocusing on this common goal and creating processes that empower designers, developers and product owners to reach those outcomes and share their expertise, even if they disagree.</p><h3>How to focus on outcomes</h3><p>If you find yourself noticing these friction points in your organization, here are some suggestions we’ve tried before with success to align design and agile towards the same outcomes.</p><h4><strong>Focus on metrics that matter.</strong></h4><p>According to behavioural economists, anything that is measured can be used as a benchmark for success, which <a href="https://dzone.com/articles/how-to-cripple-your-team-morale-motivation-and-pro">produces unintentional behaviours just to meet that metric.</a> One of the past product teams Chelsea worked on measured their velocity (a metric used for forecasting how much work a team can fulfill in a sprint) each sprint and visualized it on the wall. This caused the development team to become more agile in their own processes, but <em>also</em> caused a drop in participation in activities, like joining customer-facing research or whiteboarding sessions because they unconsciously wanted to beat their average velocity. Be intentional about what your team measures publicly.</p><p>However, another team she worked with decided to set working metrics straight from their user outcomes (i.e. “we want 50% or more of our users to revisit our site after a week”). Instead of waiting to react to customer complaints in the Google Play and App Store, the team proactively talked about the outcome they wanted to change. They were able to free themselves from the slog of reactive feature requests into actively charting their own course and prioritizing needs with the user in mind.</p><h4><strong>Use an experimental approach to developing your product.</strong></h4><p>Remember the scientific method in school? The same applies here. If we view our success metrics as a hypothesis, the next logical step is to test it. Seiden writes,</p><blockquote><em>“Changing behavior inside an organization is a hard problem, and not one easily solved by planning on paper. Instead, it benefits from an </em><strong><em>action-oriented approach</em></strong><em>…this experimental approach to achieving behavior change creates a deeply agile way to approach transformation inside organizations.”</em></blockquote><p>User tests, design feedback, prototyping — all of these are used to test assumptions about how something functions. The experimental mindset is baked into both agile through its iterative approach and design through hands-on prototyping and testing. Using both of these in tandem generates an understanding about which outcomes your team should focus. For the integrated design and agile team, they build their hypotheses in the form of user needs and then test them out with quantitative and qualitative tests.</p><p>The integrated team considers <strong>any experiment a success if their team learned something new.</strong> Each time we learn, we are closer to either achieving or adjusting our outcomes. Taking the previous outcome of “we want 50% of our users to revisit within a week,” if we released a new feature, tested it and nothing happened, we have learned something — that this does not have a measurable impact. This means that we either need to adjust what we are building or adjust our outcome. Either will bring us closer to understanding what works and what does not.</p><p>When the team succeeds, celebrate and use this as a way of enacting change in the organization. Outcomes are not only focused on the product, but can shift mindsets or processes in the organization that will ultimately lead you towards success.</p><h3>Strong apart, stronger together</h3><p>Going back to our marriage metaphor, happiness in a relationship is a result of keeping your own individuality while helping each other become better. <strong>This</strong> is the power of partnership: neither design nor agile is subordinate to the other. Striking that balance is key. Balance allows agile to focus on <em>delivery</em> and design on <em>discovery</em>, as well as<em> </em>harnesses the power of the two combined to achieve great outcomes.</p><p>When Chelsea and Davide worked together in the team behind an interactive prototyping tool, they faced the challenge of combining an almost complete rewrite of the product with discovering innovative ways to fulfill user needs in a tight timeframe. With the development team focused on getting up to speed with agile and writing features to meet deadlines, how did we make space for discovery and experimentation?</p><p>We pointed out that the outcome of the product was not cramming in as many features as we could, but instead delivering something appealing, meaningful and lovable to the end user. This shifted conversations from, “When will we release this?” to a more strategic, “What will impact our users more?” This created a space for exploration and testing hypotheses within the team. We did this <a href="https://goodpatch.com/blog/how-to-user-test/">our own way</a> that fit into the context of the team (remember, adapt processes to your context!) In the end, we integrated a <a href="https://uxdesign.cc/dual-track-agile-is-a-game-changer-for-designers-e19705fec3c1">dual-track agile approach</a> that brought our team closer together and focused towards meeting shared outcomes. It didn’t matter if our processes lined up perfectly — each had their own cadence. The important part was not to have us running exactly in sync, but rather to reduce overall handoff time and improve in-time communication.</p><p>We invite you to observe the natural cadence of your own team and try to find ways of working together that preserve the best parts of that cadence while keeping teams closely in touch with one another. A marriage of two people is not a container that both must change their fundamental personalities to fit into, but a shared space of curiosity where both can grow. And so too when integrating design and agile. Both must be given their own individual space and communal ground to grow — and once aimed at a shared outcome — watch out! — incredible things can, and will, happen.</p><h3>Some questions to consider asking…</h3><ul><li>What outcomes do we want to achieve?</li><li>How might we treat design processes and mindset as a “first class citizen” alongside agile?</li><li>How might we cultivate an environment of curiosity and experimentation in our team? Does our team have the psychological safety and mutual respect needed to do this? If not, how can we make this?</li></ul><p>We hope that you have enjoyed reading this three-part article. It was a labor of love for the both of us, and we’re looking forward to having deeper discussions within the community.</p><p>We couldn’t have had these conversations without the input of those who came to our initial event, <a href="https://ridethelightning.doorkeeper.jp/events/102718">The Hidden Challenges of Agile and Design</a>, and we thank them. Special thanks to our coworkers at <a href="https://www.yamaneco.co.jp/">yamaneco</a> and <a href="https://aqworks.com/">AQ</a> for the discussions that sparked these articles and their continuing feedback.</p><p>If you’d like to discuss with us, you can get in touch with Davide on Twitter at <a href="https://www.twitter.com/davidepetrillo"><strong>@davidepetrillo</strong></a> or Chelsea at <a href="https://www.twitter.com/chostett"><strong>@chostett</strong></a>.</p><p><em>The Hidden Challenges of Design and Agile Series</em><br>Part One: <a href="https://medium.com/yamaneco/hidden-challenges-of-design-and-agile-pt1-8639f913d516"><strong>Vocabulary</strong></a><br>Part Two: <a href="https://medium.com/yamaneco/the-hidden-challenge-of-context-in-design-and-agile-4d2cf3f1d828"><strong>Context</strong></a><br>Part Three: <a href="https://medium.com/yamaneco/a-story-of-love-and-marriage-the-hidden-challenge-of-outcomes-ec71459f5e7b"><strong>Outcomes</strong></a></p><blockquote><a href="https://medium.com/u/c0826d58f919">Davide Petrillo</a> is part of <a href="https://medium.com/u/3662e46ec61d">AQ</a>, an independent design studio with offices in Tokyo &amp; Paris, helping teams build useful digital products and services. Chelsea Hostetter is part of yamaneco, a Japanese company helping build happy teams through Agile, DevOps and UX coaching.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NDqxv9cksrvBO0yG" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec71459f5e7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/a-story-of-love-and-marriage-the-hidden-challenge-of-outcomes-ec71459f5e7b">A Story of Love and Marriage: The Hidden Challenge of Outcomes</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Birthday Letter]]></title>
            <link>https://medium.com/@chostett/a-birthday-letter-d15488686570?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/d15488686570</guid>
            <category><![CDATA[suicide-prevention]]></category>
            <category><![CDATA[grief]]></category>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[human-parts]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 00:36:02 GMT</pubDate>
            <atom:updated>2020-09-14T00:36:02.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yiZmHsi-5Pk8UQc9ThKMNw.jpeg" /><figcaption>Photo by <a href="http://instagram.com/seagull_tree">Caterina Berger</a>.</figcaption></figure><p>Happy birthday.</p><p>You wouldn’t <em>believe</em> what a year it’s been.</p><p>Tokyo shut down. For a month, you could walk the streets of Shibuya, home of the busiest crosswalk in the world and pass less than ten people. Nowadays most everyone wears masks and people who can work from home, do. That’s probably not the case for you, since you’re an English teacher.</p><p>It also brought out issues of structural inequality, poverty and institutionalized violence that already existed, but are now being exposed to the public at large in Japan. My friend described this in Japanese as 浮き彫り (<em>ukibori</em>), which is what happens when one carves wood and exposes the soft flesh underneath.</p><p>I too have been carving away pieces of myself.</p><p>I haven’t written since before you died. You were 29 then. I was 27. We were so young.</p><p>I work in design now. I talk to people, and then I sit at my computer drawing boxes, over and over again. You’d think I’d get bored with drawing boxes, but I don’t. It’s not the boxes I like but the <em>people</em> for whom I’m drawing them for.</p><p>But things were different six years ago. Then, I was a young designer who had just gotten their first big client. We’d wrapped up our first project together successfully and the client were excited to have me on for another phase of work, to start the following week.</p><p>I wasn’t ready.</p><p>I guess you weren’t, either.</p><p>I asked my client if I could miss the kickoff. Something had happened. I promised I’d be in mid-week. In the most compassionate voices, they worried over the cohesion of the project, whether they’d be able to find a replacement for me. I caved and said I’d be back by Monday. I didn’t tell them I was planning to fly out of state for your memorial. At the time, I thought doing so would be unprofessional.</p><p>I remember hoping I’d “push through it” over the weekend and then get back to work, fresh-faced and renewed. Cry my tears over the weekend, empathize with our customers on the weekday.</p><p>Unfortunately, life had other plans. The flight on Saturday was late and I missed the connecting flight. The airline offered to fly me out later the next day, but I knew I would miss your memorial. Out of a selfish fear I’d miss work on Monday, I slept in a smoky motel in South Carolina and flew back to Texas the next day. I was fine.</p><p>I came into work on Monday to concerned smiles. “Everything okay?”</p><p>“I’m fine,” I replied with a smile. I felt like someone had scooped out my insides, raw and quivering, and put them inside a locked freezer. I pushed it down, got to work, hustled. It was what I <em>thought</em> professionals did.</p><p>Sometimes, when I thought no one was looking, I’d take pieces of me out of the freezer and try to put them back inside. When I did, a wave of sudden, incontrollable grief would wash over me and I would slam the door shut again. I went back to my computer to draw boxes. Over and over again, until the fear subsided.</p><p>I was afraid of coming undone, of crying at work or worse, not being able to perform my job and have people look at me with pity in their eyes and say, “Being a designer is hard…<em>some people</em> can’t hack it, you know?”</p><p>With grief, time is cyclical. It doesn’t matter whether something is happening now or six years ago, they feel as if they are the same moment.</p><p>Back to your birthday card, sweet. That’s why I’m writing you.</p><p>There’s a worldwide pandemic going on. It has shut all of us in our houses and has slowly carved us down to soft flesh. We are raw. The freezer is in our house. At work, we can ignore it. But here, we can’t escape it.</p><p>I’m sorry I kept the door shut for so long.</p><p>I’m angry at you. You left us before saying goodbye. Instead of asking for help you tried to go it alone. When I asked you if you were okay, you said, “I’m fine.” How was I supposed to know you had your own freezer?</p><p>I’m sad. I picture a future that will never resolve where the two of us meet in a cafe and catch up. We would laugh, cry. Maybe we’d catch a <a href="https://kageki.hankyu.co.jp/english/index.html">Takurazuka show</a> together in a non-existent future. You loved Takurazuka. After you died, I avoided shows because it reminded me of you.</p><p>I miss you. You introduced me to people with whom I have lifelong friendships that I treasure to this day. You were my first window into the LGBTQIA+ community. Through you, I saw a brighter, happier future that I could have if I surrounded myself with people who taught me to be fearless and compassionate.</p><p>Thank you.</p><p>I’m sorry.</p><p>I’m angry.</p><p>I’m sad.</p><p>I miss you.</p><p>I’m terrible at ending letters, especially ones to people who aren’t living. I can’t really say, “see you soon,” can I? But up until now the door had been closed and you weren’t welcome.</p><p>So now I can say, “visit anytime.” I would love that. Come by sometime. I’ll be ready for you.</p><p>Happy birthday.</p><p><a href="https://suicidepreventionlifeline.org/"><em>The National Suicide Prevention Hotline</em></a><em> in the U.S. is 1–800–273–8255.</em></p><p><a href="https://telljp.com/lifeline/"><em>TELL Japan</em></a><em> provides a helpline support in Japan in English at 03–5774–0992.</em></p><p><em>If you or someone you know is struggling with thoughts of depression or suicide, call. I promise, it is </em><strong><em>not</em></strong><em> stupid or weak. It is </em><strong><em>strong</em></strong><em>. Some of the people on the other end of the phone are friends of mine, and the reason they volunteer is because they care about folks like you.</em></p><p><em>Love you, and stay safe.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d15488686570" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden Challenge of Context in Design and Agile]]></title>
            <link>https://medium.com/yamaneco/the-hidden-challenge-of-context-in-design-and-agile-4d2cf3f1d828?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d2cf3f1d828</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[context]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Thu, 06 Aug 2020 05:13:42 GMT</pubDate>
            <atom:updated>2020-10-28T06:58:37.003Z</atom:updated>
            <content:encoded><![CDATA[<h3>As Invisible as Water: The Hidden Challenge of Context</h3><h4><em>Making organizational change involves being experimental.</em></h4><p><em>(This article is adapted from a session </em><a href="https://medium.com/u/c0826d58f919"><em>Davide Petrillo</em></a><em> and Chelsea Hostetter did at </em><a href="https://ridethelightning.doorkeeper.jp/events/102718"><em>Ride the Lightning</em></a><em> in January 2020. It is Part Two of a three-part series on intentionally integrating agile and design.)</em></p><p><a href="https://medium.com/yamaneco/hidden-challenges-of-design-and-agile-pt1-8639f913d516">In the first part of “The Hidden Challenges of Design and Agile”</a>, we discussed the issue of overlapping vocabulary that often causes big misunderstandings. For example, a prototype within an agile context versus a design context can mean two different things depending on where you first learned the word. If you haven’t read <a href="https://medium.com/yamaneco/hidden-challenges-of-design-and-agile-pt1-8639f913d516">The Vocabulary Challenge</a> already, we recommend you do before continuing as these articles build upon each other.</p><h3><strong>A quick recap — what is a “hidden challenge?”</strong></h3><p>It is a challenge that, when integrating agile and design, the team often “feels” but cannot concretely describe. Unless it is brought to the attention of the team and agreed it is an issue, it can often get in the way of team progress, causing turnover or the organization to give up on integration entirely.</p><p>We wrote this series to give these “hidden challenges” a name so you can bring them to light. These challenges are interconnected and interdependent on your organization so we cannot recommend a one-size-fits all solution, but we <em>can</em> provide questions you can ask to better understand what parts of the challenge your organization is struggling with. You can find them at the end of each part.</p><figure><img alt="Two fish swimming around the words, “The Context Challenge.”" src="https://cdn-images-1.medium.com/max/1024/1*LVs9niQZLSJ-9_tQpPu2fg.png" /></figure><p>Today, we’ll be introducing the hidden challenge of context. It is the environment around our behaviour and influences the way we interact and communicate with others. It is almost entirely invisible. The easiest way to understand how hidden context is through a story David Foster Wallace told,</p><blockquote><em>There are two young fish swimming along who happen to meet an older fish.The older fish nods at them and says:</em></blockquote><blockquote>“Morning boys, how’s the water?”</blockquote><blockquote><em>The two young fish swim on for a bit and then eventually one of them looks over at the other and asks:</em></blockquote><blockquote><strong>“What the hell is water?”</strong></blockquote><p><em>That</em> is context.</p><h3>As invisible as water: the challenge of context</h3><p>As we mentioned in the challenge of vocabulary, the idea that we all know and agree upon various meanings of the same words is false. Let’s say your team has bought into this idea and has started to define the words they use with one another. Communication problem solved, right?</p><p>Wrong.</p><p>One part of communication are the words we use (vocabulary) but another important part is context. There are many different levels of context — layered like a pancake, but less tasty. The layers are:</p><ul><li><strong><em>Personal</em></strong> (i.e. your prior working experiences, how confident you feel in applying agile or design principles, etc.)</li><li><strong><em>Interpersonal</em></strong> (i.e. communication between the team members)</li><li><strong><em>Project</em></strong> (i.e. what the ultimate goal of the project is)</li><li><strong><em>Organizational</em></strong> (i.e. does your business structure enable or prevent close collaboration)</li></ul><figure><img alt="Picture of a pancake with the words, Personal, Interpersonal, Project and Organizational on it." src="https://cdn-images-1.medium.com/max/1024/1*k_Qfvc6Fzoo2sPZRt1Vw3A.png" /><figcaption>The context pancake.</figcaption></figure><p>We could write at length about each of these layers but for the sake of time we will only focus on the <strong>personal</strong> layer.</p><p>Personal context can be explained by asking the question, “are you a cat lover or a dog lover?” Most of the time, this answer comes with a story. “I’m a dog lover — my family kept dogs when I was a child.” When a person has had a <strong>neutral to positive</strong> relationship to dogs in the past, they are more likely to identify as a dog lover.</p><p>In the case of agile and design, typically people have had a past experience with one or the other, whether it was directly through their team or indirectly through a blog or news article. This will directly affect the way they are drawn towards or away from a process.</p><p>A few years ago, Davide joined a new team in a hybrid role of developer and coach. Having had prior positive experiences working with well-oiled teams of developers and designers who embraced Agile wholeheartedly, he expected to replicate similar approaches and processes with this new team.</p><p>Things didn’t go as planned.</p><p>The daily stand-up (which is suggested to be no longer than fifteen minutes) took up to one hour of team discussion. Such a situation created a frustration loop. Davide pushed for a shorter, focused session and the team pushed for discussing everything no matter how long it would take. Why was this happening? When Davide realized these frustrations were symptoms of a hidden challenge, he changed his mind. His personal context — prior experience with teams who had already structured their thinking around a fifteen minute timebox had gotten in the way of serving the team’s underlying needs.</p><p>And what were their needs? Due to other organization commitments, designers in the team could never block off time to have spontaneous conversations throughout the day — so this was the only time they had with their fellow teammates. The frustration settled and was replaced by a curious “what solutions can we test to fix it?”</p><p>Had Davide continued to be unaware of the context he was working in, he could have unintentionally become a blocker to the team’s work. Instead his will to meet the team’s underlying goals caused them to think outside the standup box. In the end, the team relaxed the rules of the standup to meet their communication needs, and they started working on a fix to mitigate organizational blockers.</p><p>Having context is not a bad thing. In fact, it is what allows us to infer, to read the room and to move seamlessly in the world we live in. And, like water for fish, it is always around us, invisible to our eyes. It is when your personal context collides with the environment around you that makes a challenge.</p><h3><strong>Why design and agile?</strong></h3><p>You may be asking yourself, “How does this relate to design and agile? Doesn’t this challenge of context apply to <em>every</em> problem?”</p><p>You are right.</p><p>A common problem cited in agile teams working with designers is “<a href="https://boxesandarrows.com/integrating-ux-into-the-product-backlog/">capturing design requirements</a>,” i.e. putting design tasks or explorations into the backlog.* Though not a general rule, typically this problem arises when a team tries to capture design discovery or experimentation. This is a context issue. Let’s break down why this occurs.</p><p><em>* </em><strong><em>Nerd talk: </em></strong><em>A backlog is part of scrum, not agile. In this case however, we are talking about scrum processes within an agile team. In terms of context a person’s experience with scrum processes affects the way they think about agile as the two are commonly paired.</em></p><p>Historically, putting items into the backlog meant taking a large development task and chunking it into smaller pieces to tackle in two-week sprints. Project management software such as Jira, Trello or Redmine have backlogs structured in a linear task flow (i.e. <em>To-Do → Doing → Done</em>), which follows the iterative but generally forward-moving progress in agile. Here we describe two separate things, a workflow (“making a backlog”) and software (“what we use to make the backlog”).</p><p>Prior experience with this workflow or software will affect the way your team treats the more cyclical workflow of design discovery and experimentation when they encounter it. If they had a <strong>neutral or positive</strong> experience in creating a backlog or using Jira, they are more likely to propose using Jira or traditional backlog-making methods to keep track of design discovery. If it is put in a traditional backlog, design discovery can be treated as linear and may miss opportunities to pivot or pursue other opportunities outside of this linear flow.</p><p>This new addition to a pre-existing context can cause friction. The context challenge is the reason why so many teams struggle when putting design requirements into a backlog. They won’t quite fit and require a new, hybrid solution to make the most of both design discovery and the agile framework. There are many frameworks of what this hybrid might be, like <a href="https://uxdesign.cc/introducing-dual-track-agile-27a23d12268b">dual-track agile</a> or <a href="https://www.jpattonassociates.com/the-new-backlog/">storymapping</a>.</p><p>So how do we solve this problem?</p><p>Here’s the bad news. As we said earlier, we can’t offer a one-size-fits-all solution. This is because there is none.</p><p>We cannot tell you the right solution for <em>your</em> team, but we can help you find a way forward. Be open to discarding part of your original process, if not all if it doesn’t work against a new need. Replace it with questions about the need(s) to be solved. To take the design requirements example, ask designers “what outcomes are we looking to get from our discovery?” and ask the team “what are the most important things we need to know as a team to coordinate and share learnings from our discovery?” Make an experiment to solve the needs you hear from the team. You may be surprised by the simplicity of the solution.</p><p>Among others, in her book <a href="https://www.goodreads.com/en/book/show/8337919-coaching-agile-teams">“Coaching Agile Teams”</a> Lyssa Adkins suggests using the Japanese martial art Aikido’s <em>Shu-Ha-Ri</em> method to start experimenting: first follow the rule, then break the rule, and finally be the rule. Start with a process that generally works. Then, adapt it to your team needs and your environment. Once you have full clarity of the context and what ways of working lead to performance in that specific context, you will have become the rule maker rather than the follower.</p><p>As a rule of thumb, if something that worked in your previous experiences suddenly stops working, it’s time to cultivate your curiosity, raise your hand and ask the team what’s not working for them. You’ll discover more about everyone’s personal contexts this way and involving the team in the process creates a sense of ownership that any individual member is not wholly responsible, but the entire team.</p><h3>Some questions to consider asking…</h3><p>If you find yourself recognizing context challenges in your organization, consider asking the following questions to raise awareness and cultivate curiosity.</p><ul><li>What need is this current process solving? How can we better support those needs?</li><li>Within the layers of context, which context is being challenged?</li><li>What small experiments can we try together to help us meet all our underlying needs?</li></ul><p>Some of these questions may spark defensiveness, but asking them with genuine curiosity and humility is the start to developing a process that works for your context.</p><p>In Part Two, we uncovered the hidden challenge of context, which is as invisible to us as water is to fish. Sometimes things stop working over time or when a new element is introduced, and it’s perfectly normal and natural. What is not normal is trying to continue to use that process even when needs aren’t being met. Our third and final part will cover the <strong>hidden challenge of outcomes</strong>, which tackles some of the organizational issues integrated teams face when building a product.</p><p>We hope you found this article useful. We would love to hear your feedback and know what context challenges you are facing.</p><p>What shared context does your team have? What do you feel are their blind spots?</p><p><em>The Hidden Challenges of Design and Agile Series</em><br>Part One: <a href="https://medium.com/yamaneco/hidden-challenges-of-design-and-agile-pt1-8639f913d516"><strong>Vocabulary</strong></a><br>Part Two: <a href="https://medium.com/yamaneco/the-hidden-challenge-of-context-in-design-and-agile-4d2cf3f1d828"><strong>Context</strong></a><br>Part Three: <a href="https://medium.com/yamaneco/a-story-of-love-and-marriage-the-hidden-challenge-of-outcomes-ec71459f5e7b"><strong>Outcomes</strong></a></p><blockquote><a href="https://medium.com/u/c0826d58f919">Davide Petrillo</a><em> is part of </em><a href="https://medium.com/u/3662e46ec61d"><em>AQ</em></a><em>, an independent design studio with offices in Tokyo &amp; Paris, helping teams build useful digital products and services. Chelsea Hostetter is part of yamaneco, a Japanese company helping build happy teams through Agile, DevOps and UX coaching.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C5AVNGEx97cCRkqEr5fKSA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d2cf3f1d828" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/the-hidden-challenge-of-context-in-design-and-agile-4d2cf3f1d828">The Hidden Challenge of Context in Design and Agile</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[「Is the Design Done?」 UXとアジャイルを統合しましょう！]]></title>
            <link>https://medium.com/yamaneco/is-the-design-done-ux%E3%81%A8%E3%82%A2%E3%82%B8%E3%83%A3%E3%82%A4%E3%83%AB%E3%82%92%E7%B5%B1%E5%90%88%E3%81%97%E3%81%BE%E3%81%97%E3%82%87%E3%81%86-d5aa14853ebe?source=rss-746a6c06f3fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5aa14853ebe</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[startups-in-japan]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[CJ Hostetter]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 02:10:30 GMT</pubDate>
            <atom:updated>2020-07-15T02:10:30.992Z</atom:updated>
            <content:encoded><![CDATA[<h4>開発者とデザイナーの違いを理解することで、開発やデザインにおける国境を越えたコミュニケーションにどのように役立つのか、という「sketchy」な記事。</h4><p><em>(この記事は、IDEO Tokyoで</em><a href="https://www.meetup.com/CodeChrysalis/events/266455619/"><em>Code ChrysalisのMiniConf #8: Design Edition</em></a><em>のために私が行ったライトニングトークを参考にしています。</em><a href="https://medium.com/yamaneco/is-the-design-done-integrating-ux-and-agile-intentionally-fad4abceae1e"><em>英語の原版はこちら</em></a><em>。 日本語の翻訳の手伝ってくれて、</em><a href="https://medium.com/u/d12b1686c753"><em>rtanaka</em></a><em>に感謝したいです。）</em></p><figure><img alt="「Is the Design Done?」 UXとアジャイルを統合しましょう！" src="https://cdn-images-1.medium.com/max/1024/1*exGQSFuBHCBIcRsMf-VZww.png" /></figure><p>こんにちは、チェルシーです。東京のアジャイルコーチングをメインにしている会社yamanecoでUXコーチ兼デザイナーとして働いています。</p><figure><img alt="私はUXコーチ兼デザイナーと、漫画家、デザインリサーチャーとインタラクションデザイナーなどをやっています。" src="https://cdn-images-1.medium.com/max/640/1*4RuPGI4tIuTutKD0jyoYAA.gif" /></figure><p>私は長年にわたり、同人漫画家、デザイン会社のデザインリサーチャーとインタラクションデザイナー、製品開発チームのUXコーチ／デザイナーなど、様々な仕事をしてきました。</p><p>デザインエージェンシー（デザインエージェンシーとは企業の依頼を受けてデザインをする会社です）では、国際的なクライアントと一緒に、デジタルおよび物理的なシステム全体（お店の導線設計）のリサーチ、戦略立案、プロトタイピングを行いました。2年前にエージェンシーからプロダクト開発に転職しました。その時、私はアジャイル開発という、デザインナーにとってほとんど知られていなかった世界に出くわしました。私はデザイン主導でデザイン思考の環境で仕事をすることに慣れていたので、この切り替えは大きなカルチャーショックでした。</p><p>アジャイル開発に慣れていない人のために、<a href="https://medium.com/u/d3d3e229335a">Amanda Stockwell</a>は<a href="https://medium.com/@amanda.stockwell/design-thinking-lean-and-agile-oh-my-2e72c5f36375">アジャイルをうまく要約してくれています</a>。（英語のみ）</p><blockquote>アジャイルはソフトウェア開発のアプローチです。アジャイルは、変化するニーズを理解したり、対応したりする能力に苦労していた伝統的な「ウォーターフォール」への不満から生まれました。</blockquote><blockquote>ソフトウェア開発者は、新しい構築方法の実験を始め、より良い仕事をするためにチームを導くための共通の価値観と原則を思いついた。</blockquote><p>そして、デザイン思考については<a href="https://medium.com/u/86548f7dbecb">IDEO</a>の<a href="https://jp.ideo.com/post/our-approach">サイトから</a>。</p><blockquote>デザイン思考に単一の定義はありません。それはアイデアであり、戦略であり、方法であり、世界を見る方法です。デザイン思考は、個人、組織、ウェブサイトの枠を超えて成長してきました。そして成熟するにつれ、その歴史は深まり、その影響力は進化していきます。</blockquote><blockquote>IDEOにとってデザイン思考とは、創造性によって問題を解決する方法です。</blockquote><p>表面的には、どちらも人々が問題を解決し、より良い製品を構築するための手助けをするシステムです。アジャイルとデザイン思考には多くの類似点がある。しかし、今日では似ているように見えても、全く別の歴史を持っています。</p><h4>アジャイルとデザインのそれぞれ別の歴史</h4><figure><img alt="「アジャイル開発 “と “デザイン思考 」で書かれた2本の木の図。" src="https://cdn-images-1.medium.com/max/640/1*4EWp1jM-8Y2BX8ZcktmUOA.gif" /></figure><p>アジャイルの前にはウォーターフォールがあった。ウォーターフォールは工業製品の制作を支援するために作られた。企業がハードウェアを出荷する場合、生産後の変更は非常に難しく、すべてを事前に決めておかなければなりませんでした。デジタルソフトウェアやコードの登場で、世の中の「製品」とは何かという考え方が一変しました。</p><p>デザイナーなので、私が知っている範囲でのスクラムは、ソフトウェアはリリース後も常に改良を重ねることができるため、ラグビーのカオスなエネルギー（つまり<a href="https://blogs.itmedia.co.jp/hiranabe/2012/06/origin-of-scrum-reopened-1.html">スクラム</a>）から<a href="https://ja.wikipedia.org/wiki/%E3%82%A8%E3%82%AF%E3%82%B9%E3%83%88%E3%83%AA%E3%83%BC%E3%83%A0%E3%83%BB%E3%83%97%E3%83%AD%E3%82%B0%E3%83%A9%E3%83%9F%E3%83%B3%E3%82%B0">エクストリームなプログラミング</a>に至るまで、新しい製品を作るためのより良い方法を模索するためのアイデアを提案し始めました。これらのプロセスが、今日のアジャイル思考やリーン思考と呼ばれるものを形作っていったのです。</p><p>同様に、デザイン思考は、環境保護や持続可能性など、<a href="https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Purcell/bucky.html#Synergetics">製品以外の「システム」について考える必要性がある工業デザインから始まりました</a>(英語のみ）。そこから、それは人間とコンピューターの相互作用と力を合わせて、物理的なシステムとデジタルシステムの両方の研究になりました。行動心理学および民族誌学の分野と混合されたとき、現代設計思考およびhuman-centered designは生まれた。</p><p>過去50年間、これらの考え方は互いに独立して成長してきました。彼らは異なるソースから独自の用語や考え方を発展させてきた。</p><h4>現代のアジャイルとUX統合の問題点</h4><p>多くの賢い人たちは、すでにアジャイルやUXインテグレーションについて考え、採用している。<a href="https://www.amazon.co.jp/Lean-UX-%E7%AC%AC2%E7%89%88-%E2%80%95%E3%82%A2%E3%82%B8%E3%83%A3%E3%82%A4%E3%83%AB%E3%81%AA%E3%83%81%E3%83%BC%E3%83%A0%E3%81%AB%E3%82%88%E3%82%8B%E3%83%97%E3%83%AD%E3%83%80%E3%82%AF%E3%83%88%E9%96%8B%E7%99%BA-LEAN/dp/4873118050/">Lean UX</a>や<a href="https://www.amazon.co.jp/%E3%83%87%E3%82%B6%E3%82%A4%E3%83%B3%E3%82%B9%E3%83%97%E3%83%AA%E3%83%B3%E3%83%88-%E2%80%95%E3%83%97%E3%83%AD%E3%83%80%E3%82%AF%E3%83%88%E3%82%92%E6%88%90%E5%8A%9F%E3%81%AB%E5%B0%8E%E3%81%8F%E7%9F%AD%E6%9C%9F%E9%9B%86%E4%B8%AD%E5%AE%9F%E8%B7%B5%E3%82%AC%E3%82%A4%E3%83%89-Richard-Banfield/dp/4873117801">デザインスプリント</a>があり、一部のプロダクトチームはスプリントの中でブレインストーミングやユーザーテストを採用していることさえあります。私たちがどのように進歩してきたのかを考えると、私は興奮しています。</p><p>しかし、私たちがコーチングしているチームが、デザイン思考のマインドセットを適用せずにデザインプロセス（ワークショップ、ペルソナ、顧客フィードバックなど）を統合しているのをよく目にします。その結果、これらのプロセスからのアウトプットは、開発スプリントとは別のトラックになってしまうか、バックログに永遠に残るものになってしまいます。一方で、チームは100%必要だとは思えない機能を作り続けています。</p><p>2つの異なる言語を話し、2つの異なる考え方で考えていることを理解していなければ、アジャイルとUXを統合するのは非常に難しい。</p><figure><img alt="「言葉 」と言っている人 — 私たちが使っている言葉や意味、そして “マインドセット “と言っている脳。 — 私たちが信じていること" src="https://cdn-images-1.medium.com/max/640/1*wVebpHw8Nwu23AW9NtZlmg.gif" /></figure><p><strong>「言葉」</strong>とは、私たちが使っている言葉や表現、そしてその言葉が私たちにとって何を意味しているのかということです。犬のことを考えてみてください。あなたと私は、犬の概念（4本足で、しっぽを振っている）については同意するかもしれませんが、その言葉が私たちにとって何を意味しているかによって、私たちが思い描くものは大きく食い違うことがあります。</p><p><strong>「マインドセット」</strong>とは、私たちが真実だと信じていること、私たちの行動や行動、態度のことです。これらは、築き上げるのに長い時間がかかり、習慣化されているため、取り壊すのにも長い時間がかかります。</p><p>まず、「Is the design done?」というフレーズの「<strong>言葉」</strong>の食い違いを見てみましょう。</p><figure><img alt="デザインはできているか？”というフレーズと、「デザイン 」と 「できた」という言葉の両方が誤解される可能性があるすべての方法の絵。" src="https://cdn-images-1.medium.com/max/640/1*rEhiKlYX-Onkh2pEpWDrvw.gif" /></figure><p><strong>「デザイン」</strong>という言葉は、以下の3つのうちの1つ以上を意味します。</p><ul><li><strong>私たちデザイナー中心になって作ったもの：</strong>ワイヤーフレーム、プロトタイプ、カスタマージャーニーマップなど。★</li><li><strong>モノが他のモノとどのように関係しているのか：</strong>アーキテクチャやユーザージャーニーなど。</li><li><strong>なぜソレが存在するのか：</strong>デザインの合理性やプロダクトが解決しようとしている問題など。</li></ul><p>★「デザイナー中心になる」というフレーズは、あまり好きではないのですが、分かりやすいから使います。この成果物は、デザイナーだけではなく、チーム全体の責任だと考えています。</p><p><strong>「できた 」</strong>という言葉を確認するためには、これらの質問があっているかもしれません。</p><ul><li><strong>「作ったモノを見せて」: </strong>何でも良いのです。デザイナーやノンデザイナーと共有するための仕掛中のものでも良いのです。</li><li><strong>「これは変更されるのか？」:</strong> とりあえずこのスプリントでは 「最終版 」なのか？来月に更新しますか？それとも来年？</li><li><strong>「これはコードで実装できるのか？」: </strong>今すぐコードで作ってもいいのか、それとも待つ必要があるのか？</li></ul><p>これよりもはるかに多くの定義があります。しかし、これらの単純な定義を取っても、「Is the design done?」という質問には、単純な質問の中に様々な複雑さが隠されていることを意味します。</p><h4>では、どの定義が正しいのか？</h4><p>チームメイトと一緒に「Is the design done?」という質問の意味をもっと深く探ってみると、出てくるのはこのシンプルな質問です。</p><figure><img alt="「これを作り直さなければならないのか？」と「そうかもしれませんが、作り直すのはそんなに悪いことなのでしょうか？」" src="https://cdn-images-1.medium.com/max/640/1*xlACPD5jSLHJyAZwFg96YQ.gif" /></figure><blockquote><strong>「これを作り直さなければならないのか？」</strong></blockquote><p>私のチームメイトは、設計ができていなければ、手直しや再構築が避けられず、余分な時間とエネルギーが必要になるのではないかと心配しています。</p><p>デザイナーとしての私の反応はこうです。</p><blockquote><strong>「そうかもしれませんが、作り直すのはそんなに悪いことなのでしょうか？」</strong></blockquote><p>そしてここに、UXとアジャイルを統合することの第二の難しさがあります。</p><h4>柔軟性のある媒体と柔軟性のない媒体の導入</h4><p>私のこれまでの役割の一つであるイラストレーターとしてのお話をさせてください。美術の分野では、アートを作るために使う道具のことを<strong>「媒体」</strong>(medium)と呼びます。媒体には、柔軟性のある媒体(flexible medium) と柔軟性のない媒体 (inflexible medium) があります。ここでいう柔軟性と柔軟性のないというのは、良いとか悪いとかいう意味ではなく、単にカテゴリーのことである。それぞれのメディウムは、あるプレゼンテーションやスタイルに適しています。</p><figure><img alt="柔軟性のある媒体(flexible medium) と柔軟性のない媒体 (inflexible medium)" src="https://cdn-images-1.medium.com/max/640/1*v5q01QplFK7r5dWHAHCaCQ.gif" /></figure><p>では、柔軟性のある媒体と柔軟性のない媒体をどのように区別するのでしょうか？<strong><em>「やっちまった時に、どれだけ簡単にやりなおせるか？」</em></strong>という質問です。</p><p>柔軟性のある媒体とは、鉛筆やデジタルキャンバスのようなものです。鉛筆は消すことができます。デジタルキャンバスのレイヤーは、隠したり、調整したり、完全に削除することができます。ミスをしてしまっても、通常は5秒もかからずに元に戻ることができます。紙やデジタルキャンバスは何度でも再利用できます。</p><p>柔軟性のない媒体は、インクや水彩画のようなものです。インクが紙の一部に置かれると、それは永久に紙の繊維を浸しています。あなたはペンのミスから回復することができますが、インクをカバーするためにホワイトアウトなどを使用する必要があるかもしれません。もしくは、紙を捨ててやり直すこともできます。</p><p>いくつかの例を見てみましょう。</p><figure><img alt="進行中のデジタルドローイング。画家は何度もミスをして、絵の一部をやり直しています。" src="https://cdn-images-1.medium.com/max/480/1*ZzGNP_mkRfZvDbYUuLMQfQ.gif" /><figcaption>私はこのキャラクターやシリーズを所有しているわけではありませんが、とても好きなキャラクターです。</figcaption></figure><p>柔軟性のある媒体のもう一つの例がデジタルです。この絵はiPadのProcreateで描きました。上のアニメーションを見ればわかるように、私は常に消したり、描き直したり、調整したりしています。手を広げて描いたのですが、最終的には文脈に合っていないので、消去してやり直します。これをプロセス全体を通して行っています。私は常に実験しています。</p><p>消して、調整して。消す。このプロセスの途中で誰かに「この絵はできたの？」と聞かれても、はっきりとイエスかノーかは言えないでしょう。実験中なのか、実験がうまくいったのか、うまくいかなかったのか。描かれたと感じたときに、描かれたことになる。この場合の「できた」の論理的な定義は、絵が正しいプロポーションと重さ、正しい色のバランス、その他の測定可能な基準を持っているかどうかに基づいています。しかし、デザイナーは論理だけではありません。</p><p>デザインとは、論理と感情がイコールである。この例は感情の部分です。デザインは、デザイナーたちが満足したり、見ていて一体感や調和を感じたりしたときに行われます。ビジョンがあって、そのビジョンを満たすために実験をして、実験の結果をもとにビジョンを変えていく。</p><p>このような実験的思考をサポートしてくれるのが柔軟性のある媒体であり、クリエイターは鉛筆と紙、ペンとポストイット、SketchとAdobe Illustratorなど、常に柔軟性のある媒体を使っています。</p><figure><img alt="コミックをスケッチするプロセス。サムネイル、スケッチ、そしてインク版。" src="https://cdn-images-1.medium.com/max/640/1*SlTcR4YfPYWVztxo8K-_Ag.gif" /></figure><p>これを、私がインクで伝統的な漫画を描く方法と比較してみてください。私はインパクトが強いし、「いい感じ」があるからこそインクが大好きです。しかし、インクが紙に触れた途端に完全に染まってしまうので、魔法のように持ち上げることはできません。だから、事前にプランニングをしています。レイアウトや流れを把握するためにサムネイルを描いて、下絵を描きます。その上にきれいな紙を重ねて、インクでなぞっていく。</p><p>すべてのレイヤーには、最終的な結果に向けての準備のための目的があります。伝統的な漫画を描くとき、最初はページがどのようなものになるかわからないかもしれませんが、下絵を完成させれば、インクで描かれた結果がどのようなものになるのか、想像できます。</p><p>このプロセスの途中で誰かが私に<strong><em>「この絵はできていますか？」</em></strong>と尋ねてきたら、私は簡単に答えられます。と聞かれたら、私は簡単に答えることができます。もしサムネイルが完成していたら、私はまだスケッチの上に紙を重ねていないので、明らかに絵は完成していません。すべてのレイヤーとプロセスが完了したら、それは完了です。</p><p>もちろん、ここでは私はまだ何かが完了したかどうかを私に伝えるために感情に頼っていますが、作品が完了したときの基準を私に与えるためにいくつかの余分なプロセスを追加しました。</p><p>柔軟性のない媒体は、このような層状の思考をサポートしてくれます。それぞれのレイヤーで実験が行われるかもしれませんが、プロセスの各ステップ間には明確な区切りがあります。</p><h4>コードは柔軟性のない媒体です。</h4><p>申し上げにくいのですが、コードは柔軟性のない媒体です。</p><figure><img alt="「コードは柔軟性のない媒体である 」というテキスト。" src="https://cdn-images-1.medium.com/max/640/1*9miYXdUPaqr2xpsx9EBKHw.gif" /></figure><p>1970年代の過去のハードウェアに比べれば更新は簡単かもしれませんが、コードは何層にもわたったパターンで作られています。柔軟性のない媒体だからといって、一度セットアップしたら変更できないというわけではないことを覚えておいてください。インクのミスを元に戻すことはできますが、鉛筆よりも難しいだけです。</p><p>コードの中には、CSSのように、もっとflexibleで実験的な部分があることもあります。他にも、データベースやアーキテクチャのように、はるかに柔軟性のない、変更するのが難しいものもあります。</p><p>コードは柔軟性のないので、それを実装するためには何層にも分けて考えなければなりません。上で書いた通り、「柔軟性のない」は良い意味と悪い意味ではありません。単なるカテゴリーです。そして、デザイナーやクリエーター、柔軟性のある媒体を使っている人たちは、常にレイヤーで考えているわけではありません。デザイナーたちは実験で考えています。</p><p>あなたはこの時点で、<em>「いや、コードはもっとflexibleであるべきだ」</em>と思うかもしれません。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*7mZ5SWJTwRGYcvVCEVMdxA.gif" /></figure><p>そして、あなたは正しい。私もコードはもっと実験的であってほしいと思っています。アラン・ケイ、ブレット・ビクター、ブレンダン・ドーズのような技術者たちも、コードの境界線を押し広げ、より柔軟で実験的な相互作用の方法を見つけてきました。私がインタラクションデザイナーになった理由は、コードがもっと実験的で芸術的になるのを見たかったからです。</p><p>しかし、私たちが大規模なソフトウェアシステムを構築するために使用している言語は、いまだに柔軟性のない媒体です。</p><h4>では、どうすればいいのでしょうか？</h4><p>では、どうすればいいのでしょうか？デザイナーは柔軟性のない媒体に適応するためにレイヤーの考え方を採用しているのか、エンジニアは柔軟性のある媒体に適応するために実験的な考え方を採用しているのか。私の中のアーティストの考えだと<strong><em>バランス</em></strong>を重視しています。</p><p>コンテクストに応じて、同時に両方の方法を考えられるようにしなければなりません。例えば、絵画であれば、色は実験的だと思っているので柔軟性のある媒体の方が好きですが、白黒の場合はインパクトが強いので柔軟性のない媒体の方が好きです。自分が何を作ろうとしているのかに基づいて媒体を切り替えています。</p><p>バランスをとるために、2つのアドバイスがあります。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ij2tB_RVOPCoqxJd_qiqgA.gif" /></figure><p><strong>開発者よ、愛する子を殺せ。</strong></p><p>これは言うのは簡単だが、実行するのは難しい。</p><p>美大に通っていた頃は、1つの作品に4時間以上かけたことはありませんでした。私は漫画家になりたかったので、丁寧な絵よりも速描きを優先していました。私の自慢話を聞いた先生は私に課題を与えました。</p><blockquote>「次の作品は4時間以上かけて制作してほしい。題材は何でもいい、時間だけでいい」と言われました。</blockquote><p>彼の指示に従い、何時間も何時間もかけて作品を作りました。丹精込めて作った作品を彼に見せたとき、とても誇らしく感じたのを覚えています。</p><p>彼は何も言わずに、近くの瓶から炭の粉を一握り取ってきて、私の美しい作品に塗りつけてくれてしまいました。私は完全にショックを受け、絶望しました。時間を無駄にしてしまった。</p><blockquote>「もう一回やって 」と先生は優しく言いました。</blockquote><p>先生が台無しにしたものをやり直そうと机に戻ったとき、私は怒りがこみ上げてきました。先生は優しい表情でゆっくり私に近づき、こう言いました。「あなたがこのために費やした4時間は、今では失われたように感じますが、そうではありません。あなたは学びを手に入れました。君ならもっと良い作品が作れると確信している。」</p><p>先生の言う通りでした。</p><p>その信じられないほど賢明な美術の先生から学んだことは、何かを作ることに費やす時間は決して損ではないということです。ものを作ることは、私たちの思考を助け、アイデアを伝えるのに役立ち、何かを作ってやり直すたびに、私たちは解決策に近づいていく。最初のアイデアがうまくいくと思ってはいけません。絶え間ない反復と制作を通してのみ、アイデアは素晴らしいものになるのだ。</p><p>現在のアジャイルチームでよく見かけるのは、物を捨てることを恐れていることです。デザインができているかどうかを尋ねるときでさえ、この恐怖を感じます。なぜなら、もしできていなければ、チームは手直しをしなければならないからです。アジャイルでもデザインでも、実験や反復を奨励しようとしているような反復プロセスでは、この恐怖はチームの速度を殺し、最終的には這うように遅くなってしまうだろう。</p><p>私はそれを理解しています。コードは柔軟性のない媒体ものです。しかし、たとえそれが私たちが丹精込めて作った最愛のものであっても、時にはそれを殺さなければならないこともあります。愛する子を殺すのは限りなく難しい。喜んで殺すのはもっと難しい。</p><p>でも、やればやるほどうまくなるし、やればやるほどいい開発者になれることを約束します。</p><h4>デザイナーの皆さん、チームと自分自身に正直になってください。</h4><p>ユーザーが自分のものを気に入らなかったらどうなるかなんて誰も考えたくない。今まで観察してきた多くのチームは、もともと実験的な性格を持っていますが、ビジネスサイドから<strong><em>「早く失敗してもいいから成果を出せ」</em></strong>という多くのプレッシャーを受けています。</p><p>あなたは実験と失敗の提唱者であり、常に問いかけていなければなりません。</p><blockquote>「作っているものが期待通りにならなかったら？すべてを捨てなければならないかもしれません。」</blockquote><p>チームを正直にして謙虚にしておくことが、この実験的な考え方を統合するためのコツです。そして、戦わなければならないかもしれません。</p><p>デザイナーはユーザーが何を考えているかを知っていなければならないという思い込みがあり、自分のアイデアが失敗したら、その人は良いデザイナーではないと思います。しかし、良いデザイナーの尺度は、アイデアに15％、運5％、粘り強さ80％です。デザイナーよ、粘り強く行動せよ！</p><p>粘り強さは一人で達成するのは難しいので、チームを頼りにしてサポートすることが必要です。愚かな決断をしたときは責任を取りましょう。しかし、あなたも開発チームもビジネスも、人々に愛されるものを作るために一緒にやっていることを忘れないでください。白熱した議論をしているときには、このベースを思い出してみてください。</p><p>夕日の中の二本の木、それぞれが手を伸ばして触れ合う。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*uksXSdIkbExTuzkTcqOOtg.gif" /></figure><h4>進むべき道を探して</h4><p>アジャイル開発とデザイン思考は、どちらも異なる環境で、異なる考えを糧にして、異なる方法で成長してきました。両者は表面上は似ていますが、言語や考え方の面では全く異なります。両者の歴史を理解することで、両者を完全に統合することの難しさを理解していただきたいと思います。銀の弾丸はありません。</p><p>yamanecoでは、約1年前からチームとの統合方法をテストしてきましたが、チームの規模、リモート/非リモート、チームの性格などによって、その方法は大きく異なります。</p><p>Lean UXのいくつかの側面は非常にうまくいくこともあれば、そうでないこともあります。私たちは、言語とマインドセットの切断を助けるために、情報をフレーミングする新しい方法を毎日試しています。</p><p>しかし、私が知っているのは、相手のマインドセットに踏み込むことによってのみ、真に共感することができるということです。</p><p>共感こそが、二人の素晴らしい、異なる個人の間の美しい結合を始めるための最良の方法なのです。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*25eRZhoFVvS410BacvlE0g.gif" /><figcaption><em>テキスト ありがとうございます。私を</em><a href="http://www.twitter.com/chostett"><em>@chostett</em></a><em>またはyamanecoを</em><a href="http://www.twitter.com/yamaneco_agile"><em>@yamaneco_agile</em></a><em>でフォローしてください。</em></figcaption></figure><p><em>アジャイルとUXの統合に関する賢い人たちのリソースがもっと欲しいなら、私は</em><a href="https://medium.com/yamaneco/want-to-integrate-agile-ux-intentionally-start-with-these-reads-a732003ea270"><em>「アジャイルとUXを統合したいですか？これらの本から始めよう。」</em></a><em>（英語のみ）</em></p><p><em>もしあなたが東京の組織で、バイリンガル（日本語と英語）のデザイン思考とアジャイル統合についてyamanecoと一緒に仕事をしたいと思ったら、</em><a href="/service/mailto:hello@yamaneco.io"><em>メール</em></a><em>か</em><a href="https://twitter.com/yamaneco_agile"><em>Twitter</em></a><em>で連絡を取ってください。</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5aa14853ebe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yamaneco/is-the-design-done-ux%E3%81%A8%E3%82%A2%E3%82%B8%E3%83%A3%E3%82%A4%E3%83%AB%E3%82%92%E7%B5%B1%E5%90%88%E3%81%97%E3%81%BE%E3%81%97%E3%82%87%E3%81%86-d5aa14853ebe">「Is the Design Done?」 UXとアジャイルを統合しましょう！</a> was originally published in <a href="https://medium.com/yamaneco">yamaneco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>