<?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 junu on Medium]]></title>
        <description><![CDATA[Stories by junu on Medium]]></description>
        <link>https://medium.com/@junetic?source=rss-970333e86f1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*u5HfoChZOln0YSU4.jpeg</url>
            <title>Stories by junu on Medium</title>
            <link>https://medium.com/@junetic?source=rss-970333e86f1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:24:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@junetic/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[The gap between asynchronous & synchronous remote work]]></title>
            <link>https://junetic.medium.com/the-gap-between-asynchronous-synchronous-remote-work-1dd5e0be2ca8?source=rss-970333e86f1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dd5e0be2ca8</guid>
            <category><![CDATA[collaboration-tools]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[junu]]></dc:creator>
            <pubDate>Wed, 19 May 2021 08:30:46 GMT</pubDate>
            <atom:updated>2021-05-19T08:30:46.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z-0IEYkvoHqGwfPc.jpg" /></figure><h3>Remote work is all about async…</h3><p>It’s the motto that everyone seems to aspire to. And it’s spread everywhere — from the likes of <a href="https://about.gitlab.com/company/culture/all-remote/asynchronous/">Gitlab</a>, Basecamp and more</p><blockquote>Async only. Asynchronous communication is what remote work is all about..</blockquote><p>I’m definitely not here to tell you about how <a href="https://www.holloway.com/g/remote-work/sections/synchronous-vs-asynchronous-communication">async communication</a> is so great. Or how synchronous is so great in remote work.</p><p>As much as asynchronous or async only remote teamwork is aspired to with all its benefits — the reality is that synchronous or sync communication will always exist. And why ‘<a href="https://blog.doist.com/async-first/">async-first</a>’ is a more apt approach.</p><p>We are human after all. We like talking to each other in real time. We like laughing together. Riffing off of each other. And sometimes just feeling <em>present and together</em>.</p><p>Async communication can provide all this but not to a fuller extent. Just like how sync comms cannot fully offer the flexibility, inclusivity and freedom that async comms offers.</p><p>The question is not then which is better or worse. Or how you can go all in or not on async</p><p>Like most things, it’s a balance.</p><h3>How do you find the right balance between async and sync?</h3><p>Balancing two interconnected things often requires switching between them as frequently as needed — at right amount on both sides. Maybe 70% async and 30% sync is the right balance for your team.</p><p>However, if it’s hard 30% of the time when you need to switch to sync — balancing will be hard. And communication going out of balance can be detrimental to the team.</p><p>Here’s an example. Imagine you are a tennis player (I don’t play, but was inspired after reading <a href="https://www.amazon.com/Inner-Game-Tennis-Classic-Performance/dp/0679778314">this book</a>). You want to balance having a good forehand stroke with a good backhand.</p><p>Forehand is easy for you but you still need to practice your backhand. When you are practicing, you do fine with each stroke separately. But to be a great player and win, you need to be able to switch between the two strokes seamlessly.</p><blockquote>The goal isn’t how well you use one stroke or another or how much of either stroke you use. The goal is to rally and win real games.</blockquote><p>It’s no different working together as a remote team in a fast paced environment. Your team needs to be able to switch modes quickly and seamlessly to truly go above and beyond.</p><h3>Solving the communication gap</h3><p>Despite the advantages of productivity, flexibility and freedom of remote work — the problems are still glaring. Feelings of isolation, meeting overload, maintaining trust, social motivation and team cohesion… They all remain critical challenges to be solved.</p><blockquote>Communication gaps are the root causes of these problems. The frictions around scheduling calls, texting back and forth, unproductive meetings and zoom fatigue — are all making it worse instead of being the solutions.</blockquote><p>We believe seamlessly closing the communication gap between async and sync collaboration is the key in solving these problems.</p><p>It’s what will separate ok remote teamwork from awesome remote teamwork.</p><p>It’s why we are building <a href="http://www.presence.so/">Presence</a>.</p><p>Let’s close the collaboration gap of async and sync remote teamwork.</p><p>And let’s make remote teamwork awesome 🙌</p><p><em>Originally posted on the </em><a href="https://www.presence.so/post/the-gap-between-async-sync-remote-work"><em>Presence blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dd5e0be2ca8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better isn’t always right]]></title>
            <link>https://medium.com/daylight-stories/better-isnt-always-right-b2ccbd12b351?source=rss-970333e86f1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2ccbd12b351</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[junu]]></dc:creator>
            <pubDate>Thu, 15 Dec 2016 07:56:00 GMT</pubDate>
            <atom:updated>2016-12-15T16:29:43.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2HjiG4niiOmJeI1wno2u1g.png" /></figure><p>As designers, we’re constantly analyzing and questioning everything. We say things like “I wish this app would work this way.” Or, “How can this be changed to make it more user-friendly?” These types of opinions and curiosities help us get closer to making experiences better, easier and more delightful.</p><p>Recently, we had the amazing opportunity to completely redesign MelOn — South Korea’s number one music streaming service with over 6 million users and 3.8 million paying subscribers.</p><p>Looking back on this engagement that lasted over a year and half, we learned one important lesson—that a better UX solution sometimes isn’t always the right solution. In fact, it can actually be quite counter-intuitive to what our human-centered instincts tell us</p><h4>What informs a better UX?</h4><p>Many of us in the UX field are familiar with fundamental principles of good user experience—such as affordance, feedback, consistency and more by the likes of <a href="http://www.jnd.org/books/design-of-everyday-things-revised.html">Don Norman</a>, <a href="https://hci.rwth-aachen.de/tiki-download_wiki_attachment.php?attId=797">Bill Verplank</a> and many others. More widely adopted UX and UI patterns in <a href="https://developer.apple.com/ios/human-interface-guidelines/">iOS</a> and <a href="https://material.google.com/">Material Design</a> have also been influential in setting the bar and cultural patterns for what millions of users find familiar and intuitive. Additionally, we are constantly building on each other’s work by being inspired by how different apps, products and services in the market apply various <a href="https://www.quora.com/What-are-the-best-online-UX-design-pattern-resources">UX/UI patterns</a>.</p><p>Much of our design instincts and intuitions are based on our experience and knowledge of these principles and patterns. And a better UX solution also depends on our ability to apply, combine and creatively re-invent some of these patterns and principles in the right ways.</p><p>With all this experience and practice as experts in the field, our instincts around very basic usability issues are <em>usually</em> right. Especially when we ourselves are the target users for the services we design for.</p><p>Well. We were wrong.</p><h4>Intuition = Familiarity</h4><p>We were tasked to re-design MelOn’s entire mobile music experience to push their strategic vision of becoming a connected platform beyond a simple music tool. This vision included ways that users can engage with artist updates, concert tickets, music videos and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9fxxrNBJnFc_T69mNy_UYg.png" /><figcaption>Our new UX vision and strategy was to create natural linkages between all experiences around music with listening at the center.</figcaption></figure><p>But as much as MelOn wanted to achieve this goal, it was clear from our initial research that users first and foremost wanted the music tool to be vastly improved.</p><p>The first thing that was immediately obvious to us was a very complicated music playback interaction: you had to tap to select one or multiple songs in a list <em>and then</em> press play to start listening. This was much different from services like Spotify, iTunes, and SoundCloud where you simply tap once. Though we felt there were times when you wanted to select multiple songs and add them to your ‘currently playing’ playlist—this felt too advanced to be the default interaction model. This was especially painful in cases when you might want to play one just song right away or play songs continuously from an album or playlist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ywZzQ1kVf-MmPswwUHVxg.png" /><figcaption>Two different list behaviors(old and newly proposed) for choosing and playing music</figcaption></figure><p>It seemed pretty clear that tapping once to play was much more intuitive. And better aligned with fundamental UX principles like good feedback, direct manipulation/mapping and natural expectations. Millions of people were doing this with other music services, why shouldn’t it work for MelOn users?</p><p>This way of interacting, however, was foreign and completely unfamiliar to many of MelOn’s 3.8 million paying subscribers. The risk and cost of this switch was too high for the stakeholders at MelOn because it could cause major drop-offs in subscribers. To address the issue, we came up with a solution where we added a ‘check’ icon on the right side of each song. This allowed users to select songs, as they were typically accustomed, as well as tap-to-play immediately. We thought this was the best step forward—and proceeded to prototype and iteratively test this new model against the old one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwKZ-PuogpGr9uuYoK0HXQ.gif" /><figcaption>An early prototype of the new interaction model we proposed using a ‘check’ button to select and play multiple songs. One of dozens of prototypes made with <a href="https://framerjs.com/">Framer</a> by <a href="https://medium.com/@designforhuman">David Lee</a>.</figcaption></figure><p>The results started to surface from our user sessions.</p><p>Existing users who were habitually comfortable using the old model, felt unpleasantly surprised and frustrated. Others who had tried other music apps, or had not used MelOn’s select-to-play model before, were more positive about the new model we proposed.</p><p>The two models we tested with dozens of users resulted in a complete split. For existing users, familiarity equaled ease of use — even compared to something that was actually more intuitive for new users. With this result, our main goal of improving the playing experience was still not solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mPtaVMoNQsEG7kAIRFXnBA.png" /><figcaption>During one of our testing sessions, a user is trying out one of our prototypes and comparing it to what she uses currently.</figcaption></figure><h4>Better designed to the right context</h4><p>Most people weren’t really frustrated with the initial interaction of selecting and playing songs. In fact, they were completely comfortable and habitually set in doing this. It was also a convenient method for mainstream Korean music listeners who frequently browsed Top 100 charts for multiple songs and single releases; versus entire albums. Digging deeper into our user interviews, we realized that the main frustration was what happened <em>after</em> they tapped play.</p><p>When people select songs and play them, they get perpetually added to a ‘now playing’ playlist/queue. Managing, customizing and navigating this playlist was complicated and too much to manage (most had more than 1000 songs in this list). This was the root cause of the dissatisfaction.</p><p>From this insight, we focused our efforts in developing a set of features and UI/UX optimizations that improved the experience after users hit play. Some of these included: clear feedback showing number of songs selected; the ability to search by song; sorting by album/artist/popularity/etc.; and an easy swipe method to access saved playlists directly from the ‘now playing’ queue. These improvements allowed people to comfortably choose songs and continue browsing the app without worry. It became more seamless to cycle back to find the music they were interested in or listened to.</p><p>And enabling users to naturally continue browsing was exactly in-line with MelOn’s initial strategy and vision to increase visual engagement — and not let the app live mostly in people’s pockets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4H7p5jqtfWR3U3zn-cRy4w.png" /><figcaption>Early designs highlighting features to manage and navigate your ‘now playing’ and ‘saved’ playlists.</figcaption></figure><p>MelOn’s re-designed Android app launched this past September (iOS launching soon). This was just one of the major changes we helped develop and revamp. It has so far been a success with more than 85% of users reporting positive ratings of the new re-design.</p><p>So, a better user experience based on our design instincts, experience and fundamental UX principles just might work.</p><p>However, we can only get to the <em>right</em> solutions when we deeply design to real cultural patterns, business needs, and user behaviors.</p><p><em>— <br>A project collaboration by </em><a href="http://twitter.com/daylightsf"><em>Daylight</em></a><em> and </em><a href="http://www.melon.com/index.htm"><em>Loen Enterntainment/MelOn</em></a><em> (now part of </em><a href="http://www.kakao.com/main"><em>Kakao</em></a><em>). You can read more about the project </em><a href="http://www.daylightdesign.com/work/melon-music/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2ccbd12b351" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daylight-stories/better-isnt-always-right-b2ccbd12b351">Better isn’t always right</a> was originally published in <a href="https://medium.com/daylight-stories">Daylight Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design sprint for the next big pivot]]></title>
            <link>https://medium.com/daylight-stories/a-design-sprint-for-the-next-pivot-4671b53b8c2a?source=rss-970333e86f1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4671b53b8c2a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[junu]]></dc:creator>
            <pubDate>Thu, 18 Feb 2016 13:49:38 GMT</pubDate>
            <atom:updated>2016-06-18T02:43:27.328Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73SBeZ_-AT35X-BXJgaMMw.png" /></figure><p>Design sprints can work in many contexts such as <a href="https://library.gv.com/behind-the-scenes-with-blue-bottle-and-gv-bbd7e26e9276">redesigning a web experience</a> to validating a range of solutions in <a href="https://medium.com/@ryanlanglois/data-informed-design-987d8381814#.erfybrwb7">defined problem areas</a>. For our design sprint with <a href="http://www.tamseng.co.kr/">Tamseng</a>, the start-up behind a mobile app called Study Helper, we needed to further define the large problem area around studying to find where the next big product opportunities lie. It was also important that these opportunities lie in between what users want and what Tamseng needed to develop its business model.</p><p>To explore and find this sweet-spot, our goal was to build confidence around one or two directions that could be the next big direction for Tamseng (or at least get us closer to it) in a one-week design sprint.</p><p>A bit of background about the Study Helper app before we get into the design sprint principles and process. Study Helper works by cutting off your mobile device’s vital lifelines, data and notifications while you study with a timer function. Sounds like a horrible idea for most people, but for students in hyper-competitive regions in Asian countries such as Korea, China and India, it’s been an oasis for self-discipline. Over 700k students have been using it to help them focus, avoid distractions, and keep track of their studies.</p><blockquote>Tamseng needed to figure out how they could scale from simple utility app to a service and platform with long term value.</blockquote><p>As much as their app needs to help students avoid their phones while they study, the company still wanted to figure out ways for students engage with the app outside of study times in helpful ways. They’ve started to expand into new features such as social study groups and personal metrics — but they’ve been struggling to find the next big feature that will boost engagement amidst many copycat products and apps. Additionally, their investors have been asking the looming question familiar to many startups — “How are you guys going to monetize and build a sustainable business?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*3hhykIUvR5exW3EP9CLASQ.png" /><figcaption>Our hopes were that we look for next big pivot for their business past the <a href="http://52weeksofux.com/post/694598769/the-local-maximum">local maximum</a> through a good design process and approach.</figcaption></figure><h3>Human-centered design for a better bet.</h3><p>So the big idea for this next big feature (which your users will naturally love and which will make you tons of money) might just come to you as a stroke of genius in the <a href="http://www.huffingtonpost.com/mitch-ditkoff/post_3884_b_1886134.html">shower</a>…right??</p><p>Great ideas <em>can</em> indeed come from anywhere.</p><p>But how much value will it actually add for your users? That’s an assumption and a risk — even if the idea feels amazing and intuitive to you and your team.</p><blockquote>It’s sort of like throwing darts. That great idea you had in the supermarket line could really hit bullseye in one shot. Or not. It might not have been the right solution or even the right problem (wrong dart-board). Why only give yourself one shot without practicing multiple times?</blockquote><p>In order to get more shots at the bullseye, so to speak, we use a human-centered design process to prototype, test and explore ideas in front of real people. In our case with Tamseng, we were practicing a super-condensed version called the <a href="http://www.gv.com/sprint/">Design Sprint</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*wlybCUGsA8L7WMKAIZxv9w.png" /><figcaption>We usually run design sprints in one, two or three-week time periods. We also run them in multiple successive cycles or iterations to narrow down, refine and get to better solutions (‘design scrumple’ inspired by the <a href="http://cargocollective.com/central/The-Design-Squiggle">design squiggle</a>).</figcaption></figure><p>Each design sprint or prototyping cycle roughly consists of these stages:</p><blockquote>Understand + Define → Sketch + Decide → Prototype + Prep → Test +Learn</blockquote><p>Some lessons and principles emerged from our sprint with Tamseng — and we think they could also be useful for your next design sprint.</p><h3>1. Take time to define the scope of the problem clearly.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c00o9muogOGFz6AN." /></figure><p>The Tamseng team already had three different possible solutions/concepts as to what they thought could be the next big feature. One was around using pop star idols that teens and students love, and two others were around improving their ‘group study’ feature. They all sounded like good ideas, but we wanted to dig deeper and find out why and how they might engage users.</p><p>After talking about the background assumptions behind these concepts in terms of user needs and business goals, we asked them (nicely):</p><blockquote>“Are you really sure?”</blockquote><p>At first, they seemed pretty confident. As we dug deeper into their target customers’ needs, we weren’t really sure in what ways their existing ideas would effectively address them. They also weren’t sure if these concepts were truly the best possible options.</p><p>To figure this out, we went through some exercises in organizing everything we knew about our target user needs. These needs were clustered into key problem areas and then turned into <a href="https://hbr.org/2012/09/the-secret-phrase-top-innovato">“How might we…?”</a> questions. These questions ultimately gave us specific focus and framing for the scope for our design challenge.</p><h3>2. Explore, vote and review with your team in multiple cycles.</h3><p>Once we had a bunch of concepts generated around the key problem areas we defined on Day 1, we started to vote and converge on some of them. We used blue dots for ideas that improve current features and red ones for ideas that were brand new features. This was helpful to the team in contextualizing where the current product offering lies and where other new concepts can lead us toward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HIpsrfde2lx44pAF_IeaJQ.png" /></figure><p>After voting, we reviewed ways to develop the concepts further and what things we’d need to consider. We then broke out of the group to work on them individually and then came back together again to explore, vote and review.</p><blockquote>This is the bread-and-butter of the collaborative design process. During our sprint, we had dedicated days, and even hours, for generating ideas (diverging) and narrowing down/focusing to develop them (converging).</blockquote><p>These cycles of divergence and convergence — of the group as well as concepts — helped create a highly productive and energetic rhythm for the project. These cycles also ultimately led to richer and more developed sets of solutions.</p><h3>3. Sketch, design and prototype at the right fidelity to optimize learnings and progress.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8rO1f-eXEm1zHsfr." /></figure><p>The fidelity of our ideas progressed throughout the sprint. During our very first brainstorm around key problem areas, we used one idea per post-it. We then moved to half-sheets to have more room to think through moments in the experience and how they might look on a mobile interface. Only then did we move to another round where we created black and white wireframes in Sketch on our laptops. Between each round, we built in room for reviews with the entire team.</p><blockquote>The most helpful part of this gradual increase in fidelity when developing ideas was that it helped move things with the entire team (many non-designers) at a comfortable pace with room for a lot of feedback and learnings during reviews.</blockquote><p>If we had moved quickly to computer-generated UI designs early on in the process, it would have been easy for feedback to focus on the wrong details. Our goal was to find the right feature and big direction for Tamseng, so sketches allowed us to think big-picture. Additionally, when we put black and white wireframes in front of users, it focused the conversations around features and use-cases — rather than things like how much people love/hate a particular color/style or legibility of icons.</p><h3>4. Be open to surprises and failures when testing with users.</h3><p>Our first session on Thursday was with a recently turned college student which went pretty smoothly. As we walked through each concept, we were able to learn about her detailed study habits and how it related to some of the details in our concept wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9DXJDkvvKwcvftW2." /></figure><p>At the end of all the interviews, we asked the participants to choose the top three concepts that they would find most useful as a user and reasons as to why.</p><blockquote>In every user session we’ve ever done, there is always at least one thing that surprises us.</blockquote><p>One of these surprises that quickly became apparent was around the idea around pop-star idols that everyone was excited about early on: it didn’t resonate across all our users. Ironically, another concept around social support that the team didn’t care much for resonated most positively across all five of our participants. We recruited across a range of different behavioral and demographic student types, so we knew that this concept might be the big pivotal feature we were looking for. Additionally, we were able to get feedback from users about their intent to pay for features around this concept and even how much.</p><p>After finishing all the interviews, we gathered the notes from each of the sessions and started to find patterns and common themes from the explanations people gave around each concept. Some of the insights pointed to a larger need, like how people managed their studying goals and schedules on a daily and weekly basis. Most importantly, we were able to synthesize the feedback into headlines that captured how this social support experience would be helpful to our users.</p><h3>5. Empower non-designers on your team to contribute to the design.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4uSiJ1QoMiLizX8M." /></figure><p>When we were breaking off from the group to work on ideas individually, we always tried to divide the work among all the team members. One of the most important reasons we did this was that we just didn’t have a lot of time and needed all hands on deck! One of the members from Tamseng was a patent attorney and not a designer, but he was open to making wireframes. After a quick 5-minute tutorial, he was the first patent attorney we’ve ever met who learned to wireframe with Sketch! Consequently, he actually ended up producing a lot of wireframes which was really helpful in understanding details that we had not talked about. Though we didn’t use all the wireframes he worked on for the user sessions, it was great to have everyone feel a sense of ownership and be able to improve various important details of the concepts.</p><h3>6. Always have a ‘nagging mom’ idea somewhere.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-W0qJemYtC7nNccO." /><figcaption>The ‘K-pop star helper’, ‘Daily nagging mom’, ‘MMORPG study groups’ and many other ideas were each put up, discussed and voted on.</figcaption></figure><p>During one of our brainstorms, someone threw out an idea of a ‘nagging mom’ who would send push notifications to students to remind them to study. This got everyone laughing. But we also started to talk about how an authority figure could help motivate students, not only via nagging, but through regimented programs with strict rules and time schedules (like fitness trainers and army boot camp officers). After this discussion, a whole new series of ideas were generated by the team. The lesson from this is that funny and silly ideas are not only great in brightening the mood of the team — but can also build momentum toward better solutions.</p><p>These were 6 lessons and principles that we drew from our experience running design sprints with startups such as Tamseng.</p><p>What are some lessons from your design sprints?</p><p>How have you used design sprints to help your product or business leap into the next big phase?</p><p><em>——<br>Written by </em><a href="http://twitter.com/junetic"><em>Junu Yang</em></a><em> with lots of help from </em><a href="http://twitter.com/designforhuman"><em>David Lee</em></a><em> &amp; </em><a href="https://twitter.com/s0delightful"><em>Christina Tran</em></a><em>.<br>A project collaboration by </em><a href="http://twitter.com/daylightsf"><em>Daylight</em></a><em> and </em><a href="http://tamseng.co.kr/"><em>Tamseng</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4671b53b8c2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daylight-stories/a-design-sprint-for-the-next-pivot-4671b53b8c2a">Design sprint for the next big pivot</a> was originally published in <a href="https://medium.com/daylight-stories">Daylight Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>