<?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[KeepTruckin Design - Medium]]></title>
        <description><![CDATA[Stories from the KeepTruckin Design team. - Medium]]></description>
        <link>https://medium.com/keeptruckin-design?source=rss----195243e05972---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>KeepTruckin Design - Medium</title>
            <link>https://medium.com/keeptruckin-design?source=rss----195243e05972---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:51:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/keeptruckin-design" 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 Frame a Problem]]></title>
            <link>https://medium.com/keeptruckin-design/how-to-frame-a-problem-f379c0ae4160?source=rss----195243e05972---4</link>
            <guid isPermaLink="false">https://medium.com/p/f379c0ae4160</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Zain Adeel]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 07:16:40 GMT</pubDate>
            <atom:updated>2019-08-16T07:21:37.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zY1JNpvqvWcyXTRjMQvlUw.png" /></figure><p><em>This article is an echo from a recent talk I gave at a </em><strong><em>Facebook Developer Circles</em></strong><em> conference in Islamabad, Pakistan.</em></p><p>Ever felt misunderstood? As if you are the only person that can truly realize your own perspective? As if it’s impossible to be completely objective about anything? It is impossible.</p><p>A designer working on the most insignificant problem approaches that very problem from a unique, intellectual, and emotional point of view. This frame of reference forces any design process to be subjective in nature, illustrating how design solutions are embedded in the designer’s culture itself.</p><p>Framing is the ability to switch roles and think of problems from someone else’s perspective. Although not possible in its entirety, a healthy design process depends on it.</p><h3>What is a frame?</h3><p>A frame is an active perspective, subjective in nature. When we tend to think about things we normally view them through our lens. However when solving design challenges, that is exactly what we must not do. We must try to do the exact opposite.</p><p>This Nielsen Norman Group article describes in detail how frames affect design decisions and how restating questions from a different point of view helps with better decision exploration:</p><p><a href="https://www.nngroup.com/articles/decision-framing-cognitive-bias-ux-pros/">Decision Frames: How Cognitive Biases Affect UX Practitioners</a></p><h3>What is a problem?</h3><p>A problem in the product space can either be an inefficiency or an inconvenience you wish to overcome, it can also be a conscious or unconscious unmet desire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AWLvrN9espeCyKudFZW3Gg.jpeg" /></figure><blockquote>Einstein famously said:</blockquote><blockquote>“If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.”</blockquote><p>Most products that fail, fail because they don’t spend time understanding their problems. This is important because the problem you wish to solve might simply not be worth solving. Realizing this today will save you pain tomorrow.</p><p>This podcast by IDEO talks about how to prototype a business utilizing the three circles of <strong>Desirability, Viability, </strong>and<strong> Feasibility:</strong></p><p><a href="https://www.ideou.com/blogs/inspiration/how-to-prototype-a-new-business">How to Prototype a New Business</a></p><h3>Problem framing tips</h3><ul><li>Avoid proposing solutions early on in the process. At all costs!</li><li>Ask “why” a lot. Let’s suppose someone asks you for a glass of water. You ask them “why” do they need a glass of water. They tell you that they are thirsty. You ask “why” again. They tell you they are thirsty because they have sweated a lot. You ask them “why”? They tell you they feel hot in the room. You ask “why” one last time. They tell you there’s no air-conditioning. This exercise allowed you to get to the core issue and understand where the inconvenience stems from. Essentially, whatever we build will be a small piece of a large puzzle, and we should always be aware of the bigger picture and understand our place in it. We might not be able to install an air conditioner in the room, but we can get people cold water to drink.</li><li>Reflect, take a step back once you have explored the problem space a little. Look to see if any patterns emerge. Insights here can set your product apart from your competitors.</li><li>Present the defined problem in the simplest language. The easier it is to understand, the easier it will be to work towards.</li></ul><h3>Three ways to validate the problem</h3><ul><li>Inquire (interviews). Talk to your prospective users, understand their needs, ask them “why”, etc.</li><li>Observe (Ethnographic research). Understand users in context of their environment.</li><li>Build a mock website to gauge user interest. By installing a form on your mock marketing website, you can directly measure how many people are looking forward to your product.</li></ul><p><a href="http://learningloop.io/playbooks/validating-the-problem">Validating the problem</a></p><h3><strong>Problem exploration using the four Ws</strong></h3><h4>Who is affected?</h4><p>Who is experiencing the problem? Can this user be further specified (by demographic, persona, motivation, reason for being in the situation)? Are they your customer? Have you validated the problem? Can you prove it?</p><p>The primary user will make or break your business. Once you decide on who they are, you can then plan to engage with them. There are two big advantages to understanding who is affected by a problem:</p><ol><li>Understanding the deep rooted motivations and needs of that user.</li><li>Communicating a singular objective throughout your organization so the team can focus on the furthest goal from the beginning.</li></ol><h4><strong>What is the nature of the problem?</strong></h4><p>Can it be explained in simple terms? What task needs to be accomplished? What pain points need to be relieved?</p><p><a href="https://www.nngroup.com/articles/user-need-statements/">User Need Statements</a></p><h4><strong>Where does it happen?</strong></h4><p>What is the context in which the user experiences the problem? Is it in a physical or digital space? Have you observed the problem in context? Can you describe that context? Who else is involved?</p><h4><strong>Why does it matter?</strong></h4><p>Why is this problem worth solving? What value does it bring to the user? What value does it bring to the business? Is it an acute problem for the user?</p><p>Answering these questions will result in a better understanding of the problem. I have seen products fail where teams don’t spend enough time with the problem and waste months of work by creating something that solves nothing, serves no one, and fails to meet any business goals whatsoever.</p><p>These core investigative questions help you define the skeletal structure of your idea which allows all the other processes that follow, to be applicable in the most effective and useful manner.</p><p>I urge all designers to understand that it is unintuitive to be able to keep ourselves from thinking of solutions whenever we talk about problems. Humans did not evolve to ponder over problems for too long. We evolved to be decisive and cater to personal problems rather providing impactful solutions for the society.</p><p>I will end this with a quote from <strong>Uri Levine — Cofounder of Waze:</strong></p><blockquote>“Fall in love with the problem, not the solution.”</blockquote><p>Follow me on <a href="https://www.instagram.com/zainadeelbutt/">Instagram</a> and <a href="http://facebook.com/zainadeeldesigns">Facebook</a>. You can also connect with me on <a href="https://www.linkedin.com/in/zainadeel/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f379c0ae4160" width="1" height="1" alt=""><hr><p><a href="https://medium.com/keeptruckin-design/how-to-frame-a-problem-f379c0ae4160">How to Frame a Problem</a> was originally published in <a href="https://medium.com/keeptruckin-design">KeepTruckin Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KeepTruckin’s Head of Design Shares His Journey From Islamabad to San Francisco]]></title>
            <link>https://medium.com/keeptruckin-design/keeptruckins-head-of-design-talks-about-his-journey-from-islamabad-to-san-francisco-ba5d9cd8f185?source=rss----195243e05972---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba5d9cd8f185</guid>
            <category><![CDATA[keeptruckin]]></category>
            <category><![CDATA[design-education]]></category>
            <category><![CDATA[design-maturity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tashfeen Ahmed]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 07:52:03 GMT</pubDate>
            <atom:updated>2019-04-19T07:52:03.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORxez13dPKoozQKdLYheyg.png" /></figure><p><em>Khushnood Qadir aka “KQ” is the Head of Design at </em><a href="https://keeptruckin.com/"><em>KeepTruckin</em></a><em>. Headquartered in San Francisco, KeepTruckin is a tech company that makes fleet management products for the trucking industry in US and Canada. KQ was one of the founding employees of the company, and has led its design efforts throughout. Today, KeepTruckin’s global design team consists of nearly 20 multidisciplinary designers with expertise across the full spectrum of design. To learn more, check out </em><a href="http://khushnoodqadir.com/"><em>KQ’s portfolio</em></a><em>.</em></p><p><em>IxDA Pakistan + </em><a href="https://www.facebook.com/groups/UXDesignInPakistan"><em>UXDP</em></a><em> (UX Design in Pakistan) hosted a fireside chat with Khushnood, moderated by </em><a href="https://www.linkedin.com/in/waisybabu/"><em>Awais Imran</em></a><em>, held at </em><a href="https://www.facebook.com/kncthub/"><em>KNCT Hub</em></a><em> in Islamabad. We talked about KQ’s journey into design, his experience working in Silicon Valley, designing for the complex trucking industry in US and Canada, growing as a designer, and a lot more.</em></p><p><em>Photography and title illustration by </em><a href="https://www.linkedin.com/in/zainadeel/"><em>Zain Adeel</em></a><em>. Article transcribed by </em><a href="https://www.linkedin.com/in/tashfeen/"><em>Tashfeen Ahmed</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZkkl47Bgz7uqBik-XcloQ.jpeg" /><figcaption>The event was held at KNCT Hub, Islamabad.</figcaption></figure><p><strong>Awais Imran (AI): So Khushnood, tell us about your story! From the day you were born to your early days as a child discovering your artistic/rebellious/design-ey side… all the way to today working as the Head of Design at KeepTruckin.</strong></p><p>Khushnood Qadir (KQ): I was born in Peshawar. My dad was in the army so we kept roaming around the country. I couldn’t really make any friends when I was growing up because every time I made friends, we used to move away.</p><p>Initially, I didn’t know that I was ever going to be a designer until I actually started working on design after graduation. I didn’t know what design really was and what the field meant to the world exactly. Whenever we used to pass by NUST, my dad used to say, “You have to go and study from this university”. So that just became my big goal. I found out now but surprisingly, I was suffering from ADHD at the time, so I failed in high school and when I went to college, I failed Math in my first semester but somehow made it through. That was one of the most difficult phases in my life and I couldn’t comprehend what was happening.</p><p>Up until that point, I used to sketch to clear my mind and fight anxiety. I used to make doodles in my classes and even had a comic series in my college magazine. I also made some large sketches that are hung up in my home right now. So that was my only interaction with design early on, you can say. To save myself from the embarrassment of failing, I joined the Arts Club and later became the president of the club. I did try to quit art when I failed for the second time in Math. After that my dad was like, “You need to think about what you want to do in life.” So I started focusing again more on my studies until graduation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OgdNRKtbaqDxUhZQSNPHiQ.jpeg" /><figcaption>Khushnood’s comic from CampBuzz Issue #90, National University of Sciences &amp; Technology</figcaption></figure><p>I was really fortunate to be friends with <a href="https://www.linkedin.com/in/kush-kella-3b04762b/">Kush Kella</a> and <a href="https://www.linkedin.com/in/shaneeb/">Shaneeb Kamran</a> at NUST. We worked on our final year thesis together and wanted to build a product out of it, so that’s where <a href="https://www.khushnoodqadir.com/pagify">Pagify</a> was born. We started working from my one-bedroom apartment in Bahria Town. Pagify was a really great tool for developers, and it got us incubated at <a href="https://plan9.pitb.gov.pk/">Plan9</a>. It was kind of my first professional validation after graduation. Working with Kush and Shaneeb made me realize that my life after college could be a whole new adventure.</p><p>So we started building the product more formally at Plan9 and got mentors from all over the world to teach us about running startups. One of the mentors was Shoaib Makani, our current CEO at KeepTruckin. He came and met all of the teams at Plan9 and liked our product. We were struggling at that time with finding the right target market for the product. We were engineers and didn’t know much about the business side, so we built the technology first and then thought of solving problems afterwards, when it should have been the other way around. We made a product for web developers thinking this problem existed and it did but our solution just wasn’t right for it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyoPx5mev0cuv_FM50iQaA.jpeg" /></figure><p>So that’s when Shoaib said, “You guys can join me at KeepTruckin, a new startup that is going to revolutionize fleet transportation, starting with the US”. That’s when I joined KeepTruckin. Ever since, many great Pakistani designers have passed through and are still in our team, and the good thing is that whoever joined our team has been good friends with me.</p><p><strong>AI: You have 6–7 years of experience in design, could you walk us through your self-learning journey? How have you grown as a designer?</strong></p><p>KQ: Most designers in Pakistan are CS graduates, since there aren’t many formal design programmes in the country. My journey was the same. I knew how to code a little bit, but didn’t really like it. I started with online lectures on <a href="https://teamtreehouse.com/">Treehouse</a>. When I started working with KeepTruckin, I really enjoyed that process because I looked for answers to interesting questions as part of my learning like <em>how do you put meaning in a logo? How do you create brand identities from that?</em> So it was more of me going out and finding resources for every problem that I faced as part of my work.</p><p>At KeepTruckin, I was put in a position where I had to design a mobile application for users based in the United States. It was a tough challenge to solve because of my lack of experience and the timezone difference.</p><p>I remember that my first mobile app design was hideous and I still look at it and cry, <em>what have I made!</em> But it was okay at that time to solve that problem. When I started expanding my knowledge, I realized that design is not just art but a very polished problem solving tool.</p><p><strong>AI: Tell us specifically about some great resources that helped you grow?</strong></p><p>KQ: Sure.</p><ul><li><a href="https://teamtreehouse.com/">Treehouse Online</a></li><li>Alan Cooper’s <a href="http://shop.oreilly.com/product/9781118766576.do"><em>About Face 4</em></a></li><li>Don Norman’s <a href="https://www.goodreads.com/book/show/840.The_Design_of_Everyday_Things"><em>The Design of Everyday Things</em></a></li></ul><p>When I started to get into design leadership, I started studying resources for building a design team that functions properly with the business. I learnt more about how to measure design maturity. I went through the detailed accounts of interviews and design leadership resources by Khosla Ventures and Google Ventures. In the US, I grew more rapidly as a designer as compared to when I was in Pakistan because of the exposure I received.</p><p><strong>AI: What could you have done to grow twice as fast as you did in the last 6 years?</strong></p><p>KQ: Maybe doing a bachelors in CS and then turning that into a masters in HCI or something more design-oriented…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fpBKjCAz5GV1aqQWWNlYLg.jpeg" /><figcaption>Our youngest and cutest attendee.</figcaption></figure><p><strong>AI: How did shifting to the US change you personally and professionally?</strong></p><p>KQ: In Pakistan, I started suffering from depression because I didn’t have the courage to face anything directly. But in the US, I was on my own. There was an initial cultural shock, but I made it through. With KeepTruckin, I could order anything I wanted so I had access to a lot of resources and books. So I kept reading and expanded on my knowledge.</p><p>My fundamental belief as a designer is that:</p><blockquote>Every designer should be able to work across all platforms of design and apply design thinking to anything. Design thinking should be platform agnostic.</blockquote><p><em>Awais suggested a really good resource for ordering books online — Fabingo.com. He mentioned, “When we were giving away books on UX Design in Pakistan, we found 9 out of 12 books on Fabingo.”</em></p><p><strong>AI: What were your expectations before you went to the US? What was the difference between your expectations and reality when you set foot there?</strong></p><p>KQ: Before going to US in 2016, I had only seen it in the movies. So there was a cultural shock and it was tough for me. Maybe it’s tougher for a lot of other people who move into the US. Getting used to life over there is extremely weird but also exciting i.e. if you love learning new things and meeting new people. When I landed in San Francisco, my first cultural shock was seeing a naked dude walking in the street. I was like, “Wow! This is a completely different place”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_beB4EPfDuu8eFLd91IyA.jpeg" /><figcaption>Gay Pride Parade in San Francisco. Photo via <a href="https://www.timeout.com/">Time Out International</a></figcaption></figure><p>I didn’t have a credit score, nobody trusted me and nobody let me rent their place since I had a Pakistani passport. It was a really challenging time and I didn’t have a house so I was crashing with a couple of friends. Then an Asian woman let me live in a tiny room at her place until I built a reputable credit score and started living in the apartment.</p><p>So there’s a whole new nature of practical challenges that you have to deal with.</p><p><strong>AI: There are very few companies in Pakistan that hire people here and take them to the US. We know US is the hub of the Western world for technology and design, so if someone wants to grow as a designer, what path can they follow?</strong></p><p>KQ: If you want to grow your skills, there are millions of resources available online. You don’t need a design degree for that. But if you want to have a broader career in the field of design, then I suggest you should try to go for a Masters degree in design abroad.</p><p>I’ll mention a couple of good programmes:</p><ul><li>Academy of Arts, San Francisco. I really like their course for modern media design that covers a lot of areas from web to mobile to digital design.</li><li>General Assembly Bootcamp has shorter courses and bootcamps you can opt for.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUVqVuqW3Ba-2yDv6qm9rQ.jpeg" /><figcaption>The session concluded with a series of community questions</figcaption></figure><h3><strong>Community Questions</strong></h3><p><strong>Senam Khan: Which Pakistani public institution, system or sector would you like to redesign — why, and how?</strong></p><p>KQ: My biggest pain in Pakistan is taxation. Pakistan collects a very small amount of tax and there are a few people who submit their tax. So income tax experience is what I’d really want to design. It’s not about the screen design, but it’s about the experience of the entire tax filing journey. There’s way too much ambiguity.</p><p><strong>AI: If I want to learn about design maturity, where should I go?</strong></p><p>KQ: I’d definitely start reading <a href="https://www.goodreads.com/book/show/27968897-org-design-for-design-orgs"><em>Org Design for Design Orgs</em></a> by Peter Merholz. InVision also recently came out with <a href="https://www.invisionapp.com/design-better/design-maturity-model/">a detailed report</a> on Design Maturity that’s worth checking out. I also recommend <a href="https://www.designbetter.co/design-leadership-handbook">InVision’s Design Leadership Handbook</a>.</p><p><em>Awais also recommended </em><a href="https://www.nngroup.com/articles/ux-maturity-stages-1-4/"><em>Nielsen Norman Group’s article series</em></a><em> on UX Maturity.</em></p><p><strong>Umair Khatri: 80–90% of the startups don’t know what design is. How do you think design is maturing in startups?</strong></p><p>KQ: It’s always an uphill battle, unless you’re a level 5 design team. That’s when the CEO and CTO are so immersed in design that design becomes the goal of the business for example, Google.</p><p>Design awareness is not as much about designers, as it is about the non-designers and more about communicating the value of design. Understanding the business goals and aligning them to design is essential.</p><p><strong>Amal Rathore: What are the ways to speed up the research analysis after the research is conducted? And how to convince the non-designers in the team to spend more time on analysis?</strong></p><p>KQ: I’d solve this problem in three ways:</p><ol><li>Break bigger problems into smaller ones and test for smaller interactions with a smaller user-base (i.e. have smaller sprint cycles).</li><li>Don’t take more than 5–6 users because with 5–6 users you can understand the trend.</li><li>Use Timeboxing Strategy and the Double Diamond model. Use 4–5 days for research. First two days for recruitment and then the last two days for testing.</li></ol><p>You have to be data-oriented but not always data-driven.</p><p>This event was a great learning opportunity for me as a designer. I’ve recently joined KeepTruckin as a Product Designer in their App Marketplace team. I’m really inspired by the team spirit, design thinking, processes and methodologies that the company is already using.</p><p>Before joining the company, I thought it’s going to be really difficult to communicate since half of the team is based in San Fransisco, but surprisingly, the communication is very efficient. Mainly because of the team culture and also because of the tools that we use. I hope to stay in touch with the design community and grow by being part of such events.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba5d9cd8f185" width="1" height="1" alt=""><hr><p><a href="https://medium.com/keeptruckin-design/keeptruckins-head-of-design-talks-about-his-journey-from-islamabad-to-san-francisco-ba5d9cd8f185">KeepTruckin’s Head of Design Shares His Journey From Islamabad to San Francisco</a> was originally published in <a href="https://medium.com/keeptruckin-design">KeepTruckin Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Team Grew 6x In 2 Years — Here’s How We Strengthened Our Culture & Collaboration Through This…]]></title>
            <link>https://medium.com/keeptruckin-design/our-team-grew-6x-in-2-years-heres-how-we-strengthened-our-culture-collaboration-through-this-1715b96ec074?source=rss----195243e05972---4</link>
            <guid isPermaLink="false">https://medium.com/p/1715b96ec074</guid>
            <category><![CDATA[team-communication]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[team-culture]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[remote-team]]></category>
            <dc:creator><![CDATA[Tashfeen Ahmed]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 07:49:22 GMT</pubDate>
            <atom:updated>2021-05-15T18:09:13.678Z</atom:updated>
            <content:encoded><![CDATA[<h3>Our Team Grew 6x In 2 Years — Here’s How We Strengthened Our Culture &amp; Collaboration Through This Transition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpZE__ZGIfZWfdAbaDaKng.png" /><figcaption><em>All images by author unless stated otherwise.</em></figcaption></figure><p><em>This story was co-authored by my colleague, </em><a href="https://www.linkedin.com/in/awsimran/"><em>Awais Imran</em></a><em>.</em></p><p>Our world today resembles a <a href="https://www.weforum.org/agenda/2018/11/the-fourth-industrial-revolution-is-driving-a-new-phase-of-globalization/">global village</a>, powered by information superhighways of the Internet, and software tools made for cross-continental collaboration and communication. To thrive in this new world, fast-growing teams need to scale with care and intention. If you don’t, your team culture and collaboration will be at serious risk.</p><p>In the last few years, KeepTruckin has grown from 300 employees across San Francisco and Islamabad to 1,600+ in new locations like Nashville, Buffalo, Vancouver, Lahore, Taipei, and Manila. In this process, our design team has grown even more — from 3 people in one office to 19 across multiple locations. Besides the inherent challenges of fast growth, we’ve faced significant challenges in remote collaboration; some we’ve solved, some we’re still working out.</p><p>We’d like to share our learnings with the larger design community in the hope they’ll be useful to other similarly structured teams.</p><p>Before joining KeepTruckin 3 months ago, I was uncertain about the design team’s collaboration across San Francisco and Islamabad and Lahore: how do they collaborate effectively when cross-functional teams and sub-teams are separated by thousands of kilometers and a 12-hour time difference?</p><p>As I discovered: the team uses a suite of industry-standard communication and collaboration tools that’s bolstered by a robust workplace subculture, and self-driven team members.</p><p>But of course it’s not that simple. Let’s dive into the tactics that we used to build a high-performing cross-continental design team. This is based on interviews with colleagues, and my personal observations.</p><h3>Create an inclusive design team culture first</h3><p>Team culture doesn’t just happen. You have to <a href="https://toggl.com/out-of-office-remote-company-culture/">cultivate it</a> by intentionally moulding how members work, collaborate, communicate, think, and grow as a team. This is doubly important in a global organization where people come from diverse backgrounds.</p><p>Building an inclusive team culture means making remote team members feel like they’re (almost) co-located, and that you’re all part of the same group, gunning after the same, shared objectives.</p><p>The list below is a manifestation of the values we’ve informally built over the past two years of rapid growth:</p><ul><li><strong>Love your work, and working together.</strong> Each of us landed in design because we genuinely believe it is our calling. This love of craft is infectious, and we love sharing it with our colleagues. We hold off-site collaborative team activities that allow for informal, deeper conversations to happen. More structured conversations happen in 1:1 meetings that go beyond work, and cover career, philosophy, the good life, health, relationships, personal finance and everything else you need to be a better human. We also don’t hesitate to peek over each other’s desk to ask, “Hey, that looks cool. What are you working on?” which leads to <a href="https://hbr.org/2011/02/make-serendipity-work">serendipity at work</a>.</li><li><strong>Help each other grow.</strong> “When the student is ready, the teacher will appear” is a quote that applies well to our design team. Members are encouraged to communicate their personal goals; managers and leaders support them as best as possible. The company invests in our growth by funding online courses, books, and conference passes. Team members with specialized expertise provide mentorship and regular feedback when you need it.<br>This is arguably my favorite bit about our design team’s culture. My colleagues constantly share their knowledge and wisdom; not only for design work but also for life in general.</li><li><strong>Empower designers to make important decisions</strong>. Designers are paired with product managers from the very start of each project, and are empowered to make fast design decisions without waiting for sign-off from senior leadership. Autonomy is important for engagement at work, and this is central to it.<br>Do mistakes happen? Yes, frequently, but they’re identified and fixed early because we practice open communication and proactively solicit feedback. We also keep getting better over time as we learn from our mistakes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BoSATIFDId-DyuyjQsw64A.png" /></figure><ul><li><strong>Practice open communication. </strong>We share our work early and openly to solicit feedback. Cross-functional feedback identifies feasibility and usability issues early, and saves major headaches later. We understand that feedback is for improving the design and a way to achieve better outcomes — <a href="https://medium.com/the-year-of-the-looking-glass/taking-feedback-impersonally-7c0f3a8199d9">it is not to be taken personally</a>.</li><li><strong>Celebrate success, and learn from failure.</strong> Giving shoutouts when your peers execute well reinforces this, as does impersonal group reflection when something goes wrong. This ties in closely with #2.</li><li><strong>Practice async-first communication.</strong> Cross-office face-to-face communication is expensive for us because one group ends up taking meetings at odd hours. This isn’t sustainable, so we push for asynchronous communication that respects the other person’s time and timezone.<br>Case in point: we’ve replaced synchronous daily standup meetings with asynchronous daily updates in a Slack channel, tasks documented and updated regularly on JIRA boards.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*huUV5AcM-sVKv1AaWjrV1g.png" /></figure><h3>Maintain a well-documented, single source of truth</h3><p>As design teams grow, so does the tendency for inconsistencies to creep into the user experience. Interactions that work one way in one part of the product, begin working differently in another. This was one of our bigger struggles early on.</p><p>Our design team initially kept all design resources on a central Google Drive folder. This worked while the team was co-located, but it became a bottleneck later as we expanded. It wasn’t obvious how the folders were structured, which subfolder had the latest files, and which mockup was approved for implementation — unanswered questions that slowed us down. You were out of luck if the team member who could answer this question was fast asleep on the other end of the globe.</p><p>As our team size expanded 6 times over across our existing offices, and we started operations in new cities, we felt the need for a better central repository that would serve as a single source of truth.</p><p>It was around that time that <a href="https://www.abstract.com/">Abstract</a> — the version control system for designers — launched publicly. We took a leap of faith and haven’t looked back since.</p><p>Today, all our work lives on Abstract: ongoing projects, archives, experiments, and a work-in-progress design system. Abstract supports an internal design culture, provides clear lines of control, and encourages a consistent user experience.</p><p>We’re also documenting best practices and our general design process on Confluence — our internal knowledge-base — so incoming designers can hit the ground running. Confluence also serves as a source of truth on project specs, our user research reports, organization charts, our long-term goals, and more across all functions of the business.</p><p>In the future, we want to simplify collaboration by reducing the number of design tools, and integrating our front-end design system across all our products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GghBQSGURdAcfB8P2D0HWQ.png" /></figure><h3>Expand and organize design teams with intention</h3><p>We grew from a team of three designers in 2016 — a lead, product designer, and communication designer — to twenty designers with expertise across the full spectrum of digital product design — research, interaction design, visual, and industrial designers, UI engineers and more.</p><p>Collaborating effectively with the rest of the company while staying in sync as a large design team was a core challenge. We tackled this by following the “<a href="https://www.oreilly.com/library/view/org-design-for/9781491938393/ch04.html">Centralized Partnership</a>” model championed by Peter Merholz in <em>Org Design for Design Orgs.</em></p><p>Centralized Partnership is a hybrid model that combines the best of centralized and decentralized models. Team leads work with product managers to define projects, and assign a designer from a virtual pool. This pool has smaller sub-teams of designers, each centered around a certain business problem. After a project is finished, the designer returns to the larger virtual pool, available for other projects within their sub-team, but not unavailable for projects in a related product group. This model supports a strong design team subculture, encourages individual growth, leads to a more consistent user experience, while keeping cross-functional partners happy. You can <a href="https://www.slideshare.net/KristinSkinner1/org-design-for-design-orgs">read a deeper summary on the Centralized Partnership model here</a>.</p><p>Organizational models are of course built to support people, and so its success depends largely on the calibre of people you bring into your team.</p><p>Hiring great people is a complex topic that’s outside the scope of this article, but I’ll share one tactic that has worked immensely well for us: hire for exceptionally strong self-management and communication skills. With designers, managers and cross-functional colleagues spread across the globe, team members absolutely need to be proactive at work, initiate and drive their own projects, and communicate clearly with the right stakeholders at the right time. Any lapses here can lead to days of lost work that startups cannot afford. My colleague Awais Imran wrote about hiring in more detail in “<a href="https://uxdesign.cc/my-first-year-as-a-design-manager-a2b3bc273c71?gi=2eca2c1aa8b7">My first year as a design manager.</a>”</p><p>The KeepTruckin design team is only in year two of its cross-continental team setup, so we’re still learning, and experimenting. We have our ongoing struggles, but we see them as obstacles on the way to growth. Some of the goals include:</p><ul><li>More effective asynchronous communication, so team members in Pakistan can take deeper breaks from work at night when colleagues in America start their work, and vice versa.</li><li>Integration of the front-end design system across all products to strengthen consistency in the user experience.</li><li>Stronger partnership between the designer, product manager, and engineer.</li><li>By sharing what we’ve learned, we hope we can start a conversation with the larger design community so we can all get better together.</li></ul><p>Have you worked with a remote team? We’d love to hear your experiences, tactics, process and more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1715b96ec074" width="1" height="1" alt=""><hr><p><a href="https://medium.com/keeptruckin-design/our-team-grew-6x-in-2-years-heres-how-we-strengthened-our-culture-collaboration-through-this-1715b96ec074">Our Team Grew 6x In 2 Years — Here’s How We Strengthened Our Culture &amp; Collaboration Through This…</a> was originally published in <a href="https://medium.com/keeptruckin-design">KeepTruckin Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first year as a design manager]]></title>
            <link>https://medium.com/keeptruckin-design/my-first-year-as-a-design-manager-a2b3bc273c71?source=rss----195243e05972---4</link>
            <guid isPermaLink="false">https://medium.com/p/a2b3bc273c71</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Awais Imran]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 07:30:58 GMT</pubDate>
            <atom:updated>2019-04-19T07:39:01.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zifLtKWLSZIPaC6WoUzoQ.jpeg" /><figcaption>Some of KeepTruckin’s design team. We’re now a team of 19 spread across US and PK.</figcaption></figure><p>Note: This was originally published on <a href="https://uxdesign.cc/">UX Collective</a> — one of my favorite design publications on the web. It was added to the KeepTruckin Design Blog to coincide with its launch in April.</p><p>I remember feeling a mix of unease and excitement when Khushnood, our design lead, shared he’d like me to manage KeepTruckin’s growing product design team in Pakistan.</p><p>I was uneasy because I hadn’t <em>formally </em>managed a team before. Sure, I do <em>coordinate</em> with freelance writers for <a href="https://priceoye.pk/mobiles/apple/apple-iphone-xr">PriceOye’s product pages</a>, but that is an ad-hoc affair. This felt more high-stakes, and I did not feel ready.</p><p><strong><em>What if I failed?</em></strong></p><p>But I was also excited because this was wholly new territory, and exploring newer territories helps me grow fast and feel engaged.</p><p>Now more than a year later, I’m happy to report there was no catastrophic failure, though there were many teachable moments.</p><p>Today, I’d like to share <strong>key lessons from my first year as a design manager</strong>. I hope they’ll benefit both first-time managers, as well as individual contributors looking to collaborate better with their manager.</p><h3>Key principle: strive to be a leader, not a manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4mXfiBJKUYinJ_o0hzTUAQ.jpeg" /><figcaption>Photo by Pixabay on <a href="https://www.pexels.com/photo/abstract-green-layers-fine-35196/">Pexels</a></figcaption></figure><p>At its core, management is about coordinating employees and resources to achieve company goals. Management is required only because team members don’t have access to all the information and resources they need to succeed, or because they don’t know or can’t communicate with colleagues that have that information.</p><p>As a manager, you generally have better information access, and a bird’s eye view of things that helps you connect people and resources for moving projects forward.</p><p>In an ideal world, all this information would be perfectly documented, easily accessible, and everyone would communicate and collaborate like a <a href="https://en.wikipedia.org/wiki/Group_mind_(science_fiction)">hive-mind</a>. In this ideal world, you would be a <em>leader</em> instead of a manager, providing mentorship, growth, and vision to your team.</p><p><strong><em>This is the world you need to strive for.</em></strong></p><p>You always need to be 1) identifying gaps in knowledge and collaboration, and 2) always be fixing them — all the while instilling self-management skills in your team so your efforts multiply over time.</p><p>Here’s a quick example of this 2-step process in play.</p><h4>Example: Fixing the daily standup</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wYCRPsAFOSpJ4UBrfdCZQ.jpeg" /><figcaption>Photo by Pixabay on <a href="https://www.pexels.com/photo/arachnid-artistic-blur-close-up-276203/">Pexels</a></figcaption></figure><p>In a previous company, our team manager would call for daily standup meetings where each individual contributor (IC) would share what they did yesterday, what they’ll do today, and if they need help on anything. These “scrum meetings” are common at many software companies.</p><p>The problem is they’re not scalable. Standup meetings<em> might</em> work for a small, highly collaborative team that’s working on a single project, but for larger teams it’s a waste of time for everyone <em>except</em> the manager hosting them. It breaks everyone’s state of flow, and unless meetings are aggressively time-boxed, everyone just zones out until it’s their turn.</p><p>I despised the daily standup as an IC, so when <strong>I</strong> <strong>saw this wasteful pattern</strong> in my team’s daily routine, <strong>I</strong> <strong>decided to fix it</strong>.</p><p>Today, all product designers share their day’s tasks on Slack whenever they start work. We all post to this channel — so every designer knows what their teammates are working on to get that bird’s eye view that is generally exclusive to managers. If required, I can then reach out to individual designers for more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*88xSjYXMeujqQlFTnltzLQ.png" /><figcaption>Team members posting items for today and tomorrow. Notice how Zain posted his next day’s items at night.</figcaption></figure><p>I also worked with every team member to build a habit of sharing their progress at the <em>end</em> of each day. It’s just a good habit to <a href="https://dailystoic.com/prepare-morning-review-evening/">reflect on your day</a> before you head out, so you can do better tomorrow. And since our Slack channel is public for all to see, it is also effective for maintaining accountability.</p><p>More often than not, team members now even share their next day’s tasks <em>before</em> they go home. Planning for tomorrow in the evening is also a productive habit: it helps you hit the ground running the next day.</p><p>With that example out of the way, let’s talk about effective practices for identifying those knowledge and collaboration gaps, and fixing them.</p><h3><strong>Step 1: Identifying gaps</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oos25E_FckRS7o8LJkS6ag.jpeg" /><figcaption>Photo from <a href="http://pexels.com/">Pexels</a></figcaption></figure><h4><strong>1) Schedule regular 1:1 meetings with every team member</strong></h4><p>I enjoy having deep conversations on life, career, relationships, and growth so when I learned about 1:1 meetings, I immediately adopted them in my team.</p><p>1:1 meetings are absolutely gold for building rapport with your team members, understanding each other’s strengths and weaknesses, identifying issues at work <em>before</em> they become serious, and hopefully becoming friends.</p><p>My team enjoys them so much we affectionately call them “Heart to Heart” or H2H sessions. We talk about everything from how to live life, about happiness at work and at home, passions and side-projects, our ambitions, fears and insecurities — almost anything meaningful goes except for ongoing projects. H2H sessions are also great for sharing candid feedback with one another.</p><p>There are many resources available online for having effective H2H sessions. I encourage you to explore them. You can also check out my <a href="https://docs.google.com/document/d/1i2hui1PY5raNi1Ntd9KWujKLhtIHaXTi5jsjBdTFwC8/edit?usp=sharing">H2H questions</a>. Remember: starting with just “how’s life?” and actively listening often goes a long way.</p><h4><strong>2) Actively solicit feedback from <em>everyone </em>you collaborate with</strong></h4><p>In any given project, you and your team may collaborate with product managers, customer support specialists, front-end and back-end and QA engineers, graphic designers, marketing managers and more.</p><p>By asking collaborators for feedback after each project, I’ve identified several company-level process problems. In these feedback sessions we discuss what my team and I did well that we should do again, what we should improve, and where we completely screwed up that we should fix immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYqxGE8b5_lxlvF4OoE_AA.jpeg" /><figcaption>Photo by Daria on <a href="https://unsplash.com/photos/zoCDWPuiRuA">Unsplash</a></figcaption></figure><p>Documenting this feedback and reviewing it when starting a new project ensures we learn from our mistakes, and keep getting better. It also provides value to other teams in the company for identifying internal process problems.</p><p>These two practices alone helped me identify important issues, but after a few months my pool was running dry. I was identifying issues based only on my limited experience.</p><p>To get better at identifying problems, I found great help by <strong>learning from accomplished design leaders </strong>like Julie Zhuo, Aarron Walter and Eli Woolery. You can do this too by poring over their <a href="https://medium.com/the-year-of-the-looking-glass/unintuitive-things-i-ve-learned-about-management-f2c42d68604b">design</a> <a href="https://medium.com/the-year-of-the-looking-glass/average-manager-vs-great-manager-cf8a2e30907d">management</a> <a href="https://medium.com/the-year-of-the-looking-glass/managing-more-experienced-people-9893f9903649">articles</a> and <a href="https://www.designbetter.co/design-leadership-handbook">books</a>, and applying it to your own management practice. I promise you’ll see amazing results.</p><p>Now that you’ve identified issues, it’s time for…</p><h3>Step 2: Fixing them</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSH97L7cxGPSXIgTNQ63tw.jpeg" /><figcaption>Photo by RawPixel.com on <a href="https://www.pexels.com/photo/person-fixing-pendant-lamp-1266006/">Pexels</a></figcaption></figure><h4>1) Take bold initiatives</h4><p>You have more power than you think.</p><p>My key takeaway from Tim Ferris’ <a href="https://www.goodreads.com/book/show/368593.The_4_Hour_Workweek">4-Hour Workweek</a> was the principle of “seeking forgiveness, not permission.”</p><p>Instead of waiting around for someone’s permission, I’ve found it more effective to just solve the issues I feel strongly about. If I wait for my manager, or my manager’s manager’s permission to do something, it’ll take forever to fix things — risking the health and productivity of my team in the process.</p><p>Chances are if you think deeply enough about the issue and its fix, consider the perspective of affected team members, and cater to any untoward scenarios beforehand, implementing a good fix right now is far better than implementing a great one later.</p><p>In the odd case you do genuinely screw up, take a deep breath, seek forgiveness, learn from your mistake and try better the next time — <em>but don’t lose your momentum.</em></p><p>I’ll share an example from my experience below.</p><h4><strong>Example: From Photoshop + Google Drive to Sketch + Abstract</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*qkse3Gn8bhdnf0PLXGAErQ.png" /><figcaption>Image via <a href="https://medium.com/webkul-dev/version-control-system-for-ui-designers-3022ae9c4753">Webkul</a></figcaption></figure><p>When I joined KeepTruckin, we were designing mostly in Photoshop, with some projects in Sketch. All files were sync’d on Google Drive, and were versioned <em>manually </em>by suffixing “v1”, “v2” and so on along with a summary of changes within file names.</p><p>It was a mess that was slowing us down, and causing undue stress — as it did once when a team member worked on a crucial file locally, and forgot to sync it before going home, fell terribly sick at night and couldn’t come to work for a few days. We had to grab the file from their computer to get the time-sensitive project back on track. Thankfully, both the designer and their designs recovered fine, but we lost precious time and energy because of a poor toolkit.</p><p>So I pushed for and led the move to Sketch, along with <a href="https://www.goabstract.com/">Abstract</a> for automatic version control, despite resistance from team members. We delivered a project in Sketch without asking every stakeholder for permission, and proved that this was a superior process. Today, Sketch and Abstract are central to our workflow.</p><h4>2) Document, document, document</h4><p>As mentioned earlier, one reason why management is required in the first place is because team members don’t have access to the information and resources they need to make things happen.</p><p>You can continue sharing information and providing resources each time collaboration breaks down, or you can document them and make it accessible to everyone. It frees you up to focus on more valuable work, while helping your team be more productive.</p><p>For example, I noticed every time a new designer joined us, I would spend more time telling them about tools and how to get access to internal tools, than getting to know them as a person.</p><p>So to improve onboarding for new designers, we put together a welcome deck that has everything they need to get up and running. We personalize the deck for every new hire, get it specially printed it out for them, and gift it to them on their first day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LxN_jJY2Axow8xVzRZnkYA.png" /><figcaption>Page from our welcome deck. <a href="https://dribbble.com/zainadeel">Illustrations by Zain</a>.</figcaption></figure><p>There’s a lot more you can do: document user research notes in a shared folder, share meeting minutes with relevant stakeholders, build a comprehensive design system, record system walkthroughs, print and hang your personas near your workspace, and more.</p><h4>3) Hire the right people</h4><p>Now hiring is a different ballgame, but it is fundamental to your long-term success. Your fixes will remain temporary without the right people to follow through on them.</p><p>When I started at KeepTruckin, there was just one other designer in my team. Since then, we’ve hired 5 people who constantly raise the bar for great work, help build team culture, and are just plain fun to work with everyday. They also happen to be awesome product designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnvY5Yg5qZpdoNEjCUD5Sg.jpeg" /></figure><p>To find these fine folks, I reviewed hundreds of profiles and portfolios, and interviewed dozens of designers. My core finding thus far is you need to <strong>hire for both skills and attitude, with slightly greater emphasis on the latter.</strong> Avoid egoists with excellent design skills; instead hire kind, growth-oriented people with great design skills and coach them to excellence.</p><p>Of course finding people can be a challenge in the first place. I’ve found more success in active, local communities than on international platforms like Dribbble or Behance.</p><p>You could join and participate in these communities or go one step further and create one yourself. Community building is a separate topic, but the core gist is you need to provide some value to people: whether that’s through a <a href="https://uxdesignweekly.com/">regular design newsletter</a>, <a href="https://medium.com/dropbox-design">a design blog</a>, or a fun Facebook group is up to you. I started <a href="https://www.facebook.com/groups/UXDesignInPakistan/">UXDP</a> because I enjoy community building, but it is also now a great talent platform for local companies and designers alike.</p><p>Another helpful principle is to <strong>hire for skills at a team-level</strong>. KeepTruckin’s product design team started off with generalist visual designers. We then hired for generalist interaction design skills, followed by specialist user research, specialist visual design and frontend development skills. So every time we need more people, we think deeply about how we can balance skills at a team-level.</p><p>Today, we have a product design team that is greater than than the sum of its parts. We have the skills we need to deliver successful outcomes, and a fun culture which encourages play, and growth through knowledge sharing.</p><p>There’s a lot more to hiring, of course. You should check out <a href="https://articles.uie.com/job_ad/">Jared Spool’s</a> and <a href="https://medium.com/the-year-of-the-looking-glass/7-reasons-to-no-hire-a-product-designer-part-i-95cf34a851af">Julie Zhuo’s</a> articles on hiring for more insights.</p><h4>4) Have a vision, and rally the troops</h4><p>Nothing unites and motivates a team like a bold vision for the future. As a manager, you need to think what your team will achieve, look, and work like 1 year, 5 years, and 10 years down the line. Will you create robust, evolving personas that will be adopted by the entire company? Build a comprehensive design system that outlasts everyone on the team? Have dedicated UX researchers? Skip remote interviews for in-context, ethnographic research? Design a new product that fundamentally changes an industry?</p><p>Thinking about this vision, and sharing it with your team in 1:1 meetings, all hands, and design reviews keeps our team motivated, and helps us retain talent.</p><p>Of course, it matters that you actually make progress towards that vision or your team won’t trust you. If six months go by and you’re no closer to your vision than before, it’s easy to lose that motivation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cB8IkzxH6ZPMxncIBrNAOg.png" /><figcaption>Photo by Pixabay on <a href="https://www.pexels.com/photo/abstract-background-beach-color-355288/">Pexels</a></figcaption></figure><p>All this talk about vision makes it easy for me to end this article with one of my favorite quotes.</p><blockquote>“If you want to build a ship, don’t drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea.”</blockquote><blockquote>— Antoine de Saint-Exupery, French writer</blockquote><p>Thank you <a href="https://www.linkedin.com/in/khushnood-qadir-03357266/">Khushnood</a> for trusting me with this responsibility; and thank you <a href="https://www.linkedin.com/in/daniel-erwin-ux-director/">Daniel</a>, <a href="https://www.linkedin.com/in/karstenrowe/">Karsten</a>, and <a href="https://www.linkedin.com/in/zainadeel/">Zain</a> for reviewing early drafts of this article.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2b3bc273c71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/keeptruckin-design/my-first-year-as-a-design-manager-a2b3bc273c71">My first year as a design manager</a> was originally published in <a href="https://medium.com/keeptruckin-design">KeepTruckin Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>