<?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 Sam Goertler on Medium]]></title>
        <description><![CDATA[Stories by Sam Goertler on Medium]]></description>
        <link>https://medium.com/@samgoertler?source=rss-373314836bb0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JHDOSReYpWIDM0jBDQ8-9w.jpeg</url>
            <title>Stories by Sam Goertler on Medium</title>
            <link>https://medium.com/@samgoertler?source=rss-373314836bb0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:29:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samgoertler/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[How to negotiate with product managers (and why you should)]]></title>
            <link>https://medium.com/building-asana/how-to-negotiate-with-product-managers-and-why-you-should-2112fe42837e?source=rss-373314836bb0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2112fe42837e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sam Goertler]]></dc:creator>
            <pubDate>Sun, 22 Nov 2015 23:24:17 GMT</pubDate>
            <atom:updated>2015-11-22T23:24:17.488Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently gave this talk to <a href="https://medium.com/u/45b39be42e08">Women Who Code NYC</a> and would like to open up the conversation to a broader audience. Like most tech talks, mine started out with a meme:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*hUrKEgyxvGn5jqjVRT55_Q.png" /></figure><p>Most of us can relate to this on some level, but the truth is that PMs and engineers actually aren’t adversaries. In reality, a PM can be your biggest ally for managing scope and increasing development velocity.</p><p>Now, I’m not saying tension doesn’t exist. It’s the PM’s job to figure out where the product should go, while you’re responsible for getting it there as quickly and safely as possible. Because the destination is often a moving target, naturally, conflicts arise. But, it’s possible to work <em>with</em> this tension to get better results for everyone.</p><p>For example, I recently spec’d a feature that required some user education, so I included a tooltip. When we reviewed the spec as a team, our engineer pointed out that building a tooltip in this part of the UI would be possible, but harder than usual. She then suggested that instead of a tooltip, we animate some icons to teach people how to use them, which would be much cheaper to build and still achieve the same goal. Awesome.</p><p>It seems simple, but I’ve worked with plenty of engineers who would have just accepted the spec as is and spent too much time trying to make that tooltip work. Many of them assume that not building the tooltip would make them look lazy or incompetent or antagonistic. In reality, identifying opportunities like this that save time, and effectively communicating that to your team, is a sign of leveling up.</p><p>So, how can you push back in a way that consistently leads to better outcomes instead of conflict and resentment? The key is for both sides to consider the spec merely a starting point for negotiations. Here are some tips to help you navigate the conversation from there:</p><h4>Understand the problem</h4><p>Like most negotiations, the best way to start is by listening. Your PM has likely done some research — talked to users, analyzed data, studied competitors, etc. — and they can provide you with the context necessary to fully understand the problem you’re trying to solve for the user. Spend some time digging into this together.</p><h4>Agree on goals</h4><p>Most of the time, the PM’s goal isn’t to deliver a complete solution to the user’s problem in one big launch. They’ve more likely mapped out a series of incremental releases and hope each one teaches them something new about the direction they’re headed. Once you know what they’d like to learn each step of the way, it’ll be easier to make decisions about what exactly to build (and when) to get that data.</p><p>It’s equally important for your PM to align with <em>your</em> goals — whether it’s minimizing code complexity, cleaning up tech debt, improving security, etc. — let your PM know your top priorities so they’re better able to support decisions you make about how to build a feature. Doing so will help you avoid disagreements over when to do the quick, cheap thing vs. invest in something more stable.</p><h4>Bring your expertise to the table</h4><p>As an engineer, you know better than anyone all the different ways to build a feature and the tradeoffs associated with each approach. Once you’ve chosen the appropriate technology to get the job done, you can continue providing value by calling out limitations of that technology and challenging your PM to reconsider their requirements based on this information, which may be new to them. Constraints are often very helpful, so don’t be shy or apologize for pointing them out. And, don’t worry about figuring out a workaround before raising an issue (see next point).</p><h4>Get creative together</h4><p>Once everyone is aware of constraints, now it’s time to find creative ways to work within or around them as a team. Going back to the example I gave earlier, the option to animate an icon instead of building an expensive tooltip wasn’t obvious to everyone. It seemed obvious to our engineer, though, because she was closest to the problem and knew more about our options as a result. Brainstorming workarounds with your team is another opportunity to bring your expertise to the table and ensure the final outcome achieves your shared goals.</p><h4>Repeat</h4><p>Project kick-offs are a great place to start these negotiations, but they shouldn’t stop there. New or unforeseen constraints are bound to show up throughout the development cycle, so it makes sense to keep negotiations going until launch. Repeating the process of grounding in the problem your team is trying to solve, realigning on goals, identifying opportunities to save time or energy, and finding creative workarounds will lead to faster development, better products, and stronger relationships with your teammates.</p><p>If this sounds interesting to you, <a href="https://asana.com/jobs"><em>join us</em></a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2112fe42837e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-asana/how-to-negotiate-with-product-managers-and-why-you-should-2112fe42837e">How to negotiate with product managers (and why you should)</a> was originally published in <a href="https://medium.com/building-asana">Building Asana</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Giving users a seat at the table]]></title>
            <link>https://medium.com/building-asana/giving-users-a-seat-at-the-table-379e3033cbfb?source=rss-373314836bb0------2</link>
            <guid isPermaLink="false">https://medium.com/p/379e3033cbfb</guid>
            <dc:creator><![CDATA[Sam Goertler]]></dc:creator>
            <pubDate>Mon, 09 Feb 2015 21:50:35 GMT</pubDate>
            <atom:updated>2015-02-09T21:50:35.865Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y85P0Bzl5X3UtQ0wvPsjTw.jpeg" /></figure><blockquote>If you want to build products users love, get them to help you do it.</blockquote><p>Asana <a href="http://www.wired.com/2015/01/asana-android-app/">recently launched its first native Android app</a> and we relied heavily on our users throughout the development process. This started out of necessity: nobody on the team was an Android power user at first, so we didn’t trust our product instincts the way we may have on web or iOS. We had a vague idea of the features required to deliver a great app experience, but the details were fuzzy. So, we optimized our development process around learning — collecting and incorporating feedback from a special group of beta testers early and often. What resulted has shaped the way we approach product development at Asana. Here’s how:</p><h3>Smaller MVP with room to grow</h3><p>When we initially built the product roadmap, we knew we had a lot to learn. Sure, some information was available to us from the beginning — user research, competitive analysis, lessons we learned on other platforms, etc. However, we acknowledged that lots of new information would become available to us later. For example, our team was small, but growing fast, and we expected to have a couple of Android experts weighing in on key decisions soon. We also wanted to factor in any advancements in Android technology or design that Google was planning to announce later that quarter. Most importantly though, we wanted to incorporate feedback from beta testers on the app as it developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*zPghFnbitc18nmFyMKYG-A.png" /><figcaption>The first MVP ready for internal testing</figcaption></figure><p>So we negotiated down to a tiny set of features we knew we’d need in order to test the app ourselves. For us, this was simply an inbox that presented a feed of task updates. By only committing to building the inbox, we avoided the costs inherent in gaining consensus on longer term roadmap decisions. We chose to make those calls closer to the time of actually executing on them, when we’d presumably have more information available to us. We left plenty of room in our schedule to expand scope beyond inbox for that reason.</p><h3>Design with the intention to iterate</h3><p>Knowing that our plans were subject to change based on the arrival of new information, we approached design with a light heart. Without the pressure to “get it right” straight out of the gate, we were free to experiment with fresh ideas and take chances that otherwise may have felt too risky. We considered our initial designs to be learning opportunities more than anything else.</p><p>Our approach not only opened us up to design experimentation, but also allowed us to move faster than usual. We didn’t have to bother with redlines or other documentation work about work because we expected most things to change soon. Instead, our designer put together rough mocks and tweaked them in code alongside an engineer to save time.</p><p>Since we were starting with just an inbox, we were able to narrow our focus on one feature rather than designing an entire app end to end, which would have required a longer lead time ahead of implementation. Of course, we knew we’d eventually add more features, so extensibility was always top of mind.</p><h3>Extend the roadmap incrementally</h3><p>Focusing on one feature first also allowed us to gather meaningful feedback from users early. We started with inbox because we believed testing that feature internally would answer a lot of open questions we had about Android specific use cases and allow us to make more informed roadmap decisions. So, once the inbox was fully functional and decently polished, we distributed it internally.</p><p>Because the inbox only supported a single use case, the feedback we received was very focused and provided a clear signal for next steps. We heard things like, “Getting notifications about task updates is great, but I need to see the rest of the task for more context,” and, “Once I get a notification, I’d like to be able to create a task for myself to follow up.”</p><blockquote>While it felt great to have more information than when we started, we knew that we still had a lot to learn from real users.</blockquote><p>So, we used the internal feedback to extend our roadmap a bit further out, but decided to hold off on committing to anything longer term. We would only build the features necessary to get us to our next goal, which was an app we could distribute to a small group of external beta testers in order to collect more feedback.</p><p>We added a couple of features on top of the inbox before distributing the app more broadly, but we didn’t build them all at once. Instead, we added each new feature one at a time and then collected feedback before moving on to the next feature. This prevented us from building more than what was absolutely necessary to reach our next goal of external distribution. It also allowed us to ship as soon as we recognized that our feature set was sufficient — we were never stuck with a large set of partially built features that all needed to be polished before shipping. Instead, we had a small set of fully functional and polished features ready to go as soon as we recognized our next MVP.</p><h3>Fast feedback loops with real users</h3><p>Once we had the right set of features required to collect meaningful feedback from people outside our company, we kicked off phase one of our beta program. First, we invited a handful of friendly customers into our office to meet the team, eat dinner, and get access to the app. This was not only a great opportunity to build the foundation for longer term relationships we hoped to have with our Android community, but it also gave our team (not just user research, but designers, engineers, and PMs) a chance to see first hand how our work was received. It was an incredibly humbling experience to watch users stumble through certain interactions. We realized that many of the assumptions we were making up front were not always true and learned a lot about ways we could improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*YujK8BucIf9V479Rd39l-Q.jpeg" /><figcaption>Kick-off dinner with early beta testers</figcaption></figure><p>We kept in touch with these users over the next few weeks and incorporated their feedback into our roadmap. Our user research team used <a href="https://www.getfeedback.com/">Get Feedback</a> to send out surveys gauging reactions to design iterations and new features every week. We also installed <a href="https://instabug.com/">Instabug</a> to collect one-off bug reports and feature requests. The app was transforming rapidly for these users and they were excited to be a part of the process. Working in sync with them was rewarding for us, too, because we got to see the impact we were making in real time, rather than building in the dark.</p><p>Once the app was in good enough shape to collect feedback from a broader group of external testers, we kicked off the second phase of our beta program. This was similar to the first phase, but included a larger group of about 50 testers. We hosted another dinner, observed their first experiences with the app, and then continued to collect and incorporate their feedback over the next several weeks. We eventually expanded the group of testers a third and final time to maximize learning before launch.</p><h3>Knowing when to launch</h3><p>To help us determine the best time to advance our app from internal testing to a small group of external testers to even larger groups and then eventually to launch, we used a sentiment score that tracked our progress.</p><blockquote>Each week we asked our users to rate their experience on a scale from “tough going” to “totally awesome.”</blockquote><p>Initially we saw huge gains in the sentiment score after each update to the app; this wasn’t surprising since we started with just an inbox and then quickly added features that significantly improved the overall experience for the majority of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*3GijUbagLLmflpMkwqNQUw.png" /><figcaption>Tracking progress with weekly scores from users</figcaption></figure><p>Eventually, we started seeing diminishing returns. At that point, our updates either marginally improved the experience for everyone (design polish) or significantly improved it for only a subset of users (editing capabilities for power users). For us, this was a good signal that it was time to launch. We knew we’d learn much more about how to make great leaps again once we got feedback from users at large.</p><h3>Never stop learning</h3><p>One of the best parts about giving your users a seat at the table is that you know they will welcome your launch with open arms:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*7aio6jQ2ECweR2kVsVYVIA.png" /><figcaption>Enthusiastic comments on our launch day blog post</figcaption></figure><p>Hundreds of beta testers were already getting a lot of value from the app so we felt confident that thousands of others would follow. We are by no means finished, though. Some of the most interesting insights from users are yet to come. Our plan is to build an even stronger relationship with our Android community, continue to incorporate their feedback into our lightweight roadmap, and incrementally improve our app to better serve them.</p><p><em>If you’re passionate about user driven development, </em><a href="https://asana.com/jobs"><em>join us</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=379e3033cbfb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-asana/giving-users-a-seat-at-the-table-379e3033cbfb">Giving users a seat at the table</a> was originally published in <a href="https://medium.com/building-asana">Building Asana</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working From Woods]]></title>
            <link>https://medium.com/building-asana/working-from-woods-35236950d100?source=rss-373314836bb0------2</link>
            <guid isPermaLink="false">https://medium.com/p/35236950d100</guid>
            <dc:creator><![CDATA[Sam Goertler]]></dc:creator>
            <pubDate>Tue, 26 Aug 2014 16:44:55 GMT</pubDate>
            <atom:updated>2014-08-26T19:56:56.436Z</atom:updated>
            <content:encoded><![CDATA[<h3>An unconventional kick-off to Asana’s upcoming redesign</h3><p>It was our last night in the woods and we were all sitting around the fire, silently gazing at the stars, appreciating nature. All of the sudden, our designer blurts out, “Modules! We should put task lists and team members inside modules on a project page!” Everyone’s eyes immediately lit up and we all listened intently as she put the pieces together for what would become Asana’s new UI.</p><p>You’re probably wondering why we were planning a website redesign late at night in the woods. Well, redesigns are often big, scary projects for PMs and this one’s no exception. Not only do we need to update our visual style, but we also need to rearrange some existing features and clean up navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdCl6kScQdD9yNvVhnaRWA.png" /><figcaption>“The Before”- Asana’s website pre-redesign</figcaption></figure><p>So where did we begin? Like most projects at Asana, we kicked off with a brainstorming session.</p><blockquote><em>We knew we couldn’t come up with the freshest ideas inside a conference room, so I suggested renting a cabin in the woods.</em></blockquote><p>After talking to friends who led <a href="https://medium.com/@heatherjacket/moving-faster-by-starting-over-431e874a4a7d">successful redesigns at other companies</a>, we confirmed that a change of scenery would be a good way to free us from reminders of the current design and getting out of the office would help us minimize distractions from other people and projects.</p><p>To prepare, we took some time to really understand the problems we were trying to solve. We collected lots of user research, compared ourselves to competitors, analyzed usage data, and gathered insights from teams across the company like sales and customer support. We understood that people sometimes felt overwhelmed by Asana’s UI in general and now we had a list of specific pain points to back that up.</p><p>Next, we packed up our supplies and headed to a cabin on Russian River, where the five of us — two designers, a user researcher, our cofounder, and me — made ourselves at home. We woke up early to practice yoga. We cooked three meals a day together. We went jogging along the river. But most importantly, we got down to business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*HJCqB3ABxNyMyESQ9In8fQ.png" /><figcaption>Our home for the redesign kick-off</figcaption></figure><p>First, we did a couple of exercises to help us identify our target audience. We came up with a long list of user personas — planners, dreamers, doers, overseers, lurkers, etc. — and then picked which ones we’d target for this project. Based on our early research and our product strategy, we decided to go after the planners and doers.</p><p>We then studied their motivations for using project management software like Asana and tried to get a better understanding of their goals in general. We created detailed maps of the steps they took to achieve their goals in and outside of products like ours, which helped us identify the biggest opportunities for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fs4SjYIbHeg1QNWh6lBiLw.jpeg" /><figcaption>Mapping out user flows</figcaption></figure><p>With these in mind, we explored different ways Asana could help them succeed. We broke off into individual brainstorming sessions where we each focused on specific workflows or use cases. For example, one person would think through different ways a planner could set up a project. Another person would come up with ideas for an invitation experience that serves doers relevant content as soon as they get into the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*1GUrmhGE-lQywm1njCuZAw.png" /><figcaption>Sketch of our target personas and their workflows</figcaption></figure><p>We met together afterwards to share our ideas and riff off each other. There were lots of sketches, sticky notes everywhere, some rather complicated diagrams, and eventually… clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fnNhXeEKi_xZwt6SOVYjJw.jpeg" /><figcaption>Sharing sketches after brainstorm sessions</figcaption></figure><p>We left the woods aligned on our project goals and excited about the next steps. Our successful kick-off has inspired other teams at Asana to plan similar outdoor adventures and I hope you’ll consider it for your projects, too.</p><p>Stay tuned for more redesign musings, including sneak peeks!</p><p><em>If this sounds interesting to you, </em><a href="https://asana.com/jobs"><em>join us</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35236950d100" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-asana/working-from-woods-35236950d100">Working From Woods</a> was originally published in <a href="https://medium.com/building-asana">Building Asana</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>