<?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 Jim Kalbach on Medium]]></title>
        <description><![CDATA[Stories by Jim Kalbach on Medium]]></description>
        <link>https://medium.com/@JimKalbach?source=rss-4b8b911d809b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ExKGA0muJIwqkB1T.jpg</url>
            <title>Stories by Jim Kalbach on Medium</title>
            <link>https://medium.com/@JimKalbach?source=rss-4b8b911d809b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:34:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JimKalbach/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[From Job Map to Experience Map]]></title>
            <link>https://medium.com/@JimKalbach/from-job-map-to-experience-map-88c1755557eb?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/88c1755557eb</guid>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 19:00:32 GMT</pubDate>
            <atom:updated>2026-10-17T19:00:32.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YAlvqLZmkeTWqCPv" /></figure><p>Ask ten people how they do laundry and you’ll get ten different answers. One starts with “I sort by color.” Another says “I check for stains.” A third jumps straight to “I grab the detergent.”</p><p>Sounds like ten unrelated habits. It isn’t. Underneath the different starting points, everyone does the same basic steps: gather clothes, sort them, clean them, remove excess water, dry them, and put them away.</p><p>That’s a job map: an illustration of the actual objective a person is trying to accomplish. [1]</p><p>People often confuse job maps with customer journey maps, and it’s easy to see why. Both lay out a chronology. Both tend to use the same left-to-right structure. But they’re answering different questions.</p><p>Take the same laundry example. A customer journey map (CJM) for a detergent brand, for instance, would look something like this:</p><ul><li>Become aware of detergent</li><li>Learn about the offering</li><li>Decide to purchase</li><li>Use the detergent</li><li>Stay loyal, or drop off</li></ul><p>That’s a real sequence that illustrates the journey people have with a company’s offerings. But let’s be very clear: a CJM tells the detergent company’s story, not the customer’s. It starts with the brand and ends with the brand. The actual job, getting laundry done, barely shows up.</p><p>In the third edition of <a href="https://www.amazon.com/dp/B0GQFQZSH7"><em>Mapping Experiences</em> </a>(MX3), I make distinctions between various map types. By my definition, an “experience map” focuses on the individual’s objective, not the brand or offering. It tracks the activity itself: what someone’s trying to accomplish, independent of any product, service, or company involved. (Note that your labels and language may vary, so focus on the distinctions I’m making here. <a href="https://www.amazon.com/dp/B0GQFQZSH7">See MX3</a> for more details.)</p><p>In this sense, job maps are closely related to experience maps, but more distant from CJMs. And it’s why you can build an experience map directly from a job map, layering the human experience on top of the objective itself. Here’s how to use JTBD and job maps to inform the creation of an experience map.</p><h3>JOB MAPS</h3><p>One of the most powerful things you can do in JTBD practice is map out the customer’s job step by step. This might seem simple: customers have a job, perform specific actions, and complete it. But when you actually sit down to capture those steps without references to tools or solutions: something remarkable happens. Messy interview notes suddenly become structured. Overlooked details come to the surface. Teams that used to argue about features start aligning around the flow of real customer work and spot where they stumble, waste time, or need to make progress.</p><p>Job mapping was pioneered by Lance Bettencourt and Tony Ulwick. In their 2008 article “The Customer-Centered Innovation Map,” they wrote:</p><blockquote><em>By deconstructing a job from beginning to end, a company gains a complete view of all the points at which a customer might desire more help.… With a job map in hand, a company can analyze the biggest drawbacks of the products and services customers currently use. [2]</em></blockquote><p>Since then, job mapping has become a core practice within the JTBD methodology.</p><p>Since then, job mapping has become a core practice within the JTBD methodology.</p><p>Key characteristics of a job map include:</p><p><strong>A job map is solution-free.</strong> Job maps don’t include tool actions like “click the button” or “open the app.” Instead, you capture what the customer is trying to accomplish, regardless of the solution they use. As a result, a job map does not describe the journey to buy, receive, set up, use, upgrade, clean, or maintain a product.</p><p><strong>A job map is timeless and universal. </strong>A good job map works whether someone is using the latest technology, a manual workaround, or no tool at all. The focus on human intent rather than the tools or processes used to act on it gives job maps longevity far greater than many other types of maps: they often remain valid for years, or even decades.</p><p><strong>A job map is a summary, not a detailed workflow. </strong>A job map captures the key steps in a process (commonly around 12–20) that must be completed to get the job done. It doesn’t detail every micro-task, nor does it include things like emotions, thoughts, or pain points. You’re looking for the essential moments that move the job forward to orient the team.</p><h3>CREATING AN EXPERIENCE MAP</h3><p>A job map gives you the chronological spine of what customers are trying to accomplish. But it leaves out emotional aspects, thoughts, pain points, and contextual details. That’s by design: job maps focus on the process. (Those other aspects are captured in separate categories within the JTBD framework. <a href="https://www.jtbdtoolkit.com/jtbd-canvas">See JTBD Canvas for more details.</a>)</p><p>Once you have a validated job map, you can upgrade it into a full experience map by layering additional dimensions onto that functional flow. This transforms a simple process view into a richer picture of the customer’s lived experience.</p><p>A job map is always solution-free. An experience map doesn’t have to be. Sometimes an experience map stays generic, looking at an activity independent of any product or organization. Other times, it’s grounded in a specific context: a company, a team, a particular solution someone’s using to get the job done.</p><p>Either way, starting from a job map keeps you honest. It gives you a human-centric foundation before you decide how much of a specific solution to layer back in.</p><p>The process is fairly straightforward.</p><p><strong>STEP 1: Start with a Validated Job Map</strong></p><p>First, define the job performer and focus job to frame your inquiry. Conduct interviews to understand the process. Then, distill well-formed job steps and arrange them chronologically. Finally, validate the resulting job map with job performers to ensure it accurately reflects how they achieve their objective.</p><p>Below is a simple process job map for a conference organizer (job performer) trying to run a conference (focus job). It’s broken into three simple sections: beginning, middle, and end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*I1O8AHHnLXNEgB4r" /><figcaption>This simple job map shows the process of how a conference organizer (job performer) runs a conference (focus job).</figcaption></figure><p>The job map alone can guide internal conversations. Use it to identify pain points as a team, or overlay your current projects to see which parts of the job you’re addressing and which you’re ignoring.</p><p>A <em>column arrangement </em>organizes steps under stage headers. This is the format I recommend for most situations: a map with 6–8 stage headers (columns) and 12–20 total steps distributed across those stages. It’s scannable. People can quickly see the progression from beginning to end without following arrows or getting lost in boxes.</p><p>The column format creates natural units for team discussion and evaluation. In collaborative sessions, you can assess the map stage by stage, asking, “How well do we support customers here?” The columns become zones of conversation.</p><p>With the job map as your foundation, add more rows (swim lanes) below it to capture other aspects of the experience. Typically, you’ll want to layer three to five additional dimensions onto the job map, such as:</p><ul><li><em>Thoughts and questions: </em>What’s going through the customer’s mind at each step? What uncertainties do they face?</li><li><em>Emotions:</em> How do they feel as they move through the process? Where are the highs and lows?</li><li><em>Pain points: </em>Where do they struggle? What causes frustration, anxiety, or delays?</li><li><em>Opportunities:</em> Based on the struggles and emotions, where can you create value?</li></ul><p>Draw from your research to populate these swim lanes. Look for patterns across interviews and highlight those moments.</p><p>The job steps (columns) from your job map create natural zones for organizing these experiential elements. Each column becomes a conversation space where you can see the full picture: what customers are trying to do, how they feel about it, and where they need help.</p><p>Once you have the functional flow and experiential layers, refine the diagram for your audience. Clean up the language, adjust the layout for clarity, and add visual elements that make the story clear. The result is a human-centered experience map grounded in jobs, not solutions.</p><p>The example below shows an example of an experience map based on a simple job map. This diagram was created in collaboration with Hennie Farrow and <a href="https://www.amazon.com/dp/B0GQFQZSH7">explored in further detail in MX3</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HhHA5S4EVwMhQdMe" /><figcaption>This experience map shows how to run a conference from the organizer’s point of view.</figcaption></figure><p>The top row lists actions based on the job steps. Note that they’ve been slightly modified in the transition from the job map to the experience map. That’s OK. You still get the benefit of starting with a neutral job map.</p><p>Below that, additional swim lanes capture thoughts, emotions, pain points, and goals at each stage. This particular example is a graphically refined diagram suitable for presentation, but remember: the power of a diagram lies in the information it shows and the story it tells, not the visual appeal.</p><p>One more layer is worth calling out. In the example above, the bottom row lists desired outcomes, the specific measures someone uses to judge whether the job got done well. These come directly from JTBD outcome-driven innovation, not from the mapping process itself. Adding them is optional, but it’s a direct example of how JTBD and experience mapping reinforce each other.</p><p>Overall, this approach provides a common artifact to orient teams. Mapping independent of solutions or technology also reveals opportunities you might otherwise miss. When you look beyond the parts of the experience where customers interact with you, you can spot where they struggle before they ever reach you, or where they need help after your interaction ends.</p><p><strong>References</strong></p><p>[1] Note that <a href="https://strategyn.com/jobs-to-be-done/customer-centered-innovation-map/">the term Job Map™ is trademarked by Tony Ulwick and Strategyn</a>.</p><p>[2] Lance Bettencourt and Anthony Ulwick, “<a href="https://hbr.org/2008/05/the-customer-centered-innovation-map">The Customer-Centered Innovation Map,” <em>Harvard Business Review</em></a> (2008)</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/from-job-map-experience-jim-kalbach-g4qfc/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88c1755557eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Conversation with Jay Gerhart: Guiding Innovation Teams with JTBD]]></title>
            <link>https://medium.com/@JimKalbach/a-conversation-with-jay-gerhart-guiding-innovation-teams-with-jtbd-48448b8ac8c7?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/48448b8ac8c7</guid>
            <category><![CDATA[jtbd]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[jtbdtoolkit]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Sat, 08 Apr 2023 14:23:34 GMT</pubDate>
            <atom:updated>2023-04-08T14:23:34.875Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZZJWZ9yQVJ0ngM5YKtzExA.jpeg" /></figure><p><a href="https://www.linkedin.com/in/jay-gerhart-93001490/">Jay Gerhart</a> is Healthcare Strategist at <a href="https://atriumhealth.org/">Atrium Health</a>, the 5th largest nonprofit integrated health system in the nation with approximately 150,000 teammates. He works on the corporate innovation team in Charlotte, NC called the Innovation Engine.</p><p>Business model innovation is a key focus area in his project work, as well as teaching their innovation process to teammates, called Design for Impact. JTBD plays a large role in their overall approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*403u-j1MTdfggApoZCS-gQ.jpeg" /><figcaption>Jay Gerhart, Healthcare Strategist at Atrium Health and JTBD enthusiast</figcaption></figure><p>Jay also produces and co-hosts “<a href="https://medium.com/a-sherpas-guide-to-innovation">A Sherpa’s Guide to Innovation</a>” podcast, which now has 114 episodes. Jay was our guest on “<a href="https://youtu.be/SZu8eGVd7Ys">JTBD Untangled</a>” where he talked about how he guides and leads his teams to success with JTBD. Jim caught up with him afterward the session for this interview.</p><p>— — — — — — — — -</p><p><strong>JIM: How and when did you get into JTBD?</strong></p><p>JAY: I spent the vast majority of my career at Atrium Health in strategy and planning. In 2016, I was working with colleagues to better define and deploy a consumer-focused strategy for the system. This was very different work from what I was used to. We were thinking about a new type of primary care product and we realized that we didn’t really have a product development process. However, we did have an innovation team, so I started learning more about what they did.</p><p>Two teammates on that team, Ann Somers Hogg (now with the Christensen Institute) and Will Behrmann, had recently taken a course by the late Dr. Clayton Christensen at Harvard Business School. They learned about JTBD theory and were eager to learn more about how to apply it. One of their instructors recommended Bob Moesta.</p><p>To make a long story short, the team I was working with joined forces with Ann Somers and Will to hire the ReWired Group to conduct JTBD interviews in the area of on-demand care. We had a dual purpose — (1) inform our consumer strategy work and (2) teach us how to do JTBD on our own. Needless to say, working side-by-side with Bob was an incredible experience.</p><p>It’s not an exaggeration to say it was life-changing. We were all hooked on JTBD from that time on.</p><p><strong>JIM: Amazing that you got the opportunity to work directly with Bob Moesta. Sounds incredible indeed. How have you used JTBD in practice? Can you give an example?</strong></p><p>JAY: Our team’s business model innovation process is called Design for Impact. One key element is obtaining a strong Customer Understanding. JTBD is the foundation of that, providing the mindset, language and methods we employ to understand our customers. So JTBD is present in some way in each and every body of work we carry out.</p><p>One recent example was in the area of primary care. The physician executive over our primary care division asked us to perform interviews to better inform some of their ongoing work from the consumer perspective. We conducted two parallel interview streams: (1) Switch interviews to understand what causes people to hire or fire primary care, and (2) what we call “standard” JTBD interviews to understand functional, social, and emotional jobs that people have related to their health and wellness.</p><p>As part of the second stream, we learned what pains and gains people experienced when trying to fulfill these jobs, what solutions they hired and fired, and how context might impact these elements.</p><p>This turned out to be one of our most extensive customer discovery efforts we’ve ever conducted, and we expect to be leveraging the insights for years. Another aspect that we enjoyed about the work is that two members of the primary care division participated in the interviews and analysis — one a care provider, another an administrator.</p><p>Furthermore, the physician executive took our findings and summarized them from his own perspective to communicate across the division. Partnering with our business owners is really important to our team, so this was an exciting step in helping our organization become more JTBD-centered.</p><p><strong>JIM: Great example — thanks for sharing. How would you summarize the impact of JTBD on your team’s work? What business impacts have you seen from JTBD?</strong></p><p>JAY: It’s been transformational for our team — we’re still on the journey of making it transformational for our organization, as it is a very large and growing organization. But that is our aspiration. As I mentioned earlier, JTBD provides the foundational mindset, language and methods for our innovation process, Design for Impact. We integrate it into Alex Osterwalder’s Value Proposition Canvas and Business Model Canvas.</p><p>Taken all together, these frameworks provide a structured understanding of our customers and our business models. As we discussed during JTBD Untangled, we continue to build out our JTBD toolkit to match our project needs — essentially identifying and fulfilling our JTBD for JTBD! Is that too meta?</p><p>Back to your question. Our team has articulated four key elements of our innovation mindset: Empathy, Curiosity, Collaboration, and Action. JTBD is like a channel for the first two. The method we learned from Bob is grounded in Empathy and Curiosity.</p><p>As we’ve expanded our JTBD toolkit, learning from thought leaders such as yourself and ODI practitioners like Scott Burleson, we are sharpening our skills in articulating jobs, pains and gains — key elements of the Value Proposition Canvas. The different methods and tools give our team a more robust portfolio of ways we can approach business problems and opportunities.</p><p><strong>JIM: How do you begin to assess the impact of JTBD on the organization?</strong></p><p>JAY: I’ll share one simple way we measure the impact of JTBD.</p><p>Outside of our group, we consider it a win when our leaders use the mindset and language, unprovoked. Some months ago, I was in a meeting with medical group leaders talking about our various digital pathways to our services. The dialogue was mostly in the supply-side realm, using Bob Moesta language. A senior physician executive spoke up and said something to the effect of “Wait, let’s look at this from the Jobs to Be Done perspective.” That warmed my heart!</p><p>I know it may not sound like much, but instances like that are a big deal, particularly in health care, which is heavily expertise driven. The conversation then tilted more to the demand-side, and people started thinking more from the perspective of health care consumers — which we all are.</p><p>We have some pockets of physicians and administrative leaders who use the words in a way that reflects the mindset — the way of seeing, as you put it in your book. Changing the conversation is meaningful.</p><p><strong>JIM: I’ve always said that one indication of success is when others start using your language, so that makes total sense. <br>What advice would you give someone looking to get started with JTBD?</strong></p><p>JAY: You’d think this would be a simple question for me to answer, but the reality is that it depends. It depends on your context and desired progress. So first, you should explore your own Job to Be Done for Job to Be Done.</p><p>Also, there is a growing body of helpful resources on a range of JTBD methods. So, I’ll offer a menu of suggestions for the reader to select from:</p><ul><li><a href="https://www.amazon.com/Competing-Against-Luck-Innovation-Customer/dp/0062565230/"><em>Competing Against Luck</em></a> is a good starting place for a high-level overview, more of a strategic perspective. A bit of a shortcut would be reading the September 2016 <em>Harvard Business Review</em> article “<a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">Know Your Customers’ Jobs to Be Done</a>” by the authors Dr. Clayton Christensen, Karen Dillon and Taddy Hall. However, this won’t equip you to start applying JTBD deeply to your work. One benefit of the book is that it may equip you to better explain to executives in your organization why they should hire JTBD.</li><li>One option is your book, Jim. The benefit of the<em> </em><a href="https://www.amazon.com/Jobs-Be-Done-Playbook-Organization/dp/1933820683"><em>JTBD Playbook</em></a> is that it covers the full range of JTBD perspective and methodologies. The reader can then start working with the methods that resonate with them, fit in their context, and meet their objectives. However, there is some risk of becoming overwhelmed with what methods to select and where to start.</li><li>Alternatively, someone starting with JTBD could select between Switch and ODI. For Switch, the book <a href="https://www.amazon.com/Demand-Side-Sales-101-Customers-Progress/dp/1544509987/"><em>Demand-Side Sales</em></a> is a great practical start. And Bob has many podcasts and YouTube videos to support learning.</li><li>For ODI, you have excellent content in your book on creating Job Maps as a starting point. I created my first job map with your interview guide. I also find that Tony Ulwick’s Medium post <a href="https://medium.com/outcome-driven-innovation-is-jobs-to-be-done/outcome-driven-innovation-odi-is-jobs-to-be-done-theory-in-practice-2944c6ebc40e">“Outcome-Driven Innovation: JTBD Theory in Practice”</a> is a good starting point for ODI.</li><li>These are all good potential starting points, but I’ll offer one more that is highly accessible — David Duncan’s <a href="https://marketdetective.com/"><em>The Secret Lives of Customers</em></a>. Most of the book, Part 1, is in a highly entertaining narrative form. Part 2 is a concise explanation of how you get started as a “Market Detective.” The method is not as rigorous as Switch or ODI, but it’s quickly actionable. If you or your team want to “get out of the building” and start uncovering jobs quickly, David offers a highly accessible framework. You can read the book in a sitting or two.</li></ul><p><strong>JIM: That’s a great list of resources. Are there any practical steps you’d recommend folks take to get started using JTBD? </strong><br>JAY: Reach out to friends or connections who are JTBD practitioners to get their perspective. I am happy to connect with your readers and talk with them to better understand their context and desired progress, and to offer any guidance I can. I find that some folks are intrigued by JTBD but struggle to start.</p><p>The range of approaches and different voices can create anxiety around hiring JTBD. The important thing is to start. Start building the JTBD muscles in your personal life — think about what jobs arise for you each day. Interview yourself about them. Maybe interview friends or family — but don’t drive them crazy with it!</p><p>Lastly, I would be remiss not to plug my own podcast, A Sherpa’s Guide to Innovation. JTBD has been a topic of numerous episodes, and we have been fortunate to interview many JTBD thought leaders, including yourself.</p><p><strong>JIM: Thanks, Jay!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48448b8ac8c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ideas Are Overrated]]></title>
            <link>https://medium.com/hackernoon/ideas-are-overrated-cad21c82066b?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cad21c82066b</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Sat, 07 Oct 2017 13:18:15 GMT</pubDate>
            <atom:updated>2019-05-22T05:57:10.787Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*azj0fzae2wKUItT_XdYOrg.png" /></figure><p>Generating ideas is fun — addictive even. I should know. As a design lead, I’ve facilitated many ideation sessions in my career.</p><p>You’ve probably experienced this, too: a team gets together for a few hours or days to brainstorm ideas. “Go for volume,” they’re instructed. At the end, there may be hundreds of ideas on the workshop room wall. Success is tacitly measured by the number of sticky notes used.</p><p>But volume of ideas is rarely the problem in most companies. I’ve never come across an organization that doesn’t have <em>enough </em>ideas. In fact, most are swimming in ideas they don’t know how to act on. Yet, we continue to engage in exercises that add more and more ideas to the pile.</p><p>Part of the problem is an erroneous Darwinistic view of the <a href="https://hackernoon.com/tagged/idea">idea</a> lifecycle. We assume that the best ideas will simply rise to the surface on their own merit. If you can just collect enough ideas, the chances of a few of them surviving will simply increase mathematically.</p><p>That’s a false hope. The best ideas don’t always win.</p><p>Instead, natural forces within any organization act to keep ideas down, regardless whether they’re good or not. Chief among these is <em>uncertainty</em>, a leading idea antibody within enterprises.</p><p>New concepts represent a gamble to risk averse managers, even if they are well-expressed in a high-fidelity prototype.</p><p>Many ideas seem great at the time we have them. “This is it! We’re going to save the company!” we think with confidence. But when hard decisions need to be made and those innocent ideas hit reality, even the best ones wither quickly.</p><p>Michael Schrage, MIT fellow and author of <a href="https://www.amazon.com/dp/B00NOC852G/"><em>The Innovator’s Hypothesis</em></a>, goes one step further. He believes good ideas are harmful. He writes:</p><p>Good ideas are actually the enemy of productivity. A focus on good ideas inflicts terrible damage–operational and emotional–on good managers and good businesses alike. Business ideaholics, not unlike meth addicts and other junkies, are always looking for the next fix.</p><p>Good ideas overpromise and underdeliver, Schrage contends. They distract our energy away from the “ugly duckling” ideas that could turn into swans, if given the attention.</p><p>Part of the problem is that we place too much on the face value of ideas. In reality, it’s difficult (if not impossible) to recognize a great idea in its infancy. We assume there will be some “a-ha” moment when everything feels just right.</p><p>The history of <a href="https://hackernoon.com/tagged/innovation">innovation</a>, however, shows that even the most profound innovations weren’t recognizable as such at first. Scott Berkun makes warns of the false notion of epiphany in his book <a href="https://experiencinginformation.com/2008/02/03/review-of-myths-of-innovation/"><em>The Myths of Innovation</em></a>. He writes:</p><p>Most innovations come without epiphanies, and when powerful moments do happen, little knowledge is granted for how to find the next one. Even in the myths, Newton had one apple and Archimedes had one Eureka. To focus on the magic moments is to miss the point. The goal isn’t the magic moment: it’s the end results of a useful innovation.</p><p>Take the Wright Brother’s first flight. There were only a handful of people watching the historic event, and it took them six years to even sell the first airplane. No one saw a multibillion dollar industry stemming from their invention. It’s just hard to recognize a truly great idea in its infancy.</p><p>Still, we’re obsessed with the <em>origin </em>of ideas. What is the inspiration for having a great idea? How can we tie insights about human needs and desires into ideas?</p><p>Just look at Steven Johnson’s book, <a href="https://www.amazon.com/Where-Good-Ideas-Steven-Johnson/dp/1594485380"><em>Where Good Ideas Come From</em></a>, for instance. This is a fantastically detailed look at how ideas get started. He investigates the rise of the most significant innovations of mankind and their origins.</p><p>Johnson recommends that organizations</p><p>…create an open database of hunches, the Web 2.0 version of the traditional suggestion box. A public hunch database makes every passing idea visible to everyone else in the organization, not just management.</p><p>We should of course be concerned with the natural evolution of ideas and pay attention to where they come from. But that’s not enough. Successful companies are able to convert ideas to delivered value.</p><p>We need to consider where ideas go to in organizations as much as where they come from.</p><h3>A “VALLEY OF DEATH” FOR IDEAS</h3><p>In the startup world, the term “the valley of death” refers to the difficulty of covering negative cash flow in early stages of a company. It’s the period of time it takes for their new product or service to earn revenue and become a viable business. Startups survive on early stage investment from “Angel investors.”</p><p>Ideas have a valley of death, as well. Sure, R&amp;D labs protect nascent concepts from the financial forces of the business world. But ultimately a go/no-go decision will be on business viability.</p><p>Ideas follow a similar path into the valley death, but perhaps at an even quicker rate. In many cases, the lifespan of ideas is only hours. They die in the valley immediately after a brainstorming session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/0*jp56ep8fOrY-4P0i." /></figure><p><em>VALLEY OF DEATH ALSO APPLIES TO IDEAS IN AN ORGANIZATION</em></p><p>Relying too much on ideas alone asks our business partners to take a leap of faith. Instead we need to prove the market viability of new concepts in a conclusive way.</p><p>Set the right expectations around ideas. You won’t go from sticky notes the workshop room wall directly to implementation. (I actually had this happen to me on one project). And generating cash flow within a quarter or even a year is also unrealistic. Instead, it may take several years or even decades before ideas come to full fruition as revenue generating products and services.</p><p>Bill Buxton, well-known computer scientist and principal researchers with Microsoft, <a href="http://www.bloomberg.com/news/articles/2008-01-02/the-long-nose-of-innovationbusinessweek-business-news-stock-market-and-financial-advice">shows us there is a long nose to innovation</a>. The lifecycle of ideas after they’ve been hatched requires both patience and hard work. He writes:</p><p>An idea may well start with an invention, but the bulk of the work and creativity is in that idea’s augmentation and refinement. The newer the idea, the coarser the granularity of most analysis, and the more likely people are to say, “oh, that’s just like X” or “that’s been done before,” without any appreciation for how much work and innovation is involved in taking an idea from concept to wide practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/0*U-mPGP5wGVz3qxA2.png" /></figure><p>Take the iPod. Contrary to popular belief, Apple didn’t invent digital music players. If fact, the first digital music player was created in the early 80s, nearly 20 years prior to the iPod. And the Diamond Rio pre-dates the iPod by several years as the first commercial digital music player.</p><p>Naturally, organizations strive to shorten the long nose of innovation. It starts with a recognition that thoughts expressed on a sticky note are merely nascent ideas, and there’s a long, long way to go.</p><p>Innovation is re-invention. A lot of it. Ideas go through many iterations of conceptual, technical, and business development before they are the shining examples we point to today.</p><h3>READY. FIRE! AIM.</h3><p>To be clear: ideation and brainstorming do play an important role in our teams and organizations. They bring people together to creatively envision a future that doesn’t yet exist. There is also engagement on a personal level, strengthening collaboration and bringing teams closer.</p><p>What’s more, there is also alignment of perspectives around a common cause. Groups form a shared sense of reality by working through problems together creatively. This is all important for the collective health of an organization, and I’m not advocating curtailing these types of activities.</p><p>The disappointment, however, comes after the fact, when everyone goes back to their “regular work.” The energy and excitement a brainstorming session can quickly fade. The hope of getting a new idea through vanishes instantly.</p><p>First of all, <a href="http://blog.mural.co/2015/04/13/do-you-suffer-from-workshop-amnesia">“workshop amnesia” sets in</a>. Within days workshop participants are asking, “What did we decide?” and “Who owns what?” and “How are we going to find time to do any of this work?”.</p><p>But also, the momentum needed to get out of the valley of death for ideas is lacking. Remember: there forces working against even you best ideas–uncertainty, short-term financial goals, and lack of resources.</p><p>Getting new ideas through the normal decision-making gates of an organization involves commitment, time and perseverance. It requires action first in order to build momentum to the point where ideas have a chance. It requires experimentation.</p><p>Yes, you want valid, comprehensive insights from the market as your starting point. And yes, you need to get the right group of people together to creatively problem solve. But don’t omit planning for a strong follow-through well in advance and have a path to move forward on.</p><p>Luckily, there are some fairly simple things you can do to keep the momentum going:</p><p><strong>1. Manage ideation as an ongoing project<br></strong>Invite a project manager to your ideation or brainstorming session. After participating in the action, their primary function is then to break down the outcomes into actionable steps. Have them create a plan for the continued development of ideas as they emerge.</p><p>Bringing in project management from the outset shows a recognition of the challenges ahead. It also shows commitment from a broader set of stakeholders in the organization. Idea generation is just the beginning.</p><p><strong>2. Aim for experiments as outcomes<br></strong>Your innocent idea on a sticky note is not ready for implementation, nor for making a final decision. Instead, target experiments as the outcomes of a work session. First, express ideas as hypotheses:</p><p><em>We believe providing &lt;product/service/feature&gt; will have &lt;benefit&gt; for &lt;customers&gt;. We’ll know this when we see &lt;measurable outcome&gt;.</em></p><p>This takes some humility, but sets the right expectations. You won’t go from brainstorming to implementation without proving the business value first (i.e., emerging from the valley of death). Coming out of a brainstorming session with statements that begin with “we believe” shows you don’t know if the idea has legs yet. Experiments let you do that.</p><p><strong>3. Make small bets<br></strong>Ironically, decision makers are attracted to big ideas. They want a home run and are swinging for the fences. “I want the next iPod for the our industry,” they’ll request. There is this glorified notion that big ideas are better.</p><p>Instead, make a lot of small bets. You don’t know how big an idea will be. Big ideas have less and less chance of getting implemented because the stakes are higher. What’s more, sometimes small ideas morph into a valuable business idea.</p><p><strong>4. Commit resources before you start<br></strong>Get a commitment for continued experimentation in advance, even before you start generating ideas. Line up small teams who’ll have dedicated time to conduct experiments. Clarify the budget in advance as well. A cheap experiment may only take 4–8 weeks to complete and require a budget of a few thousand dollars.</p><p>Give that team complete autonomy to conduct experiments. The goal is to get real-world feedback and understanding market reactions, business implications, and technical implications at once.</p><p><strong>5. Conduct cheap tests<br></strong>Be prepared to re-invent over and over again. After getting real-world feedback, your original idea may not even resemble the initial concept.</p><p>This need not take much investment. Ask yourself, what’s the shortest possible way to get results about the potential impact of your idea? A simple set of experiment is all that’s needed in most cases– a simple proof of concept that validates your hypothesis or not.</p><p>For instance, after one workshop I conducted a few years ago, we developed both an explanatory video and a landing page. Visitors could view the video and then sign up to be notified for a beta release. There was a short, three-question survey we introduced after signing up as well.</p><p>From these touchpoints we were able to measure traffic to the website over a given period of time, the number of sign-ups, and responses to our survey. We also spoke with selected individuals to better understand their motivations and what excited them about our value proposition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*E-8RLKLXtHOBLITk." /></figure><p><em>“FAKE STOREFRONT” EXPERIMENT TO COLLECT EARLY FEEDBACK</em></p><p>The concept was transformed all along the way. It eventually didn’t resemble its original form. Our great idea turned out to not really be a viable business or stand-alone product. Instead, it was really more suitable as a new capability within an existing flagship product.</p><h3>LONG LIVE IDEAS!</h3><p>To reiterate: generating ideas is healthy for any organization. It brings people together and provides a safe forum to exercise creative muscles.</p><p>But ultimately ideas themselves are overrated. Business decisions don’t get made based on a sketch or half-baked description of a concept. Organizations need a more realistic view of how ideas survive (or don’t). It starts with the recognition that forces will be working against you from the beginning.</p><p>Avoid the valley of death for ideas. This includes managing outcomes as projects, identifying hypotheses (not concepts for implementation), and following through action.</p><p>Cheap experiments trump good ideas every time. This takes commitment at all levels of the organization, but the results are much more satisfying than putting too much faith in ideas alone.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cad21c82066b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/ideas-are-overrated-cad21c82066b">Ideas Are Overrated</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience design is not a diet pill, it’s a lifestyle change]]></title>
            <link>https://medium.com/@JimKalbach/experience-design-is-not-a-diet-pill-its-a-lifestyle-change-c737d4dba75d?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c737d4dba75d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Sun, 24 Sep 2017 15:50:30 GMT</pubDate>
            <atom:updated>2017-09-24T15:50:49.488Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“You’ve got to start with the experience and work back towards the technology.”</em></p><p>That’s what <a href="https://www.youtube.com/watch?v=1SIeTmORl0E">Steve Jobs said in a company meeting</a> upon his return to Apple in 1997, marking a shift in business thinking. We’ve been seeing a renaissance in customer centricity ever since. Companies are realizing the imperative of creating good experiences: it’s no longer a nice-to-have, but mission critical.</p><p>As a result, it’s a good time to be in design, customer experience, and related fields. Our skills are in high demand. But with this boom come growing pains — misunderstandings, false expectations and confusion.</p><p>Part of the problem is that “design” connotes “aesthetics” for many people. (BTW, qualifying it with “thinking” doesn’t necessarily help). Then, there’s an alphabet soup of abbreviations with significant overlap: UX, CX, XD and IxD. But worse, experience design is seen — and sometimes sold — as a quick fix, a sliver bullet.</p><p>So it’s not surprising to hear stakeholders say, “Give me an order of design thinking with a side of fries, please!”</p><p>We’ll, no one actually ever said that. But sometimes it feels that way (doesn’t it?). The assumption is that all you have to do is set up a few lunch-and-learns, and everything will be good.</p><p>But in reality, becoming a customer-centric business requires a deep-rooted mindset shift. And it’s up to design professionals to make this point clear: <strong>experience design isn’t a diet pill, it’s a lifestyle change.</strong></p><p>However daunting it may seem, organizational change is needed. But where do you begin?</p><p>In addition to crafting and delivering great experiences, there are three things designers can do to start a fitness regime for the entire organization:</p><ol><li><strong>Demonstrate shared responsibility.</strong> Show that everyone in the organization impacts customers’ experience. Experience design is not separate from the business, it IS the business (particularly in software).</li><li><strong>Strategize your transformation</strong>. Assess your maturity and current position, and create a path for growth. Transformation doesn’t happen overnight.</li><li><strong>Measure impact</strong>. Good experience design requires some leap of faith. But you also have to be able to show business value. Prove the value back to the organization with measurable impact.</li></ol><p>Sure, there are many other factors involved. The point is that recognizing that there may be misaligned expectations is an important step to making Design (with a capital “D”) successful in your organization.</p><p>Design is not superficial, it’s about changing the organizational metabolism. Like it or not, designers are also agents of change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c737d4dba75d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you really need another map?]]></title>
            <link>https://medium.com/@JimKalbach/do-you-really-need-another-map-5c2320cf00db?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c2320cf00db</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 10:43:27 GMT</pubDate>
            <atom:updated>2017-07-14T10:43:27.427Z</atom:updated>
            <content:encoded><![CDATA[<p>My book,<em> </em><a href="https://www.amazon.com/Mapping-Experiences-Complete-Creating-Blueprints/dp/1491923539"><em>Mapping Experiences</em></a><em>, </em>is about possibilities. In it, I highlight many of the existing tools for mapping experiences from different perspectives. Mapping an experience is not a singular activity, and there are many ways to go about it.</p><p>But with possibility comes choice. Which diagram should be used in which situation? How do you select the appropriate model?</p><p>There are three key types of models needed to describe an experience:</p><ol><li><strong>Models of individuals:</strong> Who are your designing for? Personas, proto-personas, and consumer insight maps stand as models of the individual.</li><li><strong>Models of current experiences:</strong> Maps of experiences come seek to describe the broader context, including goals. What are the circumstances of an experience? What are the jobs to be done? What are their needs, feelings, and motivations?</li><li><strong>Models of future experiences:</strong> You may also need to create models the future state so the organization can see where it’s heading. What do solutions look like? How can we represent them for testing and evaluation?</li></ol><p>The diagram below shows the range of models outlined in the book:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*WvK4QOMEaAmLTTWJ." /></figure><p><em>Select what to map from a range of options</em></p><p>Generally, you’d select one from each group. More are possible, of course, but be careful of “model proliferation.” I’ve been guilty of this: over-modelling and subsequently over-documenting.</p><p>Don’t fall into that trap. Avoid redundancy. Ask: <em>do I even really need another diagram?</em></p><h3>Clarity Over Detail</h3><p>The goal of creating visualizations is to <em>clarify</em> human experiences for your team. If you end up with an array of different models that may only confuse.</p><p>In many situations you might need a map at all. Question <em>what</em> you need and <em>why</em> you think you need it. The amount of formality and rigor you put into your effort depends on your situation.</p><p>Typically, the less complex the solution and the smaller the team, the lower the need for mapping and visualizing the experience. On the other hand, mapping can help teams dealing with solutions that have interlocking experiences within large organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*5WPnLHYd__JNhYww." /></figure><p><em>Determine when and if you need to map experiences, as well as the level of formality</em></p><h3>Find a Balance</h3><p>Note that I am not advocating big, upfront research. Ideally, building empathy for the customer experience is a regular ongoing activity. But grounding yourself in reality first saves time and reduces risk later. It need not take long, and visualization tends to make the process go quicker.</p><p>There are different approaches to the process depending on your situation. Alternatives for a quick, <em>informal</em> set of diagrams might look like the following options:</p><ul><li>Proto-personas &gt; Experience map &gt; Storyboards</li></ul><p>A lengthier, more <em>formal</em> process might include these diagrams:</p><ul><li>Personas &gt; Mental Model Diagram &gt; Scenarios &amp; Storyboards &gt; Value Proposition Canvas</li><li>Consumer Insight Maps &gt; Service Blueprint &gt; Storylines &gt; Business Model Canvas</li></ul><p>Of course, you may have encountered or used additional models and diagrams. The above framework is not comprehensive.</p><p>Keep the intent of mapping in mind: to tell the overall story of individuals and their interactions with an organization, both past and future, to help the organization make sense of their playing field.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c2320cf00db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Shape of Navigation]]></title>
            <link>https://medium.com/@JimKalbach/the-shape-of-navigation-c2c50c58ec23?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2c50c58ec23</guid>
            <category><![CDATA[navigation]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Thu, 31 Mar 2016 21:37:39 GMT</pubDate>
            <atom:updated>2016-03-31T21:37:39.722Z</atom:updated>
            <content:encoded><![CDATA[<p>Why does a website need navigation? After all, with a good search all of the content can be accessed through a single input field. Why not just have site search and be done with the problem of designing and maintaining a complex navigation system?</p><p>It turns out that the <em>way</em> people access information makes a difference. People like information that involves sequence. They like to browse. Web navigation provides a narrative for people to follow on the web. Your navigation tells the story of your site.</p><p>When browsing a web site, people learn about other available content. This translates into bottom line benefits. For ecommerce sites, this means more sales; for a non-profit organization, higher user engagement in navigation results in more support; or for a medical information site, navigation helps provide a deeper understanding of a disease or cure. In other words, it’s the way in which navigation systems provide access to information that is important.</p><p>The best way to understanding navigation shape is through an analogy with storytelling. Like telling a good story, I see navigation shape as a combination these elements:</p><ul><li><strong>Meaning — </strong>Just as the theme of a story is important to its narration, semantics play a role in shape. With web navigation, users have a wider semantic peripheral sense of what the site is about. Site search is more surgical — you’re in and out — and users are not as aware of the meaning of the whole thing. Designing for engagement entails the construction of meaning.</li><li><strong>Flow — </strong>A gripping plot engages. Flow is about how the elements and events unfold and in which sequence. This recalls Marshall McLuhan’s concept of “hot” and “cold” media in which sequence plays a large role. Hot media, McLuhan suggested, provide complete involvement by the user, and they do so with linear ordering. Cold media result in lower involvement for the user, who often must comprehend multiple parts simultaneously. Web navigation is hot.</li><li><strong>Mode of Interaction — </strong>Think of the user as the protagonist. Their mode of interaction is relevant to the shape they experiences. For instance, we can talk about “sit back” and “lean forward” modes of interaction, as well as “known searches” and “exploratory searching.”</li><li><strong>Uncertainty — </strong>Emotions play a role in navigation, and uncertainty drives the feelings people experience. Like conflict in a good story, uncertainty creates tension and release in the shape of navigation. Site navigation provides confidence while looking for information</li><li><strong>Framing Factors — </strong>“Framing” is the difference in saying “75% fat free” rather than “contains 25% fat.” These two messages are <em>framed</em> differently. Web navigation frames the scope of the interactions people have on a website. It’s viewpoint of the storyteller that structures the narrative.</li></ul><p>All of these factors come together to create the shape of web navigation. There is a type of gestalt effect at play here. You task in designing navigation is to identify the aspects that will articulate a given shape.</p><p>So when designing web navigation, it’s not just about a UI with good task efficiency or even providing an emotionally positive experience. Look at the whole picture, the entire <em>shape</em> of the navigation experience. Like a compelling story, the goal is to engage the user. Engagement, then, plays a larger role than experience in the design of web navigation.</p><p><em>This was originally written to be a sidebar to Donna Lichaw’s new book, </em><a href="http://rosenfeldmedia.com/books/storymapping/"><em>The User’s Journey</em></a><em>. Her book had too much awesome content to fix this text, so I’m posting it here.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2c50c58ec23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make Remote Design Work]]></title>
            <link>https://medium.com/@JimKalbach/make-remote-design-work-ed2237452840?source=rss-4b8b911d809b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed2237452840</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Jim Kalbach]]></dc:creator>
            <pubDate>Mon, 24 Aug 2015 15:22:40 GMT</pubDate>
            <atom:updated>2016-01-07T21:13:06.356Z</atom:updated>
            <content:encoded><![CDATA[<p>All the signs are there:<strong> </strong><a href="http://globalworkplaceanalytics.com/telecommuting-statistics"><strong>remote work is on the rise</strong></a>, and its upward trend will continue. By some estimates, up to half of all US workers will carry out their jobs remotely by 2020.</p><p>There are numerous <em>benefits</em> to remote work: flexibility and better work-life balance for employees, and wider talent pools and reduced costs for employers, to name a few.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*xrSN-7-q1Hq20AVj_fw4XA.jpeg" /><figcaption>Remote work is on the rise</figcaption></figure><p>But what about remote <em>design</em>? Surely, designers won’t be required to work in distributed contexts. After all, our work is highly <strong>visual</strong> in nature. We need to be able to draw and point and gesture. We’re meant to work shoulder-to-shoulder.</p><p>The fact is, remote design is already prevalent in our field. A <a href="http://blog.mural.ly/remote-design-looks-like-this-an-infographic/"><strong>recent survey</strong> on remote design</a> shows that a majority of designers face remote work on most or all of their projects.</p><p>The odds are you’ll have to design with a distributed team, if you haven’t already. The question is how you’ll handle it when you do.</p><p>With a little forethought, remote design can be <strong>as productive as working in person</strong>.</p><h3>Digital First</h3><p>Effective remote design begins with a “<strong>digital first</strong>” mindset. This doesn’t mean simply transferring your old ways to an electronic medium: it means rethinking your approach.</p><p>To make remote design work for you, following these four key recommendations.</p><h3>1. Strategize for different settings</h3><p>Recognize the dynamics of different remote situations and plan around them. There are three basic configurations of remote teams:</p><ol><li>A <strong>Split Team</strong> occurs when there are two teams, each co-located, but separated physically. This creates an “us” and “them” dynamic, but typically the balance in communication is even.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/0*3OF-rDgmQT3eIfpt.jpg" /></figure><ol><li>A <strong>Mixed Team</strong> has a core group that is co-located and several remote teammates. Mixed teams have “here” and “there” dynamic: the on site team has an advantage because it’s easier for them to communicate in-person. As a result, remote participants may feel alienated.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/0*hMvn3zBOwf4-qtu9.jpg" /></figure><ol><li>An <strong>All Remote Team</strong> is the condition when no one is collocated. This levels the playing field when communicating. <a href="http://mcbeard.tumblr.com/">McBeard</a>, for example, is a creative branding and design agency that is 100% remote.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*w4KYVesKhP8qlJux.jpg" /></figure><p>Mixed teams are the most common, but also the most challenging. It’s important to address the inherent imbalance in communication in this setting.</p><p>Regardless of the team breakdown, strive to give everyone an equal say and encourage participation. Here’s how:</p><ul><li><strong>Meet in person.</strong> Get to know your teammates in person. Even if it’s just an annual get-together, meeting your teammates face-to-face strengthens interpersonal connections and avoid misinterpretations later.</li><li><strong>Dial in. </strong>To balance the interaction, try working as an All Remote group even if some people are collocated.</li><li><strong>Schedule reviews. </strong>Hold regular design reviews to make up for a lack of spontaneous hallway conversations.</li><li><strong>Post work daily.</strong> Post all design work to a wiki, blog or shared space on a daily basis. Make work visible to the whole team.</li><li><strong>Check in.</strong> Hop onto Skype for quick conversations with teammates. Calls don’t have to be long or formal: make them as casual as walking over to someone’s desk.</li></ul><p>For instance, <a href="https://hanno.co/"><strong>Hanno.co</strong></a> is a digital product design agency that is completely remote. They are even able to conduct <a href="https://medium.com/remote-design-thinking/6-0-case-study-c8d75200d2e9">multi-day design thinking sprints completely online</a>. Checking in with teammates is a key factor in their remote collaboration. They have found that daily standups help keep the design process moving forward.</p><h3>2. Maintain your digital workspace</h3><p>We spend a lot of time and energy maintaining our office buildings. Getting our physical workspaces in order is important for productive work and effective collaboration.</p><p>Why don’t we spend as much effort configuring our <strong>digital workplaces</strong>?</p><p>The remote workspace is a constellation of services and tools: conferencing calling, chat, file sharing, and project management tools. It needs attention too.</p><p>In remote design efforts, it’s up to you to coordinate services that define the digital workspace. Focus on tools that help you <strong>visualize and iterate</strong> solutions. Here are some tips:</p><ul><li><strong>Use multiple devices.</strong> Log into real-time meetings with multiple devices to share whiteboard drawings quickly via webcams. Or, try the <a href="http://www.ipevo.com/">IPEVO</a> to show sketches instantly.</li><li><strong>Created a shared folder. </strong>Set up a space to exchange photos and digital mock-ups.</li><li><strong>Prototype online.</strong> Use an online <a href="http://www.invisionapp.com/">prototyping service</a> such as InVision to mock-up ideas quickly.</li><li><strong>Ensure audio works well.</strong> For real-time meetings, poor audio brings further imbalance to team interaction and can be a showstopper.</li><li><strong>Use a virtual whiteboard. </strong>Services like <a href="https://mural.ly/">Mural</a> support flexible, visual thinking. When used with a touchscreen monitor, <a href="https://vimeo.com/126752811">a virtual board is just like working on a physical whiteboard</a>.</li></ul><p>Mural recently partnered with Jeff Gothelf to conduct his Lean UX workshop online. (See summaries of these workshops online <a href="http://blog.mural.ly/virtual-lean-ux-workshop-pilot-session-summary/">here</a> and <a href="http://blog.mural.ly/virtual-lean-ux-workshop-round-2/">here</a>.) Participants spanned nine time zones and had not previously met. The group was still able to come together and effectively complete the training. Despite not being co-located, their ability to visually brainstorm was not diminished thanks to the virtual whiteboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/0*87hC7J1OAZUqiZc_.gif" /></figure><h3>3. Rethink methods</h3><p>The digital first perspective isn’t just about tools or technology: it’s a <strong>new way</strong> of thinking about design methods. Breakout groups, for instance, don’t work well on conference calls: a single audio stream prevents concurrent conversations. Instead, you need to consider activities that are inclusive of remote participants.</p><p>Consider these aspects:</p><ul><li><strong>Work asynchronously.</strong> Plan parts of activities to be completed independently before and after workshops. For example, have colleagues collect examples from competitors ahead of time.</li><li><strong>Leverage multitasking.</strong> Integrate remote participants’ ability to multitask. Give them on-the-fly tasks, such as searching for examples on the web.</li><li><strong>Engage participants. </strong>Use polls and voting to engage all collaborators.</li><li><strong>Timebox activities. </strong>Limit the time for each activity to keep the design process focused.</li><li><strong>Take turns.</strong> Favor design techniques that allow for individual work, and then have sequential presentations.</li></ul><p>The <a href="http://www.uxbooth.com/articles/design-studios-the-good-the-bad-and-the-science/">design studio format</a>, for one, naturally works well with distributed teams. For instance, Mural conducted a design studio recently. Hand-drawn sketches were immediately photographed and upload. The result was an instant digital record of the workshop (see image).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TI7Ux1U7FuRWYbja.jpg" /></figure><h3>4. Leverage digital formats for better results</h3><p>Working online can improve the <strong>quality</strong> of your output. Take advantage of benefits of electronic media.</p><p>Digital materials can be easily duplicated, distributed, and shared. They are also extensible, portable, and archivable. Eliminate <a href="http://blog.mural.ly/do-you-suffer-from-workshop-amnesia/">“<strong>workshop amnesia</strong>”</a> after design sessions, and never worry about having to wipe the whiteboard clean.</p><p>Use digital technology to synthesize ideas and find patterns faster. Here’s how:</p><ul><li><strong>Continue modeling. </strong>Once everything is digital, you can continue clustering and synthesizing, even after working sessions are over.</li><li><strong>Discuss designs.</strong> Foster conversations online around the artifacts you produce. Tools like Basecamp and Evernote allow you to create a team dialog.</li><li><strong>Create alternative versions.</strong> Explore variations of your designs. It’s easy to try new things out: just duplicate your materials and try again.</li><li><strong>Combine steps. </strong>Keep multiple parts of your designs in one place, e.g., on virtual canvas or wall like Mural.</li><li><strong>Make work transparent.</strong> Invite others to view and comment on your work.</li><li><strong>Digitize on-the-fly.</strong> Convert physical artifacts to digital <em>as you create them</em>. Don’t wait until later.</li></ul><h3>Keep the Momentum Going</h3><p>Today, being a designer does not guarantee that you will be sitting next to colleagues all of the time. Remote design is ultimately about keeping your <strong>creative momentum</strong> going, even when you’re not in the same room.</p><p>Don’t be daunted. Moving to remote work does not signify the end of an era, a farewell to visual work. Rather, it is an opportunity to think about old practices in exciting new ways. Embrace remote design, you’ll thank yourself later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*x8u6I1M0r6jGMhji.gif" /></figure><p><em>Originally published at </em><a href="https://blog.mural.ly/2015/08/make-remote-design-work/"><em>blog.mural.ly</em></a><em> on August 24, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed2237452840" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>