<?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 Sajid Reshamwala on Medium]]></title>
        <description><![CDATA[Stories by Sajid Reshamwala on Medium]]></description>
        <link>https://medium.com/@sajidresh?source=rss-acefaf1f8a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Up08Hb_pSowLP4u8QqpqrA.jpeg</url>
            <title>Stories by Sajid Reshamwala on Medium</title>
            <link>https://medium.com/@sajidresh?source=rss-acefaf1f8a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:50:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sajidresh/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[20-minute typeform prototypes]]></title>
            <link>https://uxdesign.cc/20-minute-typeform-prototypes-e6997ad5b5bb?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6997ad5b5bb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 16:38:06 GMT</pubDate>
            <atom:updated>2021-03-29T18:32:05.655Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because logic.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXZPYgcQ7AsEnxz49U4vPA.png" /></figure><p>While prototyping a new concept, I stumbled upon <strong>a method for making workable, realistic prototypes with about 20 minutes of work with the survey tool </strong><a href="http://typeform.com/"><strong>Typeform</strong></a>. Not the catch-all prototyping tool for all situations, Typeform prototypes are great for testing concepts that require a lot of user input and could benefit from basic “if/then” type logic. Here’s a rundown of how we did what we did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*WP5OcNBmyxmPnukrG4pPJQ.gif" /></figure><h3>The setup</h3><p><a href="http://therachat.io/">Therachat.io</a> helps therapists and their clients get the most out of their work together. We built the tool based on one particular insight: Therapy isn’t about the sessions, it’s about changing behavior between sessions. Unfortunately, this change often requires clients to do work outside of the sessions and, well, most clients simply don’t do this work. If we could make this work more appetizing for clients and help therapists track their clients’ progress, people needing therapy would see faster improvements and therapists could become better at what they do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S2cRfPeR_PD1AZjQhTw7hw.jpeg" /><figcaption>The Therachat Dashboard where therapists can decide how they want to keep their clients engaged between sessions.</figcaption></figure><p>While developing our first prototypes, we realized we wanted to have a deeper understanding of a popular type of therapy called cognitive behavioral therapy(CBT). I’ve found that <strong>the easiest ways to explore a new area is to do just enough research to get a basic understanding of the field and then quickly build prototypes to test out hypotheses. </strong>The purpose of this phase of prototyping is less about creating a production ready product and more about learning from customers. After a day or two of secondary research, we decided to build our first prototype around a basic question: <strong>what’s the simplest exercise in CBT therapy that we can improve upon?</strong> We settled on making a digital version of one of the most common CBT exercises, <a href="http://feelhappiness.com/reframing-your-thoughts-make-yourself-happier/">thought reframing</a>, and would fake some data science magic to identify the negative thinking traps clients fall into.</p><h3>White-boarding the logic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DeOBzQJFIZpN1TsdoA_v1w.png" /><figcaption>We did a quick whiteboard of the logic before diving into the Typeform itself.</figcaption></figure><p>We started by white-boarding a few of the screens and putting together a basic logic diagram. Our next task was to figure out the best way to build a prototype that we could put in front of users. <strong>I generally love quick keynote prototypes but, for concepts that required a lot of user input, they can leave you doing heavy voice-over while users look at static screens</strong> (“So here, imagine that you would type something in. What might you type in? Imagine that the app correctly reads your response and responds accordingly…”).</p><blockquote>I had just sent out some research surveys and thought, why can’t we just build this prototype with a survey tool?</blockquote><p>We’d been using Typeform for all of our research and recruiting surveys because it’s quick, has basic piping logic, and the resulting surveys are clean and easy for participants to fill out. These features seemed like they’d also be useful for making a quick prototype so we decided to give it a try.</p><h3>Prototyping</h3><p><strong>After finishing up the script, we put together a Typeform prototype in about 15 minutes.</strong> Because Typeform’s well designed Survey UI was acting as our app UI, we were able to dodge common distractions about button placement, type size, and color that can slow down the prototyping process. We played around with the logic to make sure it would work as planned and we were ready for testing with users the same afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6i3mA2e6xDYbj7z6PQptQ.png" /><figcaption>Creating the actual prototype took ~15 minutes.</figcaption></figure><h3><strong>Testing</strong></h3><p>We tested the prototype with 5 participants and got great feedback. <strong>4 out of the 5 participants actually thought the Typeform prototype was a real, native app. </strong>Feedback from the sessions showed us that users were not only open to having an app help them identify negative thinking traps but also found the exercise to be a useful way to open up about their thought process with others. Our prototype helped us learn all of this without us having to implement the complex data science that we’d glossed over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KFdKRiojT3sOg-Ntu25djw.png" /><figcaption>We were able to use Typeform’s logic to Wizard-of-Oz some data science magic that would be running in the background.</figcaption></figure><h3>Bonus: A take-home prototype for free</h3><p>The in-session feedback was great but what about when our participants were using the app outside of a testing session? To get better longitudinal data, we let users take the “app” home over the weekend and had exit interviews with these users a few days later. Because the prototype was built in Typeform, the prototype could be shared with a link and all of the participants’ responses were automatically stored and ready for analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKwP8EMffj9ZFCoIqDZlgw.png" /><figcaption>Answers end up neat and tidy in a spreadsheet</figcaption></figure><p><strong>The project was a win and Typeform prototyping is a method I’ll be using again.</strong> Is it the perfect prototype tool for any situation? Not in the slightest. For testing out UI details or new interactions, I’d go with more traditional tools such as <a href="http://figma.com/">Figma</a> or <a href="http://framer.com/">Framer</a>. Are Typeform prototypes great for early stage concepts when you don’t want to get lost in these UI details? Without a doubt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fnPcXx6F3gt1G-LZO9-bbQ.jpeg" /></figure><p>Cheers and I’d love to hear about approaches you’ve used to push the limits on how fast you can explore new ideas. Hazaa!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6997ad5b5bb" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/20-minute-typeform-prototypes-e6997ad5b5bb">20-minute typeform prototypes</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting to change]]></title>
            <link>https://uxdesign.cc/getting-to-change-27bc55b2aa4d?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/27bc55b2aa4d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[activism]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Mon, 09 Apr 2018 21:28:25 GMT</pubDate>
            <atom:updated>2018-04-21T13:17:12.742Z</atom:updated>
            <content:encoded><![CDATA[<h4>A redesign of Change.org</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNo9nfsKjix9OUbfXqiz9Q.png" /></figure><p>There’s been a wave of self-organized movements in the past year (including <a href="https://www.washingtonpost.com/local/womens-march-on-washington-a-sea-of-pink-hatted-protesters-vow-to-resist-donald-trump/2017/01/21/ae4def62-dfdf-11e6-acdf-14da832ae861_story.html?utm_term=.1285fe255329">the largest single day protest in U.S. history</a> ). While Change.org has played a large role in many of these, their petitions have also, in some cases, been criticized as doing more for awareness than the concrete change their name implies. I’ve never been much of an activist myself and have been sitting on the sidelines for many of the recent political events. I decided to use a redesign as an opportunity to understand how social movements work and what could be done to make them move better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-vmgzzbNnXASJY4w0sR1g.jpeg" /><figcaption>Change.org! An awesome platform that seemed to be well positioned to help people make bigger changes.</figcaption></figure><h3><strong>How Change.org works and makes money</strong></h3><p><strong>Change.org is a for-profit social change platform that allows people to support causes they believe in. </strong>Support primarily happens in two ways; creating petitions or signing them. The for-profit company makes money through sponsored petitions that pop up after for signers after they’ve finished signing a petition. After talking with people close to the product, I hypothesized that Change.org could bridge the gap between awareness and action in a way that would also allow Change.org to serve their own larger mission.</p><h3>Where to start?</h3><p><strong>My first step in tackling this problem was to understand who is involved.</strong> I identified three primary stakeholders; people that create petitions(organizers), people that sign petitions(joiners), and the people that were being asked to make the change a petition is pushing for(decision makers). I decided to focus on organizers and joiners because they were the two groups that I could talk with directly.</p><p>I also listed out my initial assumptions and alternative tools that organizers and joiners have at their disposal to inact change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*30gRZNmP9_aKGOpZ70qP6w.jpeg" /><figcaption>What is Change.org competing with? Who are the people involved? A brain-dump helped me get started.</figcaption></figure><h3>From research questions to conversations</h3><p>I used these initial assumptions to create a list of research questions. This list helped me develop a short interview guide for each group of stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5v71GFtoYvO_T5nAeSaIfQ.png" /><figcaption>A quick, 20 minute interview guide session helped me frame up the project better than I would have otherwise.</figcaption></figure><p>My interview guides prepared me to do some light contextual inquiry with friends, family, and people that had just come off of the womens’ march.</p><h3>Take-aways and insights</h3><p>I found out stuff! No for real, I had some big realizations about the gap between how petitions and movements work that made me question how online activism works.</p><h3><strong>1. There are different levels of activism in a movement and they’re not all reflected in online petitions</strong></h3><p>In tools such as Change.org, there’s an unnatural gap between making a signature and organizing a petition of your own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*z8F5wVExpUSwvqnj9YoJqg.jpeg" /></figure><blockquote>“A supporter is different than a marcher which is different than an organizer.” — Political Organizer</blockquote><h3><strong>2. Organizers have a hard time getting their participants involved beyond just signing</strong></h3><p>People that sign a petition often form the base for a movement that an organizer is organizing. Not giving petition signers easy next steps can keep a movement from growing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*6SWkxiTAX5ERb793rAa4Mg.jpeg" /></figure><blockquote>“After our campaign grew, we couldn’t connect with all the people that signed the petition. To really [make the change we wanted to make], we needed people to actually write letters and we couldn’t pull that off.” — Organizer</blockquote><h3><strong>3. Potential signers are often unconvinced that what they’re doing will lead to significant change</strong></h3><p>Many people that would otherwise be vocal about their views don’t sign online petitions because they view them as a form of slacktivism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*elMiPubXf-BNYt3cVnHDKQ.jpeg" /></figure><blockquote>“How is signing a Change.org petition any more effective than retweeting an interesting article? What am I actually doing here?” — Petition signer</blockquote><h3>Analyzing the current experience</h3><p>I used these insights to analyze the current Change.org UX flow from the perspective of these users</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJfUfKSCeVZVUqvxW2XndQ.png" /><figcaption>Change.org seemed to have issues helping people find steps to take that matched their level of interest.</figcaption></figure><h3>Approach</h3><p>I realized that, despite my previous beliefs, both organizers and joiners felt like they weren’t really making any impact through petitioning. I decided to focus on helping both groups reach the point where they knew they were making an impact and that I could make this happen using two tactics:</p><ol><li><strong>Better, fewer petitions</strong><br> Push petition creators to help each other build great petitions together.</li><li><strong>Actionable next steps at all levels<br> </strong>Get organizers to setup petitions in a way that allows signers to easily take next steps and reward signers for taking these next steps.</li></ol><h3>Ideation and user experience mapping</h3><p>From here, I started mapping out what the initial experience could look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soLDBQXEVG_Ej10LFesQbw.png" /><figcaption>A redesigned flow could focus on connecting people around a movement and helping them create and find next steps.</figcaption></figure><p><strong>I defined 3 sections of the app</strong> that would support the three tactics I would use; finding petitions, taking action on them, and building a sense of identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3YT22z-OVTYEuh-ZNeMJ_A.png" /><figcaption>An updated app’s three primary orientations.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DvIaliWGMBZQZJ9lTtpmOA.png" /><figcaption>What if petitions were designed to be explored by area of interest?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwy8ZS-KXDtwxlCt9L3_CA.png" /><figcaption>What if starting a petition was secondary to supporting a petition?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H5A8qylMrEHeK014V1vaLA.png" /><figcaption>What if you were celebrated for activities outside of just signing?</figcaption></figure><h3>Finding out how wrong I was</h3><p>After realizing how many assumptions I was wrong about during my first round of research, I decided to create a quick Invision prototype that I could use to get feedback from organizers and joiners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGdBWzIRFLusRlpWc1b24g.jpeg" /></figure><h3>Illustrating the concept</h3><p>I used the feedback that I received to create more deliberate wireframes and mocks that could better illustrate the concept.</p><p><strong>Petition authoring as an opportunity for collaboration</strong></p><p>Because so much of the success of a petition relies on how it is made, I first laid the foundation of the experience for organizers. My biggest goal was to help organizers find missed opportunities to support each other and give their followers additional ways to support their cause.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WaADH8s3NyIo10Zg_jW-xg.png" /><figcaption>A less intimidating petition creation flow could help you find other related petitions.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wh3-3vHEbrrRT2preli9bQ.png" /><figcaption>What if you could get help from more experienced petition creators and then create steps for others to follow?</figcaption></figure><p><strong>Celebrating the signing</strong></p><p>In order for signers to know they were making an impact, I created ways for them to immediately make committments to next steps and feel like they were becoming part of a larger movement</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Twt41dTfpWQlt79KvBy46Q.png" /><figcaption>Signing petitions could be framed as joining a movement where you can commit to taking steps.</figcaption></figure><h3>My riskiest assumptions</h3><p>By this point, I was able to identify the biggest bets that this concept hinges on. These are areas that are worth questioning with alternatives:</p><ul><li><strong>Using badging to incentivize alternative methods of participation.</strong> If not developed with sensitivity to the causes that people are supporting, systems like badges can appear insincere. Are there alternative systems for getting joiners and organizers more involved?</li><li><strong>Relying on machine intelligence to avoid duplication.</strong> Are there alternative ways to get people to find other petitions with similar ideas and be excited about it when they do?</li><li><strong>Being able to continue to promote Change.org’s sponsorship model.</strong>Change.org makes money through sponsors’ petitions that you see after signing a petition. Because this solution adds alternative activities after petition signing that may compete with signing another petition, it is worth running a test to see if Change.org’s business model would be effected.</li></ul><h3>Next Steps</h3><p>From here, I would love to develop a deeper understanding of the different groups of people engaged in activism. Afterwards, the more pragmatic version of me would explore alternative approaches to solving this problem and find ways to test my riskiest assumptions in the cheapest ways possible.</p><p>Thanks for taking a read and I’d love to hear your thoughts!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27bc55b2aa4d" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/getting-to-change-27bc55b2aa4d">Getting to change</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First lessons in product design. A time traveller’s account.]]></title>
            <link>https://medium.com/iit-institute-of-design/lessons-from-a-first-year-in-startup-product-design-a-time-travellers-account-69ce50a28ff1?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/69ce50a28ff1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-research]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Sun, 10 Jul 2016 20:21:37 GMT</pubDate>
            <atom:updated>2017-06-01T21:46:19.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XVHZcHd8aagq3KPLotybLg.png" /></figure><p><em>With warm weather on our hands, I’ve decided to use the longer days to build a time machine and write a letter to give myself back in 2011. The time machine’s going to be the trickier piece so I decided to start with the letter.</em></p><p>In a few months I’ll be finishing up my fifth year of working as a designer and my second in product design at a startup. As I’ve tried to gain a handle on this torturous mistress called design, I’ve started to develop a point of view of what it means to approach the field as a practice that we must continuously strive to perfect. Here’s what I’ve learned along the way.</p><h3>Lesson # 1 : People will get frustrated with us for thinking too big and thinking too small. This is a sign that we’re doing our job.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XVHZcHd8aagq3KPLotybLg.png" /></figure><p>A characteristic of great designers that I’ve learned to appreciate is their ability to zoom in and zoom out. As my friend <a href="https://www.linkedin.com/in/rachekroft">Rachel Kroft</a> likes to say, you have to keep one eye in the telescope and one in the microscope.</p><p>The truth is that there is a natural amount of friction that exists when transitioning from being up close and personal with a micro interaction and out loose and theoretical with a blue sky proposition. With others involved, it’s unavoidable that moving back and forth between these two areas will interrupt project schedules. The thing is, to design great product you’ll have to operate in both worlds. It’s part of our job. As for the friction between these two modes? It’s the necessary but messy bit that they didn’t tell us about in designs school.</p><p>Sometimes I’ll get stuck up in the clouds or down in the wires and it’ll take an elbow from others to make that switch. Accepting this elbow from others with open arms is something I’ve just recently become comfortable with. How do you learn to get comfortable with others telling you when to step back or dive down deep? Allowing my team — which has ranged from 5 to 47 over the years — to share ownership of the design process has been the biggest step towards deflating my design ego. By continuously <a href="http://www.slideshare.net/sajidreshamwala/five-ways-to-get-better-data-from-our-users">teaching my teammates</a> when it’s right to do what types of design work, their once aggressive elbows have become productive nudges to help us keep projects on the right track. And these are nudges that I now (mostly) enjoy getting.</p><h3>Lesson # 2 : To ship great product, we’ll need conflict.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gE-gsgQsruulGbXEO5bgA.png" /></figure><p>As I’ve gotten deeper into product design, frameworks, and workshopping techniques, I’ve continued to be tempted to seek out the fabled land of peaceful problem resolution and a conflict-less work existence. If only I can nail the right workshop techniques, I’ll mutter, work would be an endless parade of hugs! After having run seemingly great projects with ineffective results, I’ve learned to be wary. My biggest take away on managing design as a process has been that it’s easy to get inclusive design confused with conflict-less design. While yes, it is possible to make it through design projects without any conflicts, a project without conflict is often a red flag.</p><p>One of my favorite definitions of <strong>product design is solving problems within constraints</strong>. In their brilliant book <a href="https://www.amazon.com/Wiser-Getting-Beyond-Groupthink-Smarter/dp/1422122999/ref=sr_1_1?ie=UTF8&amp;qid=1470673875&amp;sr=8-1&amp;keywords=wiser">Wiser</a>, Hastie and Sunstein describe all decision making processes as a movement between identification and selection. In design terms, identification is the going wide, divergent part of a design thinking process while selection is the convergent, narrowing down bit. Identification is the ideation heavy part of decision making that is most reinforced in design education and what drew me into design in the first place. Find an unsolved problem, say yes to any broad mix of ideas, and smash those ideas together. Thats identification.</p><p>The tougher and equally important peace of design is deciding on which ideas and directions to move forward with. This is the part Hastie and Sunstein call selection. While you can let selection be dictated by your own intuition when working alone, this isolated and heavily biased approach doesn’t work so well when working on a team. I’ve found that it’s often our job as designers to make sense of the different opinions that come into a project, separating emotions from the work itself, and making the most of our team’s collective intelligence. Along the way, <a href="https://medium.com/@sajidresh/turning-meetings-into-design-sessions-38202622b85c#.4eqzf68qt">I’ve learned some techniques</a> to help moderate these conversations and I recommend diving into these techniques whole heartedly. The caveat is that, unfortunately, there will always be conflicts and, instead of trying to dispense of these conflicts all together, we may be better served by making these conflicts as healthy as possible.</p><p>When conversations do get heated, I’ve learned to make sure that I have the tools I need to make these conversations productive (pro tip: make reading <a href="https://www.amazon.com/Crucial-Conversations-Talking-Stakes-Second/dp/0071771328/ref=sr_1_1?ie=UTF8&amp;qid=1470676921&amp;sr=8-1&amp;keywords=crucial+conversations">Crucial Conversations</a> a required part of your design education this year). Because our role often places us in the middle of project team, designers are in the perfect position to be the moderators of these conversations. Combined with our training in group critique and workshop facilitation, it’s only natural that we fully adopt this role into our practice by continuously developing our communication skills.</p><p>Being able to transform messy conflict into a healthier version of itself has turn what was once a source stress into a source of learning that has has helped me question my own assumptions about what it takes to build great product.</p><p>If design is like sailing an ocean, then process and workshop methods are like a compass and map. Having the right tools will help us get where we need to but, no matter how prepared we are, the sea shall have its storms.</p><h3>Lesson # 3 : Asking important people dumb questions will always be tough. To get used to it, make it part of your practice.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2bv2AfshG9RhpJWmFGqPQ.png" /></figure><p>My favorite definition of <strong>strategy is the intentional use of available power to devote resources towards a well defined goal that would otherwise not be achieved</strong>. One of the benefits of working at a startup is having proximity to that power; i.e. the founders and the board. What I’ve learned is that proximity to power isn’t the same as <em>access</em> to power and that accessing this power relies on my willingness to actively participate in the conversation.</p><p>As I’ve progressively become more useful to my teams, I’ve been invited into rooms with progressively smarter people. And this has been a good thing. The tricky part is that, as the rooms I’ve been in become smarter, it gets scarier to ask or say anything at all. Combine this with ‘Imposter Syndrome’ and one can find themselves playing the part of the quiet kid in the corner that occasionally nods. I get it. Putting yourself out there is scary and head nodding is oh so safe.</p><p>So how do we break out of this safe, head-nodding bubble? One way is to become comfortable with asking dumb questions. But how do you make asking dumb questions less intimidating? I’ve found it useful to reframe my fear of asking seemingly dumb questions as a simple communication breakdown. In this case, the communication breakdown is that a gap exists between my courage to speak up and the safety that I need to exercise that courage.</p><p>As opposed to waiting until I work up the courage to ask intimidating questions in hight stakes situation, I’ve found the easiest approach is to start with safer situations i.e. less risky moments to ask dumb questions. I’ll ask a group of friendly developers to spell out what a MySQL server is. I’ll talk with a design mentor about how he decides on new hires. Let your mind wander through seemingly obvious questions, wait for one to set off that quiver of anxiety inside of you, and take that quiver as a sign that you’ve stumbled onto a question that sits at the edge of your comfort level.</p><p><strong>Real talk:</strong> As far as I can tell, that little quiver we get when we ask a question with a seemingly obvious answers will always exist. My best advice is to make it part of what defines you as a designer. Become known as the person in the room that asks dumb questions and you’ll realize it’s not that big of a deal.</p><h3>Lesson # 4 : The group mind resides uber alles.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z26dKNyb_gVocLWoW-TVxA.png" /></figure><p>My biggest take away from studying improv in Chicago is that the foundation of a strong improv team is a common understanding of reality. This is often referred to as a <a href="https://peopleandchairs.com/tag/improv-group-mind-exercises/">group mind</a>. The aha! moment for me was when I realized that this same group mind has been the foundation for every good product team that I’ve been a part of.</p><p>Never assume that your team shares the same understanding of reality in their heads. In all likelihood, they don’t. This heuristic especially holds true when it comes to defining problems. Having a different understanding of a problem can cause systemic breakdowns for a team further down the road and I’ve found it to be a common culprit when I feel like I’m arguing over details of a solution. Creating the group mind, or a common understanding of the problem that you’re trying to solve, is the necessary step to get to this common understanding. The tough part for me is that it is often a step that seems unnecessary at the time.</p><p>So whats a simple first step for creating this mysterious group mind? One way is frameworks. For those uninitiated to my personal obsession (i.e. those with better things to do than geek out on process), a framework is just another word for a model that can be used to categorize a bunch of things and understand the relationship between them.</p><p>While words can be incredibly powerful, I’ve found that words are limited by the fact that they’re often just pointers to very different ideas in each of our heads. This limitation is multiplied by the fact that each one of us comes from a rich and unique history. Using frameworks is a way to look at concepts from new perspectives and make the nuances of a problem that are often hidden open for discussion. As Kim Erwin notes in her book <a href="https://www.amazon.com/Communicating-New-Methods-Accelerate-Innovation/dp/1118394178/ref=sr_1_1?ie=UTF8&amp;qid=1470677115&amp;sr=8-1&amp;keywords=communicating+the+new">Communication The New</a>, this limitation of words holds especially true when we’re trying to communicate new ideas. New ideas have yet to be given a common definition for all of us to hold onto and it takes a mishmash of descriptive elements, each exposing a problem or idea in a different way, to communicate them clearly. Frameworks are a great tool to do just that. I found that starting with <a href="https://www.amazon.com/101-Design-Methods-Structured-Organization/dp/1118083466/ref=sr_1_1?ie=UTF8&amp;qid=1470678786&amp;sr=8-1&amp;keywords=101+design+methods">a basic set of frameworks</a> that I can confidently use and make adjustments to has helped me start to build a collection of my own.</p><p>Sometimes when I create a framework I’ll become so obsessed with getting it right that I won’t want anyone else working on it. I’ve realized that in these moments I’m missing the point. While frameworks are partially about getting a unique perspective on a problem, they having nothing to do with getting a view that is absolute or dogmatic. I’ve found that focusing instead on creating a map that I can refer back to when things get abstract can keep me from getting lost in the clouds. Most importantly, I’ve learned that this map needs to be one that everyone on my team can feel like they own.</p><p><strong>Important note:</strong> group mind is NOT the same as group think. The first is about having a common understanding of the world, the second about ignoring the strengths and opinions of the individuals in that world. Check out <a href="https://www.amazon.com/Wiser-Getting-Beyond-Groupthink-Smarter/dp/1422122999/ref=sr_1_1?ie=UTF8&amp;qid=1470677188&amp;sr=8-1&amp;keywords=wiser">Wiser</a> for deets.</p><h3>Lesson # 5: Every team has its own innovation shape. (Stick with me here)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wI_LynJoFWGshKrU8OANkQ.png" /></figure><p>One wonderful symptom of the growth of design thinking is the widespread availability of out of the box workshop models. From the I<a href="https://www.ideo.com/work/human-centered-design-toolkit/">DEO Field Guide to Human Centered Design</a> to the brilliant <a href="http://www.gv.com/sprint/">Google Ventures Design Sprint</a>, we now have access to enough copy and paste processes to fill a double sized trapper keeper. I’ve often been tempted to take these workshop models and apply them word for word. And I think this is the right thing to do. At least once. What I’ve notice pretty quickly is that every problem and team is its own little snowflake and requires an equally unique solution. This uniqueness means that it’s often up to us to take the best bits and pieces of these different models and adjust them to the unique makeup of our teams and the problems they’re solving.</p><p>Because teams change over time, I’ve been best served by making sure to make adjustments along the way. Unfortunately, accepting this approach means that you will never have a plug and play design process. We’ll have to constantly build up our repertoire of tools and focus instead on developing an intuition for when it’s right to take which approach. While this may sound like a lot of work, as design professionals, it’s our responsibility to push the limits of the field. One way I’ve made this more approachable is to apply a 2-week sprint model to my design process and implement the all mighty<a href="http://techbeacon.com/maximize-value-agile-postmortems"> post-mortem</a>. This just means taking some time every couple of weeks to look back at the approaches I’ve been using with my team and make any adjustments that feel are right.</p><p>Taking this iterative approach also means that new methods that I’m trying out are just low weight trials. If a method doesn’t work I can just toss it out, no harm no foul. Having a willingness to create new tools and trying out untested methods has been my approach to moving beyond the application of others’ techniques and on to making contributions to design as a practice, however small these contributions may be.</p><p>If I had to pick one concept that has most transformed how I think about my role as a designer it would be <strong>identity</strong>. What characteristics do I choose to define me as a designer? What can a designer bring to a team that will make it a better version of itself? For me, the answer to these questions lies in <strong>taking on the identity of being endlessly curious at the cost of always knowing the answer</strong>. To act as a force of learning and exploration on a team, especially when asking questions that we think we know the answers to. I’ve said before that I believe that <strong>design leadership’s message to traditional leadership is that we don’t know all the answers yet and that’s ok</strong>. These past couple years has given me confidence that this is the most effective frame of mind that a designer can adopt when focusing on continuously getting better at solving messy problems. That is, as far as I know right now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69ce50a28ff1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iit-institute-of-design/lessons-from-a-first-year-in-startup-product-design-a-time-travellers-account-69ce50a28ff1">First lessons in product design. A time traveller’s account.</a> was originally published in <a href="https://medium.com/iit-institute-of-design">Institute of Design (ID)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning Meetings into Design Sessions]]></title>
            <link>https://medium.com/@sajidresh/turning-meetings-into-design-sessions-38202622b85c?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/38202622b85c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Fri, 18 Dec 2015 20:00:30 GMT</pubDate>
            <atom:updated>2015-12-20T19:00:47.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEGCJO0Zew2rlgxtqV7VsQ.jpeg" /><figcaption>`</figcaption></figure><h4>In their heart of hearts, most meetings want to be productive work sessions. Here are tools to make that change happen.</h4><p>Much of product design involves working through a repeatable process while being flexible enough to arrive at novel solutions. Like when sketching something new yet familiar, I’ve realized its useful to have back-pocket frameworks to get the underlying structure of the process out of the way so that I can focus on the interesting details.</p><p>Here is a selection of five such frameworks. Some simple, some more complex, all indispensably useful</p><h3>1) How Might We’s and Sticky Voting</h3><p><strong>Useful For:</strong> Defining a problem when Jimmy from product gets stuck in debates with that guy from marketing that always shows up (how does he keep finding these meeting invites anyways?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*JpCl-nHvU5wQp1X5wYkQlg.jpeg" /><figcaption>votes. and stickies. votes. votes. and stickies.</figcaption></figure><p>Hmm, you say. This sounds like two techniques, not one. Why yes, yes they are. And two techniques shamelessly stolen from Ideo’s <a href="https://www.ideo.com/work/human-centered-design-toolkit/">Human Centered Design Process</a> at that. But alas, this devilish pair is deserving of their exception. These two techniques are like two lumberjacks; somewhat mighty on their bristly own but pair them together and they can fell the mightiest of redwoods (i.e. loquacious meetings).</p><p>If not properly answered, the ‘what problem are we solving’ question will keep coming back to haunt your team all the way to your projects end. A great way to start answering this question at the beginning of a project is with a brain dump of all of your team’s relevant user research, analytics, and product strategy for your team to meditate on together. Simple enough, eh? The twist to make this meeting productive is, during this brain dump, don’t allow for any conversation. Instead, have everyone in the room capture their thoughts on post-its in the form of ‘How Might We’ questions. These should be the questions that team members feel are important to have answered by the end of the project. After the brain dump, have your team stick their questions up on the board for everyone to silently vote on using stickers (i.e. sticker voting). Afterwards, you’ll find yourself with a heat map of the most important problems to handle as articulated by your team members.</p><p>Sound tedious? I promise, it’ll be much faster then leaving the ‘what problem are we solving’ question unanswered throughout the life of your project.</p><p><strong>Pro Tip:</strong> In the real world, some voices are worth more than others. If there are stakeholders that will be the final decision makers, give them super votes that are worth 10x of a regular vote.</p><h4>“The goal of inclusive design is not to be democratic but rather to be open and effective.”</h4><p><strong>Further Reading: </strong><a href="https://web.archive.org/web/20150906010124/https://hbr.org/2012/09/the-secret-phrase-top-innovato/">The Secret Phrase Top Innovators Use</a></p><h3>2) The Proto Persona</h3><p><strong>Useful for:</strong> making sure everyone is trying to solve the same problem for the same type of person. Even when it feels like you should have done that already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*abdb6CMHi28OEe5jVoUr7A.jpeg" /><figcaption>the proto persona: a persona to be properly desposed of after use</figcaption></figure><p>A familiar scene: You’re white-boarding out UI with your team and trying to get aligned, but you keep getting stuck in a cross fire of varying opinions tucked behind crossed arms. Then it hits you. The reason everybody is at odds is that everybody is thinking about the problem in terms of different use cases. So what do you do?</p><p>Enter the proto-persona.</p><p>Proto-personas, or quick, good-enough personas, are like full sized, data backed personas but without the deep research and contentious detail. Proto-personas are NOT personas and don’t serve the same purpose. While personas are about creating a vehicle to capture the use cases that your users are experiencing, proto-personas are just about make sure your team is thinking about the <em>same</em> use cases. I’ve realized that a big part of product design is making sure the answers to the ‘why’ and ‘what’ questions are clearly articulated even when you’re building out the ‘how’. Creating quick proto-personas is a fast, easy way to assure that you and your team have the same answers to these questions.</p><h4>“A big part of product design is making sure the answers to the ‘why’ and ‘what’ questions are clearly articulated even when you’re building out the ‘how’.”</h4><p><strong>Pro Tip:</strong> While the proto-persona can be created during a meeting using everyones’ input, you’ll be more successful if you show up with some of the persona’s attributes in your back pocket. Your goal at this point is to align, not reinvent.</p><p><strong>Further Reading: </strong><a href="https://web.archive.org/web/20150906010124/http://www.dtelepathy.com/blog/philosophy/how-to-make-proto-pesonas">How To Make A Proto-Persona And Get Everyone On The Same Page</a></p><h3>3) 5-E model</h3><p><strong>Useful For:</strong> Getting your team to think about experiences when your product is turning into a pile of feature requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*Zn_P4WiRJ-xoW7EqX-kOHw.jpeg" /><figcaption>so simple and oh so powerful</figcaption></figure><p>This framework. This framework is my big fat beautiful baby. If you’re trying to explain to someone what user experience is, this is the framework to kick off that conversation. The 5-E Model is a chronological framework that pushes you to take whatever you’re working on and break it into a 5 step experience from the user’s point of view: enticement, entrance, engagement, exit, and extension. Seem super simple? It is and thats what makes it so powerful. One of the foundations of UX is to move beyond the meat of your product’s core use case to its outer edges. The 5-E framework forces you and your team to do that. Feel like you’re stuck talking about a feature and not a product? Sketch out how the user would use the feature in question with the 5-E’s and your team will be thinking holistically again. Do you have the nagging feeling that no one is really sure how your users arrive or leave the part of the user experience that you’re talking about? You’re probably right. This framework will make sure that you do.</p><p><strong>Pro-Tip:</strong> The 5-E framework can also be used during research to understand the current experience and what’s broken about it. Use pictures. Include peoples’ faces in said pictures.</p><p><strong>Super Pro-Tip:</strong> If it helps, you can think about entice as the ‘cue’ from Charles Duhigg’s “The Power of Habit” and extend as the ‘reward’ that you’re providing users by coming back or sharing their experience with others.</p><p><strong>Further Reading: </strong><a href="https://web.archive.org/web/20150906010124/https://desonance.wordpress.com/2011/05/29/i-heart-frameworks/">I Heart Frameworks</a></p><h3>4) UI shorthand</h3><p><strong>Useful For:</strong> Collaborating on ui flows with your dev and product team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*4eKhvBfKub796-kgo8jqpg.jpeg" /><figcaption>big ups to the mighty Ryan Singer</figcaption></figure><p>I ran into Ryan Singer’s work a couple years ago and I was put off by its simplicity. How can something so nuanced and ephemural as the craft of a user experience be expressed with words and arrows? I then I got over myself. Without getting tied up in form and shape, Ryan’s UI shorthand is a simple tool for white boarding a user experience when you’re still figuring out what that experience is. Because its so low fi, it becomes incredibly inclusive. A great exercise is to write each one of his ‘user sees, user does’ pairs onto a sticky note while you and your team talk out the flow. If you’re still working out the ux flow you’re still early in the process so feel comfortable moving these stickies around and crumpling up the bad ones.</p><p><strong>Pro Tip:</strong> The danger of low fi work like this is that its easy for everyone to have different ideas of what the final product looks like. You can get everyone on the same page by following this session up with wireframes or a hi fi mock that you can share out with the team.</p><p><strong>Further Reading: </strong><a href="https://web.archive.org/web/20150906010124/https://signalvnoise.com/posts/1926-a-shorthand-for-designing-ui-flows">A Shorthand for Designing UI Flows</a></p><h3>5) Process Flow Diagram</h3><p><strong>Useful for:</strong> Working out the logic of when your product does what.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*N94q7LJAa1Qag1lw73rtzg.jpeg" /><figcaption>I’ve got a homemade brownie for anyone that can come up with a better shape for ‘decisions’ than a freakin diamond.</figcaption></figure><p>Part of moving beyond ux and into product design is having the legs to move about in a world that requires a designer to understand how something is implemented. One simple tool to help you make this transition is the process flow diagram. The process flow diagram is basically visualized boolean logic. Being able to whiteboard a process flow diagram during a meeting can mean the difference between hand waving to ‘some problem that dev will figure out’ to getting in there and figuring the problem out with them. Warning: going through the process flow diagram with your team is going to force you to ask dumb questions. That’s the point. Being willing to ask dumb questions is a designer super power that needs to be developed. Get comfortable feeling a little stupid now and your team will thank you later. Eventually, you’ll even thank yourself.</p><p><strong>Pro-tip:</strong> Your team members will steal this framework and use it in their own meetings. And that’s cool. Let go of the black turtleneck. Embrace the embracement of design.</p><p><strong>Further Reading: </strong><a href="https://web.archive.org/web/20150906010124/http://creately.com/blog/diagrams/flowchart-guide-flowchart-tutorial/">Ultimate Flowchart Guide</a></p><h4>“Your team members will steal these framework and use them in their own meetings. And that’s a good thing.”</h4><p>And those are my five go to frameworks for turning often unproductive meetings into product work sessions. Give them a try and tell me what you think.</p><p>Better yet, go make something cool and make me jealous so that I go make something cooler.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38202622b85c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Lean Research Sloppy Joe]]></title>
            <link>https://medium.com/iit-institute-of-design/lean-user-research-or-how-i-learned-to-do-research-when-trying-to-ship-1fdbbc0b9fa2?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fdbbc0b9fa2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Mon, 07 Dec 2015 22:29:06 GMT</pubDate>
            <atom:updated>2016-01-04T19:53:52.712Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8GsnuqFcMEhuHVacBQngQ.png" /></figure><h4>Doing design research when you need to ship.</h4><p>I‘ve never met a product team that doesn’t believe user research is important. Actually getting that research done is a different story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JROdiHscVAgeCBZkxJmiQw.jpeg" /><figcaption>The oh so mighty lean ux cycle. But where’s the room for research?</figcaption></figure><p>When I first moved from a dedicated design research role to a hybrid UX role, I struggled with balancing spending time to understand user problems with working on designs that needed to get out the door. Not long after, I ran into <a href="https://web.archive.org/web/20150905195919/https://www.youtube.com/watch?v=9TJTbRw4ri8">Tomer Sharon’s work on Lean User Research</a>. I realized that, because I was still thinking of design research as its own independent discipline, I was getting stuck <a href="https://web.archive.org/web/20150905195919/http://www.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/">in the deliverable business</a> and burning time. By switching my focus to working with my team to identify the right problems to solve, I found an approach thats helped me make my research more actionable and nudged our team to GSD.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPh1yp4POnpI%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPh1yp4POnpI%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPh1yp4POnpI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8bf3965985b280361cbfea3e7fcd601c/href">https://medium.com/media/8bf3965985b280361cbfea3e7fcd601c/href</a></iframe><p>Earlier this year I got a chance to talk at <a href="https://youtu.be/Ph1yp4POnpI">SAP</a>’s UX Boost Event on what I’ve learned about making research work at startups. Here are the principles that have guided me and my team along with some pointers for getting started. Forward!</p><h3>User research needs to be less like a sandwich and more like a sloppy joe. Let me explain.</h3><p>Part of making research work is making sure its not a big deal. When talking about the differences between explorative research and evaluative research, I describe design research as a sandwich. You kick off with field studies before you begin building and then do usability research afterwards to get feedback on what you’re making.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bj6pfKTWov3W4ma47jGn-A.jpeg" /><figcaption>Design research is generally thought of as sitting on 2 sides of a design project…</figcaption></figure><p>While this model is great for introducing design research to a team, I’ve since learned that research is never this clean and, well, it shouldn’t be. By letting the process get messier and letting your explorative and evaluative research mix into a design, you can maintain momentum while still getting out there and connecting with real humans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slZsKxIwEDRCaxXLDQAW6w.jpeg" /><figcaption>…but when you’re moving fast things need to get messy. And that’s a good thing.</figcaption></figure><p>Breathe. Let the process get dirty and let go of the beautiful presentations. Plus, showing off a great product will be more impressive than a process case study. I promise.</p><h3>For research to work in a quickly moving team, everyone needs to smell users.</h3><p>Having worked as a full time researcher, the biggest time sink can be in the creation of decks and research reports for the people that weren’t there. These decks take so much time because so much of user research is about building empathy in your team for users. Creating empathy with dead slides takes a lot of time and <strong>the emotions that the best presentations can provoke are only a shadow of what you experience in the real world</strong>. After trying to cram the time to put these decks together while also doing design work, I realized that you can short-circuit the share-out by having your team with you in the room during research sessions. While this doesn’t negate the need for analysis, it does get you and your team to solving the problem together much faster and leads your team to feel design problems much more intimately.</p><p><strong>Powerpoint decks don’t fire off </strong><a href="http://www.apa.org/monitor/oct05/mirror.aspx"><strong>mirror neurons</strong></a><strong>**</strong>. Real experiences with real people do.</p><h3><strong>User research can be fast. But there’s still a methodology.</strong></h3><p>While lean user research can get you to solving the right problem faster, it takes an understanding of the rich fields of ethnography and human and computer interaction to trully understand these complex organisms that are ourselves. <strong>The only thing worse than bad design research is mediocre design research presented persuasively.</strong> So lets walk through some principles that you can stick to when trying to do the good kind.</p><h3>5 PRINCIPLES OF LEAN USER RESEARCH</h3><p>Here are five guidelines that I like to share out with teams to get them started on understanding this methodology:</p><h3>1. Watch more than you listen.</h3><p>The intent of listening to our customers is the right one. The problem with listening to users is that, when people start talking, they usually start trying to predict their future behavior. And, well, we’re all generally horrible at this. Until you become an expert at analyzing user conversations, you’re better off asking questions that lead users to show, not tell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MpRGOj7UwDjWP7AY4r3TQw.jpeg" /><figcaption>When people are doing stuff, you can watch and understand their behavior. Once they start rationalizing, you’re now running a marketing study.</figcaption></figure><p>A great heuristic is that you want people leaning in and doing stuff. As soon as they’re leaning back, they’re rationalizing. This is a sign that you want to get people back to completing some sort of task.</p><p>Well what if you can’t get in there and get people to actually do stuff? That’s ok. While not ideal, you can still <strong>get people to tell recent stories about the problems you want to help them solve</strong>. The great thing about stories is that they include details that are easier for our memories to recall with efficacy. They’re also usually littered with little details that you would otherwise miss and can help you find that little insight that will help make your product special.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7z5YVOJT7vzfwRybiTs6pQ.jpeg" /><figcaption>If you can’t watch people do stuff, get them to tell recent stories.</figcaption></figure><h3>2. Observe in Context.</h3><p>Getting out of the office and watching users in their natural context is an activity thats easy to overlook when working in tech, especially when designing for desktop. While its impossible for me to tell you what weird and interesting thing you’ll learn from a user in their natural environment, I promise you that there will be something weird, interesting, and, most importantly, useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iGSD2Ac2QStFIihEqk4VOg.jpeg" /><figcaption>Watching users do stuff in their natural environment leaves you open to discover the unexpected…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-6_ad-Uo0UEt-iCdYLPCA.jpeg" /><figcaption>… and you’ll often be surprised as to what that natural environment is.</figcaption></figure><h3>3. Features are our job. Look for the why.</h3><p>This guideline is probably the most contentious of all.</p><p>If we made a hierarchy of good user research queries…</p><ul><li>In the ﬁery depths of hell would be theoretical future prediction questions</li><li>At the top you would have watching people</li><li>Next up you would have questions that lead users to tell stories about recent experiences</li><li>And somewhere in the middle you’d have ‘what features do you want’</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZtMl0AUa4S1CQvUs6R69hA.jpeg" /><figcaption>From the heavenly heights of great contextual inquiry to the dark hell fire of theoretical questions</figcaption></figure><p>The reason feature questions are dangerous is because a feature is usually one person’s particular solution to a much bigger problem. If we can get our teams to back up from a feature to the bigger problem, then we can come up with more solutions that are a better matched to the goals of our teams.</p><p>When users do come up with a feature (which they will), don’t worry. Just <strong>figure out why your users think their feature ideas are important and then use this ‘why’ to develop features with your team</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uUUqYqXK6Gn-nDbPPhACLA.jpeg" /><figcaption>When users do come up with a feature, work to understand the underlying problem.</figcaption></figure><h3>4. Start by watching out for 3 things*</h3><p>There are a lot of really good guides for field research that are beyond the scope of an article. The below list of three things will help you capture most of the experience breakdowns that are relevant to product design.</p><ul><li><strong>Routines — </strong>What rituals do they have? What do people do repetitively?</li><li><strong>Interrupts —</strong> What interrupts them? What disrupts their ﬂow?</li><li><strong>Transitions —</strong> Where do they transition? What are the in-between moments that connect disparate activities?</li></ul><h3>5. Watch 5–6 People Using Your Product</h3><p>When it comes to understanding how we can better solve the problems we’re trying to solve, watch 5–6 people. <a href="https://web.archive.org/web/20150905195919/http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">Research shows</a> that we can get to 80% of usability problems with this heuristic and its a great starting point. That is, as long as we do a good job deﬁning our user and recruiting the right participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*2Q9Lfo_zjevBbADqlqBUmQ.gif" /><figcaption>Them boys at Nielsen Norman know whatsup</figcaption></figure><p>Those are my guidelines for getting started for making research work when you need to ship.</p><p>Agree? Disagree? <a href="http://sajidreshamwala.com/">Check me out</a>, and Get at ya boi.</p><p><em>*This list of three things is a sub-set of a list presented by the brilliant </em><a href="https://www.youtube.com/watch?v=9TJTbRw4ri8"><em>Tomer Sharon</em></a><em>.</em></p><p><em>**A lesson taught to me by a brilliant mentor, </em><a href="https://www.linkedin.com/in/mkronthal"><em>Michael Kronthal</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fdbbc0b9fa2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iit-institute-of-design/lean-user-research-or-how-i-learned-to-do-research-when-trying-to-ship-1fdbbc0b9fa2">The Lean Research Sloppy Joe</a> was originally published in <a href="https://medium.com/iit-institute-of-design">Institute of Design (ID)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Of Monsters and Data Mayhem]]></title>
            <link>https://medium.com/@sajidresh/of-monsters-and-data-mayhem-bd0f33cca980?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd0f33cca980</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[animation]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Wed, 11 Nov 2015 08:41:41 GMT</pubDate>
            <atom:updated>2015-12-08T08:12:52.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CRfrBSKYe8PSVvp46b_8Aw.png" /></figure><h4>Bringing in delight when there aint no time for that.</h4><p>Our startup (<a href="https://www.skillshare.com/classes/design/Simple-Character-Animation/1750772942/projects/jut.io">Jut.io</a>) is building a data analytics tool for developers and its been as technically challenging as that first clause of this sentence would have you imagine. Over the past 6 months of product development, I’ve been trying to find opportunities to bring a human element to our app. While I believe that the core of product design is solving problems within constraints, I also believe that designers are forever the champion of the human and, unless there’s a concerted effort, products left to themselves will develop void of personality. After having addressed our baseline information architecture and ui concerns, I had just started to playing around with animation and experimenting with how animation could make an experience feel more human. It was true that Jut helps their users build dashboards that were at their core pragmatic but, if all of our dashboard’s quantitative data was an abstraction of more squishy qualitative data, why couldn’t a dashboard communicate with a user in a more personable way than just tiles of graphs and numbers? In the end, we got a totally bonkers, unexpected yet lovely monster into our product roadmap that looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CRfrBSKYe8PSVvp46b_8Aw.png" /></figure><p>Here’s how we did it.</p><h3>Finding an Opening</h3><p>Jut holds a quarterly hackday. Given our intense product development schedule, I figured this break from our sprint routine could be the perfect opportunity to try and build out a proof of concept that would bring personality to our app. I had the idea of making a data driven ‘character’ so I teamed up with one of our D3 developer/designers and started hashing out an idea. After agreeing that a simple proof of concept would be an animation driven by our user’s system data, we defined three simple states that we could use for our MVP: 1- your system dashboards is not receiving any data 2 — your dashboard IS receiving data and 3 — you have an alert.</p><p>With some exploring, I found a tutorial on animating sprite sheets with CSS. This gave me a start for building an animation that we could control with CSS and javascript and drive with data:</p><p><a href="http://blog.teamtreehouse.com/css-sprite-sheet-animations-steps">http://blog.teamtreehouse.com/css-sprite-sheet-animations-steps</a></p><p>To control our animation with code, we would export our animation frames from Adobe Photoshop into a sprite sheet using a web app (the internet is freaking beautiful):</p><p><a href="https://draeton.github.io/stitches/">https://draeton.github.io/stitches/</a></p><p>To see how the concept would play out, we created a Codepen prototype:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Frambolee%2Fembed%2Fpreview%2FyYazRQ%3Fheight%3D600%26slug-hash%3DyYazRQ%26default-tab%3Dresult%26host%3Dhttp%253A%252F%252Fcodepen.io&amp;url=http%3A%2F%2Fcodepen.io%2Frambolee%2Fpen%2FyYazRQ&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F155713.yYazRQ.small.7a2e86f9-1acb-4c96-a67a-83355e6e89f3.png&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/5b050eebd9e4efa95a79a1bb063821ec/href">https://medium.com/media/5b050eebd9e4efa95a79a1bb063821ec/href</a></iframe><h3><strong>Inventing Something We Could Own</strong></h3><p>After seeing that we could get a simple animation to work with code, it was time to build out a distinct, expressive character that could represent Jut. Luckily our product was still in beta and we were free to create a completely new character that matched the curves and color of our product. But what type of animal or creature was abstract enough to be relatable but articualted enough to be sufficiently expressive? Enter the Jut Monster. Because the number of different data types that can be brought into Jut were endless, we knew an imaginary character was the right move for our first attempt at a data driven creature. We started iterating on some ideas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*mR3lwBDC_b0emf7YMkXXcw.png" /></figure><p>I wanted something that could be active when it needed to grab a user’s attention yet understated when it needed to get out of the way. So, with iteration, we specked out our first three states.</p><p>During the passive state, our character would be quietly waiting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*rWXO5MKCCvfz9i680Md5iA.gif" /></figure><p>When receiving data, our monster would exhibit just enough movement to let a user know all is well:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*qIZ22jrTS52e3Z20Z81WiA.gif" /></figure><p>And, finally, when there was an error our monster would be attention grabbing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*hRx7E1bCM74jyPMiFqf_2A.gif" /></figure><p>After prototyping out how the animation worked, we were able to wire the Jut Monster up to our native coding language (Juttle). We could then see how he’d react to different situations that our users would run into.</p><p>The morning of the Jut hackday came around and it was time to share our idea with our team. The concept of bringing life into our product resonated with our team and we were voted the winner for the ‘necessary product feature before launch’ category. Our win with our engineering heavy team was an especially vindicating victory for universal appreciation of delight in product design and a vote of confidence that any product, no matter how technical, can use a touch of whimsy.</p><h3>Where to From Here</h3><p>Our next and final steps was to get the Jut Monster production-ready. This was the nuts and bolts piece of the equation and, with the support of our team, we were able to get him into our product roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hyWJnmSyE-6bbBAqGWtZiw.png" /></figure><p>From here, we’d like to create an open source version of the Jut Monster that could be driven by any data thats wired to a website or app. This is going to be uncharted territory for me so any words of encouragement and, more importantly, advice will be welcomed with opened arms from here :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd0f33cca980" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Algorithmic Expressiveness]]></title>
            <link>https://medium.com/@sajidresh/algorithmic-expressiveness-274a4db27a2e?source=rss-acefaf1f8a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/274a4db27a2e</guid>
            <category><![CDATA[posters]]></category>
            <category><![CDATA[generative-art]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sajid Reshamwala]]></dc:creator>
            <pubDate>Wed, 11 Nov 2015 07:36:16 GMT</pubDate>
            <atom:updated>2015-12-08T08:13:40.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*emUVU-tMYz3MvvB74INyxg.png" /></figure><h4>Designing with hands and programs</h4><p>So my brother and sister have birthdays a day apart on the 9th and 10th and I can usually get away with making a couple t shirts for my siblings but my sister decided to mix it up by getting engaged this year.</p><p>And I decided to take that mix and shake it vigorously by being kind of broke. Time to learn a new thing and try making some stuff. Hazaaa!</p><p>I knew I had our studio’s plotter at our disposal and having just worked through a <a href="https://www.skillshare.com/classes/design/Programming-Graphics-I-Introduction-to-Generative-Art/782118657/projects/22943?via=user-profile">generative art class on Skillshare</a> I thought, hey, why not make a super sweet poster? My sis and her fiance (that sounds weird) are a couple that’s always out and about adventuring. I figured I could use some of their recent exploits for inspiration. Here is a pic of their adorableness:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3WwxkIiJd5bM5-2So0y4aQ.jpeg" /><figcaption>My sister’s engagement flyer. Words are not enough.</figcaption></figure><p>For my atomic units of expressiveness, I figured I’d try and find something that was fun that could be broken down pretty easily into bits and pieces. I knew my sister and her fiance had recently gone on a trip to mexico so I decided to start with some oaxacan wood carvings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Bu0FceVi_DuQD1BzxnddSA.png" /><figcaption>Oaxacan wood carvings. What life you contain in your teak!</figcaption></figure><p>I took this guy and broke him into some basic shapes, ending up with this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ztSCCWSMAA5jNFhqSOGvRg.png" /><figcaption>vector outlines of most interesting oaxacan shapes</figcaption></figure><p>Afterwards I dropped my sister a text to discretely find out what things her and her fiance dug and pen-tooled out some sketches:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/208/1*VC0S34XGwSYfZet_9m3Ubg.png" /><figcaption>Things my sis loves</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/208/1*PzRJ5iEP-0zrXvJ3Oia65A.png" /><figcaption>Things her irish blooded fiance loves</figcaption></figure><p>At this point I knew I wanted to do some sort of totem or symmetrical reflection but I couldn’t figure out how to do it. I first tried to make a simple shape by reflecting some randomly placed vectors over ay axis, but I wasn’t ending up with anything sexy. Mostly I just ended up with something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*2d_qSngmbuzklq-hpL5OqA.png" /></figure><p>Alas! This wasn’t jivin so I thought I’d try some randomizing on a grid to see what could pop out. I played around with random pools of color and ended up with some pretty yet nice and messy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AEvkaydBsoL6NMcbWRsHZg.png" /></figure><p>Afterwards, iterated on some colors and played around with stroke weight. I started getting somewhere closer to where I wanted to end up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*emUVU-tMYz3MvvB74INyxg.png" /></figure><p>I couldn’t quite figure out what I wanted to put onto paper and that’s when I ran into a project by Shahib Amin (link at the bottom). I dug into his use of kaleidoscoping and I figured, what the heck, lets put a few hours in and use nodebox to work out some patterns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*7vpj-GkX1rHfBUMSM2KN9w.png" /><figcaption>first kaleidoscope test</figcaption></figure><p>and as I started getting the jib and jive of it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*f6rO8UkVAtXcoaUMG651eQ.png" /><figcaption>second round of kaleidoscoping</figcaption></figure><p>NOTE: For anyone trying to layout complex graphics on not so super mega machines, you’re probably dealing with some heavy render times. A great work around is to make an outline of the shape, use it to layout the design, and then replace it with the original more complex shape. Something lika dis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*c17qDEPmHNJNMVwamGmWBQ.png" /><figcaption>rig for testing out designs</figcaption></figure><p>So at this point I’ve got a few patterns, some a bit more complex thanothers, but I still needed something to pull it all together. So I figured this was a good place for some hand craftin’. Hm, how about a little sealy majig?:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*U6dmtI5ZGdFVZ0kJ_ZMPFg.png" /><figcaption>bespoke center seal to add a bit of craft to the piece</figcaption></figure><p>And babam, that was the cream that the poster sundae needed. After that, it was just a matter of laying out the different elements I’d built out and nailing the colors. NOTE: for people printing from a pdf, I had endless troubles when I started using any opacities or gradients at all and I had to resort to full 100% tones. If anybody has any solutions for printing opacities, holla at ya boy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*91IrsIl820-_7TyJi6R_rQ.png" /><figcaption>The Final Poster</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VA-7cNA1gJDX_nByreMiw.png" /><figcaption>Detailed Shot</figcaption></figure><p>I finally got a chance to print it and show it to my sis during our thanksgiving beach week. She tots dug it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*U5FAHnxodL9s7wjFF5o71g.png" /><figcaption>“Alas, when in the presence of such greatness all we can muster is a deep reflective gaze into the distance”</figcaption></figure><p>Of course now all I can think about is the million more ways I can apply this approach.</p><p>Thoughts? Feedback?</p><p>And those notes I promised:</p><p>Shahib Amin’s project:</p><p><a href="http://www.skillshare.com/classes/design/Programming-Graphics-Introduction-to-Generative-Art/782118657/projects/20432">http://www.skillshare.com/classes/design/Programming-Graphics-Introduction-to-Generative-Art/782118657/projects/20432</a></p><p>Nodebox Kaleidoscope tutorial:</p><p><a href="http://nodebox.net/blog/2013/01/kaleidoscope-tutorial/">http://nodebox.net/blog/2013/01/kaleidoscope-tutorial/</a></p><p>Update: I’ve finally figured out Github and uploaded my project files here:</p><p><a href="https://github.com/sajidsan/kaleidohype/blob/master/README.md">https://github.com/sajidsan/kaleidohype/blob/master/README.md</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=274a4db27a2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>