<?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 productboard on Medium]]></title>
        <description><![CDATA[Stories by productboard on Medium]]></description>
        <link>https://medium.com/@productboard_?source=rss-1249ab0ce8a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*4bV2KvpIZt6bnY_rt3JKyw@2x.png</url>
            <title>Stories by productboard on Medium</title>
            <link>https://medium.com/@productboard_?source=rss-1249ab0ce8a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:18:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productboard_/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 the productboard design team is learning from the best]]></title>
            <link>https://medium.com/productboard-design/how-the-productboard-design-team-is-learning-from-the-best-ae0081e9207d?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae0081e9207d</guid>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 17:38:28 GMT</pubDate>
            <atom:updated>2022-04-01T11:52:24.890Z</atom:updated>
            <content:encoded><![CDATA[<h3>How the Productboard design team is learning from the best</h3><p>At Productboard, one of our core values is a relentless improvement. That means that each day, we strive to be better at what we do. Sometimes this requires us to reach out beyond our teams, even beyond the company itself, for expert guidance and advice.</p><p>This is exactly what our design team did when they asked Joshua Goldenberg to become their official design advisor. With over 25 years experience, Joshua has headed up design teams at Palantir, Slack, and now Loom — experience our team is now tapping into on a regular basis.</p><p>I caught up with Productboard designer Zdenek Kuncar to find out how it works, what they discuss, and why this is such a unique opportunity.</p><h3>So what’s it like working with a design advisor?</h3><p>It’s really helping to push us to the next level. We reached out to Joshua because we want to grow and improve as designers, and that’s exactly what we’re getting from the collaboration. He’s seen and experienced so much in the design world, and we just want to absorb all that expertise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*1kdX78NxbV4zDfB2" /></figure><p>Just smile and wave, boys. Smile and wave. Meet our design team: <a href="https://www.linkedin.com/in/hamrik/">Pavel Hamrik</a>, <a href="https://www.linkedin.com/in/zdenekkuncar/">Zdenek Kuncar</a>, and <a href="https://www.linkedin.com/in/peterpilat/">Peter Pilat</a>.</p><h3>How does the collaboration work?</h3><p>We have a conference call with Joshua once a week for an hour. Discussions tend to focus on two different aspects of our work: operational and product.</p><p>For example, we’ve had sessions where we discussed how we organize our work and team, our approach to the hiring process, and our overall design strategy. We already had effective processes in place prior to teaming up with Joshua, but we’re always striving for better, and his input has helped us understand how the best companies in the world organize themselves.</p><p>One subject that came up was diversity. It’s not exactly design-specific, but we’re aware that the team needs to be more diverse going forward — not just because we value inclusion, but because diverse teams are proven to perform better.</p><p>We’ve also had sessions where we focus purely on the features we’re working on, where we organize a design critique, and Joshua offers his opinion. He’s been around hundreds of designers and worked on countless products, so his feedback is like gold to us.</p><h3>Can you give an example of a particularly insightful session you’ve had?</h3><p>Sure. Last month we discussed designing for growth — how best to approach it, where growth designers fit in relation to the product team, and how growth features differ from regular product features. This is a relatively new area in the design world, but Joshua has first-hand experience of making it work at Slack and Loom.</p><p>We learned so much in this session. For example, the growth team at Loom sits somewhere between the product and marketing teams, but it’s separate from both. It has its own sprint cycle, development process, and timeline. One of the ways growth designers differ from regular designers is their extraordinary focus on metrics. They focus on the metric they want to move and then experiment with ideas to make this happen.</p><h3>How did this opportunity come about?</h3><p>We were actively looking for a head of design. The business was growing fast, and although we had solid processes in place, we felt that some guidance around leadership and scaling would be useful. But for whatever reason, we just couldn’t find the right person for the job, and we certainly didn’t want to rush the process. So, we thought, if the hiring process is going to take time, why not look for an external advisor who can help us right now?</p><h3>How did you find Joshua?</h3><p>We originally had three candidates for the role. All of them were super talented, but Joshua stood out — not only because of his vast experience but because he was such a great fit for the team. We wanted an advisor that we all felt comfortable sharing our work and ideas with, someone whom we trusted, and that’s exactly what we saw in Joshua.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*8vHxaI7_VUytPLiJ" /></figure><p>Joshua Goldenberg, our new design advisor.</p><h3>How did you approach him?</h3><p>Initially, Joshua was approached by Lucie Ličmanová, a recruiter at Productboard. Then, our VP of Product and Design, Andrej Danko, set up an initial call with the team. This was really just a high-level meet and greet. But we really liked him and were eager to close the deal.</p><p>We wanted to do something a bit special to show him exactly why we needed him. Originally we prepared a video, but we eventually chose to share our ideas via a Notion page titled ‘A Package for Joshua,’ where we explained in detail what we wanted his advice on, how we work, and what our company culture is all about.</p><p>Joshua loved it and agreed to become our design advisor. This was back in August, and we’ve been working with him ever since.</p><h3>Is working with external advisors standard practice for design teams?</h3><p>Not in the Czech Republic, but it is in the US. Although Productboard is largely based in Prague at this point, the Silicon Valley entrepreneurial spirit is very much a part of our company’s DNA. We have an office in San Francisco, and our CEO and VP of Product are based there too. They both have amazing networks, and we all get to tap into them.</p><p>For example, we travel to San Francisco fairly regularly. Last year I went three times, each time for around three weeks. While there, I got to meet some amazing designers and product managers from companies such as Figma, Slack, Groupon, Salesforce and Facebook. The advice and inspiration I received on these trips have been priceless.</p><p>With Joshua, however, the team gets access to an experienced design leader on a weekly basis, which is an amazing opportunity for us to learn and grow.</p><p><strong>Want to work with the best?</strong></p><p><em>Last week, we raised an additional $45 million of Series B funding to further the vision of our company — to help product managers, teams, and organizations make products that matter, together.</em></p><p><em>Over the coming year, fuelled by this investment, we aim to expand our team globally. So if you are a talented product designer who wants to work with the best, why not head over to our careers page?</em></p><figure><img alt="Nicholas Edwards is a content writer at productboard." src="https://cdn-images-1.medium.com/max/200/0*9OYQgrSdLyuR52J-" /><figcaption><a href="https://www.linkedin.com/in/nicholas-edwards-160881140/">Nicholas</a> is a content writer at Productboard.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae0081e9207d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productboard-design/how-the-productboard-design-team-is-learning-from-the-best-ae0081e9207d">How the productboard design team is learning from the best</a> was originally published in <a href="https://medium.com/productboard-design">Productboard design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supporting mental health the productboard way]]></title>
            <link>https://medium.com/productboard-engineering/supporting-mental-health-the-productboard-way-a70a7322ce55?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a70a7322ce55</guid>
            <category><![CDATA[anxiety]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Sat, 18 Jan 2020 15:14:16 GMT</pubDate>
            <atom:updated>2020-04-28T10:53:27.067Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aOsVdlq_DCIxljwEFy4ZAw.png" /></figure><p>As a long-term sufferer of anxiety, and consequently panic attacks and depressive thoughts, I know how important it is to be open about mental health issues. Sharing your experiences, hearing those of others, and having supportive people around you are some of the most important factors in dealing with and recovering from mental health issues.</p><p>And as we spend a large chunk of our time at work, it’s important that our employers acknowledge that there are people struggling with mental health issues and offer support when needed. Here’s how we approach this at productboard.</p><h3>Breaking the stigma around mental health</h3><p>Issues such as anxiety and depression are surprisingly common. According to recent research from <a href="https://hbr.org/2019/10/research-people-want-their-employers-to-talk-about-mental-health">Harvard Business Review</a>, up to 60% of respondents experienced symptoms of mental health issues in the past year. Yet despite the prevalence of such conditions, people are more likely to suffer in silence than open up about their struggles.</p><p>Why is this? Simply because of the stigma that’s attached to mental health issues. People fear being judged negatively. This is why acknowledging the issue is one of the most important things an employer can do. Acknowledgment is the first step towards breaking the stigma.</p><p>At productboard, we have a dedicated Slack channel called #talk-mental-health where people are encouraged to share their experiences with mental health issues. The channel is a safe haven where we can talk about anything related to this topic without judgment or shame. Having struggled a fair bit with mental health issues myself, I know how important it is to have a space where you can talk freely about these issues, and this channel does exactly that.</p><p>Sometimes, we send out an anonymous poll in the channel just to see how everyone’s doing. For example, we recently sent out a multiple-choice question asking <em>“I have experience with…,”</em> with options like anxiety, depression, panic attacks, and so on. Seeing that quite a few people also struggle with anxiety or depression really helped me feel less worried about what I was dealing with.</p><p>We also have a Slack bot called Freud. If you write Freud a direct message, it’ll be posted anonymously in our mental health channel. That way, people that struggle to talk openly about their issues can still ask others for advice, tips, or share their experiences.</p><p>A while ago, someone used Freud to ask for advice about finding a therapist, and a few people shared their experiences, which was really helpful!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E_0zn_EWH_CoK3YU.jpg" /></figure><h3>Mental health as an employee benefit</h3><p>These days, most companies offer benefits relating to physical health. This might be a gym membership, a budget for sports, or something similar. It’s not yet common to offer mental health as a benefit, however.</p><p>At productboard, we teamed up with <a href="https://www.headspace.com/">Headspace</a>, an app that offers guided meditation. Through this partnership, everyone at productboard can benefit from the positive effects of meditation and mindfulness, which are proven to alleviate stress, anxiety, depression, and other mental health issues. Anyone with a productboard email address can subscribe to Headspace for free.</p><p>We also meditate together in the office, and Lucie, our People Ops Specialist, teaches yoga in our Prague office every week. During our company offsites, Lucie, as well as our San Francisco-based Luke, lead yoga and meditation sessions to keep everyone grounded.</p><p>Many forward-thinking companies take a similar approach. Buffer, for example, offers its employees a free subscription to Joyable, an app that helps users manage anxiety and depression. And it’s not just tech startups, employers in more conservative sectors such as Ernst &amp; Young, Barclays, and American Express all have inspiring mental health programs.</p><p>Such companies may still be the exception to the rule, but as the taboo around mental health slowly dissolves away, more and more employers will start to take the issue seriously.</p><p>Aside from being the right thing to do, there is a sound business case for addressing mental health in the workplace. While mental health is fundamentally a human issue, it clearly has a big impact on productivity and performance. Research from Soma Analytics found that FTSE 100 companies that prioritize mental health and wellbeing outperform those that don’t by 10%. Meanwhile, the World Health Organisation (WHO) calculated that for every $1 invested in scaled-up treatment for mental health disorders, there’s a return of $4 in improved health and productivity.</p><h3>Living our values</h3><p>Policies and benefits can only do so much, however. To truly tackle mental health issues at work, we need to focus on building an environment where trust, openness, and mutual support are standard.</p><p>At productboard, our culture and values aren’t a fancy-sounding PR exercise; they help inform our decisions, actions, and interactions every day. That means keeping judgment out of our interactions and avoiding toxic behavior, hurtful jokes, and gossip. We strive to create an environment where people genuinely listen and help each other, and where all personality types and characters are accepted and welcomed.</p><p>We’re aware that as employees of a fast-growing tech startup, work can fast-paced and ever-changing. This comes with the territory. On the other hand, we understand that to be at our best, we need to take our feet off the pedal from time-to-time. It’s all about finding the right balance between pushing productboard forward and maintaining mental clarity.</p><p>Ultimately, we can’t do the former if we don’t have the latter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uEc6DK9pqmJDzXfL.jpg" /></figure><h3>A new journey into remote work</h3><p>A few months into my journey at productboard, I started to feel more and more anxious. I had relocated to Prague from Amsterdam, and while I enjoyed the city, I missed my life in Amsterdam. I had a hard time feeling grounded and at home in my new environment. I shared this through our mental health channel on Slack, and I got a lot of support from team productboard.</p><p>A few months later, I decided to move back to Amsterdam and deal with my anxiety head-on instead of spending days desperately trying to find my comfort zone in a new country. Luckily, I had been open about my anxiety from the get-go, so when I raised this with my manager, our CTO Daniel, he understood where my head was at. Moreover, his response was that this could be the perfect time to start experimenting with remote work.</p><p>The combination of me being open about my anxiety and productboard’s open and inclusive culture turned into an awesome opportunity. I’ve relocated back to Amsterdam and am in the midst of building our first fully remote team!</p><h3>Taking responsibility as a company</h3><p>Although we’re making great strides towards tackling mental health at productboard, this is a journey we’re on together, and there’s always room for improvement.</p><p>I think it’s important that we all take personal responsibility for improving the way we think and talk about mental health, both at work and outside of work. We need both processes in place at an organizational level as well as to look out for each other at an individual level. That means recognizing when others are struggling, offering support when needed, and understanding that we all have different tolerance levels when it comes to stress.</p><p>Because really, we are all responsible for creating a work environment that is conducive to mental wellbeing.</p><p><em>Want to join a growing, global startup that truly cares about its employees? We’re always on the lookout for talented engineers! Head over to our </em><a href="https://careers.productboard.com/engineering/"><strong><em>careers page</em></strong></a><strong><em> </em></strong><em>to see our latest vacancies.</em><strong><em> </em></strong><em>It could be the start of an amazing adventure.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/84/0*R04JuG7bFMdnxOCs" /><figcaption><strong>Maurice Kleine</strong></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a70a7322ce55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productboard-engineering/supporting-mental-health-the-productboard-way-a70a7322ce55">Supporting mental health the productboard way</a> was originally published in <a href="https://medium.com/productboard-engineering">Productboard engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our 6 favorite interface design talks from Krupa 2019]]></title>
            <link>https://medium.com/@productboard_/our-6-favorite-interface-design-talks-from-krupa-2019-31208b98b7e8?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/31208b98b7e8</guid>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 15:58:42 GMT</pubDate>
            <atom:updated>2020-01-17T15:58:42.178Z</atom:updated>
            <content:encoded><![CDATA[<p>On April 6th, I, along with my colleague and fellow designer <a href="http://twitter.com/xpetur">Peter Pilat</a>, hopped on a plane to Kyiv, Ukraine for the interface design conference, <a href="https://prjctr.com.ua/krupa-en">Krupa 2019</a>. We attended several amazing talks about what different people are doing today in the field of design, and we were so fortunate to have the one and only Don Norman, who headlined the conference, sign his book for us!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/0*VisnFbOCUVj0GzmF.jpg" /></figure><p>We picked a few of the talks we attended and wanted to share some of our thoughts on what we learned over the weekend in Kyiv.</p><h3>Product design in automotive by Dmitry Starkov</h3><p>CloudMade’s Dmitry Starkov delivered the opening talk. He discussed some of the challenges he faces when turning connected cars into intelligent cars. While he gave his talk in Ukrainian, the English translation was excellent and helped us to understand everything quite well. The product he works on transforms a large amount of data generated by modern cars into meaningful driver profiles to deliver personalized experiences to those drivers.</p><p>Since we’ve never worked on automotive products, it was fascinating to hear about the challenges he experienced in that environment. Drivers have a wide range of interactions with their cars, and it was helpful to see how a designer accounts for all of them!</p><p>Learnings:</p><ul><li>Designs should look natural and respect the chosen platform. What works on your screen or prototype might not work inside of a VW Golf.</li><li>Car manufacturers consider themselves as serious businesses, and their designs need to respect that. Showing mockups won’t work, so they work from final visualizations.</li><li>Elements like tabs are difficult to operate in cars, so layered content doesn’t work well.</li><li>Even the largest manufacturers are looking for innovation that comes from smaller teams working on improving various aspects of the driving experience.</li><li>The design must not be distracting, as safety is the most important factor. Notifications are not desirable, but predicting what the driver will need is a key.</li></ul><h3>Facilitation of product interface development by Alexander Ivanov</h3><p>Also speaking in Ukrainian with an English translation, Alex talked about the fact that a product is not created by only a product manager, product designer or a front-end engineer. It’s a collaboration of many functions in an organization, and everybody contributes to the user experience. That’s why it was great when he brought out his whole team including back-end and front-end engineers, support staff, marketing specialists, and others.</p><p>Alexander, the PM and previously a developer, described how exciting it is to work with users and how he struggled to hire a designer for the team years ago. He talked about how the potential designer candidates all wanted to redesign the product’s homepage while ignoring some key insights from the data he provided them. Alex struggled to find a product-oriented person that had a keen sense of what was important and impactful. He eventually hired a front-end developer instead.</p><p>One of his key messages was that if your product includes search, the search queries are a great source of what users are trying to do in your system. He closed the talk with a <a href="https://www.facebook.com/flatfy/videos/1276842422449767/">very impressive video of their rebranding that we enjoyed a lot</a>. There’s a lot of talent on the team and wish them the best of luck as they build their product!</p><h3>Visual design testing by Jiří (Jerry) Tvrdek</h3><p>After introducing his company, kiwi.com, and their mission, Jerry mentioned that one of his first tasks as the Head of Design was to unify the company’s visual style. They developed a framework consisting of four phases — Preparation, Interviews, Surveys, and Report.</p><p><strong>Preparation</strong> requires a defined design brief, recruited participants, a lab setup with scripts, and a set of design deliverables that are ready to be shown. For their design unification project, they developed 4 different visual styles — Frank, George, Alpha, and Omega.</p><p>During the <strong>interviews,</strong> they asked participants to score these deliverables on a <a href="https://en.wikipedia.org/wiki/Semantic_differential">semantic differential</a> scale from -2 to +2. As an additional validation tool after the surveys, they followed up with <strong>surveys</strong> to help eliminate extremes.</p><p>At the end of his talk, Jerry walked us through the <strong>report</strong> and showed us the final winner — George. One thing that we really liked was that they tested everything, such as screens, stylesheets, landing pages, and even ads.</p><h3>Relationship advice from our users by Guillermo Torres</h3><p>Guillermo talked about how when he worked on Google Maps in Brazil, that it was the only market where Waze was the leading navigation app. What the team had learned was that users wouldn’t trust Google as they perceived it as an institution from far away. On the contrary, Waze was a platform which relied on data from the local community, giving it a much more personal feel.</p><p>To make it humane and add delight, they began showcasing major events, such as using colorful markers to represent the Gay Pride parade in Sao Paulo — all updated in real time. To classify customer preferences, they used the well known Kano model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/0*V9Bbh1mYmxWsqMKl.png" /></figure><p>He also gave an example from his current design role at Airbnb that shows how the company focuses on making sure everyone feels included and that they belong. The checkout process on Airbnb includes two steps that aren’t necessary for the actual checkout. The first one is a summary of the rules that a host sets up and the second one is a message to the host. It creates friction in the checkout flow, but it’s a clear example where the design focuses on ensuring that each Airbnb user belongs to the community.</p><p>Guillermo also showed a great example of how Spotify sends you a breakup playlist when you unsubscribe. He stressed that makers are responsible for the platforms they build and that platforms are never neutral. If you make it easy for users to perform specific actions easily, you have to take into consideration that people will use them frequently. He empathized that makers should think about what benefits certain features bring but also how those features can be abused.</p><h3>Advanced interface challenges from the dark corners of the web by Vitaly Fridman</h3><p>Vitaly is a showman, and his funky personality filled the whole stadium while throwing chocolate to the crowd and teaching us how to tie a balloon. Vitaly pitched four topics: Designing for touch, Navigation, Breaking out of the box, and Privacy. There were many useful takeaways, but we listed those we liked the most.</p><p>He showed statistics that not everybody is using the newest iPhone — many people are using cheap phones. He asserted that interfaces need to account for performance and network constraints. In other words, phones are getting cheaper, but not better.</p><p>He also showed data that, on average, people check their phone every 12 minutes. With this kind of mobile interaction, we need to budget less than 30 seconds for each standalone task.</p><p>Vitaly continued talking about mobile usage gestures. He stated that the one-handed grip and thumb taps matter the most and that we should test designs with accuracy dots because people never hit icons precisely. An excellent example of a thumb-driven design is the <a href="https://ada.com/">Ada app</a>.</p><p>He also touched on some of the navigation patterns, such as always keeping the “close” button on the same spot as the “open” button or other menu icons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/0*7dB7WqEKu9QaoZEY.jpg" /></figure><p>Lately, Vitaly has spent a considerable amount of time reading privacy policies. He found some funny examples, such as “subscribing your immortal soul to the service (though the company won’t claim it),” or this bit included in Tumblr’s policy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hh1mQE3sxDwoo0WF.png" /></figure><p>However, there are not only jolly policies. For example, there is a clause in Instagram’s <strong>Terms of use</strong> that even though you are the owner of your photos, you grant them royalty-free license to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2g09zYLqCa1OgOwv.png" /></figure><p>Services know more about you than your friends or family. Invest some time in reading the policies, or you will never know what you accept. This also applies to the other side of the table. You should invest time in designing privacy policies that are easily digestible. Make them easy to read and more understandable. Vitaly ended the talk on a positive note and proved that he not only teaches you a lot but also entertains.</p><h3>21st century design by Don Norman</h3><p>Don conveyed the problems of today’s designers and his talk was exactly what we expected. It was very provocative and sparked discussions during networking.</p><p>He began by showing us his phone and asking why we need to replace phones every 2 years. Is it really needed? Why do we produce things we can’t recycle? We are destroying nature by harvesting rare materials just to throw them away after some time. Designers chould be solving much more significant problems such as climate change, hunger, and access to education by using design frameworks and our problem-solving skills.</p><p>Don stated that a major problem is the lack of designers at the executive levels (C-Suite) and in decision making positions. Why is that? Why are we building features proposed by marketers and not by designers? When others control the decision making, then the value is presented by numbers in a spreadsheet but not actual designs.</p><p>Like Vitaly, Don mentioned that another problem is the relentless selling of our privacy. Ads, analytics, data — companies know everything about us.</p><p>One of the essential tasks for a designer is to solve complex problems. Don described how to approach this:</p><p>Use the four principles of <strong>human-centered design</strong>:</p><ul><li>Always focus on people. They are the ones using the product.</li><li>Ask “why” to get to the underlying need. Don’t just solve the symptoms, solve the problem.</li><li>Think of everything as a system. Remember that problems are interconnected and decisions have consequences.</li><li>Test all your decisions. Everybody gets it wrong so make, observe, test, and iterate everything while assuming you will always have to change something.</li></ul><p>Combine both top-down and bottom-up approaches:</p><ul><li>You can’t build a system with only specialists, so let designers work with local experts who know the local conditions.</li></ul><p>Leverage opportunistic incremental learning if you need big changes:</p><ul><li>Start with small quick projects. You will face less opposition, and it will be easier to abandon the wrong solutions.</li><li>You can apply this in government projects as well.</li></ul><p>Don mentioned two books in his talk, and we wanted to mention them in case anyone missed it — <a href="https://www.amazon.com/Tyranny-Experts-William-Easterly-2015-04-09/dp/B017MYSJV8/ref=sr_1_2?keywords=tyranny+of+experts&amp;qid=1554736034&amp;s=books&amp;sr=1-2">Tyranny of Experts</a> &amp; <a href="https://www.amazon.com/Design-Real-World-Ecology-Social/dp/0897331532">Design for the Real World</a>.</p><h3>Summary</h3><p>Big props to <a href="https://prjctr.com.ua/">Projector</a> for putting together such a great conference! Peter and I enjoyed the talks and the atmosphere, we met new friends, and we were pleased to see that designers in Ukraine are incredibly talented. We appreciated the focus on delight and how it can be a major differentiator and that companies, such as Airbnb and Google, understand the potential impact it has on users. It’s something we’ve been trying to leverage since productboard started and we will continue delighting our users through our designs.</p><p>The conference also reminded us to never stop experimenting and to have fun! It’s okay to insert some friction if it helps the design be more inclusive. And when in doubt, focus on the principles of human-centered design stressed by Don Norman. Be humane and design responsibly.</p><p>Thank you Projector and see you next year!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/84/0*wqtPXflXCWWjB8fP" /><figcaption>Zdenek Kuncar</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31208b98b7e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we used customer feedback to launch our Slack integration in 20 days]]></title>
            <link>https://medium.com/@productboard_/how-we-used-customer-feedback-to-launch-our-slack-integration-in-20-days-7cc47b0b9301?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cc47b0b9301</guid>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 15:54:30 GMT</pubDate>
            <atom:updated>2020-01-17T15:54:30.781Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3QTZyMy5CSXcPRZI4RPDkg.png" /></figure><p>Previously, <a href="https://productboard.com/blog/3-techniques-to-quickly-discover-what-your-customer-really-needs/">Geda talked about how we use the Customer Discovery Process to make sure we are building the right products</a>. Based on feedback we had been getting about how our customers manage their workflows, we recently launched <a href="https://help.productboard.com/how-to-articles/push-messages-from-slack-into-productboard">our Slack integration</a> so that users can push their customer feedback sitting across a variety of conversations in Slack into our Insights board. In a talk we <a href="https://productboard.com/blog/a-recap-of-our-amazing-january-product-feedback-event-in-prague/">recently gave at our Product Feedback meetup</a>, I discussed how we used this feedback to launch our Slack integration in 20 days!</p><h3>Define the feature</h3><p>The first step was to define the feature based on customer feedback. Of course, to accurately do this, as Geda explained, we need to dig deeper beyond “I need a Slack integration.” So we talked to our customers to get additional insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8EvBHKGIVUQTKFKC.png" /></figure><p>These insights gave us a better sense of what our customers really needed and how to build our solution. But we still needed to get more clarity about how the feature would operate, so we continued to engage them to see how teams would use this feature.</p><ul><li>Would only product managers or other team member use it?</li><li>Would this be active only in internal Slacks or in community ones as well?</li><li>Do we need to tag messages sent to productboard based on various characteristics, such as user?</li></ul><p>After getting these questions answered, we wrote our feature brief.</p><h3>Create a mockup to make the idea real</h3><p>Based on these learnings, we created an InVision mockup and circulated it internally. This serves 2 goals:</p><ul><li>Get quick internal feedback</li><li>Align everyone on the feature</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GoJhXuwqIBlJxdo8.png" /></figure><p>This step was so helpful because it let me know that I had missed a couple of use cases when I showed it other people on my team. Since it was a mockup, I was able to iterate it and recheck those use cases quickly.</p><p>It also aligns everyone on the feature so everyone understands what’s coming. Ultimately the mockup, along with the feature brief, is a communication tool that allows the product and engineering teams to collaborate more effectively.</p><h3>Create a working prototype for internal validation</h3><p>After validating the mockup, we built a working prototype within a few days! From a technical perspective, it really helped us learn more about the API and better understand best practices for handling things like metadata within Slack. One of the main benefits of building the prototype is to get feedback from our customer-facing teams since they’re intimately aware of customer sentiment and can predict some of their feedback or objections based on their relationships with them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oaUwIYWRUCq10uqk.png" /></figure><h3>Beta test for external validation</h3><p>After validating the feature internally, it was time to test it with some customers! When Geda wrote about the Continuous Discovery Process, she said it’s important to make sure you keep all your feedback consolidated in one location. A huge benefit of this is that you can quickly find the customers that requested this feature to include them in a beta test.</p><p>We were also able to use our Slack community channel to test our beta. Our engineers participated in the Slack channel and were able to resolve bugs within an hour. Since we were doing these fixes live with customers, the process was completely transparent, and we updated customers immediately. The feedback loop was insanely short.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ovt287u9JPJrkt_v.png" /></figure><h3>Launch and celebrate!</h3><p>Using a tight process to turn feedback into a product with our internal teams and customers always in the loop, we were able to launch our Slack integration in 20 days. If we hadn’t kept close contact with our customers, identified actual needs instead of user requests, and kept our feedback in a central location, we probably wouldn’t have been able to launch it so quickly to wonderful reviews!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SB44Aesyyd3RzPgf.png" /></figure><p>One of the important things we always make sure to do when we launch a new feature is to celebrate it. A lot of work and thought always goes into these initiatives, and it’s always important to make sure that everyone gets to celebrate when things go well. It keeps the energy and momentum going because remember, the work doesn’t stop here. The next step is diving back into customer feedback to understand how we can continue to make our Slack integration work better!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/84/0*pfNg_da-Xxy7nZ7v" /><figcaption><strong>Zdenek Kuncar</strong></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cc47b0b9301" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UXDX recap: Product design experts from Uber, Mastercard, and more share their insights]]></title>
            <link>https://medium.com/productboard-design/uxdx-recap-product-design-experts-from-uber-mastercard-and-more-share-their-insights-b3bc344528a7?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3bc344528a7</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[uber]]></category>
            <category><![CDATA[uxdx]]></category>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 15:52:37 GMT</pubDate>
            <atom:updated>2020-01-17T15:56:11.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0YrRwF5OomLTQX5c-sinew.png" /></figure><p>Last week, my fellow designer <a href="https://www.linkedin.com/in/zdenekkuncar/">Zdenek</a> and I hopped on a plane to Dublin to attend the 4th annual <a href="https://uxdxconf.com/">UXDX conference</a>. During our time in Dublin, we spent 2 days at the Royal Dublin Society listening to design thought leaders share their perspectives on product development and how they bridge the gap between product, design and engineering.</p><p>We identified two big themes from the talks:</p><ol><li>The need to think about design beyond a simple problem-solving approach. The context and ecosystems in which products exist must be considered as well</li><li>How to optimize design culture by working within Agile and finding solutions to misalignments within the organization</li></ol><p>Below we summarize four talks from the conference that we found both inspiring and enjoyable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c-TpkLHaIwzj1_Yi.jpg" /></figure><h3>The road to excellence</h3><p><strong>Speaker:</strong> <a href="https://twitter.com/vernalkick">Kevin Clark</a>, Design Lead at Shopify</p><blockquote>To find excellent design ideas, find the correct problem, focus on quantity over quality, and explore varied interests.</blockquote><p>Kevin is obsessed with excellence and fascinated by products that go above and beyond. I have to admit that this resonates with us a lot (maybe because of <a href="https://productboard.com/ebook/productexcellence/">Product Excellence</a>? ?). Here are three unconventional ideas on how to achieve excellence:</p><ol><li><strong>Solving problems is easy as soon as you find the correct problem.</strong> The designer’s first and most essential task is choosing the correct problem to solve. Because if you get that wrong, every choice you make after that is irrelevant.</li><li><strong>Quantity over quality</strong>. Illustrating his point with a story about Shopify experimenting with 30 design variants for an order-tracking feature, Kevin explained how exploring many ideas will help you find the one that is excellent. He calls it design by brute-force.</li><li><strong>Explore varied interests, don’t specialize! </strong>Everyone has different backgrounds, hobbies, and skillsets. We should go and explore for ourselves and apply those diverse skills in design. For example, Kevin developed a weather app for Apple Watch as a side project and part of the code was actually reused for Shopify.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1-yvQJQAl5tbK1_0.png" /></figure><h3>Definition of Done</h3><p><strong>Speaker: </strong><a href="https://twitter.com/Padday">Paul Adams</a>, SVP Product, Intercom</p><blockquote><em>A high functioning company can be explained by a simple mechanism that consists of three pillars — </em><strong><em>inputs</em></strong><em>, </em><strong><em>outputs</em></strong><em>, and </em><strong><em>outcomes</em></strong><em>. Successful makers obsess with the whole system rather than just one part of it.</em></blockquote><p>Definition of Done is a well known and contentious term in the world of software development. It’s when all conditions that a software product must satisfy are met and ready to be accepted by a user. It was also the cryptic name of Paul Adams’ talk, which he opened by stating that nothing is ever done in the world of software.</p><p>Paul went on to share his view on how organizations can move towards delivering outcomes (rather than working in functional silos) through a simple mechanism of <strong>inputs </strong>(the understanding that enables new projects), <strong>outputs </strong>(shipping products and features — the heartbeat of a company), and <strong>outcomes </strong>(the impact that ties to higher level business goals).</p><p>This mechanism captures how high-functioning Product and Engineering teams work. Teams do <strong>projects</strong>, which change the <strong>product</strong>, which then change the behavior of <strong>customers</strong>. In order to work on these projects, organizations need to first <a href="https://productboard.com/blog/what-do-users-need/">deeply understand customer problems</a>, which are inputs that feed roadmaps. Once a team changes a product (ships a feature), that’s clearly an output. And an outcome is the impact the change has and how it is defined as a business result.</p><p>Paul stresses that <strong>makers should obsess with the whole system and not just inputs, outputs, or outcomes.</strong></p><p>His spin on this topic was really refreshing. It reminded us of what’s important — that we should obsess with the whole system rather than individual pieces of it. Shipping features is a company’s heartbeat, and while you need to consistently deliver output, that’s just one part of the story.</p><h3>Design for patterns</h3><p><strong>Speaker:</strong> <a href="https://twitter.com/michaelgough">Michael Gough</a>, VP of Design, Uber</p><blockquote>Uber has built products that have a direct impact on millions of lives every day. By studying that impact, it allows Uber’s design team to spots patterns in the world and intentionally design for them.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lR0M0bOsjEFpi3BQ.jpg" /></figure><p>Seeing a VP of Product Design from a company like Uber is an exciting event in itself. Michael is a great storyteller, and sat on a bar stool in front of the audience and talked about how Uber has created an ecosystem with its product — a virtual world of logistics connecting people to people, and people to things. Embedded in the virtual world are real customer experiences.</p><p>He then talked about how<strong> Uber spots patterns in the world and intentionally designs for them, but at the same time stays aware of the implications and impact — whether it’s social, economic or environmental</strong>. Micheal graciously shared some examples.</p><p>One involved helping those with hearing impairments gain new employment opportunities. Seventy percent of people with impaired hearing in the US couldn’t get a job, but began driving Uber when the app caught on. It did not end there, Uber then expanded its rider app so riders would know if they wouldn’t be able to communicate verbally with drivers. Uber also added sign language basics in the app so riders could thank drivers after a ride.</p><p>Despite these achievements, Michael admits that Uber isn’t perfect. Still, his team is focused on continually noticing patterns that they can improve on with design.</p><h3>Create a tangible, achievable, and actionable product vision</h3><p><strong>Speaker: </strong><a href="https://twitter.com/cchastain">Cindy Chastain</a>, SVP Customer Experience &amp; Design, MasterCard</p><blockquote>A strong product vision articulates <strong>tangible</strong> value for both the customer and business, is <strong>achievable</strong> by the business, and is <strong>actionable</strong> by teams.</blockquote><p>When Cindy joined Mastercard 5 years ago, the company had just started developing its digital product portfolio. A piece of advice she received was to find quick wins fast. She found her opportunity with Priceless.</p><p>Cindy worked with a small team and agency, developer and designers. They leveraged research and design thinking…everything felt great! Until they had a session with CMO. Right from the start they received feedback that the product experience they created was terrible. Why? Because it didn’t live up to the strategy he had in his head.</p><p>To prevent this, Cindy articulated the importance of a <a href="https://productboard.com/blog/dent-in-the-universe/">strong product vision</a>, and involving stakeholders from the beginning of the product management process.</p><p>A strong product vision articulates <strong>tangible</strong> value for both the customer and business, is <strong>achievable</strong> by the business, and <strong>actionable</strong> by teams.</p><p>Our main takeaway?</p><p>If you want to achieve alignment around your product vision, you need to bring diverse stakeholders to the table and let them speak. A strong product vision that is tangible, achievable, and actionable will de-risk your product, and accelerate speed to market!</p><h3>Customer needs as environments and constraints</h3><p><strong>Speaker:</strong> <a href="https://twitter.com/alanklement">Alan Klement</a></p><blockquote>Simply understanding customer needs is not enough. Instead, makers should understand the environments and contexts that shape these needs.</blockquote><p>Alan started his talk with a series of metaphorical questions:</p><ul><li>If you plant an acorn in the ground, will the outcome be a full grown oak?</li><li>What if I plant the acorn in the Sahara, or at the bottom of the ocean?</li><li>Can I take credit for growing an oak? If it doesn’t grow, is it my fault?</li></ul><p>Alan used these examples to describe his perception on user needs through the lens of their environments and constraints. <strong>He stressed that simply understanding customer needs is not enough. Instead, makers should understand the environments (in the oak example, there are multiple factors, such as humidity, sunlight, fertility of ground, etc.) that shape these needs.</strong></p><p>To learn more about these environments, Alan recommends asking these specific questions:</p><ul><li>What can you do now with the product that you couldn’t do before?</li><li>If you were to use this product, what would you give up?</li></ul><p>These findings helps uncover where teams can focus their resources as they build products.</p><p>–</p><p>UXDX was a wonderful learning experience for the productboard design team. There were many actionable takeaways from the event’s talks, and unbeatable networking opportunities. We hope to see you next year!</p><p>. . .</p><p><em>productboard is a product management system that enables teams to get the right products to market faster. Built on top of the Product Excellence framework, productboard serves as the dedicated system of record for product managers and aligns everyone on the right features to build next. </em><a href="https://productboard.com/"><strong><em>Access a free trial of productboard today</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/84/0*uvoH5b7NCptNsa9T" /><figcaption>Peter Pilat</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3bc344528a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productboard-design/uxdx-recap-product-design-experts-from-uber-mastercard-and-more-share-their-insights-b3bc344528a7">UXDX recap: Product design experts from Uber, Mastercard, and more share their insights</a> was originally published in <a href="https://medium.com/productboard-design">Productboard design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talking UX and product discovery with the Prague tech community]]></title>
            <link>https://medium.com/@productboard_/talking-ux-and-product-discovery-with-the-prague-tech-community-377dcbb02f4d?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/377dcbb02f4d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[events]]></category>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 15:49:21 GMT</pubDate>
            <atom:updated>2020-01-17T15:49:21.461Z</atom:updated>
            <content:encoded><![CDATA[<p>productboard recently collaborated with <a href="https://prjctr.com.ua/prague">Projector</a> to host a UX and design meetup at HubHub, a sleek coworking space that houses our Prague team and other up-and-coming Czech startups.</p><p>Over 70 people showed up to chat about all things UX and design, network with the growing Prague tech community, and enjoy delicious Pilsners and sliders. They left with new insights on how to leverage learnings from users to make better product decisions, as well as how teams can execute difficult product redesigns while still maintaining excellent user experience.</p><p>Let’s dive deeper into the event’s two great talks.</p><h3>The feature lifecycle process: How to build the right things</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qetwBAcjrKAk_hwk.jpg" /><figcaption>The first speaker was productboard’s very own Product Designer, Zdeněk Kunčar.</figcaption></figure><p>Zdenek talked about how the productboard team ensures that they are building the right features. <strong>He also shared the discovery process used by the team to deeply understand the problems users face.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*6OzST3kOBzWw-FE3.png" /></figure><p><strong>Understand</strong></p><ul><li>The teams consolidates user research, feedback, and requests and identifies insights that will inform prioritization and design</li><li>Different perspectives from PM, design, engineering, CSM, and other cross-functional teams are gathered and taken into account</li></ul><p><strong>Define</strong></p><ul><li>The problem statement in multiple products and areas are defined</li><li>A “storm of ideas” are researched that could potentially solve the problem</li></ul><p><strong>Ideate</strong></p><ul><li>The team comes up with different ideas for solutions to the problem they are trying to solve</li></ul><p><strong>Validate</strong></p><ul><li>The understanding of the problem and solution ideas are validated with users via testing, prototyping, and more</li></ul><p><strong>Solution</strong></p><ul><li>The problem is clearly defined and the whole team understands the problem space</li><li>There is full alignment across cross-functional teams around what is being built next and why</li><li>Though design critiques and collaborations with team members throughout the company, the team figures out how to build the solution the best possible way</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ON9-gHUmNCpuJxfK.jpg" /></figure><p>Along with introducing this process, Zdenek provided a real-life example of a feature one of the teams at productboard is currently working on. When everyone was clearly aligned on the right problem, they were able to validate and prototype solution ideas that later evolved into a feature that makes the user experience within productboard much smoother for customers.</p><p>Attendees were very curious about how discovery works at and within productboard, and Zdenek answered a flurry of questions from the audience. It sparked a great discussion that continued informally over food and drinks afterwards.</p><h3>How teams can execute difficult redesigns while maintaining an excellent user experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YYGqW0awo_4tbjN9.jpg" /><figcaption>Denis Rojčyk, Senior UX Designer at Kiwi.com, took the floor after Zdenek.</figcaption></figure><p>Transitioning from Zdenek’s topic on deciding what to build to how to build it, Denis shared a story of the successful app redesign that he led at Kiwi.</p><p>Product redesigns are usually released without warning. Though the intention is to improve the user experience, the suddenness of the change often confuses users rather than providing immediate value.</p><p>When redesigning their mobile app, the Kiwi team wanted to mitigate confusion around big changes. To ease users in, they decided to introduce updates gradually rather than all at once.</p><p>Denis described how the team started by unifying colors across the whole app. Typography came next. Components were built little by little to slowly replace what was originally there. By relying on a UI kit as a source of truth, they were able to easily experiment with different layouts until they found their sweet spot.</p><p>His story is a great example of how teams can keep the user experience in mind during difficult redesigns.</p><h3>More events to come!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eVhmZSk4dmnsALGI.jpg" /></figure><p>As a fast-growing startup focused on product management, we love talking about all things product and tech. As things ramp up, we will continue to expand our community and host meetups in Prague and beyond. We also have lots of talks lined up this year that are specifically for the developer community.</p><p>If you’re interested in joining any of our events, or if you want to join forces to host an event, feel free to drop us a line at <a href="/service/mailto:events@productboard.com">events@productboard.com</a>.</p><p>. . .<em>productboard is a product management system that enables teams to get the right products to market faster. Built on top of the Product Excellence framework, productboard serves as the dedicated system of record for product managers and aligns everyone on the right features to build next. </em><a href="https://app.productboard.com/register"><strong><em>Access a 15-day free trial of productboard today</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=377dcbb02f4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Relentless Search of a Restless Developer]]></title>
            <link>https://medium.com/productboard-engineering/a-relentless-search-of-a-restless-developer-ef215da1d1f2?source=rss-1249ab0ce8a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef215da1d1f2</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[productboard]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 12:01:30 GMT</pubDate>
            <atom:updated>2020-04-28T10:47:37.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gpQZnrI8AuOoJUszgFl1Bg.jpeg" /><figcaption>Hi, I’m Tomas, a full-stack developer at<a href="https://www.productboard.com/"> productboard</a>.</figcaption></figure><p>Hi, I’m Tomas, a full-stack developer at <a href="https://www.productboard.com/">productboard</a>. I’ve been meaning to put in writing how I got this gig and more importantly, why.</p><p>After giving notice to my previous employer, I thought it would be best to chart my professional trajectory to better understand what I want to do next.</p><p>My thoughts below are necessarily subjective. I still hope you might find some use in them.</p><p><em>All the names of my previous employers are obfuscated.</em></p><h3>Perilous part-time</h3><p>Before landing at my first programming employment, I’ve spent a lot of time doing freelance development. For most of my professional life, I’ve been doing freelance gigs on the side for extra income or when I was in between jobs. Nope, I wasn’t a consultant. Like many wide-eyed juniors before me, I picked from the low hanging fruit when it came to this market.</p><p>In general, being a freelance developer was personally rewarding and taught me so much. It was certainly an experience. Not necessarily a pleasurable one, but valuable nonetheless.</p><p><strong>I eventually stopped doing freelance altogether.</strong></p><ul><li>It can be lonely.</li><li>There’s very little financial security when you’re starting out.</li><li>You have to manage a business on top of being a developer. Otherwise, you’ll get squeezed by the market (and clients). But that’s a skill I didn’t care for much at that point in my life.</li><li>It’s challenging to plan your professional growth when you can’t be picky about projects.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZpPsDOgT-ryYEK8Rmv5sEQ.jpeg" /><figcaption>Beggars can’t be choosers. When short on cash, you do work on anything that runs JavaScript.</figcaption></figure><h3>Humble beginnings</h3><h3>CORP inc.</h3><p>My first employment in tech was for a US corporation, let&#39;s call it <em>CORP inc.</em> They’re pretty huge with about 30K employees and offices all around the world. I was there when they moved their offices from Prague’s city centre to Karlin, which was kind of funny. I can almost see the building they’re in from productboard 😅</p><p>I’ve been doing a QA job there hoping to eventually transition to be a dev. I spent about 18 months there and learned a ton of things.</p><p>Most of it was about how to operate in a corporation rather than how to handle the cool tech. I didn’t find the culture too stifling, but I felt like a very small cog in a very big machine.</p><p><strong>Some things I wasn’t quite satisfied with there:</strong></p><ul><li>The money wasn’t as good as I hoped. But I was fresh out of school and knew jack squat about negotiation.</li><li>I didn’t feel my contribution mattered. In one of the projects I was involved in, there was a critical need to involve more people to ensure the success of the project. But it was as if nobody cared.</li><li>The tech was obsolete to the point senior developers didn’t want to work on it (legacy 12-year-old software solution).</li><li>The people there were by and large easy going with and helpful. But apart from one notable exception they didn’t seem passionate about the work they were doing.</li><li>I gave the notice before my contract was up for renewal. I felt the transition to the full dev position was still the same distance away as when I started. Part of that was due to my inexperience with self growth, paired with the fact that there was nobody who had a vested interest in seeing me grow.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujOKHsXX0ysxCBbAtj1INg.jpeg" /><figcaption>I recall there was lot of thumbs up going around. And not that much work being delivered.</figcaption></figure><h3>Raising steam</h3><h3>Distruptor s.r.o.</h3><p>I wanted to work on a web platform as a developer. This new technology called React was picking up and I wanted to get on board. I didn’t think about what the job should be about. I just wanted to do web development and avoid corporations.</p><p>Then I came across a small, family-run company that focused on creating tools for online learning. There was a lot to engage with, like peer to peer videos &amp; audio, in-browser collaboration tools and a small focused team where every decision mattered.</p><p>It was a great place to learn how to get started as a frontend dev, to build with React, Typescript, and MS technologies. But it soon turned out that there is more to satisfying work experience than the tech stack alone.</p><p><strong>Some of the things that made me realize this wasn’t exactly where I wanted to be:</strong></p><ul><li>The team and the product didn’t grow in terms of scale and I soon reached my limit of what I could learn as a frontend developer there.</li><li>There was no concept of culture. There was friction between people and frequent ego clashes.</li><li>I didn’t have faith in the leadership and often questioned their decisions.</li><li>The money was alright. I took this as an opportunity to learn and increase my value.</li><li>It became apparent that the ambitions either weren’t there or that the founders didn’t have a clear enough vision. We were bought by a big telecom company (our biggest customer) eventually. They had a roadmap, but we just couldn’t hire.</li><li>I burned out hard in about 3 months when I tried to fill the role of Product Manager, UX designer and Engineering lead as well as being a frontend developer.</li><li>There were hard boundaries around the product development that I didn’t have time to learn about. There simply wasn’t time for it. Things in the realm of dev-ops, infra, and DX.</li></ul><p>What I really wanted to do was to own the development from start to finish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a5xmRJA2vJbMhv_8gSEMcw.jpeg" /><figcaption>That’s how I remember the family run business.</figcaption></figure><h3>Git gud</h3><h3>FNKY s.r.o.</h3><p>As I left my cooperation at the previous company, I interviewed for a <strong>frontend</strong> position at a small digital agency where I already knew some folks. I got the gig, started working but didn’t have enough projects lined up so I ended up having to do some freelance work to keep the lights on. It was a bit of a rough start.</p><p><strong><em>But good God.</em></strong></p><p>The work was so much fun. I knew every layer of the stack. I talked with talented and passionate people every day. There was so much creativity with a real “let’s get things done” mentality there.</p><p>At first, there didn’t seem to be a solidified culture concept, but then this organic culture sprang up on its own.</p><p>The agency was like the holy grail now. Small teams of capable and passionate people with well-scoped projects built from scratch to finish. The promise felt too good to be true.</p><p>The engineering team was bigger than the one at my previous job. Although I was strong in contemporary frontend development, I suddenly had to take on diverse responsibilities:</p><ul><li>I created a new FE build pipeline and formulated the FE coding guidelines.</li><li>We had weekly coding challenges.</li><li>I picked up BE development in PHP.</li><li>Got to work with big companies.</li></ul><p>The money was way below the market at the time, but I was happy. I was content with the money because I got to be around these amazing people every day. I got a chance to grow and learn.</p><p>But there was always this tension between projects. Sometimes, things spilt into the next project. Or the next project wasn’t quite ready. Other times, I had to make an engineering compromise I wasn’t happy about.</p><p>The engineering wasn’t the pillar on which the business stood. It was just one of the services we provided. After years of trying to bring the engineering to the next level, the lead engineer left.</p><p><strong>Where did that leave me?</strong></p><ul><li>The culture was great. There was stress and tension and hustle, but it was enjoyable in a way I didn’t think possible.</li><li>The job felt fulfilling until it didn’t. I widened my expertise and became more of a generalist. But the project switching eventually got repetitive.</li><li>There was a limit to how the company could solve complex problems with the engineering department and it became apparent that I wanted to go bigger.</li><li>There was some deal of financial instability. The money wasn’t great, but I wasn’t undervalued in the context of the company. Everybody knew how much the client invoiced for an hour of our time.</li><li>I wanted to have ownership of the code and the product. There is rarely time to be perfect, but there was seldom opportunity to be at least great. The transitive nature of short projects paid by the man-day doesn’t allow that.</li><li>When the most senior engineer left for greater challenges, I felt the company didn’t have much to offer me.</li></ul><p>I gave my leave notice after that and spent a lot of time thinking about what it is that I <em>really</em> liked and wanted to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-xiV3408Og4McJZTtcNPQ.jpeg" /><figcaption>This is strangely on spot for the ambiance and average age :D</figcaption></figure><h3>Searching</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytTSGFH8VyKrPnIGINWgvg.jpeg" /></figure><p>I set out to get ahead of the technological curve again (as I got stuck in reusing proven tech). I knew I had to up my value on the job market for whatever it was I decided to do next.</p><p>I uploaded and polished a single GitHub project that I felt was good enough example of my work.</p><blockquote>What I wanted to do differently was to have a clear gap between employment. To give myself time to reflect.</blockquote><p>To give that a structure, I put down in writing different aspects of employment, such as financial compensation, remote vs on-site, tech stack, culture, mission, product. I put these on index cards and started shuffling them around, trying to envision the companies that would embody those qualities and me in them.</p><p>When I started this soul searching, I thought I wanted to work remotely for a foreign company with a product. When I ended my search, remote work ended up at the bottom of my list.</p><p><strong>Here is what I realized mattered most to me:</strong></p><ul><li>I need to feel financially secure.</li><li>I want to be surrounded by people more capable, smarter, <strong>BETTER</strong> than me. So I can soak it all up, learn relentlessly.</li><li>I’m scared to give up the culture I had at FNKY s.r.o.. To end up in some corporate slog. This is fear is bigger than I anticipated.</li><li>I want to do product development. I want R&amp;D. I want ownership of the code. I want to build and nourish a thing that I can be proud of.</li><li>I want to work on a modern tech stack. I don’t care for cutting edge, I want a mature approach to adoption.</li><li>I need to trust the leadership, the mission and the product. Enjoyment of work is no longer just about solving technical challenges.</li></ul><p>Turns out that my longing for remote was dictated by the fact that I felt there was no one in the Czech republic to satisfy the rest of my requirements.</p><blockquote><strong>I wanted all of the above but didn’t want to move.</strong></blockquote><p>As I started searching for companies, I still felt that the best options were outside the Czech Republic, outside Europe even. I sent out about 15 emails, got some replies, scheduled a few interviews.</p><h3><strong>Then it happened</strong></h3><p>Out of the blue, I got an email about this USA startup called productboard — but it didn’t ring any bells at the time. It turned out that they have an engineering team in Prague.</p><blockquote><strong>Look, I have a lot of headhunters on my back. I imagine you do too. But this pitch was on point.</strong></blockquote><p>I shot them a short reply and got one back in a matter of minutes. That very same evening, I talked with a bunch of people from the engineering department. I found out they were just cooling down from ReactiveConf 2018. I also met with the CTO, Daniel, over a beer.</p><p><strong>What were my biggest fears at the time?</strong></p><ul><li>The technical prowess of the few people I met there was intimidating. Was I good enough?</li><li>This is a startup during takeoff, would I be able to keep up in terms of skill?</li><li>This would be my first startup. Would my work-life balance suffer?</li></ul><p>I was scared of the technical interview. But I was intrigued by the cultural interview as it was my first. It was also obvious that they cherish and protect the culture at productboard at all costs. As Dan Jacobs famously said,</p><blockquote>“I’d rather have a hole than an asshole.”</blockquote><p>It turns out I’m not that much of an asshole, since I’ve been at productboard for over a year now 😅</p><h3>On the fast track</h3><h3>productboard</h3><p>It’s good to do some housecleaning each year. Did I manage to hit the goals I setup? How is productboard treating me?</p><blockquote><strong>Well, I’ve learned more about web frontend in a year than in the three past years combined.</strong></blockquote><p>I mentioned during a one-on-one talk that I might be interested in going full-stack, but that I don’t know the language. They then gave me the time allowance to go slow and learn by doing, along with a mentor who was ready and eager to help.</p><blockquote>Now I’m full-stack 🤷‍♂️.</blockquote><p>I learned a ton about Postgres, Docker and lately Kubernetes.</p><p>If I’m in the office after 6pm, it’s usually because there’s a party going on (Thirsty Thursdays FTW 🥂). I can count on the fingers of my hand how many times I had to crunch and stay late at work. All of those could have been avoided if I wasn’t an idiot 😅.</p><p>Each and every person I meet on a daily basis passes my <strong>Beer Test</strong> — basically if I would want to grab a beer outside of work with them. I also got a chance to deliver some kick-ass features and see their impact on our customers (some 2,400 companies trust productboard). A day doesn’t go by without a discussion about clean code, TDD, best practices and the adoption of new tech.</p><p><strong>The whole company transformed tremendously. There’s a 4x increase in headcount. Amazingly, still a notable lack of assholes in the office.</strong></p><p>When I first started, we had one QA guy. Now there’s a team of five and they run over 200,000 tests per month 🤯. Our whole shebang was migrated from Heroku to a different cloud provider by a new dedicated infra team. There was a small group playing board games every Tuesday after work. Now I’m part of a DnD campaign 🎲.</p><p><strong>You get the point. There’s still so much to do and the learning possibilities are endless.</strong></p><p>We also started doing a 360 feedback. There’s a career ladder being put in place. I now know what steps to take if I’m aiming for a different title. Nobody’s pushing me though.</p><blockquote>What I’m saying is — I like it here.</blockquote><p>The only thing missing from my year-old soul-searching list was remote work. And what do you know, we’re building a fully remote team starting this year (in European timezones).</p><p>I get goosebumps when I look at some of the customers that are using our product. It feels surreal to know who will be happily clicking away on things in your today’s deploy.</p><p>I can’t begin to imagine where productboard will be in another year. But I’m pretty certain I want to be there to see it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_BQ7zS7jYQegvXZqG1sbg.jpeg" /><figcaption>productboard</figcaption></figure><p><em>Interested in joining the Czech Republic’s hottest startup? We’re always on the lookout for talented engineers. Check out our </em><a href="https://careers.productboard.com/engineering/"><em>careers page</em></a><em> for the latest vacancies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef215da1d1f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productboard-engineering/a-relentless-search-of-a-restless-developer-ef215da1d1f2">A Relentless Search of a Restless Developer</a> was originally published in <a href="https://medium.com/productboard-engineering">Productboard engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>