<?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 Matthew Voshell on Medium]]></title>
        <description><![CDATA[Stories by Matthew Voshell on Medium]]></description>
        <link>https://medium.com/@mvoshell?source=rss-cc843ab86cbc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sbWXUP322-Mb7D49ewAgdQ.jpeg</url>
            <title>Stories by Matthew Voshell on Medium</title>
            <link>https://medium.com/@mvoshell?source=rss-cc843ab86cbc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:43:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mvoshell/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[Reinventing the Way We Work]]></title>
            <link>https://medium.com/@mvoshell/reinventing-the-way-we-work-759d488c0273?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/759d488c0273</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Wed, 15 Mar 2023 04:49:17 GMT</pubDate>
            <atom:updated>2023-03-22T17:43:46.262Z</atom:updated>
            <content:encoded><![CDATA[<h4>Agile Pods 2.0 and the Future of A.I.-Driven Product Teams</h4><p>Recent advancements in generative AI is ushering in a radical transformation to the structure of agile pods. It will completely reinvent what it means to be a “product team” and how we approach designing, developing, and shipping digital experiences.</p><p>Companies will be required to shift away from building extensive teams comprising of dozens, or even hundreds, of engineers and designers aimed at completing tasks quickly while maintaining low costs.</p><p>Instead, a new model will arise of small globally distributed teams. They will comprise of three or four highly-skilled individuals with complementary skill sets.</p><h4>Approach</h4><p>Three focus areas will be:</p><ul><li><strong>Product </strong>a person with a range of skills, from psychology to art</li><li><strong>Engineering</strong> skilled in machine learning and various programming languages</li><li><strong>Artificial Intelligence</strong> It handles tasks such as development, testing, design, quality assurance, and accessibility.</li></ul><blockquote><strong>TL:DR</strong><br><em>The future of agile product development involves a complete reimagination of what it means to be a team, and the integration of OpenAI’s GPT-4 to create teams of just a few highly skilled individuals with transferable skill sets and strong emotional intelligence.</em></blockquote><p>The use of AI in product development will enable for the automation of (efficient) repetitive and mundane tasks. This will allow the team to focus on more complex and creative work, hence multiplying efficiency and productivity.</p><p>These smaller pods will also be easier to coordinate and manage, as decisions can be made rapidly with streamlined communication lines that will reduce costs, increase productivity, and support teams to produce quality product experiences that actually meet the end-user’s needs.</p><h3>Roles</h3><h4>Product</h4><p>The Product role of the future agile pod will require a diverse skill set that ranges from psychology to art. This person will hold a key position in the team structure and be equipped to function at all levels of the digital experience process, including strategy, tactics, and operations. They will be responsible for overseeing the digital experience and ensuring that it meets the desired standards laid out in the beginning.</p><p>They will possess the ability to put themselves in the shoes of the end-users and create an empathetic digital experiences. Product will ensure that the experience both meets the desired business outcomes and the end-users’ needs. <strong>Ensuring a human point of view for the product experience will be the most critical responsibility.</strong></p><h4>Engineering</h4><p>The engineer will possess a range of skill sets, from machine learning and programming to networking. They will be responsible for the technical aspects including solving any problems that may arise.</p><p>Moreover, their skill sets will include “tuning” and correcting the AI when it malfunctions or goes off the rails when the AI’s output is not meeting the desired results. They’ll make the necessary corrections and ensure the optimal performance of the AI. Ultimately engineers will spend most of their time debugging technical issues and automating tasks that the AI can perform.</p><p>In situations of doubt or where the AI is not capable of performing the assigned tasks, the Engineer will know how to manually override and fill in whatever is necessary. This means that they will have a broad range of skills that allows them to make any last-minute adjustments and ensure that the project delivers the expected outcomes.</p><h4>Artificial Intelligence</h4><p>AI will play a central role in the development process as it will handle several essential aspects for the agile pod.</p><p>In addition to being developers, AI technology will also perform testing, design work, quality assurance, accessibility testing, and more, all rolled into one. The integration of AI into the product team will bring many benefits in terms of improved efficiency, accuracy, and innovation.</p><p>Lastly, AI will fundamentally change the way agile pods approach designing for accessibility. It will automate critical tasks such as alt-tagging images, saving time and minimizing human error. Teams will more quickly and easily ship an accessible digital experience that caters to all users’ needs, regardless of any limiting factors.</p><h4>Conclusion</h4><p>AI technology will play an increasingly vital role in the future of product development. It will automate many essential tasks, such as design, testing, and accessibility, freeing up human workers to focus on more complex tasks, allowing the development process to be more efficient and cost-effective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=759d488c0273" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finally Learning to Code]]></title>
            <link>https://medium.com/series/finally-learning-to-code-202f587dfb99?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/202f587dfb99</guid>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sat, 31 Mar 2018 18:52:05 GMT</pubDate>
            <atom:updated>2018-03-31T19:12:51.172Z</atom:updated>
            <content:encoded><![CDATA[<p>MY CODING JOURNEY</p><p>Thanks for checking out this story and joining along on my journey to learn to code! I’ll be updating from time to time on the progress and share projects I create!</p><p>CHALLENGE</p><p>I’ve been putting it off for a long time; to some degree on purpose as not to limit the possibilities of my imagination</p><p>PROBLEM</p><p><a href="https://medium.com/u/89a1103c5c78">Framer Team</a> is finally a product I can use to express a design in my head in a dynamic way… but I recognize not understanding object oriented languages is hindering my ability and I’m just hacking away at prototypes</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLuI9UhhkDj6nx6U1tCwSg.png" /><figcaption>BEATMIX FRAMER PROTOTYPE</figcaption></figure><p>SOLUTION</p><p>I’ve tried books and bootcamps are expensive. Then I discovered <a href="https://medium.com/u/fb8d78e7d205">Treehouse</a> and it has been amazing.</p><p>The mix of video instruction, quizzes, and code challenges makes it really approachable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUQVh246AwqFi_x6XWVUNQ.png" /><figcaption>TREEHOUSE JAVASCRIPT COURSE</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wY4hUQESqHasixaSezEO9A.png" /><figcaption>Phaser.JS Game</figcaption></figure><p>Like halfway through and getting more into the basic programming concepts like variables, data types and conditional statements</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=202f587dfb99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Design Kickoff Checklist]]></title>
            <link>https://uxdesign.cc/product-design-kickoff-checklist-16dac082dccf?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/16dac082dccf</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sat, 27 May 2017 19:34:10 GMT</pubDate>
            <atom:updated>2017-05-31T05:10:41.611Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>The information designers should make sure they have to consistently create amazing products</em></h4><p>After completing a project I always perform a retrospective from a design aspect to understand what could have been done better. Often times these issues I discover tend to be challenges that other designers and companies are also dealing with.</p><p>The main issue I’ve noticed lately with products that flop is that they fail because they try to build a solution before <strong>truly understanding the problem</strong>. Stop me if you’ve heard this before.</p><p>But if you want to truly define the problem what info do you need? Where do you even start? Your goals for this initial stage involves answering the following:</p><ul><li>What’s the problem statement?</li><li>Who’s going to use it?</li><li>What are their processes?</li></ul><p>Obtaining this data is often seen as a “waste of time” or something that delays wireframes or designs from being created. And in a sense, yes, if you attempt to answer the questions above it will indeed annoy your project managers and make your stakeholders anxious. But much like amazing food at a 5 star restaurant, good things come to those who wait.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_aa4mxVbFl6LB9BFGVCovQ.png" /><figcaption>Product Design Kickoff Process</figcaption></figure><p>The research collateral you’ll have at the end of this process are:</p><ul><li>Product Story</li><li>Personas</li><li>Workflow diagrams</li><li>Product Story Map</li></ul><p>These items will play a pivotal role in establishing a foundational understanding around the problems you should be solving with a product.</p><p>No matter how hard you are pressured as a designer you should never attempt to design a product without at least a cursory understanding of the above.</p><h3>Deliverables</h3><h4>Product Story</h4><p>What is the target for this product? What problem is going to solve? In a meeting, known as a kickoff, the product team, stakeholders, and users should establish the product story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7MJn-WxrdpRZVhP-_ejFA.png" /><figcaption>Trello product story</figcaption></figure><p>A product story should only be 1 or 2 sentences. Consider this the product’s “elevator pitch”. This story will set the scope and target for what the product will actually look to do.</p><h4>Personas</h4><p>Who is actually going to use this product? Understanding your users and their behavior, both quantitatively and qualitatively, will impact the usability and functionality of your product. Building <a href="https://www.usability.gov/how-to-and-tools/methods/personas.html">personas</a> will come from data obtained through <a href="https://www.usability.gov/how-to-and-tools/methods/contextual-interview.html">contextual user interviews</a>.</p><blockquote>If you are designing for everyone you’re designing for no one</blockquote><h4>Workflow Diagrams</h4><p>How do the users work? What are their processes? Also obtained through contextual user interviews <a href="https://www.lucidchart.com/pages/workflow-diagram">workflow diagrams</a> are the steps the identified persona’s take to complete a task or goal.</p><h4>Product Story Map</h4><p>Which features / use cases should be considered within the product design? A <a href="http://jpattonassociates.com/user-story-mapping/">product story map</a> helps understand the epics and user stories that should be considered. Referred to as <em>situational design</em> by Don Norman in <strong>Living With Complexity</strong> the product story map is master backlog for all use cases matched to persona’s workflows that are required to be addressed by design.</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=16dac082dccf" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/product-design-kickoff-checklist-16dac082dccf">Product Design Kickoff Checklist</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[Product Design Playbook]]></title>
            <link>https://uxdesign.cc/product-design-playbook-103d3a5cf2e3?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/103d3a5cf2e3</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sat, 27 May 2017 17:33:58 GMT</pubDate>
            <atom:updated>2017-06-23T20:11:44.372Z</atom:updated>
            <content:encoded><![CDATA[<h4>Concepts and Methodologies To Live By</h4><p>At the time I’m writing this post, I’ve been a full-time product designer for ~3 years, though my overall professional career is closer to ~8 years. Every couple of months I would sit down and braindump lessons learned and methodologies I’d absorbed from work, Meetups, articles, podcasts, etc.</p><p>As a believer in paying it forward I am sharing everything here in the hopes that it becomes a reference point not only for myself but for any product designer, experienced and inexperienced alike. My hope is for the inexperienced to learn concepts needed in the modern agile product design environment. The experienced can use it as a place to help demystify design for coworkers and higher-ups.</p><p>Every so often I’ll continue to update this; a living document to grow as I continue to become the best product designer I can be. Enjoy!</p><h3>User Experience Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/0*1uN9O5hLpvH7qIBi." /></figure><p><a href="https://www.nngroup.com/articles/definition-user-experience/">Nielsen Norman Group defines</a> <em>User Experience (UX) Design</em> as “encompassing all aspects of the end-user’s interaction with the company, its services, and its products.”</p><p><a href="https://www.usability.gov/what-and-why/user-experience.html">Usability.gov defines</a> it as “focusing on having a deep understanding of users, what they need, what they value, their abilities, and also their limitations.”</p><p>User Experience Design places a value on business goals and objectives of the group managing the project in addition to user requirements. Designers’ overall goal should be focused on increasing user satisfaction through engaging interactions with their product, functionally and aesthetically.</p><h4>UX Design Facets</h4><p>Peter Morville at Semantic Studios <a href="http://semanticstudios.com/user_experience_design/">defines</a> the various pillars of user experience design as:</p><p><strong>Useful</strong> Your content should be original and fulfill a need<br><strong>Usable</strong> Site must be easy to use<br><strong>Desirable</strong> Image, identity, brand, and other design elements are used to evoke emotion and appreciation<br><strong>Findable</strong> Content needs to be navigable and locatable onsite and offsite<br><strong>Accessible</strong> Content needs to be accessible to people with disabilities<br><strong>Credible</strong> Users must trust and believe what you tell them</p><p>User Experience Design is actually comprised of various specialties executed together including:</p><p><strong>Visual Design: </strong>the use of imagery, color, shapes, typography, and form to enhance usability and improve the user experience</p><p><strong>Information Architecture: </strong>organizing, structuring, and labeling content in an effective and sustainable way. The goal is to help users find information and complete tasks.</p><p><strong>Content Strategy: </strong>planning, creation, delivery, and governance of content. Content not only includes the words on the page but also the images and multimedia that are used</p><p><strong>Interaction Design:</strong> the design of the interaction between users and products</p><p><strong>Usability: </strong>the degree to which something is able or fit to be used.</p><p><strong>User Research:</strong> understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies.</p><h3>Ethnographic User Research</h3><p>Understanding the people who will use a product is a key first step in trying to create empathy and influence what the initial problem statement will be. A technique known as Ethnographic Research allows designers to get a clear picture of the user’s problems and processes.</p><p>Claude Lévi-Strauss in his 1963 book <a href="https://www.amazon.com/Structural-Anthropology-Claude-Levi-strauss/dp/046509516X"><em>Structural Anthropology</em></a> said that, “Ethnography consists of the observation and analysis of human groups considered as individual entities (the groups are often selected, for practical and theoretical reasons unrelated to the nature of the research involved, from those societies that differ most from our own). Ethnography thus aims at recording as accurately as possible the perspective modes of life of various groups.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*6EFpDx66VdlzfUEM." /></figure><p>The groups Lévi-Strauss mentions are known today as personas. Personas allow for the generic concatenation of user data from both a qualitative and quantitative perspective. To many project managers this observational method may appear inefficient but it’s a very important exercise that informs designers about the context in which customers would use a new product and the meaning the product should hold in their lives or jobs.</p><h4>Ethnographic Study</h4><p>A user interview, where a designer sits down with a user to discuss their problems and processes, is known as an Ethnographic study.</p><p>Study findings provide an understanding of user behaviors, needs, and motivations using observation techniques, task analysis, and other feedback methodologies. Depending on the situation and required information various research techniques are available including surveys, A/B testing, focus groups, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uzKBMsrFz2IDeKcX." /></figure><p><a href="https://www.nngroup.com/consulting-field-studies/">Nielsen-Norman Group defines</a> Ethnographic studies as “the best way to learn about your customers’ goals and needs. Visiting people in their own environment can help you learn very different kinds of information from that collected in usability labs or other methods. They are commonly known as “field studies” and “contextual inquiries”.</p><p>There are 4 research keystones that inform long term product strategy:</p><ul><li>Identify user needs that have yet to be met</li><li>Test market demand for products that do not exist</li><li>Provide a holistic view of a problem space</li><li>Expose opportunities for competitive differentiation</li></ul><h4>Challenges</h4><p><a href="https://www.nngroup.com/consulting-field-studies/">Nielsen Norman Group points out</a> that despite the unique insights gained from field studies, few organizations take advantage of this technique — usually due to some combination of the following:</p><ul><li>Lack of understanding of the importance of this technique</li><li>Uncertainty about how to plan and conduct a field study</li><li>Misconceptions that it will be too time-consuming or expensive</li><li>Difficulty in interpreting the piles of data collected</li></ul><p>One specific challenge faced within organizations is that user research is not entirely a quantitative process. You don’t get lots of neat numbers, graphs and figures at the end. User research is very much a predominantly qualitative process. It produces lots of unstructured data that can be hard to summarize. It’s also difficult to prevent bias from creeping into the research process. Bias can cause our own understanding of something to introduce a lack of objectivity. To help prevent bias delve into the user much like a character actor does. Your goal should be to understand them and their contribution to your research. It’s never a good idea to assume that all interviewees view problems they face similarly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*JBk_xHVTx7BPTrSg." /></figure><h4>Interviewee Interaction</h4><p>User research begins by developing a relationship with the interviewee. Developing a level of rapport helps show you possess empathy and understanding with that person. When they feel comfortable with you they tend to be more honest when participating in the process.</p><p>Take the time to introduce yourself prior to starting. Explain what’s going to happen and invite questions from the start. Make sure you are engaged in the conversation throughout and thank them for taking the time when finished.</p><h4>Interview Strategy</h4><p>If the interviewee states they took an action or made a judgment call but do not explain their motivation, this is an opportunity to ask “why” to explore if you can find a root cause to truly address their problems within their existing processes.</p><p>Each time you ask “why” you get someone to re-evaluate their position and dig a little deeper into their own reasoning. It can seem odd to keep asking “why” at first but it brings great insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ixBimNVX228badlY." /></figure><p>If the interviewee mentions something often or seems to trigger a strong emotional response to a topic that is also an indicator of something you’ll want to spend time exploring to discover new opportunities or problems that aren’t currently being addressed.</p><p>Bonus points if you are forward thinking and book a room with a whiteboard. Don’t be afraid to ask the interviewee to sketch out a particular process. It’ll be more accurate and, honestly, it saves you from drawing it later on. It doesn’t need to be perfect and, if they won’t, you can just draw it following their instruction. This tends to help the interviewee wrap their head around a bigger picture instead of just focusing on one aspect of a process or software that doesn’t hold great value across personas.</p><h3>Human-Centered Design</h3><h4>What is Human-Centered Design</h4><p>Human-Centered Design aligns what your users and your team members want, with what is technically feasible and financially viable. It can be applied to both physical and digital products.</p><p>It is one of the best pathways to products that are embraced by users whilst also meeting an organization’s business goals.</p><p>It’s an approach that helps make sure new products are tailor-made to meet people’s needs and wants. It is achieved when the following pillars of the methodology intersect:</p><p><strong>Desirability</strong>: What do people desire?</p><p><strong>Feasibility</strong>: What is technically and organizationally feasible?</p><p><strong>Viability</strong>: What can be financially viable?</p><p>This methodology is flipping the heart of product design from system-focused to human-focused. That means building a product thats interaction fits the way a particular persona works instead of requiring the user to learn new processes through documentation in order to conform to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a5tf9Stiec_2-F-C." /></figure><p>HCD can generate insights about both your target users and internal stakeholders through the following activities:</p><ul><li>User testing and interviews</li><li>Focus groups</li><li>Behaviour analysis</li><li>Digital analytics</li></ul><p>Human-Centered Design is really all about building <strong>empathy</strong> for every person involved in the product design process. This way the final product is tailored as close as it can be to meeting user and stakeholder needs. It maye take a few iterations of the design process to finally understand a problem or create an user-accepted solution.</p><h3>Design Thinking</h3><p><a href="https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process">Interaction Design Foundation describes</a> Design Thinking as “a design methodology that provides a solution-based approach to solving problems. It’s extremely useful in tackling complex problems that are ill-defined or unknown, by understanding the human needs involved, by re-framing the problem in human-centric ways, by creating many ideas in brainstorming sessions, and by adopting a hands-on approach in prototyping and testing.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*6toxsrJEdVIt_tnVjDVQUw.png" /></figure><p>It draws upon logic, imagination, intuition, and systematic reasoning to explore possibilities of what could be and to create desired outcomes that benefit the target user.</p><p>Design thinking can greatly reduce uncertainty to facilitate lasting and innovative products by regularly engaging with users using rapid prototypes to learn, test, and refine designs. It’s important to understand these insights are gained through real-world experiments and not just analytical data or marketing research. Research data can tell you “what” but only real-world experimentation will tell you “why”.</p><p>“<em>Design thinking is a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success</em>.” — Tim Brown, president and CEO, IDEO</p><h3>Rapid Prototyping</h3><p>A process that uses rapid iteration to get to a product that will add the maximum value to the user. It is a cyclical concept where you move through each stage to the next and when you reach the end, you return to the beginning (over and over again) until you have the result that you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*GN1fyjaPuuxO1Ltf." /></figure><p>Rapid prototyping is to let your users / clients know the objective of the prototype.</p><p>It is also very important to explain to them that ultimately, the prototype is not the actual solution. This avoids confusions and encourages feedback from the clients. The other thing to keep in mind is, it is not necessary to prototype every single feature of the application.</p><p>Analyze the application carefully in breadth and depth and make a list of the features that you feel users will use the most and then prioritize the features that needs to be prototyped.</p><h3>Tactical Design Critique</h3><p>TDCs allow us to quickly get a shared sense of how we feel about an existing design, what might need to be done about it — and also grow stronger as a team while we’re at it.</p><h4>Objectives</h4><ul><li>List of tensions around the current design</li><li>Tackle either tactically or strategically</li><li>Team members have a chance to voice their opinions</li><li>Shared understanding around parts of our user experience</li></ul><h4>Process</h4><ol><li>Design presented for entire group on TV</li><li>Round Robin; Each person shares only 1 tension</li><li>Repeat / Skip</li><li>Cross Talking Prohibited</li><li>30 min limit</li></ol><h4>Participant Guide</h4><ul><li>What is the problem we’re trying to solve?</li><li>Make sure you understand the problem before providing feedback (don’t be afraid to ask for clarification)</li><li>Stay focused on what was asked</li><li>Be honest and constructive</li><li>Tie feedback to business/user goals</li><li>Be positive + negative</li><li>Don’t try to solve the problem; just express tensions</li></ul><h3>Agile, Scrum, and Kanban</h3><h4>Agile</h4><p><a href="https://www.agilealliance.org/agile101/">Agile Alliance defines</a> Agile as “the ability to create and respond to change in order to succeed in an uncertain and turbulent environment.” A Manifesto with 12 principles was written in February of 2001 by 17 software practitioners.</p><h4>Manifesto’s 12 Principles</h4><ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</li><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</li><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</li><li>Business people and developers must work together daily throughout the project.</li><li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</li><li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</li><li>Working software is the primary measure of progress.</li><li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</li><li>Continuous attention to technical excellence and good design enhances agility.</li><li>Simplicity — the art of maximizing the amount of work not done — is essential.</li><li>The best architectures, requirements, and designs emerge from self-organizing teams.</li><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.</li></ul><h3>Scrum</h3><p><a href="https://www.scrumalliance.org/why-scrum">Scrum Alliance defines</a> Scrum as “an Agile framework for completing complex projects. Scrum originally was formalized for software development projects, but it works well for any complex, innovative scope of work.”</p><h4>The Scrum Framework</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*EVanNKGIEjGHXIgI." /></figure><ul><li>A <strong>product owner</strong> creates a prioritized wish list called a product backlog.</li><li>During <strong>sprint planning</strong>, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.</li><li>The team has a certain amount of time — a <strong>sprint</strong> (usually two to four weeks) — to complete its work, but it meets each day to assess its progress (<strong>daily Scrum</strong>).</li><li>Along the way, the <strong>ScrumMaster</strong> keeps the team focused on its goal.</li><li>At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a <strong>stakeholder</strong>.</li><li>The sprint ends with a <strong>sprint review</strong> and <strong>retrospective</strong>.</li><li>As the next sprint begins, the team chooses another chunk of the <strong>product backlog</strong> and begins working again.</li></ul><p><a href="http://www.scrumguides.org/scrum-guide.html">The Scrum Guide lists</a> 3 pillars that uphold every implementation of empirical process control.</p><h4>Transparency</h4><p>The entire process must be visible to those responsible for the outcome. Transparency requires a shared understanding and goals. For example “A common language referring to the process must be shared by all participants” and; “Those performing the work and those accepting the work product must share a common definition of “Done””</p><h4>Inspection</h4><p>Participants should frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work. This is typically performed at the end of a sprint in a retrospective group session.</p><h4>Adaptation</h4><p>If an inspector determines that one or more aspects of a process deviate outside acceptable limits and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.</p><h3>Kanban</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lUqP6BI8XNOK7zU9." /></figure><p><a href="https://leankit.com/learn/kanban/what-is-kanban/">According to Leankit</a> Kanban is Japanese for “visual signal” or “card.” Toyota line-workers used a kanban (i.e., an actual card) to signal steps in their manufacturing process. The system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when. It also standardized cues and refined processes, which helped to reduce waste and maximize value.</p><p><a href="https://www.scrumalliance.org/community/articles/2014/july/scrum-vs-kanban">Scrum Alliance describes</a> four core principles that Kanban follows:</p><h4>Visualize work</h4><p>Create a visual model of work and work flow, so as to observe the flow of work moving through the Kanban system. Making the work visible, along with blockers, bottlenecks, and queues, instantly leads to increased communication and collaboration.</p><h4>Limit Work In Process</h4><p>Limit how much unfinished work is in process and reduce the time it takes an item to travel through the Kanban system. Problems caused by task switching and the need to constantly reprioritize items can be reduced by limiting WIP.</p><h4>Focus on Flow</h4><p>By using work in process (WIP) limits and developing team-driven policies, the Kanban system can be optimized to improve the smooth flow of work, collect metrics to analyze flow, and even get leading indicators of future problems by analyzing the flow of work.</p><h4>Continuously Improve</h4><p>Once the Kanban system is in place, it becomes the cornerstone for a culture of continuous improvement. Teams measure their effectiveness by tracking flow, quality, throughput, lead times, and more. Experiments and analysis can change the system to improve the team’s effectiveness.</p><h3>User Story</h3><p><a href="https://www.interaction-design.org/literature/article/user-stories-capturing-the-user-s-perspective-quickly-and-simply">According to Interaction Design Foundation</a> a User story is used to “facilitate the functionality of a system but can be used in any environment to ensure that design and development are focused on user needs.” It focuses on the who, what and why, never how. User stories are structured as the following:</p><p><em>As a [</em><strong><em>persona</em></strong><em>], I want to [</em><strong><em>goal</em></strong><em>], so I can [</em><strong><em>motivation</em></strong><em>].</em></p><p>Understanding the motivation helps because:</p><ul><li>it gives clarity as to why a feature is useful;</li><li>it can influence how a feature should function;</li><li>it can give you ideas for other useful features that support the user’s goals.</li></ul><h4>Story Sizing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/0*yj_1llK_2Zaw1WKM." /></figure><p>In an attempt to understand the total effort required to complete a story, points are assigned. Points are the unit of measurement for expressing the overall effort required to complete the acceptance criteria for a user story or any other piece of work.</p><p>They are assigned using the fibonacci sequence (1,2,3,5,8,13…). 1 story should equal 1 point for 1 day of work. A 3 would merely mean 3x the effort, not necessarily 3 days.</p><p>Because story points represent the effort to develop a story, a team’s estimate must include everything that can affect the effort. That could include:</p><ul><li>The amount of work to do</li><li>The complexity of the work</li><li>Any risk or uncertainty in doing the work</li></ul><p>A story point estimate must include everything involved in getting a product backlog item all the way to done. If a team’s definition of done includes creating automated tests to validate the story (and that would be a good idea), the effort to create those tests should be included in the story point estimate.</p><p>Stories estimated at very large sizes are called Epics. Epics are made up of smaller journeys. Journeys are made up of many stories. So it goes:</p><p>Epic -&gt; Journey -&gt; Story</p><p>These organizing principles are used when building a Product Story Map.</p><h3>Agile Sprints</h3><p>Scrum.org <a href="https://www.scrum.org/resources/what-is-a-sprint-in-scrum">describes</a> a Sprint as <em>a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/0*rz86MVwa_A2w-lI8." /></figure><p>Sprints events include Planning, Daily Scrums, Review, and Retrospectives. Any stories not completed within the assigned sprint are pushed to the following sprint to be completed first or sent to the backlog to for inclusion in a future sprint.</p><p>During an Active Sprint:</p><ul><li>No changes are made that would endanger the Sprint Goal;</li><li>Quality goals do not decrease; and,</li><li>Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.</li></ul><p>Sprints help to determine predictability of team velocity through inspection and constant fluctuation of progress toward a sprint goal while also reducing risk of misapplying effort towards an invaluable goal.</p><h4>Sprint Planning</h4><p>Sprint planning helps product teams determine which stories should be targeted for completion in the upcoming sprint by adding them to a sprint backlog list. The session is moderated by a scrum master who ensures the session is conducted within a time-box of ~45 min.</p><p>As stories are added to the sprint backlog from the product backlog the product team should be cognizant of the total number of points added to a sprint much in the way a baseball manager monitors the number of pitches thrown by a pitcher. Using the team’s prior sprint velocity as a barometer, make sure not to set unrealistic goals by over stuffing the sprint backlog. Yet with each successive sprint the scrum master should increase the sprint target story point completion by 5% to continually push team speed and productivity.</p><p>Once the session is complete there is now a clear window into what stories will be targeted during the sprint. This also provides a window for stakeholders by setting expectations for what should be completed during the sprint.</p><p>Once the sprint starts the stories in the sprint backlog are locked for that sprint. Any planning after this is applied to the next sprint.</p><h4>Backlog Grooming</h4><p>Backlog Grooming is a session where the product team in collaboration with stakeholders prioritize, add, or remove user stories in the product backlog. Prioritizing the backlog includes arranging the stories with the highest priority at the top and lowest priority at the very bottom. Grooming sessions are occur prior to the start of the next sprint.</p><p>Beware that this is generally an informal session and should not be viewed as a status meeting.</p><p>Backlog Grooming includes the following elements:</p><ul><li>Attendees include the Scrum Team and key stakeholders invited by the Product Owner;</li><li>The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;</li><li>The Product Owner discusses the Product Backlog as it stands. They will estimate the likely completion dates based on progress to date (if needed);</li><li>The entire group collaborates on what to do next, so that the backlog grooming provides valuable input to subsequent Sprint Planning;</li><li>Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,</li><li>Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.</li></ul><p>The result of backlog grooming is a oft revised product backlog that alludes to the probable stories for the next sprint. The Product Backlog may also be adjusted overall to meet new opportunities.</p><h4>Sprint Retrospective</h4><p>Scrum Guides <a href="http://www.scrumguides.org/scrum-guide.html#events-retro">describes</a> the sprint retrospective is “<em>an opportunity for the [Product] Team to inspect itself and create a plan for improvements to be enacted during the next Sprint</em>.”</p><p>At the completion of each and every sprint the product team should gather for an informal session for a formal opportunity to focus on inspection and adaptation of the sprint process. All members of the team, including the scrum master, participates.</p><p>Topics considered:</p><ul><li>Evaluate how the last sprint went with regards to people, relationships, process, and tools;</li><li>Identify aspects of the process that went well along with any potential improvements.</li><li>Initiate next steps to implement approved improvements</li></ul><p>At the conclusion of the session the team should have identified improvements to review and implement in the upcoming sprints.</p><h4>Scrum Huddle</h4><p>A scrum huddle is a daily 15 minute session lead by a scrum master where a product team can synchronize. Huddles are used to understand progress toward a sprint goal and to inspect how progress is trending toward completing the work remaining in the sprint backlog. The huddle is held at the same time and place each day to reduce complexity. The scrum master is responsible for ensuring that only product team members participate in the huddle and not stakeholders.</p><p>The team’s updates touch on three points:</p><ol><li>What stories did you complete yesterday?</li><li>What stories will you focus on completing today?</li><li>Are there any impediments preventing you from completing anything?</li></ol><p>A huddle increases the probability that the product team will meet their sprint goal. On a daily basis the team should understand how it intends to work together as a self-organizing group to accomplish the sprint goal. The primary target should be trying to complete all the stories in the sprint backlog by the end of the sprint.</p><p>Scrum huddles are specifically designed to have smaller meetings more often. This approach can improve communications, eliminate other meetings, identify impediments, highlight and promote quick decision-making, and improve shared knowledge amongst the team. A secondary goal for huddles is to inspect and adapt to the work currently in progress.</p><h4>Velocity</h4><p>At the end of each sprint the team adds up the effort estimates associated with each user stories that was completed. This rate is known as velocity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7C-rqQz8_i8ZOv0u." /></figure><p>In understanding team velocity the team is able to compute (or revise) an estimate project milestones. This is based on the estimates associated with remaining user stories and assuming that velocity over the remaining iterations will remain the same. Scrum Alliance <a href="https://www.scrumalliance.org/community/articles/2014/february/velocity">describes</a> three specific valuable aspects for understanding team velocity:</p><ol><li>Predicts how much scope can be delivered by a specific date</li><li>Predicts a date for a fixed amount of scope to be delivered</li><li>Understand our limits while defining the amount of scope we will commit for a sprint</li></ol><p>As sprints are completed the planning and forecasts will begin to become more accurate as it will become more clear how many points the team can complete within a given sprint.</p><h3>Product Story Map</h3><p>A product story map is an holistic approach to building a shared understanding for teams around a user’s experience with a product. The map is a simple way to visually tell a product story. Stories are arranged top to bottom to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release. Jeff Patton <a href="http://jpattonassociates.com/storymappingslides/">describes</a> story maps providing a visual representation of understanding:</p><ul><li>Why we’re building the product</li><li>What are the product and user goals and requirements</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*zU5VcCW9cjzdobi2." /></figure><h4>Horizontal Slices</h4><p>The product map is an evolving product backlog where stories can be pulled into a sprint backlog. The map, as seen above, has horizontal slices denoting the group of stories intended to be added to a particular sprint. These often correlate with product release schedules. The first row of stories on the map is considered the stories required to create an minimum viable product (MVP). The stories in the this row are the bare necessity to create a functioning product.</p><h3>Acceptance Criteria</h3><p>Leading Agile <a href="https://www.leadingagile.com/2014/09/acceptance-criteria/">describes</a> acceptance criteria as “<em>the conditions that a software product must satisfy to be accepted by a user, customer, or in the case of system level functionality, the consuming system</em>.” in other words criteria are the lowest level tasks required to be completed for a given story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*lFvH1R_DOHj8iDUd." /></figure><h4>Focus</h4><p>Acceptance Criteria should be quantitative in nature. It can be added to stories at any point in the process but any story added during a sprint planning session should have acceptance criteria assigned before the sprint starts.</p><p>Its also important to define the <strong>what</strong>, and not the <strong>how</strong>. This tact ensures that requirements are met but allows for flexibility in implementation for the team member working on a story. Tasks should never dictate steps to take.</p><p>Acceptance criteria can vary on topic but not intent. Design acceptance criteria is usability-oriented such as “users should encounter no major usability issue while completing task A”. Whereas development acceptance criteria is task-oriented such as “Write script X for connect to API Y”.</p><h3>User-Centric Product Design Lifecycle</h3><p>The user-centric product design lifecycle is a high level process combining user-centered design principles with agile and scrum methodologies. Following this process will ensure that the product meets both user and stakeholder requirements. The 5 pillars of this process are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T8L6Dtdc3vesvbLL." /></figure><ul><li>Strategy</li><li>Discovery</li><li>Analysis</li><li>Design</li><li>Production</li></ul><p>By following these pillars, and their subsequent events, a product team is enabled to create a more informed and usable application with the expectation of low user rejection and high user satisfaction.</p><h3>Strategy</h3><p><em>Stakeholder Discussions</em></p><p>Especially in an enterprise setting, the stakeholder often commissions a project to create a product to solve a perceived problem.</p><h4><em>Project Vision/Goals</em></h4><p>The stakeholder will have a “vision” to execute a solution for a perceived problem. This vision will often drive priority of the roadmap release schedule. The problem statement / product story is defined here to help focus the scope of the product and what challenges it will look to solve.</p><h4><em>Brand Strategy</em></h4><p>Branding can play as big a role as user experience and functionality. The product must fit into an overall brand strategy (marketing analysis). This can include what integrations are targeted to using the same typography and color palette.</p><h4><em>Measure of Success</em></h4><p>Defining success at the onset w/ stakeholders buy-in is crucial so that everyone both inside and outside of the product team can measure if they have been successful. It’s important that the goal posts be set at the onset and not change.</p><h4><em>Project Priority</em></h4><p>Determining which aspects of a product should be prioritized over others. This should guide the project manager in designing the release schedule and what features to work on when.</p><h3>Discovery</h3><h4><em>Business Requirements</em></h4><p>This is traditionally what is used to drive product development. These requirements help establish acceptance criteria later on in the process. These are the “must-have” aspects of the product.</p><blockquote>“We must begin digital projects by exploring and pinpointing the needs of the people who will use the service, and the ways the service will fit into their lives. Whether the users are members of the public or government employees, policy makers must include real people in their design process from the beginning. The needs of people — not constraints of government structures or silos — should inform technical and design decisions. We need to continually test the products we build with real people to keep us honest about what is important.” — via U.S. Digital Services Playbook</blockquote><h4><em>Analytics Review</em></h4><p>How often are users competing tasks? How many users use a particular system? How many tasks are they processing? Obtaining analytical data about users helps understand <strong>what</strong> they are doing.</p><h4><em>Content Audit</em></h4><p>Understanding the data users are utilizing during their tasks helps for user defined acceptance criteria. If specific types of data are used it’s important to understand this so you make sure to include that in your product.</p><h4><em>User Interviews</em></h4><p>Contextual user interviews help understand <strong>why</strong> users take specific actions. This is the most qualitative event and provides a trough of information about user behavior. It also helps define user processes, tasks, and personas.</p><h4><em>Surveys</em></h4><p>Theses are great if you need quick responses to quantitative information.</p><h4><em>User Testing</em></h4><p>This can be done during the interviews but doing some sort of testing on the user’s existing products can help you improve your product by avoiding the pitfalls the current software falls into.</p><h3>Analysis</h3><h4><em>Use Cases</em></h4><p>These are often situational understandings of a particular user action. Nowadays these are written as user stories, encapsulating the persona, action, and motivation of the task.</p><h4><em>Persona Creation</em></h4><p>A persona is an document that contains the analysis of qualitative and quantitative information about a identified meta-person. Personas are made up of groups of real people who identify with a particular role. Each persona has their own goals, tasks, and motivations.</p><h4><em>Story Boards</em></h4><p>Storyboards help understand user stories in a visual way. They are created at specific situations or use cases.</p><h4><em>Experience Map</em></h4><p>An experience map They can help organize user stories in a logical way that enables product teams to quickly and efficiently build products.</p><h4><em>Workflow Diagram</em></h4><p>When trying to map a product flow to a user’s processes, workflow diagrams are essential in understanding when to present information to the user.</p><h3>Design</h3><h4><em>Mood Board</em></h4><p>Much in the vein of Pinterest, mood boards are “yes, and…” exercise where designers will collect colors, typography, existing products, etc to form a basis for the overall look, feel, and function of the product.</p><h4><em>Site Map</em></h4><p>A site map visually shows the steps a user could take to navigate a product, this is analogous with information architecture.</p><h4><em>Sketching</em></h4><p>Jotting down general ideas in a notebook or on a whiteboard is the free-form exercise designers can perform to get a general idea of concepts that could be used in the design of a product.</p><h4><em>Wireframing</em></h4><p>The next level up in fidelity from sketching, wireframing takes into account the device constraints and dimensions on a whiteboard or a program like balsamiq creating very low fidelity mock ups for what a real design could mimic.</p><h4><em>Prototyping</em></h4><p>Using the wireframes as a basis, prototyping is where the designer creates “good enough” products.</p><h4><em>User Testing</em></h4><p>Using the wireframes or prototypes, designer show users what they’ve come up with in a short amount of time. Users are able to physically interact with the product but no actual code or data is present. This instant feedback look avoids expensive development effort to make sure when the product is built, very little changes would need to be made.</p><h3>Production</h3><h4><em>Prototyping</em></h4><p>Prototypes at this point have been thoroughly vetted in the previous step so they should be much more fully formed and tested with a users outside the initial pilot group.</p><h4><em>Beta Launch / MVP</em></h4><p>This is when a minimum viable product (MVP) gets deployed to a set of pilot users. The product should be thoroughly QA’d from both a design and development standpoint.</p><h4><em>User Testing</em></h4><p>Testing with the pilot user group, and more if possible, should be stringent using testing plans to make sure all use cases are thoroughly tested and functionality has no errors.</p><h4><em>Release / Launch</em></h4><p>The big day has come to deploy your release! User behavior should be closely watched using analytics and contact with users should be higher than usual to make sure the product is fully functional.</p><h3>User Involvement</h3><p>Throughout this user-centric process there are multiple points in which the people who will use this product on a daily basis have multiple instances of interaction w/ the product team. Following the learn, build, test methodology stakeholders and users are heavily involved in the beginning during the strategy and discovery phases when building empathy and understanding is the focus. During the design and production phases we are following more of a QA model in eliciting direct feedback from users.</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=103d3a5cf2e3" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/product-design-playbook-103d3a5cf2e3">Product Design Playbook</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[The Great Designer Contradiction]]></title>
            <link>https://uxdesign.cc/the-great-designer-contradiction-b6430889a5ec?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6430889a5ec</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[addiction]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Wed, 25 Jan 2017 14:50:26 GMT</pubDate>
            <atom:updated>2021-10-11T20:29:35.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atIKcM1zNCA1mKnTmMk99Q.jpeg" /></figure><h4>Trying to understand our role in societal electronic addiction</h4><p>Silence fills the air. Pure unadulterated awkward silence only broken intermittently by the screeching of the train wheels running over the rails as it barrels across the Williamsburg bridge into Manhattan. The subway car I’m on is completely packed. No one is talking or even making eye contact with other riders. Instead they’re entranced by their mobile devices consuming content from apps like <a href="https://medium.com/u/a4c6efa67fe0">Instagram Engineering</a> and <a href="https://medium.com/u/5aad0942f068">Facebook Design</a>.</p><p>Riding on the New York City subway I often look around the car to observe how people are spending their time on the train. On average 90% of the people in the car are on their smartphones. 85% of those are Apple devices.</p><p>At first I think, wow, the folks at Apple, Google, and other smartphones makers have made a revolutionary change in our lives on a grand scale in a very short amount of time. People are able to communicate even more seamlessly, it created the app environment employees thousands of developers, and has given a voice to the voiceless by spawning movements bad and good.</p><p>But then my second thought is to ask what price we’ve paid for this convenience? What aspects of life before smart phones have we abandoned? Is it better? worse? The same? This contradiction is something I struggle with and I’m not alone. Let’s review some other people who were also conflicted with success.</p><h3>Conflicted Characters</h3><h4>Steve Jobs</h4><p>Watching Alex Gibney’s documentary <em>Steve Jobs: Man in the Machine</em> one of the interviewees uttered the phrase in reference to the current smart device landscape as <em>Being Along Together. </em>That Steve effectively enabled a generation of people to become these e-zombies slaves to their devices.</p><p>Now I think Steve’s idea in itself was revolutionary and changed the modern technology landscape. But at the same time I don’t think even he could have foreseen the damage his frankenstein spawning things like the foxconn suicide nets, neck injuries, insomnia, and full on electronic addiction.</p><p><a href="http://www.magpictures.com/SteveJobsTheManInTheMachine/">Steve Jobs: The Man in the Machine - Directed by Alex Gibney - Available on DVD, Blu-ray™ and Digital Download</a></p><h4>Thomas Jefferson</h4><p><a href="http://www.jonmeacham.com/">Jon Meacham</a>, In my opinion one of the greatest historians along with <a href="http://www.doriskearnsgoodwin.com/">Doris Kearns Goodwin</a>, wrote a biography about Thomas Jefferson called <em>The Art of Power. </em>If you haven’t read it I really suggest reading it. Meacham takes a different taft in covering Jefferson trying to explain how conflicted he was with the power and esteem of his family, his struggles with death, and his place in the new world as a slave owner.</p><p><a href="https://www.amazon.com/Thomas-Jefferson-Power-Jon-Meacham/dp/0812979486">Thomas Jefferson: The Art of Power</a></p><h4>Henry Ford</h4><p><a href="https://medium.com/u/de1e47ed35d9">American Experience | PBS</a> is an amazing series. When I watched their episode on Henry Ford I couldn’t help but think of Jefferson and Jobs. Credited with the birth not only of the automobile but the assembly line and vertical integration, amongst many other things there’s no denying Ford’s genius.</p><p><a href="http://www.pbs.org/wgbh/americanexperience/films/henryford/">WGBH American Experience | PBS . Henry Ford</a></p><p>Yet Ford found it hard to step away when it came time for his son to take over and destroyed that very relationship in favor of trying to continue growing <a href="https://medium.com/u/db92c082f24a">Ford Motor Company</a> into the behemoth that it is today.</p><p>There are varying reports but Ford was driven to the fact that we pushed his assembly line workers to get every ounce of productivity. He created entire societies around his factories to support his workers but also ran them into the ground and treated them more as objects that assembled his creation that actual people.</p><h3>Victim of Success</h3><h4>Cost</h4><p>So what do these people have in common? They all started with an idea. An idea they expected to go one way that exploded and took on lives of their own they couldn’t contain; much in the vain of <a href="https://www.amazon.co.uk/Frankenstein-Collins-Classics-Mary-Shelley/dp/0007350961">Mary Shelley’s Frankenstein</a>. Each person had both amazing character traits and also severe defects. It’s in these men that I can try to discover an answer.</p><p>Books like <a href="https://medium.com/u/295258f6269d">Nir Eyal</a>’s <em>Hooked</em> tries to help assist designers in created habit-forming products. You also will see articles online like Forbes’ <a href="http://www.forbes.com/sites/avidlarizadeh/2013/07/19/eight-tips-for-a-successful-app/"><em>Eight Tips For A Successful App</em></a><em> </em>that promise strategies for ensuring your app&#39;s success<em>. </em>The concepts explored by these authors are certainly relevant given today’s hyper technological landscape.</p><p><a href="https://www.amazon.com/Hooked-How-Build-Habit-Forming-Products/dp/1591847788/ref=tmm_hrd_swatch_0?_encoding=UTF8&amp;qid=&amp;sr=">Hooked: How to Build Habit-Forming Products</a></p><h4>Addiction</h4><p>But what does ease to use <strong>cost? </strong>Are we making the users pay in other ways? <a href="https://www.addiction.com/addiction-a-to-z/technology-addiction/technology-addiction-101/">Addiction.com</a> asks the following questions to understand if you might suffer from electronic addiction:</p><ol><li>Feel <strong>preoccupied</strong> with the Internet (meaning thinking about previous online activity or anticipating the next online session)?</li><li>Feel the need to use the Internet with increasing amounts of time in order to achieve <strong>satisfaction</strong>?</li><li>Feel <strong>restless, moody, depressed</strong> or irritable when attempting to cut down or stop Internet use?</li><li>Stay online longer than originally intended?</li><li>Use technology as a way of <strong>escaping problems</strong> or relieving feelings of helplessness, guilt, anxiety or depression?</li><li>Feel the need to respond <strong>immediately</strong> to your smartphone?</li><li><strong>Constantly check</strong> the phone even when it does not ring or vibrate? (Phantom vibration, or thinking the phone vibrates when it hasn’t, is a real phenomenon.)</li><li>Ignore what’s happening in real time in favor of what’s happening in the virtual world?</li><li>Feel <strong>anxious</strong> when away from the device or computer?</li></ol><p>Diving deeper <a href="https://www.psychologytoday.com/basics/addiction">PsychologyToday defines addiction</a> as:</p><blockquote>a condition that results when a person ingests a substance (e.g., alcohol, <a href="https://www.psychologytoday.com/conditions/cocaine">cocaine</a>, <a href="https://www.psychologytoday.com/conditions/nicotine">nicotine</a>) or engages in an activity (e.g., gambling, <a href="https://www.psychologytoday.com/basics/sex">sex</a>, shopping) that can be pleasurable but the continued use/act of which becomes compulsive and interferes with ordinary life responsibilities, such as work, relationships, or <a href="https://www.psychologytoday.com/basics/health">health</a>. Users may not be aware that their behavior is out of control and causing problems for themselves and others.</blockquote><p>With companies like Apple and Google including <a href="http://www.theverge.com/2016/3/29/11326194/apple-night-shift-blue-light-sleep"><em>Night Time modes</em></a> in recent software updates due to the fact that warm light can give people insomnia and other health issues that could increase risks.</p><p>To a degree these companies have started to resemble the tobacco companies doing anything to get people to keep using their products say of suggesting outright taking a break.</p><p><a href="http://www.dailymail.co.uk/health/article-3974060/Digital-heroin-children-Youngsters-spend-five-hours-day-glued-smartphones-televisions-according-shocking-Ofcom-report.html">Screen addiction is the new tobacco for Britain&#39;s youngsters</a></p><h3>Design as an Enabler</h3><p>As a designer I’m public enemy number 1 when it comes to enabling and discovering ways for people to spend even more time on these devices. So I ask the question, what responsibility do we as designers have in helping to curtail overall electronic addiction?</p><blockquote>…what responsibility do we as designers have in helping to curtail overall electronic addiction?</blockquote><p>To be honest I don’t really know the answer to that question to try and understand what we could do to try and curtail these issues. As a design community we could start designing apps that are cognizant of how long people are using our apps and building in call to actions to suggest users take a break after prolonged use?</p><p>We could also put time limits on sustained app usage and force people to go outside! More than likely even if some apps adopted these methods others won’t and will gladly take user’s eyes spending more time in their apps.</p><p>Going forward I will certainly be contemplating these issues while trying to take steps to design responsibility in trying to reduce this ever growing epidemic.</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=b6430889a5ec" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-great-designer-contradiction-b6430889a5ec">The Great Designer Contradiction</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[My Design Philosophy]]></title>
            <link>https://medium.com/sketch-app-sources/my-design-philosophy-94636c413137?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/94636c413137</guid>
            <category><![CDATA[opinion]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Tue, 20 Dec 2016 21:12:01 GMT</pubDate>
            <atom:updated>2018-03-06T20:38:54.636Z</atom:updated>
            <content:encoded><![CDATA[<h4>My personal outlook on the art of user experience design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*tMsIvDmlnB0JnNZ6ZhsUSw.png" /><figcaption>Source: <a href="http://www.co-d.net/about/squiggle/">The Process of Design Squiggle</a>, Damien Newman</figcaption></figure><p>Design is messy. Your mind tends to go in all different directions after distilling the research. You’ve got a ton of ideas running around in your head to address design challenges and you have no idea where to start.</p><p><strong>This realization can be very intimidating as a designer.</strong> You begin by trying to answer very basic questions like <em>what tasks take precedence over others?</em> <em>What will the design eventually look like?</em></p><p>In moments like these, and you will have them, you need to place your trust in your design processes and accept two universal forces: uncertainty and change.</p><p>Take solace as a designer that after you go through your steps you’ll have some kind of design at the end. It may not be the best one but it’s better than not delivering anything.</p><blockquote>“accept two universal forces: uncertainty and change”</blockquote><p>Now the guide for your designs should be based on a design language. Yet knowing WHERE things go and knowing WHY they need to exist on the screen in the first place is what we designers are for.</p><p>As the designer it also means you’ll need to consider various perspectives around feedback on designs. If someone has a tension with an aspect of the design you as a designer need to have the ability to synthesize that feedback and understand which would most benefit the product’s overall user experience.</p><p>Do work. Deliver. Have Fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94636c413137" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/my-design-philosophy-94636c413137">My Design Philosophy</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Machine Learning Compliance Product / Part 4]]></title>
            <link>https://medium.com/sketch-app-sources/designing-total-conduct-part-4-83ec44bf6a1c?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/83ec44bf6a1c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 03:09:17 GMT</pubDate>
            <atom:updated>2020-01-30T18:57:24.613Z</atom:updated>
            <content:encoded><![CDATA[<h4>User Research</h4><h3>Finally…</h3><p>Getting access to interview users in an enterprise environment is a tall order. It ended up taking me over 4 months from the kickoff meeting till my first interview. I had to give numerous presentations and attend 1:1 meetings with key stakeholders to convey the value of <a href="https://www.interaction-design.org/literature/article/contextual-interviews-and-how-to-handle-them"><strong>contextual user interviews</strong></a>. This may seem like an unusual request if they’ve never heard of UCD (<a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.94.381&amp;rep=rep1&amp;type=pdf"><strong>User centered design</strong></a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w74izuHUYsEE2PHZX4_0XQ.jpeg" /><figcaption>UX Design Process Presented to Project Stakeholders</figcaption></figure><p>Subscribing to UCD ensures that user happiness and acceptance of the product is high. Instead of forcing the user to conform to a product workflow, It’s much easier to match the product workflow to the user.</p><p>I employed the following tactics to spread the gospel of User Experience Design:</p><ul><li>Schedule multiple meet and greets w/ potential users, project managers, product owners</li><li>Educate project managers all the way to sub C level bosses</li><li>Create educational presentations about user experience research and best practices</li><li>Perform mock user interviews w/ project managers so they go through the experience</li></ul><h3>Learn, Understand, Design, Learn again</h3><p>I interviewed 8 users in total spread out over the course of a few weeks. I conducted a ~1hr interviews utilizing ethnographic principles to extract data about the user&#39;s responsibilities, frustrations, processes and interactions. This information was instrumental in shaping what has turned out to be an amazing user experience.</p><h4>User Interview Framework</h4><p>It’s a good idea to have a well constructed high-level strategic plan on what aspects of the user&#39;s responsibilities/process you want to learn about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*h8wDcD7uvyMPdigGxYEjBw.png" /><figcaption>User Interview Questions</figcaption></figure><p>I create a <a href="https://medium.com/u/fb5dd2d116a1">Trello</a> card for each interviewee. I can have a great view to track and drive the research progress. This is also a great place for anyone else on the team to review raw interview data.</p><p>How you conduct your user interviews is entirely up to you and should be customized to the specific industry and audience you are interviewing.</p><p>I often follow a loose improvisational style. You have to follow where the user takes you and select the correct question to ask at the right time. I guarantee you no interview ever goes exactly like the previous one. Users prioritize differently so you have the be flexible but keep on a topic but also allow opportunities to ask the <a href="http://designresearchtechniques.com/casestudies/5-whys/"><strong>5 whys</strong></a>. Contextual interviews have often been <a href="https://hbr.org/2009/03/ethnographic-research-a-key-to-strategy">described as an art unto itself.</a></p><h4>User Interview Pillars</h4><p>There are a few tactics I utilize during an interview:</p><ul><li><strong>Ask Open Ended Questions</strong>, I can&#39;t stress this enough…</li><li>Why? Why? Why? Why? Why?</li><li>Don’t be afraid to go off script</li><li>Be mindful of time [<em>It’s ok to let them talk but try to stay on topic</em>]</li><li>Listen for emotions/topics repeated multiple times</li><li><strong>ASK OPEN ENDED QUESTIONS </strong><em>(it’s ok not to know exactly what you&#39;ll learn. That&#39;s why you’re conducting the interview in the first place!)</em></li></ul><h4>Interview Analysis</h4><p>For the first analysis I decided to be completely and unforgivingly transparent. I was going to leave every piece of data extracted from the interview for all to see.</p><p>I tend to write outlines and draw workflow diagrams. The outlines are the basis for my information architecture. The users often describe a process and I simply illustrate it. This could take some time as I rewind over and over to make sure I understand. A 2 hour interview can take ~2–3 days just to analyze.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tcitJF6drEVVCSrJj-JO2Q.jpeg" /><figcaption>Persona Post Interview Analysis Whiteboard</figcaption></figure><h4>Analysis Focus Areas</h4><p>There are a few aspects of the interview I make sure to understand. These include emotion, repetition, examples, and overall themes.</p><p><strong>Emotion<br></strong>I deconstruct the interview in front of a 8&#39; high by 12&#39; wide whiteboard wall. My interviews follow a general pattern so each question maps to a outline heading.</p><p><strong>Repetition<br></strong>Users will often return to things that either really make them happy or annoy them to no end.</p><p><strong>Examples</strong><br>Users give examples of things they do like from other applications. I believe it’s an aspect of my job as the user experience designer to distill what technique the references software is doing well and include it into whatever I design.</p><p><strong>Themes</strong><br>A user interview can often be like watching an episode of <a href="http://www.imdb.com/title/tt0944947/">Game of Thrones</a>. There are 4 or 5 different story lines all going on and the interviewee will often call back as they unpack their mind about what it is that they actually do everyday. Writing all those data points on a giant whiteboard wall helps me uncover commonalities. These end up as epics in user as story mapping cards.</p><h3>Personas</h3><p>Armed w/ interview information I finally felt like I had my head around some of the challenges the analysts were facing. I was able to become one of them much in the way method actors become their characters (<em>PS I’m writing a full length article around this topic</em>).</p><p>The current software is a rules-based system yet our product would be driven by <a href="http://www.economist.com/news/leaders/21650543-powerful-computers-will-reshape-humanitys-future-how-ensure-promise-outweighs"><strong>Artificial Intelligence</strong></a> through the use of techniques like NLP and Deep Learning. This data established our <strong>acceptance criteria</strong>:</p><ol><li>Analysts would need a channel in which to provide feedback to the data science models</li><li>Actions taken by the model need to differentiate from user actions</li><li>Comments should be tied to a potential violation not the whole alert itself</li><li>Contextual information is needed to provide additional data to assist the analysts when they make a ruling on the legality of the communication.</li><li>Utilize screen space on enterprise issued monitors running 1920 x 1080 resolution</li></ol><h3>Workflow Breakdown</h3><p>Understanding the workflow of how a task it completed allows you to understand the factors that will influence the information architecture of a given view. It also gives you insight into the features being used in secondary software. If you can include these features in your designs then there is a greater chance for a high user adoption rate.</p><h4>Quantitative vs Qualitative</h4><p>Post the Alpha 1.1 release (<em>actually the 3rd iteration of the design started 4 months earlier</em>) I learned the breakpoint I’d chosen was not in fact the default resolution for the users. They used twin widescreen dell flat panel monitors at 1920 resolution. It was like turning a corner and discovering heaven. Think of all the screen real estate!</p><p>You’ve made it this far! Next up we get to the pot of gold at the end of the rainbow, the design composition evolution. Coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83ec44bf6a1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/designing-total-conduct-part-4-83ec44bf6a1c">Designing A Machine Learning Compliance Product / Part 4</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Machine Learning Compliance Product / Part 3]]></title>
            <link>https://medium.com/sketch-app-sources/designing-total-conduct-part-3-6f22407220fd?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f22407220fd</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 02:12:39 GMT</pubDate>
            <atom:updated>2016-12-20T20:39:19.201Z</atom:updated>
            <content:encoded><![CDATA[<h4>Agile sprints, user stories, &amp; atomic design</h4><p><a href="https://www.agilealliance.org/agile101/"><strong>Agile methodology</strong></a> is a way of running projects that you may have heard of. You’ve probably also heard the terms <a href="https://www.scrumalliance.org/why-scrum/scrum-guide"><em>Scrum</em></a>, <a href="https://www.atlassian.com/agile/kanban"><em>Kanban</em></a>, and <a href="https://www.interaction-design.org/literature/article/a-simple-introduction-to-lean-ux"><em>Lean</em></a>. What does it all mean right?</p><p>Speed. More to the point... <a href="https://www.agilealliance.org/glossary/velocity/"><strong>Velocity</strong></a>. It’s a way to continually discover ways to work faster and more efficiently whilst also removing wasted effort at the same time. It also has a game element to it. Each task or <a href="https://www.scrumalliance.org/community/articles/2013/september/agile-user-stories"><strong>User Story</strong></a>, is assigned a number that represents the level of effort it would take to complete that task. Numbers are assign on the <a href="http://mathworld.wolfram.com/FibonacciNumber.html"><strong>fibonacci numbers</strong></a>. Depending on the length of your sprint (<strong>most companies run 1/2 week sprints</strong>) 1 person could complete X number of points. In a 2 week sprint I was averaging ~60 points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*V5ffrq712WCt6rxVVoHANA.png" /><figcaption>The above cartoon (Amend 2005) shows an unconventional sports application of the Fibonacci numbers (left two panels). (The right panel instead applies the <a href="http://mathworld.wolfram.com/PerrinSequence.html">Perrin sequence</a>).</figcaption></figure><p>When the next sprint planning session occurred, a meeting where the stories are collected and assigned, you would see if you could add 5 more points this sprint. You are constantly pushing how many pts you can complete. When a team attacks this growing sprint backlog it’s known as <a href="https://www.agilealliance.org/resources/experience-reports/swarm-beyond-pair-beyond-scrum/"><strong>swarming</strong></a>.</p><p>Ideally when you estimate stories you want them to all be 1 pt. 1 roughly equals 1 day of effort. Anything larger and you should break them down into smaller more specific stories. If I don’t I hear the voice of <a href="https://www.linkedin.com/in/mark-fischer-625975">Mark Fischer</a> in my head yelling…</p><blockquote>1 point!… 1 story!…1 day!</blockquote><p>My focus is always on what design would make the user story true. This allows for ultimate creative freedom while still adhering to feature requirements through <a href="http://blog.teamtreehouse.com/when-is-a-user-story-done-acceptance-criteria-definition-done"><strong>Acceptance Criteria</strong></a>. User Stories go a long way to ensuring the quality and consistency of the designs are always high while also being fast.</p><h3>User Story Mapping</h3><p>The user story is the main instrument used in the agile design process. They provide a multitude of understanding around Feature Value, Prioritization, and Effort.</p><p>I follow the user story structure of</p><blockquote>As a &lt;role&gt;, I want &lt;feature&gt; so that &lt;reason&gt;</blockquote><p>User story mapping is the foundation for sharing overall understanding and setting expectations on what can realistically be achieved in a sprint. Or as <a href="http://jpattonassociates.com/user-story-mapping/">Jeff Patton says</a>,</p><blockquote>User Story Mapping is a dead simple idea. Talk about user’s journey through your product building a simple model that tells your user’s story as you do. But it turns out this simple idea makes working with user stories in agile development a lot easier.</blockquote><p>If User Story Mapping is new to you you should read Jeff’s book first! It’s really well done and covers all aspects around the process of creating story maps.</p><p><a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=2&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjlnp7CmaTQAhVEw1QKHZc9DwsQFggtMAE&amp;url=https%3A%2F%2Fwww.amazon.com%2FUser-Story-Mapping-Discover-Product%2Fdp%2F1491904909&amp;usg=AFQjCNEPFtZ_n4KhLnTrxIf1sX2go0VhVQ&amp;bvm=bv.138493631,d.eWE">User Story Mapping: Discover the Whole Story, Build the Right Product</a></p><h4>Product User Story Map</h4><p>Around 12 people participated in building the initial map. Using the whiteboard space (8&#39; tall x 12&#39; wide) people were told about the identified roles and were asked to write stories. There had been a few workshops prior to the sessions just around how to write stories for those that didn’t have much experience w/ it. We really wanted everyone’s point of view to be considered and heard.</p><blockquote>…my focus is always on what design would make the user story true</blockquote><p>I typically start w/ this exercise for most projects AFTER presenting the findings of contextual user interviews. But in this case I had no research data yet so I had to invite stakeholders into the session to lend context and information about what they knew about the users.</p><p>The stories pertained to enabling the users to process the alerts at a quicker rate and more efficiently .Many of the assumptions made during this exercise actually ended up being disproved by user research.</p><h4>Identified Roles</h4><p>Several roles were identified through this exercise including Level 1 Analyst, Level 2 Analyst, Supervisor, Queue Manager, and System</p><h3>Design Sprints</h3><p>The user epics and stories identified from the mapping session are fed into a kanban board. I followed a 2 week sprint schedule. <strong>Side Note:</strong> <em>I’m almost done the </em><a href="http://www.gv.com/sprint/"><em>GV design sprint</em></a><em> book and will be changing to 1 week sprints.</em></p><p>Kanban boards in conjunction with the screenful.me tracking provides a large window into the design process at any given moment. I find that this allows for ultimate agility when deadlines change, and they always do.</p><p>Daily <a href="https://www.scruminc.com/origins-daily-standup/"><strong>scrum huddle</strong></a><strong>s</strong> informed the rest of the team on what I <strong>actually</strong> accomplished yesterday and what I <strong>planned</strong> to accomplish today.</p><h4>Project Board Columns</h4><p>For those Agile junkies out there here is my kanban stages:</p><ul><li>Use Story Mapping Backlog</li><li>Whiteboard Backlog</li><li>White Sprint Backlog</li><li>Whiteboarding</li><li>Design Backlog</li><li>Design Sprint Backlog</li><li>Designing</li><li>Design Critique</li><li>Activity Trail Icon [If one needed to be created]</li><li>Zeplin Backlog [To be pushed to Dev]</li><li>Prototype Backlog</li><li>Prototyping</li><li>Graveyard</li></ul><h4>Evaluating Progress &amp; Effort</h4><p>Using the <a href="http://help.trello.com/article/797-adding-labels-to-cards"><strong>Labels</strong></a><strong> </strong>feature in <a href="https://medium.com/u/fb5dd2d116a1">Trello</a> and a powerup built-in third party app called <a href="http://screenful.com/">Screenful.me</a> I’m able to automaticlly create realt time burndown charts, cummulative flow, and understand team velocity. I assign cards w/ the appropriate labels, which represent <a href="http://www.allaboutagile.com/thats-not-a-user-story-thats-an-epic/"><strong>Epics</strong></a>. Those labels drive the flow chart below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkiqCqI9cP07UFsIq1JdcA.png" /><figcaption>Screenful.me Epic Cummulative Flow</figcaption></figure><p>To determine effort you add a“(#)” at the beginning of the card title to assign an estimation. Screenful will understand this and update accordingly.</p><p>Screenful.me also has a “<em>radiator</em>” mode where it automaticlly pages through the screens. It’s great to just leave on a screen in a open area in the office to offer a view of what is being worked on and when it might be complete.</p><h3>Atomic Design</h3><p>Developed by the amazing <a href="https://medium.com/u/52f676b44c62">Brad Frost</a>, I’ve follow Atomic Design principles in my <a href="https://medium.com/u/d39f69b23aa2">Sketch</a> files. If you haven’t seen this drop everything and watch the video below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F109130093%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F109130093&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F493127040_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/2fb2a9b15ca23573741de2bdba2eceef/href">https://medium.com/media/2fb2a9b15ca23573741de2bdba2eceef/href</a></iframe><h4>Project Atomic Library</h4><p><strong>Atoms<br></strong>These are the smaller bits. For me this means toasts [call to actions], Category icons, General icons, Audit icons, and logos;</p><p><strong>Molecules<br></strong>Comprised of many atoms, Molecules represent the next step in constructing interchangeable components. Typical convention is to read left to right and follow the flow/changes in the component.</p><h3>Developer Handoff</h3><p>If you aren’t already you should be using <a href="https://medium.com/u/5d3d19cfe01">Zeplin</a>. This product enables me to develop very quickly by removing the tedious tasks of creating redline comps or writing CSS for style specifcs like Hex #’s for colors.</p><p><a href="https://medium.com/u/5d3d19cfe01">Zeplin</a> instantly provides the frontend development team w/ up to date:</p><ul><li>CSS Stylesheet incl. color pallette</li><li>Asset Images</li><li>Object placement/spacing measurements</li><li>Feedback/Comments</li></ul><p>Utilizing the <a href="https://medium.com/u/5d3d19cfe01">Zeplin</a> <a href="https://medium.com/u/d39f69b23aa2">Sketch</a> plugin and <a href="http://sketchrunner.com/">Sketch Runner</a> pushing updates takes only a few minutes. The more detailed your designs the longer it tends to take to upload. You also can only do 1 page in <a href="https://medium.com/u/d39f69b23aa2">Sketch</a> at a time but unlimited count of artboards on that page at once.</p><p><a href="https://medium.com/@mvoshell/designing-total-conduct-part-4-83ec44bf6a1c#.lta0ijhg0">Next we finally get to discuss the user research!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f22407220fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/designing-total-conduct-part-3-6f22407220fd">Designing A Machine Learning Compliance Product / Part 3</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Machine Learning Compliance Product / Part 2]]></title>
            <link>https://medium.com/sketch-app-sources/designing-total-conduct-part-2-decc84cb05af?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/decc84cb05af</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[financial-regulation]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sat, 03 Dec 2016 20:57:34 GMT</pubDate>
            <atom:updated>2016-12-20T20:29:35.210Z</atom:updated>
            <content:encoded><![CDATA[<h4>Picking a design language framework</h4><h3>Material Design</h3><p>I had just completed a side project using <a href="https://material.google.com/">Material Design by Google</a> in an effort to try it out. Given that the existing UI of the client side project was a mix of Bootstrap and Material Design I assumed I could easily get away with going full-on material.</p><p><a href="https://material.google.com/">Introduction - Material design - Material design guidelines</a></p><p>By establishing a design language framework at the beginning it allows the designers <strong>and</strong> the developers to operate in the same world. It helps in conveying user interface best practices and the rules for the given design world. Having a foundational agreement on this allows designers and developers to focus on design questions that matter and not on things like the shape of a button.</p><h4>Color</h4><p>I followed the client’s publicly available theme and built my color pallette around that. There are a few tools out there that can help you create this for you but there are two I’m particularly fond of;</p><ul><li><a href="https://www.materialpalette.com/">Material Palette - Material Design Color Palette Generator</a></li><li><a href="https://github.com/romannurik/MaterialColorsApp">romannurik/MaterialColorsApp</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yH22vklxX1EA-akFPd7mgQ.png" /><figcaption>Color palette cards created using <a href="https://github.com/ment-mx/Prism">Prism</a> <a href="https://medium.com/u/d39f69b23aa2">Sketch</a> plugin</figcaption></figure><h4>Typography</h4><p>Given that I’d chosen <a href="https://material.google.com/">Material Design</a> as my design language I went along with the default Roboto font. It has a clean modern feel that I could also get away with in an enterprise environment.</p><p><a href="https://material.google.com/style/typography.html">Typography - Style - Material design guidelines</a></p><h4>Icons</h4><p>Again, In an effort not to reinvent the wheel I often find relevant metaphorical meanings for the icons I use within the product. Most of them can be found in the base set offered by Google.</p><p><a href="https://design.google.com/icons/">Material icons - Google Design</a></p><h4>Components</h4><p>For basic building block pieces I use the built in stickersheet provided by <a href="https://medium.com/u/d39f69b23aa2">Sketch</a>. I also use another component set I found on <a href="http://www.sketchappresources.com/">Sketch App Resources</a>.</p><p><a href="https://material.google.com/resources/sticker-sheets-icons.html#sticker-sheets-icons-components">Sticker sheets &amp; icons - Resources - Material design guidelines</a></p><p><a href="https://medium.com/@mvoshell/designing-total-conduct-part-3-6f22407220fd#.4jwnujorh">Up next is Part 3 where we discuss Agile sprints, User stories, &amp; Atomic design</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=decc84cb05af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/designing-total-conduct-part-2-decc84cb05af">Designing A Machine Learning Compliance Product / Part 2</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Machine Learning Compliance Product / Part 1]]></title>
            <link>https://medium.com/sketch-app-sources/designing-total-conduct-part-1-a9e20bf326e1?source=rss-cc843ab86cbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9e20bf326e1</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Matthew Voshell]]></dc:creator>
            <pubDate>Sat, 03 Dec 2016 20:28:16 GMT</pubDate>
            <atom:updated>2016-12-20T21:05:25.790Z</atom:updated>
            <content:encoded><![CDATA[<h4>Understanding the challenges &amp; product landscape</h4><h4>Introduction</h4><p>This series is a running journal I kept over a 10 month period while designing a financial technology (<a href="https://en.wikipedia.org/wiki/Financial_technology">FinTech</a>) application for a major US financial institution.</p><p>The product’s goal is to enable financial compliance analysts to discover and mitigate employee malfeasance. Analysts often have legal backgrounds or more often are former traders themselves. This domain knowledge of what terms traders use and topics they discuss is the best tool banks have currently.</p><p>This series will cover the following aspects of the product design:</p><ul><li>Part 1: Understanding the challenges and existing product landscape</li><li><a href="https://medium.com/@mvoshell/designing-total-conduct-part-2-decc84cb05af#.cgyk9p82k">Part 2: Picking a design language framework</a></li><li><a href="https://medium.com/@mvoshell/designing-total-conduct-part-3-6f22407220fd#.epiq7ceyg">Part 3: Agile sprints, User stories, &amp; Atomic design</a></li><li><a href="https://medium.com/@mvoshell/designing-total-conduct-part-4-83ec44bf6a1c#.hcmim1rwq">Part 4: User Research</a></li><li>Part 5: Composition Evolution [Will return after updates, sorry]</li></ul><h4>Problem Set</h4><p>The financial industry is suffering from an out of control wildfire of fraudulent activity that has cost financial institutions billions in fines from regulatory agencies. Wall street needs software that will assist them in being able to discover and mitigate employee malfeasance on an enterprise-level scale asap.</p><ul><li><a href="https://www.theguardian.com/business/2016/sep/16/deutsche-bank-14bn-dollar-fine-doj-q-and-a">The $14bn Deutsche Bank fine - all you need to know</a></li><li><a href="http://www.cbsnews.com/news/wells-fargo-ceo-john-stumpf-sold-millions-in-company-stock-before-bank-fraud-revelations/">CEO sold millions in Wells Fargo stock before fraud revelations</a></li></ul><h4>Product Roadmap Strategy</h4><p>As with most other products a kickoff meeting was conducted over a 3 day period. This was the stakeholder’s chance to set the agenda and establish the overall direction for the product. Features considered critical path included Information Leakage Detection, Collusion Detection, Trader Profiles, and Email Communications Analysis.</p><p>The meetings were on track until day 2 when one of the project managers began to draw on his iPad a wireframe of how he foresaw the product looking. I quickly chimed in to say,</p><blockquote>Until we complete some initial research, discussing the layout of the app is a complete waste of time</blockquote><p>The reaction by most in the room was split. Half the room agreed and understood many steps were being skipped. While the other half were shocked and dismayed that anyone would stand up and say no to a project manager.</p><p>I continued by sharing the vision that this would not just be a product that picked up where competitors had left off. But that it would be a completely new person-centric, not alert based, machine learning driven compliance product.</p><p>As a user experience designer I feel it’s important to establish at the beginning of a project who is responsible for what tasks. If anyone, most often an over zealous project manager, tries to do your job for you it&#39;s on <strong>YOU</strong> to speak up and explain why it isn&#39;t. Having the guts to defend design (or sometimes over defend) is, in my opinion, one of the more lacking characteristics of less experienced UX designers.</p><p>There is also a fine line with this. Push back too hard you’ll offend the stakeholder. Do too little and you risk being run over and have every design decision questioned. It’s up to you to evaluate the balance needed here based on your relationship with the stakeholder to successfully work together without surrendering your ability to be creative and try new things.</p><h4>Existing Product Landscape</h4><p>With my background in US federal consulting it was oddly comforting to see that both government and financial industries suffer from similar issues. It’s changing slowly, with groups like the <a href="https://www.usds.gov/">US Digital Service</a>, but user experience is still an afterthought.</p><p>When I was on a call not long after the kickoff meeting one of the stakeholders was talking about another product and simply stated,</p><blockquote>Just get the infrastructure up and we’ll slap a UI on it.</blockquote><p>It was clear from this point that I had my work cut out for me when it came to educating the stakeholders about all the effort that goes into designing a truly amazing user experience.</p><p>This lack of empathy towards users in an enterprise setting is understandable to a degree. There is no real incentive for companies to dedicate time and money when the employees are required to use the software to perform their job.</p><p>But there are certainly <a href="http://www.industryweek.com/workforce/well-designed-software-crucial-productivity-improvement">qualitative factors</a> that employee’s demand for happiness and satisfaction. These qualities have been shown to be a <a href="https://www.fastcompany.com/3048751/the-future-of-work/happy-employees-are-12-more-productive-at-work">factor in overall employee productivity</a>.</p><h4>Browser Spreadsheets</h4><p>Spreadsheets have been bastardized for years in situations where a database would be the better solution. What became a simple ledger evolved into pivot charts. I pledged to myself at the start of this project that I would work as hard as I could to avoid spreadsheets.</p><p>Below is an example of <a href="http://www3.ca.com/us/securecenter/ca-data-protection.aspx">CA Technologies Dataminder</a>. It uses regexes made of simple “dumb” rulesets to identify possibly bad behavior. But as traders evolve their slang so does the work of the analyst to modify these rules to continue to discover malfeasance.</p><p>Since the rules are term based the recall is incredibly low and analyst spend much more time managing the rules and eliminating false positives than they do reviewing for potentially bad behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJExf76QZ_mtQDA-afiGPQ.png" /><figcaption>CA Technologies Orchestria</figcaption></figure><h4>User Interview Impediments</h4><p>It was a struggle to get the stakeholders to understand the value of contextual user interviews and the data it would yield. Obtaining this data would go a long way in guaranteeing the user experience was designed to meet both the business <strong>and</strong> user needs. Until now the stakeholders, not the users, had total control over all user experience design decisions. It was clear this would be the first major battle and one I was determined to win.</p><blockquote>Stakeholders, not the users, had total control over all user experience design</blockquote><h4>The Blind Designer</h4><p>My initial requests to speak directly with users was met with bewilderment and disbelief. I was told by one project manager,</p><blockquote>The user&#39;s time is very valuable to this firm. If you’d like to know anything I can tell you. What would you like to know?</blockquote><p>It was very clear he was gatekeeping. It was also clear that he had no concept of user research as he told me, <em>“How does amazon know to make changes to their site? They don’t call my grandmother and ask her what she thinks, they just build it.” </em>This is of course a ludicrous statement as Amazon has amazing user research teams in Washington state and London, UK.</p><p>I left that meeting with no resolution and no access to users. So with no research to help me define the problem I would be trying to solve, I was stuck in a awkward position.</p><p>In a situation like this I often use the following metaphor:</p><p><em>Imagine you hired an interior decorator for your home. Throughout the entire process, where you select and install furniture, wallpaper, paint, etc. you never have a single meeting with the designer. There is no opportunity for them to obtain an understanding of your taste and style. Without this interaction the likelihood that you’ll be happy with the results probably won’t be very high.</em></p><p>It was clear I was just going to have to gather what information I could from stakeholders knowing that it would carry bias and not be entirely accurate. Their area of focus was to concentrate on speed and reducing the amount of mouse clicks. When I finally got to interview the users this turned out not to be anywhere on the main list of user needs.</p><p><a href="https://medium.com/@mvoshell/designing-total-conduct-part-2-decc84cb05af#.9zn8ex1s5">Next we’ll dive into picking the design language framework!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9e20bf326e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/designing-total-conduct-part-1-a9e20bf326e1">Designing A Machine Learning Compliance Product / Part 1</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>