<?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 Jake Wells on Medium]]></title>
        <description><![CDATA[Stories by Jake Wells on Medium]]></description>
        <link>https://medium.com/@wells_jake?source=rss-1d8dff7c6d1f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1W9aHkkWzjLfFwJjXBmZ2A.jpeg</url>
            <title>Stories by Jake Wells on Medium</title>
            <link>https://medium.com/@wells_jake?source=rss-1d8dff7c6d1f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:40:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wells_jake/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[Evil, Wicked, Asynchronous Collaboration]]></title>
            <link>https://medium.com/@wells_jake/evil-wicked-asynchronous-collaboration-211e76a754ec?source=rss-1d8dff7c6d1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/211e76a754ec</guid>
            <dc:creator><![CDATA[Jake Wells]]></dc:creator>
            <pubDate>Tue, 25 Nov 2014 14:50:57 GMT</pubDate>
            <atom:updated>2015-12-29T14:55:23.257Z</atom:updated>
            <content:encoded><![CDATA[<h4>What is it and why you should care.</h4><h4><strong><em>What is Asynchronous Collaboration?</em></strong></h4><p>Asynchronous collaboration is the evil cousin of regular old collaboration.</p><p><strong>Asynchronous Collaboration: </strong>the collaboration between 2 or more people when actions are taken in separate time frames and physical locations. An example is emailing a client:</p><p>Sending the email is your action.</p><p>The client opening, reading, and responding to the email are their actions.</p><p>After reading your email and before responding, there exists time and space. Within that time and space, the client is engaging in collaboration with their own team and having conversations. By the time the email response is sent back by the client and read by yourself, the collaboration between yourself and the client becomes offset creating an instance of asynchronous collaboration.</p><p>With asynchronous collaboration, it is important to be conscience of how your team is collaborating and how effective that collaboration is. No longer is it ok to just say you collaborated as a team, now we must understand how that collaboration happened, the tools that were used, the time frame in which it happened, the structure, and the outcomes that occurred as a result. The reason it’s important to be aware of the details is because asynchronous collaboration can be evil. The evil can be found in our example where time and space occurs between you and the client.</p><h4><strong><em>Why is Asynchronous Collaboration evil?</em></strong></h4><p>Asynchronous collaboration is evil because, while necessary in all professional environments, it creates a whole slew of issues that can become sticky and anxiety ridden if not dealt with appropriately. In the example I used above “…After reading your email and before responding, there exists time and space<em>…</em>” a perfect situation for the evil side of asynchronous collaboration to rear its ugly head. As I described, the client collaborated internally with their own team in that space and time. In that internal collaboration, knowledge is gained by the client but not all the knowledge is shared back to you.</p><p>As we work autonomously, either as teams or as individuals, we think less about our remote collaborators and create gaps in knowledge and communication. During a project cycle these gaps can be detrimental to the success of the project. The mentality of ‘out of sight out of mind’ becomes a time issue, misalignment starts to occur and our project timelines slip. The more we work with off-site clients and remote teams the chances of this type of collaboration become more and more likely. When we communicate with our teams and clients in an asynchronous way, it is more likely that:</p><ol><li>Details will slip through the cracks</li><li>Emphasis &amp; Sentiment will be lost</li><li>Context will be misunderstood</li><li>Knowledge gaps grow</li></ol><p>Collaborating in this manner is unavoidable. As technology advances, it becomes less necessary for teams to be located in the same physical location and more necessary to create new/better ways to work remotely.</p><p>On a positive note, asynchronous collaboration has some redeeming qualities:</p><ul><li>It promotes autonomy, allowing individual collaborators to be flexible with their time when working toward project goals.</li><li>It fits well within the structure of an agile framework, in which a team of collaborators works individually toward specific goals leveraging the team and collaborating when necessary.</li><li>It is necessary with all client relationships and remote teams.</li><li>Tools for asynchronous collaboration, like email, have become ubiquitous.</li></ul><h4><strong><em>Why should you care?</em></strong></h4><p>You might be thinking that this isn’t something you specifically worried about previously, so why should you care now. You should care, because when asynchronous collaboration isn’t managed strategically it makes everyone’s job more difficult. Chances are that in some way asynchronous collaboration has been an issue in every project you’ve ever worked on, you’ve learned from those experiences and it has become second nature to your project habits. However, being aware of it can help alleviate some of the anxieties associated with:</p><ul><li><strong>Reaching Project Goals</strong></li><li><strong>Attaining Project Requirements</strong></li><li><strong>Processing &amp; Tracking Feedback</strong></li><li><strong>Team Alignment</strong></li><li><strong>Client Dictatorship</strong></li><li><strong>Holistic Project Vision &amp; Communicating Concepts</strong></li></ul><h4><strong><em>How can we solve for some of these issues?</em></strong></h4><p><strong>Reaching Project Goals</strong></p><p>This is a large topic of discussion. Reaching project goals is affected by asynchronous collaboration because time is one of the offending characteristics of asynchronous collaboration. For 99% of our project work time is a metric for project completion and profitability. Essentially, if collaboration is not working smoothly the pace of the project slows down quickly and makes hitting pre-defined project milestones difficult. Additionally, as those milestones and project goals get pushed out, more hours are used from an allocated budget that can quickly eat away at the project’s profit margin.</p><p>With web based tools like<a href="http://invisionapp.com/"> invision</a>, wireframes and designs can be uploaded as they are iterated on, linked together to create flows and allow commenting by collaborators. This way clients can access the designs on their own time as the designs are being created. They can comment and leave feedback directly on the design where they have questions or concerns. This starts to break down the problem of email and response. It allows the process to become more fluid between the designer and the client. All feedback can be housed in a single location creating transparency and accountability.</p><p><strong>Attaining Project Requirements</strong></p><p>We all know that it can be difficult attaining thorough details around business, functional and non-functional requirements. Or if we do get them, many times, they are incomplete or not very descriptive. These details are what define the constraints that allow us to be innovative and creative in our solutions. Even if we push for better requirements or make them a stipulation in the SOW, waiting for them can hinder a project’s progress.</p><p>No one likes waiting for or pleading for requirements. One solution is to make your own. Based on what the client is communicating to you, do your best to write and develop the project requirements. Allow them to be accessed in a collaborative space for the client to review, edit and react to. Many times creating a situation for the client to react with feedback is easier than asking them to take the first step toward action. This can be done in google docs, confluence or any type of collaborative web based tool. The important part to note is that a reaction to something does not account for the gaps in knowledge the client creates when they don’t share all the details with you. Creating requirements for your client to react to is a start in the right direction but not a full solution to the problem.</p><p><strong>Tracking Feedback</strong></p><p>Asynchronous collaboration can make tracking and processing feedback really difficult. If feedback is not being given in a common space it can be misaligned. If coming from multiple sources with differing opinions it can become confusing and debilitating. Asynchronous collaboration can make feedback become sporadic and take time. It can lose context. And it can get lost or buried in the daily email chains. As a result, appropriately processing the feedback can become extremely daunting.</p><p>Invision and other collaborative tools allows commenting to be done in context of the subject. It allows the collaborators, both client and designer to comment directly on the page creating a back and forth conversation that is viewable by all collaborators. This alleviates misaligned feedback by creating a single place to leave, view and track feedback. It won’t get lost in an email chain, and will remain as a recorded comment for the duration of the project if it needs to be revisited. It is important to note that these practices should be set upfront in a project so that they become habitual to all members of a team.</p><p><strong>Team Alignment</strong></p><p>One of the largest issues with our internal teams is that more and more we are working remotely across multiple time zones and countries. This makes collaboration and alignment really difficult. Working in separate physical locations naturally creates the situation for our work and thinking to become silo’d. Communication breaks down and suddenly all of our hands and feet are doing and thinking differently.</p><p>For remote teams, keeping up with changes in a fast paced project can be difficult. As the designers on a project iterate on the project, invision allows the same link to constantly be used. The designers just update the screens associated with the link. This way, all collaborators can constantly have an up to date view of the application or project. Project collaborators can access a page in invision that allows them to see changes and comments that have occurred since their last login.</p><p><strong>Client Dictatorship</strong></p><p>We’ve all had experiences with clients that remain absent to the project until it is time for them to swoop in and start barking orders. If for no other reason, they are paying us, so we must listen to them. However, it is not the best case scenario when attempting to collaborate creatively with your client and can even make the project feel completely non-collaborative.</p><p>I believe that a great solution for this is to gently invite your client into situations where the dynamics call for them to become a collaborator. This also means avoiding some situations in which they can fall back into their dictatorship. <a href="http://invisionapp.com/">Invision</a> does a great job of this. It serves as a common ground that belongs to the project rather than to either client or agency sides of the team. In a non-territorial, neutral space, collaboration becomes easier for everyone.</p><p><strong>Holistic Project Vision &amp; Communicating Concepts</strong></p><p>Asynchronous collaboration makes holistic project vision a difficult task. As I mentioned earlier it can lead to:</p><ul><li>Details slipping through the cracks</li><li>Emphasis &amp; Sentiment to be lost</li><li>Context to be misunderstood</li></ul><p>When working through big new concepts and attempting to communicate visions for entire solutions. These things are extremely important and extremely difficult to maintain. If our view of the project is different from our client’s, we will run into detrimental issues at some point during the project.</p><p>A solution that I’ve been using is to use <a href="http://invisionapp.com/">invision</a> to create a menu that outlines and allows access to all portions of the project. The menu can link to individual prototypes that show details of the experience, as well as. supporting materials, like visual designs, animations, user personas, research documents, and spreadsheets that outline use cases or requirements.</p><h4>In Review</h4><p>In most cases you wouldn’t want to choose to use asynchronous collaboration as a sole means for interaction between two individuals or groups. However, as technology allows us to collaborate more efficiently across time and space, asynchronous collaboration becomes an everyday reality we need to face. If we are aware of it and manage our interactions appropriately we can make sure our collaborations are successful and valuable for everyone involved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=211e76a754ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 5 design answers]]></title>
            <link>https://medium.com/@wells_jake/my-5-design-answers-77d6ec0b5c5f?source=rss-1d8dff7c6d1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/77d6ec0b5c5f</guid>
            <dc:creator><![CDATA[Jake Wells]]></dc:creator>
            <pubDate>Fri, 03 Jan 2014 18:55:21 GMT</pubDate>
            <atom:updated>2015-12-29T14:59:49.538Z</atom:updated>
            <content:encoded><![CDATA[<h4>An intro to my thoughts as a human centered product designer.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*ZYXT9XiwiITOUmj3Wc5pHw.jpeg" /><figcaption>This is me and my friend Pizza the cat reuniting. As you can see we are both excited to see each other.</figcaption></figure><h4><strong>Tell us who you are in one sentence.</strong></h4><p>I am a product strategist and human-centered designer hovering at the intersection of design, technology and business, hellbent to develop new products and business models that create amazing value and make the lives of people happier and healthier.</p><h4><strong>If you weren’t a designer, what would you do?</strong></h4><p>If I was not a designer I’m not sure what I would be doing…it’s hard to say. Part of my personality, as a designer, is to dream and so I feel like there are an endless amount of things that I would love to do and could fully see myself doing. Some of those include: Motorcycle Builder, Carpenter, Diamond Thief, National Geographic Photographer, Farmer, Writer, Time Traveler and the list goes on. Honestly I believe that no matter what I would be doing, a design mentality would play a role, it’s just who I am and not so much who I’ve chosen to be. I’ve chosen to be a UX designer as my current role and I’ve developed specific hard skills over the years, but my soft skills as a designer were born and bred into me…Thanks mom and dad!</p><blockquote>“If I was not a designer…Motorcycle Builder, Carpenter, Diamond Thief, National Geographic Photographer, Farmer, Writer, Time Traveler, and the list goes on. Honestly I believe that no matter what I would be doing, a design mentality would play a role, it’s just who I am and not so much who I’ve chosen to be.”</blockquote><h4><strong>What is something you wished you designed, either because you love it, or because you feel you could have done it better?</strong></h4><p>I get excited about great design. For instance, I love Rdio. I think that as far as streaming music services go they are above and beyond doing it right. However, <strong>I’ve never wished I could have designed something that I love (out of envy), nor do I wish to design something better than someone else. </strong>To me design, in its most simple form, is an approach to problem solving. This said, even if I were to approach a problem that someone else already has, in an attempt to design their product/service better, my solution would ultimately be different than theirs. The reason for this is that my understanding of the problem being solved would be different and so the result would be different and any number of other factors could be different. This is where innovation comes from, not trying to have a “better design”, but a better understanding of the ultimate underlying problem (better design will follow).</p><h4><strong>What was your biggest design mistake?</strong></h4><p>As a professional designer I feel as though I have to constantly walk a line between allowing myself to be vulnerable and empathetic –while also– maintaining an air of confidence through the display of “expert opinion” or “best practices” in regard to design problems. The caviat there is that as a designer it is my opinion that we are not experts in any sort of specific problem (all problems are different), but people look to us to be those experts. I believe designers are experts in process and approach, the ingredients to finding the solutions. This said, designers are often forced into professional situations, whether it be for gaining an account or calming a client, that require us to “act” as experts when we are not. The mistakes come when you find yourself being pulled off the invisible line that separates vulnerability and confidence, but it does happen and it has happened to me. The important part is to recognize when it is happening and have the ability to react appropriately.</p><h4><strong>What advice would you give someone entering the design field?</strong></h4><p>My advice would be to just concentrate on doing great work that ultimately makes the people you are designing for happy (usually that’s not the client). In addition, always track your assumptions, aggressively test against them as if you are in fact wrong, and always be willing to change (letting go of a bad idea is the only thing that will allow you to move on to a good idea).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77d6ec0b5c5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>