<?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 Arsalan Khatri on Medium]]></title>
        <description><![CDATA[Stories by Arsalan Khatri on Medium]]></description>
        <link>https://medium.com/@marsalank?source=rss-742c6d0f1f38------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*X3z59GGpQSAsVEdDuOiDuQ.png</url>
            <title>Stories by Arsalan Khatri on Medium</title>
            <link>https://medium.com/@marsalank?source=rss-742c6d0f1f38------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:53:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marsalank/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[Morphing your UI/ UX folio for product design roles]]></title>
            <link>https://marsalank.medium.com/morphing-your-ui-ux-folio-for-product-design-roles-5744da1d4a8c?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/5744da1d4a8c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Wed, 17 Sep 2025 05:54:34 GMT</pubDate>
            <atom:updated>2025-09-17T05:54:34.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PLOMU2tjg2Humk7b" /><figcaption>Photo by <a href="https://unsplash.com/@simplicity?utm_source=medium&amp;utm_medium=referral">Marija Zaric</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>“What makes my case study stand out for product design roles”</blockquote><blockquote>“I’m a freelancer/ part of a software house and not part of the implementation team.”</blockquote><blockquote>“Projects aren’t long term and we are just expected to handover designs. How do I create relevant projects?”</blockquote><p>Over the past couple of months, I’ve reviewed hundreds of profiles and spoken to dozens of folk and there’s been some themes which still haven’t made much progress over time. Its unfortunate but it is what it is.</p><p>What matters is <em>‘how might we’</em> fix this.<br>For product design roles, one of the deal-breakers is portfolios.</p><p>The queries above are a selected few from many similar ones. I usually end up repeating some permutation of these core themes as a starting point:</p><p>• Research your domain/ industry.<strong> </strong>What is expected from the role? Where is the design industry headed? What competencies truly help differentiate you? Most of this has nothing to do with employers or job applications but simply awareness of expectations.</p><p><strong>Fix: </strong>Internet’s your best friend and learning how to learn is key. Research and get answers to the above as a start. From the role expectations, what are the gaps and how can you fix it. Update your folio to reflect those. There are answers available and waiting for your action. Hard work improves your chances of getting a break.</p><p>• In traditional UI/ UX roles, your understanding of the business, how your product functions, and what value does it provide to the user is rarely evaluated, and this gap spills over in case studies when you will just have interface designs and prototypes with zero context.</p><p>Fix: Ensure that you show/ tell not just the product, but the business, it’s customers and what the general landscape looks like. Put your non-designer hat on and put in genuine effort to understand the product/ feature you are building. Understand what metrics matter to the business and how did your work contributing to moving the needle.</p><p>• User feedback’s on whatever you’ve built is missing. Sure you followed the brief and delivered what was required, but what do the users think about it. What does success look like?</p><p>Fix: You have to showcase and document YOUR effort to how you attempted to validate this. Even if your delivery timelines didn’t allow you to research, put in the effort afterwards regardless to get feedback from users and document it. Bonus if you go a few steps ahead and update your design/ prototypes to reflect it.</p><p>There are many more, but just these 3 themes alone can make all the difference.</p><p>Here’s to us putting in the work, level up and putting our best foot forward. <a href="https://www.linkedin.com/search/results/all/?keywords=%23growth&amp;origin=HASH_TAG_FROM_FEED">#growth</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23career&amp;origin=HASH_TAG_FROM_FEED">#career</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23design&amp;origin=HASH_TAG_FROM_FEED">#design</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23tech&amp;origin=HASH_TAG_FROM_FEED">#tech</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23learn&amp;origin=HASH_TAG_FROM_FEED">#learn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5744da1d4a8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key reflections from my 3 (ish) year journey building design @  Bazaar]]></title>
            <link>https://marsalank.medium.com/key-reflections-from-my-3-ish-year-journey-building-design-bazaar-382786b7bd04?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/382786b7bd04</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Sat, 12 Aug 2023 09:41:43 GMT</pubDate>
            <atom:updated>2023-08-12T09:41:43.164Z</atom:updated>
            <content:encoded><![CDATA[<h3>Key reflections from my 3 (ish) year journey building Design @ <a href="https://medium.com/u/6b3115424f59">Bazaar</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QYcHa3qOQWOHvkkp" /><figcaption>Photo by <a href="https://unsplash.com/@ourlifeinpixels?utm_source=medium&amp;utm_medium=referral">Our Life in Pixels</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This post is a theme continuation of sharing a <em>few</em> significant reflections and takeaways from a 3(ish) year journey at <a href="https://www.menabytes.com/bazaar-series-b/">Bazaar</a>. I’ve done a<a href="https://uxplanet.org/key-reflections-from-my-5-year-journey-at-careem-b81319648458"> similar writeup</a> about my Careem experience.</p><p>These reflections have shaped me and help share themes from what works, what doesn’t, and everything in between. In light of keeping it fresh and actionable, think of the following pointers as executive summaries.</p><p>Let’s go!</p><ul><li><strong>Placing bets by becoming ‘the first follower’<br></strong> Even though you might be a ‘leader’, it takes courage to be amongst the first to stand by someone when its not the expectation. Everyone needs their first follower. Follow a vision you resonate with. Build a convincing case for yours. <a href="https://www.youtube.com/watch?v=fW8amMCVAJQ">Absolutely love this video if you want a recommendation.</a></li></ul><blockquote>“If the leader is the flint, the first follower is the spark that really makes the fire.”</blockquote><ul><li><strong>Having a strategy for culture<br></strong>We’ve all heard the phrase “Culture eats strategy for breakfast,” so why not have a <em>strategy</em> for it? One of the things I got to experience the closest is setting up team culture. Having solid values at the core is essential, and as you scale you have to make sure they don’t just become decoration on walls. Act your values. Steadfast; protect your team culture.</li><li><strong>Being a solid team player is the ultimate trait to master<br></strong>If you’re someone who people love working with, both personality wise and competency wise, other things rarely would matter. Even if you feel you’re not good enough, you’d establish relationships where people will open up to you and tell you so, and help you grow!</li><li><strong>Growth priorities: Self &gt; Team &gt; Organization<br></strong>Yes, in that order. When you’d witness your mind expanding, you’d naturally impact those around you. Its vital not to misinterpret this with becoming selfish in the typical sense. Looking after your own growth will ultimately have ripple effects on your team and eventually the organization.</li><li><strong>Non-designers can make the best designers<br></strong>This perspective for me has strengthened overtime. Peers from different functions like customer success, growth or operations often have significantly much more access to customers (and their perspectives) than a designer ever would.</li><li><strong>The powerful combination of branding &amp; performance data</strong><br>In the local context we’ve been taught historically that brand identity is subjective and its more about the ‘feel.’ While perception does hold value, I’ve seen it being misunderstood as we don’t need to measure anything we post online. This couldn’t be further from the truth, and over these years I’ve seen the benefit of being data informed as you go about curating your brand.</li><li><strong>Setting a global ambition, but forming local milestones<br></strong>Building something great takes time, and a lot of benchmarking of what does great look like at an international scale. Its then vital to also circle back to where you stand today, and start charting a roadmap to getting there. An example which stands our was design recruitment where we looked at all hiring processes of (M)FAANG orgs but ensured our process is cognisant of the challenges of hiring designers in Pakistan.</li><li><strong>Fostering next-gen leadership from day zero<br></strong>I’ve had the pleasure of hiring and coaching dozens of individuals during my time, and I understood that with time expectations from leadership evolves. For that evolution to make sense, they naturally would get the flavour of leadership on the receiving side to course correct ideals, and then start assuming leadership wherever they see gaps to fill.</li><li><strong>Marathon of sprints — a LOT of (intensely smart) hard work is needed for a long time </strong><br>This ones pretty straight forward but it also comes as a surprise to many. We’re in an ecosystem where we definitely have a lot of challenges, but that only means that we will have to go that extra mile to do something big and meaningful (loosely quoting Careem’s Mudassir Sheikha and what he often used to tell us.) Its definitely a marathon, but there would be phases where you’d have to run faster than you’ve ever ran before.</li><li><strong>Taking regular breaks and focusing on mental health<br></strong>The above implies that it will default to a burn out. Its critical that you take out time for yourself to unplug and recharge yourself, especially to keep your focus in tact. The best breaks are those where you genuinely don’t <em>worry</em> about what’s happening at work, and embrace the FOMO. Easier said than done, I know.</li><li><strong>Master the balancing act between a leader and a player-coach<br></strong>Overtime your role evolves and depending on the situation you might get management responsibilities. It’s important to always keep a close pulse on how are you doing on both fronts, get feedback from your stakeholders on your ability to balance between the two type of roles. I personally believe having some component of being hands on will always reap dividends.</li></ul><p>Here’s to hoping not to repeating the same mistake twice, making new mistakes, and being able to support each other as we build together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=382786b7bd04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘How to start writing’ — an actionable mini guide]]></title>
            <link>https://marsalank.medium.com/how-to-start-writing-an-actionable-mini-guide-42d538fd7cd9?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/42d538fd7cd9</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 18:51:59 GMT</pubDate>
            <atom:updated>2021-08-20T12:47:18.955Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to start writing — an actionable mini guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lLIYwQkpt9A8hOlQ" /><figcaption>Photo by <a href="https://unsplash.com/@ashleywedwards?utm_source=medium&amp;utm_medium=referral">Ashley West Edwards</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>“We are kept from our goals not by obstacles, but by a clear path to a lesser goal.” — Robert Brault</blockquote><p>Writing’s very close to me as it helps me share my learnings and become a better individual. The above is one of my favorite quotes, and what I like the most about it is how functional it is.</p><p>Let’s try to break down the obstacles to achieve the ‘goal’ based on the quote.</p><p>If your goal is to ‘start writing’, then your objective is to break that goal into as many levels of a lesser goal as you can possibly handle. This automatically helps overcome the obstacles which contribute to your <em>writer’s block.</em></p><p>For the purpose of the exercise, let’s see if we can write an article on something as random as… <strong>‘sticky notes.’</strong></p><blockquote>I’d highly encourage you open your text editor or grab a pen/ paper, but follow along the cues which accompany each step!</blockquote><h3><strong>Our goal — Write an article on sticky notes</strong></h3><p>Let’s break it down into layers:</p><h4><strong>1st layer — Content themes</strong></h4><p>These are high level pointers you want to cover in the writeup. Don’t worry about order just yet.</p><blockquote>In our example for sticky notes, we would probably talk about relevance (what made you write and why’s it important to you.) You can possibly add a bit of history and the original purpose of sticky notes. This can then be followed by their types, and maybe anything else you might want to add (like colors, it’s applications, contributing to global paper waste etc.)</blockquote><p>—</p><h4>2nd layer — Setting up the skeleton:</h4><p>This is where you would want to just list out phrases of anything you can possibly write about in each content theme.</p><blockquote>Continuing our example of sticky note, let’s break down one theme: types of sticky notes. Don’t spend too much time overthinking and just pen down whatever comes to your mind at this point. Types can be shapes they’re manufactured in, or countries where it’s produced. It can even talk about physical attributes of sticky notes. This can cover paper quality, color, dimensions, their stickiness, etc.</blockquote><blockquote>You can take a different tangent and continue to talk about its variance of application.</blockquote><p>—</p><h4>3rd layer — Filling in the mass</h4><p>This layer is all about forming single sentences on what you wrote in the previous layer. Again, don’t overcomplicate it, just write simple, easy sentences.</p><blockquote>In our examples of the type of sticky notes, a few sentences in this layer can be as simple as:</blockquote><blockquote>“Available in various colors, shapes, sizes and adhesive strengths.”</blockquote><blockquote>“As of 2019, they’re available in 26 documented colors.” <a href="https://en.wikipedia.org/wiki/Post-it_Note">(1)</a></blockquote><blockquote>“The most common stickies are paper-based yellow squares.”<br> <br>(Feel free to borrow from the internet but do share your sources to show you’ve done your research. I based the second above sentence based on a single search on Wikipedia. PLEASE always share sources.)</blockquote><p>—</p><h4>4th layer — Formulate paragraphs</h4><p>By now you’ve basically done the heavy lifting and possibly 80–90% of the work. The remainder’s all about connecting the dots. With the sentences, see if you can arrange them in a way where they look like a single block of content and have a sense of continuity.</p><blockquote>Our example of the types of sticky notes in a short paragraph would read something like this:</blockquote><blockquote>“The most common stickies are paper-based yellow squares. They are available in various colors, shapes, sizes and adhesive strengths. As of 2019, there are at least 26 documented colors of Sticky Notes.”</blockquote><p>—</p><h4>5th layer — Put it together</h4><p>Expanding on the previous layer, use the momentum to re-arrange the paragraphs to see if your content themes makes sense individually. Once all your content themes are complete, re-arrange them together and see if it still makes sense. Lastly, it always helps to have aim for a solid conclusion.</p><blockquote>In our stickies example, share your perspective. Do you like them? Do you find them a complete waste? Tell the world!</blockquote><p>—</p><h4>6th layer — Edit, edit, edit, and repeat!</h4><p>This is basically an optional step, but most of the writers you like and follow have gotten really good at this step. One of the biggest misconception is that you need to have good foundations in English before you start writing. I can promise you everyone starts with spelling mistakes and incorrect grammar.</p><blockquote>The internet is an amazing resource and there are so many amazing tools out there which can help. (I’m personally a fan of using <a href="http://hemingwayapp.com/">HemingwayApp</a> as a proofreader.)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U6Hfqxoa6NLHxn2f" /><figcaption>Photo by <a href="https://unsplash.com/@freegraphictoday?utm_source=medium&amp;utm_medium=referral">AbsolutVision</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Watch yourself get better!</h4><p>Writing is an extremely undervalued ‘soft’ skill. It helps you become a much better communicator and helps you collaborate better. Just writing with the intention of sharing makes you better at whatever you want to achieve. The key is to keep practicing and sharing. I’ve found it to have compounding effects on how much I get to learn. For e.g. in this case, I learnt about sticky notes :)</p><p>Hope this mini guide helped, would love to get an insight on your perspective.</p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42d538fd7cd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A tale of side projects, translations UX, giving back, and a lot of messy problems to solve]]></title>
            <link>https://uxplanet.org/a-tale-of-side-projects-translations-ux-giving-back-and-a-lot-of-messy-problems-to-solve-145e2236bcb5?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/145e2236bcb5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[social-change]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[medicine]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Thu, 22 Jul 2021 12:39:41 GMT</pubDate>
            <atom:updated>2021-07-23T10:06:41.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rPpzXiZdMuOuuRyn" /><figcaption>Photo by <a href="https://unsplash.com/@nicnut?utm_source=medium&amp;utm_medium=referral">Nicola Nuttall</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’ve known me for a while, you would know my interest in side projects. I like helping out anyone who needs a hand, especially on anything focused on social change.</p><p>This article’s me trying to walk you through one such amazing experience. It’s also a peek into the frustrations and the mistakes I made and reflections on how to do some of these things better.</p><p>☕ <em>P.S. This one’s going to be a long read, would recommend you grab a cup of chai/ coffee. ️</em></p><h3>How it all started</h3><p>Around a year ago, I saw a post in one of the many design groups I am part of on Facebook. It sounded like the person was working on a fascinating problem. I felt could some spare time and I’d be okay with supporting them. (Regardless of whether or not I’ll be financially compensated for my time.)</p><figure><img alt="FB group screenshot of Bradley’s msg." src="https://cdn-images-1.medium.com/max/982/1*5Tv8NXB7Tbix4BoXbuYeag.png" /><figcaption>FB group screenshot. Link to original post <a href="https://www.facebook.com/groups/M5.2012/permalink/2493623880735253">here</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uf2uvn92dRJaBF0pwnUyiA.png" /><figcaption>Snippet from the DM after my ‘pitch’ , and Bradley being super kind (as usual) and me being persistent (as usual)</figcaption></figure><p>I reached out to Bradley with a quick intro (interestingly, within 20 minutes as the screenshot suggests.) My usual pitch involves a lot of description, and I expressed my interest in helping out for the project. She replied and I got to know a couple of others were already keen and had reached out.</p><p>It was good to see a solid problem getting the attention of many peers. However, I was also bummed out as I had never been exposed to this problem space so far in my career. The situation sounded very intriguing and I still remember a lot of the keywords used in the description. I wanted to help.</p><p>I acknowledged the wait, and as life would have it, was contacted again by Bradley. She was able to get a service designer but they still lacked visual design support, so I excitedly hopped along.</p><h3>TL;DR — The situation</h3><p>To avoid writing about the mundane play by play, I’ll summarize the whole journey in a couple of paragraphs to the best of my ability.</p><p><strong>The (messy) problem and context<br></strong>Migrant and indigenous communities in the west (Europe for the purposes of our project to be specific,) currently have a lot of problems in getting access to relevant healthcare. One major cause of that is a language barrier. Inability to communicate leads to a lot of wasted time and frustration at best, and incorrect treatment at worst (due to misdiagnosis.)</p><p>Currently, institutions attempt to mitigate this problem through in-house translators. Unfortunately these only cater to a minority of cases where the non-English speaker is speaking the ‘common non-local’ language. From the research we know there are less than about 10 languages which are sufficiently covered.</p><p>There are tech based solutions like Google Translate, which cover about forty languages, but unfortunately the quality of the translations for non-mainstream languages is questionable. In this context a bad translation can actually cause a lot of problems.</p><p><strong>Product<br></strong>This platform aims to build a database for translations in over 7,000+ different languages. These will be crowd-sourced through volunteers. In most cases, these will be medical students, in training, or doctors.</p><p>The end goal is to empower doctors and first level medical attendants. The translations from this tool will assist with diagnosis and and eventually treatment. This was a noble direction to pace towards. However, tech was just one of the many mystical creatures the team had to overcome in order for this to become a reality.</p><p><strong>Issues with what was done so far<br></strong>The project has been going on for a while. The current prototype had already been developed by a passionate team of developers. However, when it got through to the users, there were fundamental usability issues. Unfortunately, this meant that the project in its current state wasn’t good to release. The team was advised to get a ‘UX designer’ to support with the ‘User Experience.’ This is what led to the initiation by Bradley which you see above.</p><p><strong>Lack of awareness of how tech works<br></strong>Bradley and the team’s journey started with a problem to solve (the ‘what’,) without a lot of visibility on the ‘how’. Like any epic with countless obstacles, tech was a beast of its own. She is an academic by profession, and has a noble cause at heart. However, the dev and product side of things were something which was missing as it was an <a href="https://hbr.org/2017/10/simple-ways-to-spot-unknown-unknowns"><em>unknown unknown</em></a><em>. </em>This included things like platform security, web standards, engineering best practices. There was a need to understand how some product decisions may completely break as the platform would scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0nIiqoUl72PqQYTApPjsQ.png" /><figcaption>A glimpse of the initial analysis of the cards we were dealt with.</figcaption></figure><h3>Starting fresh with a blank slate</h3><p>Alright, so you have a bit of context of what all was happening. Now it’s time to shed some details on some of the things which we did when ‘UX’ was brought into the mix. Luckily, for a few weeks, we got the support of Rose*, a seasoned service designer. We worked together to debrief and gather everything we knew about the project. We got to work and probed ourselves to start asking some fundamental questions.</p><p>(*Full name hidden for privacy.)</p><p><strong>What were our objectives? What became our new objectives? <br></strong>The end goal of Twig was to become a volunteer driven platform which medical professionals could reference from. This would help with their day to day diagnosis and treatment . The objective remained the same, but I feel we broke the end goal into a series of micro tasks which helped us march in that direction. Our ‘new’ objectives intended to reduce the scope just enough for us to release something small. This had to be a good start, as it helps validates our hypothesis. In tech terms however, it wasn’t the traditional MVP.</p><p><strong>Who’s our user?<br></strong>Our platform is designed for anyone who can be categorized as a healthcare professional. However, in order to have better focus, we have narrow the focus to students who are towards the end of their professional education. It’s a platform driven by volunteer medical translations. According to the collective research we had gathered, they were best suited for the role. They were ambitious in terms of giving back, had the time and competence for it. More importantly, this could become part of the extra credit which can support with their overall education. It’s a win-win for everyone.</p><p><strong>What do we know about the problem so far?<br></strong>As mentioned earlier in the writeup, Twig went into development but didn’t see the light of day for long due to some core constraints. It was this realization which connected me to Bradley. She’s been working in this space for a while, and is very clear on the ‘Why.’ The scale and complication of the problem is clear. We know that there aren’t a lot of solutions currently and the existing ones are missing a lot of the fundamentals. These include basics like a coverage of languages, as well as more nuanced needs like the contextual translation of medical terms.</p><p><strong>What do we want to learn?<br></strong>With learning to unlearn as the foundation of what we’re doing, we wanted to continuously update our world views. We wanted to learn about our personas the best we can.</p><p>This includes the volunteer and what a day in their life looks like.</p><p>This includes the doctor and how they would eventually be using the translations in their day to day.</p><p>This includes the indigenous community who are eventually going to be recipients of the donated translations. It’s extremely important that they’re able to understand the content for all of this to work.</p><p>Lastly, this includes us, our team and all internal stakeholders working together to make this work and become something meaningful.</p><p><strong>What are the important questions we need to ask?<br></strong>We believe this will be a never ending list, but there are core questions for which we keep on seeking answers. These also help us update our own understanding of the situation. Some of the questions we keep on coming back to:<br>- What problem are we trying to solve for?<br>- Who are we doing this for? <br>- Why’s it important to do so right now? <br>- How will the user interpret this?<br>- Is there an alternative approach to doing this? Is it really important to do this in the manner suggested?<br>- How do we know this will work?<br>- How can we validate this? What feedback do we have?<br>- How does this happen currently? What other things are they used it?<br>- Where does this belong in the overall flow? How does it help the user in the grand scheme of things?<br>- Again, what problem are we ACTUALLY trying to solve?</p><p>On a glimpse, the nature of the questions is similar. We really want to understand the root cause of things, and evaluate the cost against the potential benefit from doing/ not doing something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVTEeVepInNl-SxHEgLzog.png" /><figcaption>Bird’s eye view of part of the (messy) workspace</figcaption></figure><h3>Collaboration, tooling, and the ‘design’ process</h3><p>Twig’s set a great example for teaching me why some popular ways to collaborate work well, and which ones need some revision. Just giving the team a high level overview on how tech generally works was followed by a bunch of ‘ah-ha’ moments. We tried to plan our phases and next steps. Introducing agendas in meetings was not just specific to tech, but we felt it really helped us work better and more efficiently. We were split across 3 locations and timezones, regions and cultures. Given limited/ no budgets, we obviously had a bias for free tools we were already accustomed to.</p><p>A summary of the tools we used to work together:<br><strong>- G Sheets </strong>— Found this one the most surprising. Generally served the purpose of what otherwise would be done on Miro. Helped us compile everything quickly and the tabular format ensured we keep it brief and factual.<br><strong>- GMail</strong> — Comms/ ‘official’ stuff. We didn’t opt to have a realtime platform like Slack because all of us were not really working on Twig all the time. Email was surprisingly an okay mode of communication which everyone was already used to. For times where more active communication was required, we’d jump on a quick call.<br><strong>- Figma</strong> — Mockups / ideation/ workspace/ sandbox. As always, helped me visualise things to present during meets and get the team to drop their feedback and comments as well.<br><strong>- Meets/ Zoom </strong>— General discussion, meeting, bottlenecks, walkthroughs. We had to switch to Zoom in some cases</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aU0aacChEorkfF0d" /><figcaption>Photo by CDC on Unsplash</figcaption></figure><h3>Learnings and reflection</h3><p>I’ve had this bias for offering a helping hand to those who do their fair share in expressing interest and seriousness in whatever they’re after. Besides the social impact, a great incentive for me has always been reflecting back on the process and learning new things. I’ve tried to list out a bunch of facts I have been reminded of, as a result of this journey, with more to come as time progresses, which I’ve categorized by theme.</p><p><strong>Tech, digital products, and processes:<br></strong>- A LOT becomes irrelevant and sounds stupid when you remove profits out of the picture. Naturally, that brings sustainability at risk, but that’s not the focus at this time.<br>-<strong> </strong>Not everyone who wants to build something meaningful has access to venture capitalists (or in fact even aware of their existence.)<br>- Working with PHDs and medical experts from academia is going to be world’s apart from the tech industry. The type of context required is very deep as compared to the counterpart in tech which we’re used to, in relative terms, of course.<br>- All industries create silos in order to emphasize and the appreciate the nuances. The sense of other-ing, however, magnifies as well. This becomes a problem during onboarding external stakeholders.</p><p><strong>Communication and collaboration:<br></strong>- Working on Twig made me wish I could speak a few more languages. The languages which we see on mainstream media is less than 1% of total languages spoken across the globe (7,000+ lanuages!) <a href="https://www.ethnologue.com/browse/names">View them here. </a><strong><br></strong>- Not everyone is familiar with how tech works and the cadences it brings along the way. <br>- Communication is key. Not only the act of communication, but also sharing knowledge and context where it’s otherwise missing. You’ll also have to keep coming back to the foundations.<br>- Have all major discussions in real time and on-call. Video calls make it even better. NOT LOOKING YOUR BEST IS OKAY.</p><p><strong>Design, values, and personal growth:<br></strong>- There is an unexplainable feeling of fulfilment which you get when you help someone and see their vision come alive.<br>- Figma is beyond a design tool. Working on Twig is where I’ve really stretched my understanding of Figma as a tool for facilitation. <br>- Communities across the globe can use all the help they can get to make the world a better place for them.<br>- G Sheets is a solid tool in terms of being easily accessible and enabling you to start something.<br>- It’s a surreal feeling to see something you create/ re-create from ground up, actually being used. First hand feedback from actual users and them appreciating it is a high on its own, and it’s addictive.<br>- Resisting pixel perfection is difficult, but necessary for understanding what truly solves the problem at-hand.<br>- A lot of folk outside of the tech space don’t have much information of the science behind good experiences. The onus is on us to proactively find such people and reach out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*1KnbhitSKdeOETfy" /><figcaption>The art for Twig’s Kickstarter campaign was created by the award winning graphic artist Bill Walsh at Wing Design: <a href="http://www.wingdesign.co.uk/">www.wingdesign.co.uk</a></figcaption></figure><h3>What’s next</h3><p>Development is still underway, and it’s still far from complete, but we’re making steady progress. We’re hoping to get more traction in terms of grants. These grants fund the project and support what Bradley and the team are up to!</p><p>If you’re an EU based organization which can support the team through a social development grant, feel free to get in touch with me or <a href="https://www.linkedin.com/in/daltonbradley/">Bradley</a>.</p><p>Visit our makeshift website <a href="https://twigcare.org/">here</a>. Get a summary of the action through the out-dated kickstart campaign <a href="https://www.kickstarter.com/projects/twigcare/build-a-medical-translation-wiki-for-migrants-and-refugees?ref=project_build">here</a>. View more details on the official chain of events on the about page <a href="https://twigcare.org/about-us">here</a>.</p><p>View Bradley’s peer-reviewed paper here:<br><a href="https://www.emerald.com/insight/content/doi/10.1108/IJHRH-01-2017-0004/full/html">https://www.emerald.com/insight/content/doi/10.1108/IJHRH-01-2017-0004/full/html</a></p><p>Major Kudos to <a href="https://www.linkedin.com/in/daltonbradley/">Bradley</a> for leading this, and giving me permission and feedback to publish this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=145e2236bcb5" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/a-tale-of-side-projects-translations-ux-giving-back-and-a-lot-of-messy-problems-to-solve-145e2236bcb5">A tale of side projects, translations UX, giving back, and a lot of messy problems to solve</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking your way into the local ‘product’ design scene — A cheatsheet]]></title>
            <link>https://uxplanet.org/hacking-your-way-into-the-local-product-design-scene-a-cheatsheet-9b4c9e2566fd?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b4c9e2566fd</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[learn]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Sat, 20 Mar 2021 20:11:26 GMT</pubDate>
            <atom:updated>2021-03-21T08:53:06.547Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hacking your way into the local ‘product’ design scene — A cheatsheet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tz7b7WHn_MeJ1P2W" /><figcaption>Photo by <a href="https://unsplash.com/@bamagal?utm_source=medium&amp;utm_medium=referral">&quot;My Life Through A Lens&quot;</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Over the past couple of quarters, it’s been great to see tech and the startup scene in Pakistan pick up pace. Even with a mutating virus not making our lives easier, we see a new wave of product based startups getting empowered via international investors and firms. More importantly, a lot more is happening and the pipeline seems to be thriving at a motivating trajectory.</p><p>Design, in parallel, is also playing catchup. Various folk are switching industries and their software design agencies to give product a chance and play a more closer/ deeper role with a single ‘client.’</p><p>In a similar light, this article is a list of reflections/ feedback based on the your existing situation and where you see yourself headed, with action items you might find helpful for your journey.</p><p>—</p><p><em>A lot of it won’t even be about design. It might not even have the right categorisation. Here goes…</em></p><h4>If you’re a student, exploring this space and aiming to learn more</h4><ul><li>Start searching and compiling a list of local startups. Learn more about the amazing products we have.</li><li>Research about problems you’re interested in. What are people across the globe doing to tackle it. See if anything’s happening locally.</li><li>Try to understand their business models. What works for them. How do they differentiate. What can you learn about them.</li><li>Learn about people. A startup can not survive for long without a team. Learn more about the founders. Get to know their early battles. Learn about culture and how they’ve scaled.</li><li>Lookup basic definitions of some of the buzzwords.</li><li>Read. Read. Read. Can’t emphasise this enough. This has been the differentiator for me personally, and a habit I wish I could have developed years ago.</li><li>Talk to people. Send that message. Act.</li></ul><h4>If you’re a junior designer trying to get the hang of product</h4><ul><li>Make sure you’ve covered the basics of design. This will help you put your best foot forward and get the right attention.</li><li>Showcase your work and have evidence that you are a do-er. Thinkers are great, but you need to build that case for design and the value you will provide. You are powerful and they need you. Remember that, but work for it to make it count.</li><li>Read the above pointers, but look at the best product design teams. Also read about different models. Lookup design leaders. Understand how design teams work. Learn how they are structured.</li><li>Premise of product companies and design needs to be around impact. Spend time understanding ways design delivers values. Start building your portfolio accordingly. You may have a lot of things already, it might be just about how you package it.</li><li>Learn the basics of tech, how do thing work. How does a business function. Watch a few episodes of Shark Tank / Dragon’s Den. Understand the format. Research into the new keywords you learn.</li><li>Tell your story. Learn how to share. Focus on communication skills as a muscle.</li><li>Personal branding is essential. Pitch yourself. Tell them how you’d deliver value as someone who is part of the product team.</li></ul><h4>If you’re a senior designer and seeking greener pastures</h4><ul><li>We need you to speak up. Your voice matters. The community would love to hear your advice and what you’ve learnt over the years.</li><li>Making the switch to product may seem difficult. Have an open mind.</li><li>Unlearn. Learn again. Repeat.</li><li>Figure out connections in product companies. Start approaching them. A simple conversation can turn into a collaboration within a few messages. It can even turn into a role in a few more messages.</li><li>Seek your allies. There might be people who are non-designers but do appreciate good design. Partner with them. Explore the space together. Learn from each other’s weaknesses. Help yourself by helping them. Keep sharing.</li><li>Collaborate.</li><li>Your portfolio possibly needs a bit of rework. Lookup case studies and experiment with projects. As you get senior, recruiters will expect projects where you will have to prove the value you’ve created by the work you’ve done.</li><li>If you don’t have anything solid. Work with non designers to create something from scratch. Doesn’t have to be profitable. You need to live the product journey and instances of it.</li><li>Keep at it. You’ll get there. It’s a small world, and an even smaller community. Reach out to people starting out or early teams.</li><li>Read. Understand the concept of Zero to One. Learn business.</li><li>Focus.</li></ul><h4>If you’re a non designer but would like to represent design in your org</h4><ul><li>You are amazing.</li><li>Research product teams and where design fits in. Understand the touch points where you need to build the case.</li><li>Preach. You are our interpreter for the rest of the org.</li><li>Start things off with small projects. It will not happen overnight.</li><li>Please be a bit patient with us. We’ve not been used to collaboration as a default.</li><li>Work on projects together with us. Doesn’t have to be about work.</li><li>Trust us.</li><li>Treat us as partners. Good designers will genuinely prove their value without you even asking for it.</li><li>Talk about problems, and focus less on solutions. We’ll get to those eventually.</li><li>We’ll do it together.</li></ul><h4>If you’re working on a startup and/ or plan to set one up</h4><ul><li>You’re a rare breed. Not a lot of people have the guts you have.</li><li>The earlier you get a designer’s lens on the figurative table, the sooner you’ll see the value of design.</li><li>We love prototypes. Collaborate with a designer. We can help you visualise your ideas.</li><li>It doesn’t have to be someone with the label of a designer. It’s the mindset of being user-problem focused.</li><li>“Org Design for Design Orgs” is an amazing read if you want a playbook.</li><li>Please think of us as problem solvers, and let us prove we’re more than pixel pushers.</li><li>You’ll probably have to do all of the above, and more.</li><li>Ask for help, there are amazing people out there. Reach out.</li><li>I’m cheering for you!</li></ul><p>—</p><p>Fostering and actively engaging in the local design scene should be everyone’s responsibility. It’s a steep journey to the top, and we will need all the help we can get.</p><p>I’m sure I may have missed something, and would love to get feedback. For any queries, feedback or even a casual chat, feel free to reach out. Let’s get started.</p><p>That’s all for now, until next time. <br>Happy hacking!</p><p>🔥</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b4c9e2566fd" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/hacking-your-way-into-the-local-product-design-scene-a-cheatsheet-9b4c9e2566fd">Hacking your way into the local ‘product’ design scene — A cheatsheet</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key reflections from my ~5 year journey at Careem]]></title>
            <link>https://uxplanet.org/key-reflections-from-my-5-year-journey-at-careem-b81319648458?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/b81319648458</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 20:17:04 GMT</pubDate>
            <atom:updated>2020-11-15T09:19:55.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Zoomed in view of reflective water droplets on an opaque surface." src="https://cdn-images-1.medium.com/max/1024/0*x79ceaW02VHfhK38" /><figcaption>Photo by <a href="https://unsplash.com/@devano23?utm_source=medium&amp;utm_medium=referral">Devon Janse van Rensburg</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This post is going to be a rapid-fire writeup of a <em>few</em> significant reflections and takeaways from an almost five year long journey at <a href="https://www.menabytes.com/careem-super-app/">Careem</a>.</p><p>Maybe each pointer below eventually becomes an article probe on their own.</p><p>Who knows.</p><ul><li><strong>Become more outcome focused as opposed to output focused<br></strong>For those who may not know, I was actually part of a <a href="https://www.techjuice.pk/careem-acquires-a-chunk-of-venturedive-in-a-hefty-deal/">aqui-hire</a> move when I shifted to Careem in Mid 2016. The core ‘pitch’ given to me was that as part of a product team you grow as the product grows. Living through product life cycles, you get to own the impact of the products you design. This is close to non-existent if you work in an agency setting as its mostly output/ deliverable focused.</li><li><strong>A pair working together is much more than just 2 people<br></strong>When you work in a pair, you’re learning, sharing and growing at twice the rate. You’re each other’s critic and confidant. Be it another designer or anyone from any other team really. As long as you’re working towards a unified goal, working as a pair will always be a great utilization of your times.</li><li><strong>Leadership matters</strong><br>This eventually is the deal breaker, view it from any lens you deem fit. A solid leader will rally you and your peers where you would happily dash the extra mile. Their behaviors will inspire you and make you want to replicate their ways of working. The opposite however, is true too. If things go south, there will be similar repercussions, at scale.</li><li><strong>Defining your own work life matters<br></strong>The whole mindset of the 9 to 5/ 10 to 6 needs a revamp and we are past the age of the timestamp. As long you and the team delivers on mutually decides goals, or at least makes steady progress towards it. It’s going to be alright. Another way to interpret this; in order to achieve significant results, you’d have to put in a significant amount of not long, but smart hours.</li><li><strong>Culture is everything<br></strong>Similar to the point around leadership, culture’s a very close second. You want to be in an environment where you’re uplifted, challenged and provided with the ownership to take things to the finish line. With peers who go beyond the call of duty for you when required, there’s nothing stopping you and your peers from being the best versions of yourself.</li><li><strong>The obsession to seek order in chaos<br></strong>Plans are just bunch of decisions, a few words/ phrases, typed/ printed on a shared space with leaders aligned to it. However, the reality will rarely meet your expectations. The key’s to be comfortable with the unknown and preparing for a course of action as soon as things don’t go according to plans. It’s an essential skill to be able to be comfortable with the uncomfortable, and navigate those grays with confidence.</li><li><strong>There’s always going to be a downside, but there’s always going to be an upside too</strong><br>Continuing the above point on uncertainty. Things are likely to go south in your personal or professional journey, but there will ALWAYS be something you can hold on to, no exceptions. If you don’t find it, you’re probably not looking at the right places. It’s a blindspot, hiding in plain sight. Often, the silver lining may not present itself, but in the long run you’d almost always be able to connect the dots.</li><li><strong>Communication is key<br></strong>One of the most marketed yet under estimated life skills to be able to articulate your points well. It’s been preached by millions of people by now, yet it doesn’t feel it’s said enough. it’s vital to have the ability to share your thoughts. Be it your team, your peer or just for yourself, communication helps you navigates your thoughts and differentiates the good from the great. If you plug this into your habits, a conversation will snowball and get your the right leads/ breaks you were looking for.</li><li><strong>Design’s a team sport<br></strong>I had this preconceived notion a few years back that design is a thing you do alone and there’s an end goal to it. Design is never <em>done. </em>There’s always going to be a better version. You need to work together to reach that milestone. Its not about the destination, but the journey you and your team will explore together. The iterations and feedback you go work upon as a team is what builds the product, not a bunch of pixels on an interface.</li><li><strong>Growth is all about processes<br></strong>The greatest sign that you’re growing as an individual is to make yourself redundant. A lot of books touch upon this subject in great details. A decent process will not only make room for you to do more things better, but also create a stretch opportunity for others to own and lead. Amazing read on letting go, <a href="https://firstround.com/review/give-away-your-legos-and-other-commandments-for-scaling-startups/"><em>here</em></a><em>.</em></li><li><strong>Dissolve the labels you’ve been tagged with<br></strong>Personally find this a pet peeve of mine. Titles do hold some value but for sure they’re not as important as we claim them to be. You should feel empowered to be curious and enabled, end of story. If you feel that you want to try out visual design to share your thoughts, do it. Want to take a stab at coding a business proposal? Do it. Want to learn more about sales as a researcher? Don’t see a reason why you shouldn’t explore.</li><li><strong>You’re as busy as the free time you have<br></strong>You can choose to get free at 5pm and end your workday. You can choose to block 30 mins daily to read a book. You can take a longer lunch break to call a friend or meet them as its been quite a while ago since you last had a decent conversation. You can choose to spend a few extra hours to push a pending project to the next level. You can stay busy and not do any of the above.</li></ul><p>Here’s to experimenting some more, and learning from the mistakes to come. Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b81319648458" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/key-reflections-from-my-5-year-journey-at-careem-b81319648458">Key reflections from my ~5 year journey at Careem</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a roadmap for myself]]></title>
            <link>https://uxplanet.org/building-a-roadmap-for-myself-b55205b803a3?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/b55205b803a3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[self]]></category>
            <category><![CDATA[improvement]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Tue, 26 May 2020 14:29:06 GMT</pubDate>
            <atom:updated>2020-05-28T20:37:34.853Z</atom:updated>
            <content:encoded><![CDATA[<p>Using Figma for an exercise to bring myself some clarity on what will keep me occupied for the next few months.</p><figure><img alt="Screenshot of the template with quick pointers describing the sections" src="https://cdn-images-1.medium.com/max/1024/1*67JzNeoRFhXFeRXXlNXQcw.png" /></figure><h3>The issue</h3><p>Over a year ago, there were a lot of changes happening at work and us being a small team, had our hands full. I personally faced the following:</p><ul><li>Not being able to focus and prioritise my time well</li><li>Losing track of competing deadlines</li><li>Too occupied with the day to day deliverables to focus and calibrate my personal goals</li><li>Stakeholders were lost as they didn’t have full context on what’s on my plate to support them</li></ul><h4>Building a roadmap</h4><p>Roadmaps are not something new. Every team and individual has it in some shape or form. A lot of project management tools can solve most of the issues mentioned above. In fact, many teams use Google sheets because of its ease of use for making gantt charts.</p><p>These tools just didn’t work for me. Be it the traditional pen/ paper or software alternatives. They were too restrictive to maintain at an individual level. In case of digital solutions, they were adding a couple of added layers of complexity.</p><figure><img alt="A skeleton of a table which shows calendar months in columns and project placeholders as rows." src="https://cdn-images-1.medium.com/max/1024/1*J_Hw0l7ANGTl0rG7-IehvA.png" /><figcaption>Initial versions of the roadmap. Something didn’t click</figcaption></figure><h3>The experiment</h3><p>I decided to make a simple roadmap of my own. Since my go-to design tool was Figma, I decided to create one within my workspace. Figma had <a href="https://www.figma.com/templates/gantt-chart/">a template available</a>, but it didn’t serve my purpose.</p><p>I took inspiration from different tools and fused them within Figma to keep it flexible. Another advantage for Figma was its<em> ‘default to open’ </em>approach to design in general. Being web based made it easier to share with others for feedback. It also avoided extra effort of logins/ learning new tools. However, you can do something similar on other tools as well. (Sketch/ XD/ Illustrator/ Google sheets etc.)</p><p>It started off being pretty simple. Time progressing left to right as columns. Rows being the individual projects themselves. I initially thought of a few colors to highlight my focus for that time period.</p><figure><img alt="Image of the cheatsheet of the color representations." src="https://cdn-images-1.medium.com/max/1024/1*5CZYF3fbWHXawusO6kYtew.png" /><figcaption>Cheatsheet — Legend of what each color may represent.</figcaption></figure><h4>Where it got interesting…</h4><p>Sometime mid last year, I was introduced to a few management frameworks. They looked pretty useful and relevant. So, I decided to add them to the roadmap. Surprisingly, these were great additions! They added a good layer of details along the roadmap. Will describe them briefly below:</p><p><strong>Assumptions: </strong>What are some factors you’ve considered while you made this roadmap? Add them. It’s always good to mention assumptions. These can be around team dynamics, your workload and team budgets etc.</p><p><strong>North star: </strong>The buzzword you’ve all possibly heard a lot of times by now. Take a moment to add what is something which you’d love to do more of. How would you like to best utilise your time? In my case this was the part which helped me emphasise my personal goals and how teams could help.</p><p><strong>Risks: </strong>Clearly highlight the concerns with the current roadmap which you see. Do you clearly see there’s too much on your plate? Any approvals / pieces of the process really holding you back from doing your best?</p><p><strong>Help request: </strong>Keep it real and clearly write down what do you need to do the best you can. If it’s some buffer space for personal projects, write it down. If it’s budget for a new tool, pen it down.</p><p><strong>Team breakdown: </strong>For you to always have an idea of team breakdown/ peer to design ratios. No other purpose but found this context useful for discussions.</p><figure><img alt="Image of the gameplan from last year — Describing a roadmap which is partially complete with focus and non focus items." src="https://cdn-images-1.medium.com/max/1024/1*pr3ezoLeLuSCLfQftH-eUQ.png" /><figcaption>One of drafts from mid year last year</figcaption></figure><h3>Reflections</h3><p>This exercise works because of its simplicity.</p><p>It comes in handy when I’m welcoming a new member to the team. This visual becomes important especially when I want to escalate something to leadership. With the right context, it enables me to ask for help and provide the right amount of visibility.</p><blockquote>You’re doing this for yourself, please keep that in mind!</blockquote><h4>Pro-tips:</h4><ul><li>Don’t worry too much about it. This is a self-awareness exercise. Change things whenever you like. Stop doing it if it’s not useful for you.</li><li>After every couple of months, make a duplicate of the artboard and make the changes. See if you spot any patterns emerging around your priorities.</li><li>Don’t review it too often. Don’t view/ make changes more than twice a month.</li><li>Keep in mind the more micro tasks you add the more of a burden maintaining this will become.</li></ul><figure><img alt="Image with examples of tasks to keep items on a category level and not on a micro level" src="https://cdn-images-1.medium.com/max/1024/1*OUGzKwPPB453qTqFePiF8A.png" /><figcaption>Avoid adding micro tasks. Keep it at category level and use grouping for context.</figcaption></figure><p>Let’s take an example. You’re building an app and it’s due in 6 months. Don’t write “Design home screen UI” as a task. Instead, bucket them together as “Conceptualise navigation,” or “Complete sign up flow.”</p><figure><img alt="Screenshot of the template with quick pointers describing the sections" src="https://cdn-images-1.medium.com/max/1024/1*67JzNeoRFhXFeRXXlNXQcw.png" /><figcaption>Preview of the template (<a href="https://www.figma.com/file/YI5DUKPpbzdtzPXcrMVgX9/Personal-roadmap-Template?node-id=2%3A9">link to file)</a></figcaption></figure><h3>Get started with this freebie!</h3><p>Thanks for reading. I’ve prepared <a href="https://www.figma.com/file/YI5DUKPpbzdtzPXcrMVgX9/Personal-roadmap-Template?node-id=2%3A9">this Figma template</a> incase you’d like to give this a shot. I’d love to know if you have any other hacks which you’ve come-up to manage yourself.</p><p><a href="https://www.figma.com/file/YI5DUKPpbzdtzPXcrMVgX9/Personal-roadmap-Template?node-id=2%3A9">Link to template.</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href">https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b55205b803a3" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/building-a-roadmap-for-myself-b55205b803a3">Building a roadmap for myself</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designers — Stop blaming your introvert self]]></title>
            <link>https://uxplanet.org/designers-stop-blaming-your-introvert-self-f64eb6a279fd?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/f64eb6a279fd</guid>
            <category><![CDATA[life-hacking]]></category>
            <category><![CDATA[self-development]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Mon, 18 May 2020 20:10:36 GMT</pubDate>
            <atom:updated>2021-07-26T07:34:10.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo of a speech bubble image made with paper" src="https://cdn-images-1.medium.com/max/1024/0*xVyvvLVeJl52B8pa" /><figcaption>Photo by <a href="https://unsplash.com/@lunarts?utm_source=medium&amp;utm_medium=referral">Volodymyr Hryshchenko</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Designers — Stop blaming your introvert self</h3><p>A collection of actionable tips to flex your extrovert muscles.</p><h3>Another generic human behavior article?</h3><p>A good chunk of the internet is filled with content recommending tips and advice for people to become more extroverted (and vice versa.) If you‘re unfamiliar on the subject, go through resources available online. Some examples can be found <a href="https://www.quora.com/How-can-I-be-an-extrovert">here</a>, <a href="https://www.youtube.com/watch?v=aOFikJDdFwk">here</a>, <a href="https://www.business.com/articles/15-tips-to-become-an-extrovert/">here</a>, <a href="https://socialpronow.com/blog/introverts-becoming-extroverted/">here</a>, <a href="https://www.wikihow.com/Go-from-Introvert-to-Extrovert">here</a>, <a href="https://www.jobsite.co.uk/worklife/introvert-extrovert-6-simple-steps-10412/">here</a>, <a href="https://hbr.org/2016/05/learn-to-love-networking">here</a> and <a href="https://www.wikihow.com/Be-an-Extrovert">here</a>. Get a good list of books <a href="https://socialpronow.com/blog/5-best-books-introvert-reading/">here</a> as well.</p><p>I’ve watched this amazing TED Talk a bunch of times, and I’d recommend you view it as well. She talks about some root causes of this issue and elaborates the divide it creates which we all can relate to.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fc0KYU2j0TM4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dc0KYU2j0TM4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fc0KYU2j0TM4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e5997c31e0583596ed8b255b21ab6ba/href">https://medium.com/media/5e5997c31e0583596ed8b255b21ab6ba/href</a></iframe><h3>Okay that’s all great, but why are you writing this article then?</h3><p>Great question. Within the design fraternity, (at least in Pakistan,) there seems to be a strong categorisation bias coming into effect between introverts and extroverts. Stereotypes are becoming the norm without enough discussion on the fruitful attributes of both. This needs to be addressed at all levels and one way to do that is to discover these traits and use them to your advantage.</p><figure><img alt="Comic strip commenting on ‘stay at home’ attributes of introverts." src="https://cdn-images-1.medium.com/max/740/0*09K7aa2PkAN9a7p2" /><figcaption>Still find this relate-able! Source:<a href="https://www.sinfest.net/view.php?date=2013-10-14">https://www.sinfest.net/view.php?date=2013-10-14</a></figcaption></figure><h4><strong>What’s the harm? I’m very happy the way I am!</strong></h4><p>It’s great that you’re a kick-ass designer who can do deep work in solitude and are very happy working isolated from everyone else. Keep in mind that without these extroverted attributes you risk the following:</p><ul><li>Any group activity (i.e. most of your career/ work life) needs you to have charisma to represent your thoughts at the right moments. You may be able avoid that early in your career, but will feel impeded if you aspire to become a leader one day.</li><li>If you want to help others and share your knowledge/ wisdom, you’d have to broaden your network and get in touch with multiple members of the fraternity.</li><li>If you want to initiate your own thing, you’d have to talk to people and figure out the right connections to make. Forming organic relationships can only happen if you’re doing it right and often.</li><li>Great designers are amazing facilitators. Complex problem solving is a team sport. You need to be able to drive conversations and introverts won’t naturally have this capability or strive for it.</li></ul><blockquote>This is a DIY guide (at best), you’ll have to put in the effort.</blockquote><h4>Fair points, but how’s this article different from the content mentioned in the intro?</h4><p>One of the problems I felt was that even with so much being written and said, there’s a lack of actionable take-aways which can help someone get started. Thats where this article is intended to support. Even though I’ll be writing from the shoes of a designer, a lot of these equally apply to others as well.</p><figure><img alt="Photo of a pair of gym shoes and dumbbells." src="https://cdn-images-1.medium.com/max/1024/0*NZu7dnZKDBEEFPis" /><figcaption>Lace up! Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Getting to work!</h3><p>The good news is that you already have an extrovert within. You simply need to train. I personally try to put these into practice wherever I can. As a rule of thumb, if it’s making you uncomfortable, you’re progressing in the right direction.</p><p>You can start with these, but eventually you’d notice that some things naturally suit your personality more. I’ve tried to loosely plug the actions into themes but they can easily spillover each other as well based on your situation. A lot of these tips will also help you with design research, conducting critiques and user testing as well!</p><blockquote>You can only improve if you recognise it as a shortcoming.</blockquote><h4>Mindset shift</h4><ul><li>Stop saying “It’s not meant for me as i’m an introvert.” It just triggers <a href="https://en.wikipedia.org/wiki/Confirmation_bias">confirmation bias</a>. A lot of the research indicates that no one is only an introvert or an extrovert (we’re all some combination of ambiverts). It’s okay for you to be an introvert but still like to talk to people.</li><li>Be patient. It will require steady and deliberate practice. Just like you can’t do 200kg on the bench on your first day at the gym. Use some of the probes from the list below.</li></ul><blockquote>“We are kept from our goals not by obstacles, but by a clear path to a lesser goal.” — Robert Brault</blockquote><h4>When at work</h4><ul><li>Talk to a new co-worker everyday, small talk is fine. Ask them their thoughts of what design means. Ask them what they do. Pick questions from <a href="https://www.themuse.com/advice/48-questions-thatll-make-awkward-small-talk-so-much-easier">this list</a> to begin with if you need more inspiration.</li><li>Practice <a href="https://www.syntaxis.com/your-voice-during-a-presentation">vocal variety </a>during presentations to hook the audience. Be okay with behaving differently in different settings. Laughing during casual conversations and even breaking for a picture is fine.</li><li>When sharing designs with stakeholders, see if you can get them on a call and use this time to get to know them at a personal level and then proceed with the agenda. Just an additional 5 minutes can really help you understand each other better.</li><li>During breaks: Form a habit of catching up with a peer. Borrow 15 min of a colleagues time. Book it on their calendar as a 1:1 if you’re a bit formal. If not, simply grab a cup of chai/ coffee together.</li><li>Talk about food at work. Food’s naturally something which unites most of us! Offer to ask an unknown peer if they’d like to order the same thing which you’re having for lunch. Form multiple lunch club!</li><li>Don’t eat alone. Don’t also have lunch with the same people all the time. Use this time to randomly tag along another <em>loner</em> like yourself.</li></ul><figure><img alt="Top down photo of two people having black coffee" src="https://cdn-images-1.medium.com/max/1024/0*LKA7NnMlUoBqc_-f" /><figcaption>Do you like black coffee? Lemme know! Photo by <a href="https://unsplash.com/@theexplorerdad?utm_source=medium&amp;utm_medium=referral">Joshua Ness</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>During a conversation</h4><ul><li>Start early and begin a chat with <em>icebreakers</em>. Ask the person how they like their coffee. Are they morning people or night owls. A lot of other great recommendations in <a href="https://museumhack.com/list-icebreakers-questions/">this list</a>.</li><li>Pay attention when others are speaking, really listen. Question their thought process not to interrogate them but to genuinely learn how they approach things.</li><li>Ask them about what they’re up to these days, what are their interests etc. what’s their past time, their favourite music etc. Again, pick questions from <a href="https://www.themuse.com/advice/48-questions-thatll-make-awkward-small-talk-so-much-easier">this list</a> if you’re stuck.</li><li>Ask open ended questions. Be curious to understand them. Reflections from the past often are the easiest ones to begin with. Pick a few from <a href="https://conversationstartersworld.com/open-ended-questions/">this list</a> if you can’t think of other questions.</li><li>Be vulnerable. Openly share something you wouldn’t share otherwise. Ensure you make it relatable to the your conversation. Sharing about yourself is key if you expect others to get to know you better and do the same.</li></ul><figure><img alt="Photo of a random person posing as a note-taker" src="https://cdn-images-1.medium.com/max/1024/0*XW9VcZ-L4MQiKqsg" /><figcaption>Take a note of all the things you need to communicate — Photo by <a href="https://unsplash.com/@gabriellehenderson?utm_source=medium&amp;utm_medium=referral">Gabrielle Henderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>In your free time</h4><ul><li>Call over a friend for lunch or meet someone for lunch or coffee. 30 mins is fine. Commute to them, they’ll appreciate the effort even if they don’t express it.</li><li>Improve your body language. Practice non verbal cues / power poses. They’re natural confidence boosters. Read more <a href="https://blog.ted.com/10-examples-of-how-power-posing-can-work-to-boost-your-confidence/">here</a> or watch this great talk <a href="https://www.ted.com/talks/amy_cuddy_your_body_language_may_shape_who_you_are">here</a>.</li><li>See if you can join speaking groups or weekend fraternity groups which offer you a platform. Toastmasters is one org which does this really well and does it in a structured fashion, but it’s very specific to public speaking and not everyone’s cup of tea. However, you can simply gather a group of friends and their friends to discuss a topic of interest and knowledge share. Get a few people interested and then start a Meetup session. Sky’s the limit.</li></ul><blockquote>Socialise based on your interest, it’s fine if at first you don’t meet complete strangers. You got this.</blockquote><ul><li>Make it a point to meet people around you. I’ve personally kept a goal of meeting 2–3 new folk every month or at least reconnect with a bunch of old ones. Again, the idea is not to force anything but naturally build this momentum. Start with a simple phone call or a chat :)!</li><li>Attend events partially, request early leaves. Have an escape plan. Tag with an extrovert friend, explicitly tell them to intro you to strangers. They’d be thrilled to do so and you’ll meet amazing people.</li><li>Volunteer. Help people out without the expectation of getting anything in return. Working towards a cause masks your comfort zone and opens new doors for collaboration.</li></ul><figure><img alt="Photo of a person in cafe at sitting at the last row" src="https://cdn-images-1.medium.com/max/1024/0*z2xQwWX7Q5kLXdEu" /><figcaption>It’s fine to take the backseat like this dude — Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>On the internet</h4><ul><li>Search for the slack communities which may interest you. Join them. I can be found relatively active <a href="https://thedesignership.com/">here</a>. There are SO MANY amazing communities for designers, developers and more. Pick a few from <a href="https://uxdesign.cc/the-best-slack-groups-for-ux-designers-25c621673d9c">this list</a>.</li><li>Search for useful Facebook groups which may interest you. Contribute in these groups. For design, a few of the ones i’m trying to follow closely are <a href="https://www.facebook.com/groups/UXDesignInPakistan">this one</a> and <a href="https://www.facebook.com/groups/M5.2012">this one</a>. A lot of other recommendations <a href="https://cgfrog.com/most-active-facebook-groups-for-designers/">here</a>.</li><li>If you’re already part of them, message. Don’t be a silent observer, don’t give in to the perception of others. Imagine you representing an entity, you’d have to do it someday, so might as well begin now. You don’t have to just give feedback, you can also request feedback and advice. It’s a two-way stream.</li><li>Given COVID-19 it’s more relevant than break physical boundaries and make meaningful connections remotely.</li><li>Take a look at amazing work other folk have done. Read their blogs. Subscribe to their newsletters. If you found it useful, see if you can reach out to them and say so.</li></ul><figure><img alt="“Choose your words” made with Scrabble blocks" src="https://cdn-images-1.medium.com/max/1024/0*qQv2iWaq2S3uLFIr" /><figcaption>You’d have to do it cuz the Scrabble blocks said it now! — Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>That’s a lot… where do I begin?</h3><p>As I promised, my intention is to support you with as many micro steps as I can possibly can. Do the following as you read through.</p><ul><li>Login to your Twitter account</li><li>Go to <a href="https://twitter.com/Arsalan__">my profile</a></li><li>Tap on the message icon/ send me a DM</li><li>Share with me a one liner of an intro, what you found useful in this article, and what do you plan to start with.</li></ul><p>Do it. Right now. This is as simple as it can get.</p><p>I would really like to get your thoughts and feedback on the practicality of this article. I’ve tried to make sure the recommendations are bite sized with enough room for exploration. Feel free to let me know if it didn’t work out that way. Would be happy to iterate and improve.</p><p>Thanks for reading, hope to see you flex those extrovert muscles soon!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href">https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f64eb6a279fd" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/designers-stop-blaming-your-introvert-self-f64eb6a279fd">Designers — Stop blaming your introvert self</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All you need to know about creating robust design docs]]></title>
            <link>https://marsalank.medium.com/all-you-need-to-know-about-creating-robust-design-docs-e633c740b4ad?source=rss-742c6d0f1f38------2</link>
            <guid isPermaLink="false">https://medium.com/p/e633c740b4ad</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Arsalan Khatri]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 12:36:03 GMT</pubDate>
            <atom:updated>2020-04-28T12:36:03.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Image of a pencil on a notebook." src="https://cdn-images-1.medium.com/max/1024/0*GO90laHodpTAkOo6" /><figcaption>Photo by <a href="https://unsplash.com/@honza_kahanek?utm_source=medium&amp;utm_medium=referral">Jan Kahánek</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>This article is an offline write-up for a remote masterclass I conducted for</em><a href="http://2020.uxpakistan.com/"><em> UX Pakistan</em></a><em>. If you feel this is something you and your team can really benefit from, feel free to reach out and let’s collaborate.</em></p><figure><img alt="List of speakers and names of workshops. For full list please visit 2020.uxpakistan.com" src="https://cdn-images-1.medium.com/max/1024/1*yfyO-7kOy7Dl398MYyAnng.jpeg" /><figcaption>TL;DR of the event itself — Kudos to the student team for pulling this spectacle off!</figcaption></figure><p>Design documentation (a.k.a design docs) has been something which I strongly feel is not talked about enough within the design space. This is an attempt to create a design doc to document how to create a design doc <em>(I know… this is very meta.)</em></p><blockquote><strong>Important note:</strong></blockquote><blockquote>While researching on the topic, I came across a lot of content around written case studies for individual projects. While there is some overlap between these topics, I would highly recommend you don’t read this write-up with that expectation.</blockquote><blockquote>This is primarily targeted for anyone who’d like to keep track of their thoughts and process. This is not necessarily for your portfolio (but can be packaged to do so.)</blockquote><blockquote>There’s a lot of material available on case studies documents. I personally love this essay (linked below) which I highly recommend you at least skim through and see if that’s more relevant to what you were looking for.</blockquote><p><a href="https://essays.uxdesign.cc/case-study-factory/">The case study factory</a></p><p>Anyways, coming back to creating a design doc, let’s get started.</p><h3>Purpose</h3><p>While working with different teams to create products and services, I always felt a LOT of context slipping through the cracks. There wasn’t single source of truth. As a consequence, it was highly likely that some aspect got overlooked in the final deliverable.</p><blockquote>“The purpose of design docs is to record how you got to a possible solution.”</blockquote><h4><strong>Wait… documentation in design?!</strong></h4><p>If you search google for the terms design and documentation individually, these are what you received as results:</p><figure><img alt="Definitions of “design” and “documentation” on Google" src="https://cdn-images-1.medium.com/max/1024/1*nI0n3h9gEwCfXuiASBGwPg.png" /><figcaption>This is what searching these terms individual return (Source: Google)</figcaption></figure><p>Based on the definitions you saw above, the simplest way to understand the purpose of design docs is to <em>record how you got to a possible solution</em>. This is a general definition, which can swiftly be tailored to the needs of your projects.</p><h4><strong>But… why would I need to document this journey?</strong></h4><p>Good question, I highly recommend to utilise this as <em>a powerful tool to gather your thoughts</em> in a single space. This will improve the way you work, and in parallel help you become a much better team player. I’ve also broadly used it for various other reasons, some of the major ones being to:</p><ul><li>act as a living document to align stakeholders</li><li>document key decisions</li><li>share progress with broader leadership</li><li>document the project as a case study for future reference</li><li>create a single source of truth of updated (design) decisions</li><li>improve collaboration amongst your (cross functional) team</li></ul><p>… and the list goes on. As some of these may suggest, there is no ‘right time’ to begin documentation. The sooner you begin, the better.</p><h4>Okay, i’m interested. How do I begin?</h4><p>Don’t worry, the rest of this write-up will enable you to create a doc on your own and attempt to break it down to keep it focused on the core elements.</p><figure><img alt="A screenshot of the participants from the remote masterclass" src="https://cdn-images-1.medium.com/max/1024/1*2HMG2fI2g2EVNoKiT3cjmw.png" /><figcaption>A snapshot from the remote masterclass</figcaption></figure><p><em>Note: This part of the masterclass was very tightly coupled. The crux of the exercises were wrapped up within an hour and leaving the rest of the time for reflections + questions.</em></p><p><em>There were ~11 participants so we made 3 teams and they collaborated amongst themselves to get this done. The audience was a mix of designers + developers + business folks.</em></p><figure><img alt="A woman taking notes and discussing them with a coworker" src="https://cdn-images-1.medium.com/max/1024/0*DlQKRlYbcsEp1wEy" /><figcaption>Photo by <a href="https://unsplash.com/@sarah_elizabeth?utm_source=medium&amp;utm_medium=referral">Sarah Shaffer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Phase 0 — Prelude: An ‘extremely realistic’ situation</h3><p>Let’s imagine that you and your friends are part of team which creates digital products and services for a living. Your best friend’s uncle’s neighbour knows your team and gets you a project.</p><p>The scope is to redesign a mobile app. Introducing the latest startup to takeover the messenger space; <strong>YOLO Messenger!</strong></p><p><em>Disclaimer: For the purpose of the masterclass, I created YOLO Messenger. I created this fictional app to give participants a problem space they are familiar with. I put a lot of effort to ensure it looks really out of place.</em></p><figure><img alt="Actual slide from the masterclass slide-deck describing YOLO messenger" src="https://cdn-images-1.medium.com/max/1024/1*BmjQMyTA54KRWnKn8CMG0Q.png" /><figcaption>Actual slide from my masterclass slide-deck</figcaption></figure><h4><strong>Expectations from your team:</strong></h4><ul><li>Evaluate the current app</li><li>Quick competitor research</li><li>Compile feedback</li><li>Redesign their UI</li><li>Recommend next steps</li></ul><blockquote><strong>Side note:</strong></blockquote><blockquote>The expectation for the masterclass was to not spend too much time the specifics of the redesign. The teams had to go through these phases and collaborate their way to create their own documents.</blockquote><p>I experimented with creating a sandbox on <a href="https://medium.com/u/bf1152b11387">Figma</a> to get everyone onboard. We used a few tailored components to really collaborate and track key information almost like a virtual whiteboard.</p><figure><img alt="Screenshot of the Figma file which we used as the sandbox — Includes timer/ tracker/ and the handy list of essentials!" src="https://cdn-images-1.medium.com/max/1024/1*6Sxiwd4kYmRA8nolmkfbqw.png" /><figcaption>Masterclass Sandbox — Includes timer/ tracker/ and the handy list of essentials + slide deck + a lot more!</figcaption></figure><h3>Phase 1— Setting up the core (10 mins)</h3><ul><li>Begin by opening your go-to word processor. We used Google Docs for our masterclass as it was a free. (I highly recommend a cloud based solution to support multiple editors in parallel.)</li><li>Add key headings to your document. Then add a few lines of description for each section, to summarise the context which you have so far.</li></ul><p>Some headings you can take reference from and rephrase and re-arrange:</p><ul><li>Title — Don’t shy away from making it witty</li><li>Purpose/ Project scope/ The ‘why’</li><li>Team breakdown / contact details</li><li>Current state of project/ context of the situation</li><li>Competitor / Inspiration</li><li>Proposed solution/ Latests draft</li><li>Useful links/ Source files/ Code repo</li><li>Sandbox/ Workspace/ Raw data</li></ul><p>Once your document’s setup. Adding few lines to describe each section will spark a lot of ideas. It will get your team to start adding anything useful for additional context.</p><figure><img alt="Slide of encouragement." src="https://cdn-images-1.medium.com/max/1024/1*NtyfnCI1beCWoxOBr8lMQw.png" /><figcaption>Once the document is created — The most difficult obstacle is behind you. Just keeping adding to the document as you go.</figcaption></figure><figure><img alt="Interface design of the YOLO messenger" src="https://cdn-images-1.medium.com/max/396/1*kWRF6Jno-UcG8_soRw-OJg.png" /><figcaption>YOLO messenger — Home UI</figcaption></figure><h3>Phase 2— Deep dive into the current situation (10 mins)</h3><p>The next step is to collect everything you know about the current state of affairs. For example, the teams used this time to compile their thoughts about YOLO messenger. They documented what were some clear problems which they could see and added notes. This included issues ranging from contrast ratios all the way to typos.</p><p>To bring this to your own workflow, begin by literally penning down all your thoughts on the subject. This will enable you to identify blind spots and form connections within the space. You can also go a step deeper and include current metrics and anecdotes of feedback data. Feel free to add related reading which would be great for any stakeholder to get a gist of the problem space.</p><figure><img alt="CollectUI page for message app references — https://collectui.com/challenges/direct-messaging" src="https://cdn-images-1.medium.com/max/1024/1*Xd1d34lz5ENq5bu8IZMwdA.png" /><figcaption>CollectUI page for message app references — <a href="https://collectui.com/challenges/direct-messaging">https://collectui.com/challenges/direct-messaging</a></figcaption></figure><h3>Phase 3— Research and Inspiration (10 mins)</h3><p>This phase required the teams to spend researching competitors, their interactions and interface. It’s important to have a good understanding around multiple problem spaces. For this purpose, inspiration boards are a great fit to spark a lot of fruitful conversations. Some links which you can also use for finding references:</p><ul><li><a href="http://www.dribbble.com/">www.dribbble.com</a></li><li><a href="http://www.pinterest.com/">www.pinterest.com</a></li><li><a href="http://www.behance.com/">www.behance.com</a></li><li><a href="https://collectui.com/">https://collectui.com/</a></li></ul><p>The idea here is to probe a lot of possibilities and get familiar with the problem space. This includes what others (including indirect competitors,) might have already solved. In reality, the end discussion of course is also a lot about feasibility, amongst a lot of other topics. Participants discussed and debated what they’d like to include in the doc. As a single unit, the teams explored what the future of YOLO could look like.</p><p>One key point was that any reference (image/ gif/ video etc.) which went into the document needed a one liner. This could be a quick summary of why the editor felt it’s a good fit for the document followed with other details.</p><figure><img alt="Slide with images of medium fidelity paper wireframes" src="https://cdn-images-1.medium.com/max/1024/1*rcp_Sll70Go7Nh349VUV0A.png" /><figcaption>Reference images to reflect the expectation on the wireframe’s fidelity (both images via google search)</figcaption></figure><h3>Phase 4— Laying the foundations (10 mins)</h3><p>This was when things got really fun and we went analog. Participants now had use the next 5–7 minutes wireframes of the revamped interface. The limitation was to stay away from software and stick to paper + pencil. The idea here is to focus on iterations. Teams used this time to document various approaches in their proposals.</p><p>Participants uploaded their suggestions to the master documents. Documentation ensures that teams consider multiple perspectives. This also ensures everyone on the team has an equal voice. It’s vital to also add a brief description to the suggestion for better context.</p><figure><img alt="Screenshot of the call when a group was sharing their quick wireframes for feedback." src="https://cdn-images-1.medium.com/max/1024/1*FnDSplUmZ4H4W8GzJHu2sw.png" /><figcaption>Snapshot of a team discussing potential UI variants — Not perfect but that wasn’t the point — Whatever gets the point across</figcaption></figure><h3>Phase 5— Regroup and sift things up (5 mins)</h3><p>Teams gathered again and this time to debate to come up with final variants. It’s important to highlight that it was NOT necessary to come up with 1 final design. The teams could document as many variants as they’d like. As long as the approaches were different and backed up by rationale, it is fine.</p><p>The practical use of this particular phase is pretty relevant. Mentioning the advantages and disadvantages of each approach always adds value. Use the same principles to breakdown even something grand as entire navigation experiences.</p><figure><img alt="Screenshot of a team presenting their final document." src="https://cdn-images-1.medium.com/max/1024/1*gur-EEaw2v2t7E8yXYSulw.png" /><figcaption>Presentation mode — One of the teams going their their design doc overviews</figcaption></figure><h3>Phase 6— Showtime! (10 mins)</h3><p>The final phase in the masterclass was to add finesse to the document. The document can be raw and a work in progress, but it needs to be scannable. Teams spent a few minutes proofreading and stylising the document.</p><p>Senior stakeholders , including leadership usually have a pretty tight schedule. So it needs to be structured in a way where you can can walk an executive through the doc in 2–3 minutes. They can then follow up and read the relevant sections on their own when they choose to do so. These documents can be a great avenue to get the right attention</p><p>Some tips to double-check during this phase. A lot of this basic principles and is echo’ing the pointers mentioned in the very beginning:</p><ul><li>Proofreading the document</li><li>Making sure it tells a story</li><li>Mention things to be done/ next steps</li><li>Don’t forget to give credit to your team</li><li>Optional: Notes to developers</li><li>Optional: Essential links to prototypes/ flows/ other group activities</li></ul><p>Once the teams were ready, they presented their documents. Followed by opening the floor for question and sharing reflection. It was motivating to see the amazing progress made in less than an hour of intense collaboration.</p><p><em>View the final PDFs and snippets from their final presentations </em><a href="https://drive.google.com/drive/folders/17aSFGCO8EnSpoxFGrqY2EfG_MJ3XHiYJ?usp=sharing"><em>here.</em></a></p><figure><img alt="Picture of a laptop, mug of coffee, notebook and a mobile phone on a wooden table." src="https://cdn-images-1.medium.com/max/1024/0*LmImH4o5H6VKlrqu" /><figcaption>Photo by <a href="https://unsplash.com/@andrewtneel?utm_source=medium&amp;utm_medium=referral">Andrew Neel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><em>“Think of yourself as a museum curator. You don’t necessarily create any content. Your role is to maintain harmony and ensure everyone’s on a single page, literally.”</em></blockquote><h3>Encore — A quick overview of the various design docs</h3><p><em>This section wasn’t part of the masterclass. </em>It is an attempt to jot down a few types of docs you may create to keep track of the amazing work you do. This is based on the docs I’ve created and the feedback I’ve received in the past.</p><blockquote><strong>Important note:</strong></blockquote><blockquote>I’ve intentionally not created template doc files. I highly believe the individual themselves would discover what works for them best. The cheat sheet in the end of this section can be a good reference point to have. Your document can of course be a mix of these or even all of these combined.</blockquote><h4><strong>The 101</strong></h4><p>The go to format which will really support you and your team to get everyone on the same page, literally. This is one of the first things I do when I’m introduced to a project where there was no form of design doc before. Usually includes a lot of snippets from different documents/ presentations/ recordings etc.</p><p>It’s important to keep a healthy list of all useful links here. This is followed by the progress which your team makes as you get more details and work on the solutions.</p><h4><strong>The full picture</strong></h4><p>This is a breakdown of a very complicated project spanning across a lot of different teams. These kind of documents also work best to give a new joiners an overview. This gives them enough context on the problem space to get them an idea of the beast they’re dealing with. This one is well suited for a lot of stakeholder management and getting feedback from all teams.</p><h4><strong>The workspace</strong></h4><p>The most common format which I use. It’s perfect I just need to document a lot of complicated use-cases but still maintain the context. The need for this came about because none of the design tools solve for preserving context. At the same time, docs are flexible enough to be shared/ edited by multiple stakeholders. This includes interfaces which might have 5–6 different form of data types/ and a lot of sub-flows. Feel free to take snippets from your Figma/ Sketch etc file and plug them directly inside the doc. (These can also be used as the core doc for developer notes and handoffs)</p><p>It’s best to keep everyone on the same page and updated with the most recent designs. Maintenance for these is manual, and you’re not accountability to keep it 100% updated. Once the core of the project is complete, it’s natural for things to become outdated.</p><h4><strong>The incubator</strong></h4><p>Best document type for anything which doesn’t exist as of today. It’s an extremely dynamic workspace with a lot of thoughts floating around. A wealth of wisdom will be gathered as a lot of people will get tagged for feedback and discussion. It’s great to collect all useful references in a single page to support with ideation. This can also overlap with documenting service design and user research activities. Different data points can be plugged together to make sense of the bigger picture as a whole.</p><figure><img alt="A table to quickly summarize the differences between the various document types I’ve used." src="https://cdn-images-1.medium.com/max/1024/1*X8K-oIlHiwP_zGP-KyOLIw.png" /><figcaption>Design docs — A cheat sheet to summarise the above</figcaption></figure><h3>Conclusion</h3><p>Conducting this masterclass was a great experience for me. The biggest reflection for me? As designers, we dive straight into the solution or ‘sprint mode.’</p><p>One key reflection from a bunch of folk was that this enabled them to systematically take a step back. Design docs enabled them to look at other aspects of the product which may get overlooked.</p><p>I had a lot of fun and from the feedback I got I’m happy to report that folk found it useful as well (I can only hope they didn’t lie.)</p><p>If you found this article useful, I would really recommend you share it with others. It’s about time we get into a habit of penning down our thoughts. Hopefully, our peers will also begin to see this as a valuable addition to the team’s way of working.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e633c740b4ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>