<?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 Thomas Michalak on Medium]]></title>
        <description><![CDATA[Stories by Thomas Michalak on Medium]]></description>
        <link>https://medium.com/@mighty_mess?source=rss-2c6d17d3381f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lhflyjj41qyCmium.png</url>
            <title>Stories by Thomas Michalak on Medium</title>
            <link>https://medium.com/@mighty_mess?source=rss-2c6d17d3381f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:14:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mighty_mess/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[Three Design Thinking principles to shape a great product.]]></title>
            <link>https://uxplanet.org/three-design-thinking-principles-to-shape-a-great-product-99c91b518a9?source=rss-2c6d17d3381f------2</link>
            <guid isPermaLink="false">https://medium.com/p/99c91b518a9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Thomas Michalak]]></dc:creator>
            <pubDate>Mon, 14 Aug 2017 19:22:40 GMT</pubDate>
            <atom:updated>2019-12-10T07:39:58.277Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18ZsKeVL5uDv4pOJqgQncw.jpeg" /><figcaption>The Great Wave off Kanagawa — Katsushika Hokusai</figcaption></figure><p>Creating a product that is profitable to your business while being exciting to the users and not a technological mine field isn’t an easy task, it can almost feel impossible to achieve, as if success is reserved for the tech giants.</p><p>I face that challenge on a daily basis and I believe that with the right mind set, anyone can achieve greatness. To keep myself and the team in-check, I use 3 simple principles borrowed from Design Thinking:</p><blockquote><strong><em>👉 A great product has to be </em>Desirable<em>, </em>Viable<em> and </em>Feasible<em>.</em></strong></blockquote><p>Those 3 principles helps me and my clients keep the balance right and create sustainable products. It’s easy to understand why ignoring these principles would be bad or even how it would be tempting to simplify things by choosing one at the expense of the other.</p><p>The tension of those opposing models can generate creative solutions that will make each principles feed one another. A desirable product that isn’t overly complicated to build or to operate will be profitable to your business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twyidgx0F1eG44t5eEfRFQ.jpeg" /><figcaption>☝️ Obligatory Venn Diagram ☝️</figcaption></figure><h3>Desirable</h3><p>Design is user-centric and starts with people. To understand how to create value that will resonate with your target audience, you have to understand your users. Understanding your users goes beyond their interaction with your product; you need to understand the root of the problem you’re solving, the context of that interaction and where the possible gap is. It’s often beneficial to look at when and where do they turn to your product. What is the first thing they’ve done before and after that interaction.</p><p>It might sound obvious but all too often we avoid talking directly to users and hide behind complex UX artefacts that we’ve built on assumptions. I’m a big fan of prototyping because I believe that it’s only when we put our ideas into the world that we start to understand their strengths and weakness.</p><blockquote>“Instead of thinking about building we have to build to think.”</blockquote><blockquote>— Tim Brown, IDEO</blockquote><p>This point might sound fairly obvious (although still a hard sell) and most agencies will see this as the most important part of the product. I agree with this, especially at the start, but if you decide to ignore the other 2 principles your product will just be series of hard compromises that will bastardise your proposition and make a sloppy customer experience. How many times I’ve heard designers say: <em>“The UX was great but they couldn’t build it like I designed it”</em> or product managers admit that <em>“The business couldn’t afford the operational expenses around the product so we had to kill it”.</em></p><p>It’s true that clients can underestimate the cost of product development, but even teams that know this can underestimate the impact it will have.</p><h3>Viable</h3><p>Let’s be honest, if your business doesn’t make money from your product then it is quite likely it will get killed or at least not get the investment it needs to sustain growth. Measuring success and demonstrating ROI is key to proving to the business that it’s worth investing into your product. <a href="https://medium.com/the-year-of-the-looking-glass/how-do-you-set-metrics-59f78fea7e44">Defining clear metrics</a> to validate your <a href="http://ashmaurya.com/uvp-vs-unfair-advantage/">Unique Value Proposition</a> is a good start and will help you focus your effort. Defining a long term goal and designing a cost effective solution that will generate revenue can be overwhelming but if you’ve done the up front work on <em>Desirability</em> this should be a little bit easier.</p><blockquote>“Getting a customer to give you money is one of the hardest actions you can ask them to take and is an early form of product validation.”</blockquote><blockquote>— Ash Maurya, Running Lean</blockquote><h3>Feasible</h3><p>Producing rock solid solutions that are operationally and technically sound isn’t a small task and can often be under estimated. Efforts in this area are often focused on technology but there is another aspect to feasibility that, when ignored, can have dramatic consequences: <em>Operations</em> and <em>actors</em>.</p><p>Actors are all the people that live and operate on the peripheral of the user. To find out who are those actors, you will have to step back a little, looking at the customer experience in context and investigating what needs to be true for implementing a smooth experience. You will need to understand all these actors and their responsibilities to get the user through that journey.</p><p>Whether it’s training staff, migrating to new tech, hiring an ops team or integrating with third parties, peripheral actors that don’t understand your product, or worse, see it as a threat, can become a huge risk to its feasibility. You will have to spend that extra time investigating their needs and point of view to secure your product.</p><blockquote>“As users, our journey is always influenced by the course of others. It is important to understand all these actors and their responsibilities to get the user through that journey.”</blockquote><blockquote>— Me, this article</blockquote><h3>How to apply those principles?</h3><p>There’s no silver bullet. Good product is hard work, and you might never hit that sweet spot, but there are ways to implement those principles:</p><h4>Turn risks into opportunities</h4><p>Sometimes when overwhelmed, it feels easier to work on the small things and the low hanging fruits. Ignoring the biggest threats to your product is just delaying the inevitable. In the long run, focusing on the biggest threats can be a quicker route to finding opportunities.</p><p>To do this I like to look at the long term goal and write down what would be the reasons for failing and what would need to be true for us to succeed. Doing this too often could prove distracting or discouraging, but it is a great way to help you and your team focus on the right problems and turn risks into opportunities.</p><p>For a more bird’s eye view I would recommend going through the exercise of filling up a <a href="https://blog.leanstack.com/why-lean-canvas-vs-business-model-canvas-af62c0f250f0">lean canvas</a> and methodically working your way through by validating or dismissing the sections with the biggest assumptions and risks.</p><h4>Run design sprints to see the wood from the trees</h4><p>Unfortunately design thinking workshops aren’t as good as its core principles. You’re also not always going to be able to do a lot of user research or have regular access to all stakeholders. I found that running <a href="http://www.gv.com/sprint/">design sprints</a> with just enough research upfront is the quickest way to design a testable and relevant solution.</p><p>A design sprint will help you map out a customer journey involving all actors, learn fast from putting prototypes in the hands of users, get your stakeholders engaged, and test hypotheses while keeping momentum. That said, preparation is key. If you want to get the most out of those sprints I believe that collecting data before hand is crucial to paint a picture of your customer’s context.</p><h4>Build an MVP to measure and validate</h4><p>What comes naturally after those sprints is a <a href="https://blog.leanstack.com/minimum-viable-product-mvp-7e280b0b9418">Minimum Viable Product</a>. It’s the only way to measure how well you are doing against those 3 principles. User research, prototyping, projections, etc.. are all artefacts that are, to some degree, detached from the reality that surrounds your product.</p><p>Putting your product into the wild is the only true test. Looking at how people receive it, discover it, talk about it and most of all live with it will give you hard data to confirm or dispute all the work you’ve been doing.</p><p>But remember to start by validating your hypotheses using the methods above. Beware of jumping ahead without spending time understanding your customers or verifying your <a href="https://leanstartup.co/a-playbook-for-achieving-product-market-fit/">product-market fit</a>!</p><blockquote>Remember that the best motivation for your decisions is wanting to create a product that your users will love.</blockquote><h3>Design for outcomes</h3><p>Those 3 simple principles will help you or your clients measure confidence in their product and decide where to focus your effort, time and money.</p><p>👉 By repeatedly questioning your assumptions and focusing on outcomes before features, you can create a product that will be viable for your business, feasible, and highly desired by your users.</p><p><em>Big thanks to Luke Gibson for helping editing this article — </em><a href="https://twitter.com/heylukegibson"><em>@heylukegibson</em></a></p><h4>References</h4><p><a href="https://www.ideo.com/post/design-kit">Design Kit: The Human-Centered Design Toolkit</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Ftimothy_prestero_design_for_people_not_awards&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Ftimothy_prestero_design_for_people_not_awards&amp;image=https%3A%2F%2Fpe.tedcdn.com%2Fimages%2Fted%2Fd91a1f2a256a77fcc435b9c488211555e67a5687_240x180.jpg%3Flang%3Den&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="315" frameborder="0" scrolling="no"><a href="https://medium.com/media/46d262519e3cf850366d454b7a63e2a1/href">https://medium.com/media/46d262519e3cf850366d454b7a63e2a1/href</a></iframe><ul><li><a href="https://leanstartup.co/a-playbook-for-achieving-product-market-fit/">A Playbook for Achieving Product-Market Fit the Lean Way</a></li><li><a href="https://www.amazon.co.uk/Running-Lean-Iterate-Works-OReilly/dp/1449305172">Running Lean: Iterate from Plan A to a Plan That Works (Lean (O&#39;Reilly))</a></li><li><a href="http://www.gv.com/sprint/">The Design Sprint - GV</a></li><li><a href="https://medium.com/the-year-of-the-looking-glass/how-do-you-set-metrics-59f78fea7e44">How do you set metrics?</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fsimon_sinek_how_great_leaders_inspire_action&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fsimon_sinek_how_great_leaders_inspire_action&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Fpe.tedcdn.com%2Fimages%2Fted%2F04916ee6e81065c8333e6546184af512eee37bbe_2880x1620.jpg%3Fh%3D316%26w%3D560&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="316" frameborder="0" scrolling="no"><a href="https://medium.com/media/53a20d723f1da23a665359cf015bf082/href">https://medium.com/media/53a20d723f1da23a665359cf015bf082/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99c91b518a9" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/three-design-thinking-principles-to-shape-a-great-product-99c91b518a9">Three Design Thinking principles to shape a great product.</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alexa. Tell me a brand’s story.]]></title>
            <link>https://uxdesign.cc/how-can-we-tell-a-brands-story-and-create-a-recognisable-identity-through-ai-sound-and-46d9d793e145?source=rss-2c6d17d3381f------2</link>
            <guid isPermaLink="false">https://medium.com/p/46d9d793e145</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[alexa]]></category>
            <dc:creator><![CDATA[Thomas Michalak]]></dc:creator>
            <pubDate>Wed, 22 Feb 2017 14:51:34 GMT</pubDate>
            <atom:updated>2017-03-07T02:29:44.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5WIRpY7wf53atP_g45zew.png" /><figcaption>Image by Ryan Phipps Mitchel — <a href="http://rpm-design.co.uk/">http://rpm-design.co.uk/</a></figcaption></figure><p><strong>With all the recent hype around voice enabled AI, there’s been a lot written about the UX of VUI or the business of AI. It got me wondering: Imagine if tomorrow, we stopped using screens (as if!) and our main medium was voice activated AI like Alexa, Siri, or Google home? How does a brand’s story and identity come across with just sound and conversation? What are the possibilities for brands?</strong></p><h3>Story Tools</h3><p>Firstly, by <em>‘story’</em>, I don’t necessarily mean a brand’s history, although sometimes that is important. I’m talking about what makes a brand, their values, their mission, what they stand for and offer, their identity. There are many tools to tell that story and branding is one (colours, logo, type, tone of voice, actions, etc…) but when you’re looking at Voice User Interface (VUI) like in Alexa, branding is stripped back to pretty much 3 things: tone of voice, customer experience and the interaction’s outcome.</p><blockquote>When you’re looking at VUI like Alexa, branding is stripped back to pretty much 3 things: tone of voice, the customer experience and the interaction’s outcome.</blockquote><h3>Tone : Do you trust your AI?</h3><p>Tone of voice and vocabulary are interesting because it’s the two things we can work with right now<strong>.</strong> But here is another caution — when using something like Alexa you’re not interacting with a brand directly, but primarily with Alexa, and the line between Alexa and that brand can seem blurry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*6_inz225DYeMB2lbdpEH5g.png" /><figcaption>How can we get brand values through Alexa?</figcaption></figure><p>Some Brands still struggled with social media, and adjusting to being behind someone else’s product and brand can be challenging.</p><p>Just like with social media, not every brand will understand the required shift in the way they communicate with their customers, but those that do have the opportunity to stand out.</p><blockquote>When Alexa gives feedback on her interaction with your product, there could be an opportunity here to be inventive with getting your values across</blockquote><p>If you trust Alexa, It’s almost like having a mate telling you about how good a brand is or witnessing her using a product and see how good that felt. When Alexa gives feedback on her interaction with your product, there could be an opportunity here to be inventive with getting your values across. For example, if you’re getting a free pastry with your coffee order, Alexa could say:</p><p><em>— “That’s nice, the barista is offering us a free pastry, what would you like with your coffee?”</em></p><p>or she could give some extra information about the product:</p><p><em>— “Your fair-trade coffee served in a sustainable cup will be ready in 15mins for pick-up”</em></p><p>or have some random reactions like:</p><p><em>— “Hmmm the smell of freshly grind coffee, I could do with a coffee too, yours will be ready in 15mins for pickup”</em></p><p>There’s obviously a big danger here! I imagine going too far would be a problem. People are getting used to Alexa’s personality and altering it too much would be a messy and confusing experience. It’s like if one of your good friend suddenly behaved like a butler when he gets in the car or pretend to be Jamie Oliver when helping cooking. Same goes with using regional sayings or changing the level of familiarity the AI has with you.</p><blockquote>People are getting used to Alexa’s personality and altering it too much would be a messy and confusing experience.</blockquote><h3>Conversation Design</h3><p>Humans have this amazing ability to project ourselves in time, to imagine and dream of possibilities, reclaim memories but also fear the unknown and our future. We’re emotional beings and we can transpose that emotion onto anything, reading between lines and attaching feeling to objects. Brands and advertising use this and often abuse it by playing with our fears and desires, tricking us into thinking we absolutely need their products.</p><p>At the moment, those voice activated AI are not very emotional and pretty rubbish at holding a conversation that goes beyond being asked to do basic stuff and replying that it’s done (or the frustratingly familiar “I wasn’t able to understand the question I heard”).</p><p>They lack energy and spontaneity, and creating an emotional connection through VUI is going to be hard for a while yet. Still, intelligent AI is new and exciting, and quite a lot of energy comes from us wanting to believe they are ‘real’. The rest is space for some clever UX design to create an illusion of intelligence.</p><h3>Sound Design</h3><p>In the future, some brands might be able to have their own voice (cars manufacturers and home appliances, for example) and we could become more comfortable interacting with AI that have a personality and a voice. Just like some actors, brands will have a recognisable voice that are part of their DNA and IP. (Think Morgan Freeman or Alan Rickman)</p><p>Sound design might even help us support the AI with background ambience or light sound touch to set the brand’s identity.</p><h3>Add value or get forgotten</h3><p>Voice activated AI are all about serving the user, supporting them and making their life easier. So before creating a bot or a skill, you should ask yourself: <strong><em>What will the user get from it?</em></strong></p><p>At the moment most skills for Alexa are gimmicky and add nothing to the experience of any real value to the user’s life. If you want to stand out, be user centric and add value or be forgotten.</p><blockquote>While there are now more than 7,000 Skills to choose from on the Alexa platform, only 31% have more than one consumer review. — <a href="http://voicelabs.co/2017/01/15/the-2017-voice-report/">2017 voicelabs’ report</a></blockquote><p>As with any product or service, The best way to get your brand values through is with the value you’re adding to the user’s experience.</p><h3>We will face challenges and make mistakes</h3><h4>Discovery</h4><p>I know it’s very new and people are just getting used to talking to a robot but most use Alexa’s default capabilities and don’t search any further. How are we going to communicate the existence of our new apps for VUI? At the moment Alexa won’t chat to you about what’s available so you have <a href="https://backchannel.com/voice-is-the-next-big-platform-and-alexa-will-own-it-c2cf13fab911#.cdui91lta">to grab your phone</a> and browse the crappy skills store.</p><h4>Over-promising</h4><p>I think the first mistake came from the people who are creating AI personalities: they over-promised. If you are expecting to have a conversation with a robot but it fall flat after one sentence then your experience shatters and you may lose your audience. That’s part of what happened to Siri.</p><h4>This is not the web</h4><p>It’s often said that we’re visual beings, but this medium won’t be about promoting visual products or complex e-commerce. Far more likely are practical tools, lifestyle hacks and maybe conversation with the brand.</p><p>If you try to replicate a website, how would the Information Architecture come through? How would the user know to explore what they don’t know or can’t visualise? How will they know where they are and what can be explored?</p><p>Sound and conversation are momentary and so keeping track of what has been said can be difficult. But it’s worth remembering that voice is more natural than text, as Marcel Just said about printed text in a recent interview:</p><blockquote>“It’s very convenient and it’s worked very well for us for 5,000 years, but it’s an invention of human beings. By contrast Mother Nature has built into our brain our ability to see the visual world and interpret it. Even the spoken language is much more a given biologically than reading written language.” — <a href="http://niemanreports.org/articles/watching-the-human-brain-process-information/">Marcel Just’s interview</a></blockquote><h3>Final words</h3><p>At this point it’s hard to predict how ubiquitous VUI will be, or what the biggest use cases will be.</p><p>What matters is that it’s new and young and we need to start experimenting now, to make those mistakes, to fail and learn so when we have the opportunity we will be ready, not just with thoughts but with data and case studies.</p><p><em>Illustration by Ryan Phipps Mitchel — </em><a href="http://rpm-design.co.uk/"><em>http://rpm-design.co.uk/</em></a><em><br>Edited by Luke Gibson — </em><a href="https://twitter.com/heylukegibson"><em>@heylukegibson</em></a></p><h4>References</h4><ul><li><a href="http://voicelabs.co/2017/01/15/the-2017-voice-report/">The 2017 Voice Report</a></li><li><a href="https://trends.fjordnet.com/trends/me-myself-ai">Fjord Trends 2017</a></li><li><a href="https://en.wikipedia.org/wiki/Conversation">Conversation - Wikipedia</a></li><li><a href="https://developers.google.com/actions/develop/conversation">Conversation Actions | Actions on Google | Google Developers</a></li><li><a href="http://niemanreports.org/articles/watching-the-human-brain-process-information/">Watching the Human Brain Process Information</a></li><li><a href="https://backchannel.com/voice-is-the-next-big-platform-and-alexa-will-own-it-c2cf13fab911">Voice Is the Next Big Platform, and Alexa Will Own It</a></li><li><a href="http://www.recode.net/2017/1/23/14340966/voicelabs-report-alexa-google-assistant-echo-apps-discovery-problem">Alexa and Google Assistant have a problem: People aren&#39;t sticking with voice apps they try</a></li><li><a href="https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-voice-design-best-practices">Alexa Skills Kit Voice Design Best Practices - Amazon Apps &amp; Services Developer Portal</a></li><li><a href="https://ifttt.com/amazon_alexa">IFTTT</a></li></ul><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=46d9d793e145" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-can-we-tell-a-brands-story-and-create-a-recognisable-identity-through-ai-sound-and-46d9d793e145">Alexa. Tell me a brand’s story.</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[Will Inspect from Invision replace Zeplin in your workflow?]]></title>
            <link>https://blog.prototypr.io/will-inspect-from-invision-replace-zeplin-in-your-workflow-9b30ce36d75a?source=rss-2c6d17d3381f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b30ce36d75a</guid>
            <category><![CDATA[invision]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[zeplin]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Thomas Michalak]]></dc:creator>
            <pubDate>Thu, 08 Dec 2016 18:18:15 GMT</pubDate>
            <atom:updated>2016-12-08T18:18:15.619Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pD5KxsWdjHCjHukvqdYTNQ.jpeg" /><figcaption>Graphite’s website in Inspect</figcaption></figure><p>Over the last few years the challenge of making communication between designers and developers more natural has been a topic close to my heart. I’ve always hated condescending designers that think their job stops once they’ve exported their mockups. The final product is the build, not your fancy high definition mockups! The same goes for developers who just think that it makes no difference whatsoever if that line is 4px in height instead of 2px</p><p>At Graphite we’ve solved this by doing two things. Firstly, by over-communicating. Developers are involved from the very beginning; helping designers to make the right decisions as well as enabling them to explore new opportunities. Designers always put their designs in front of developers before we share with our clients. It’s a practice that doesn’t require anything formal, just a quick chat to iron everything out. Everybody gets involved which has the power to save us from a few embarrassing or awkward conversations down the line.</p><p>The second thing is by introducing <a href="https://zeplin.io/">Zeplin</a>, a blessing of a tool that has been making things a lot easier for both sides. Developers don’t have to worry about slicing assets and designers don’t have to create extensive documentation around their designs. This means that we can spend time fine tuning the build instead of making sure that this h3 has the right leading everywhere or that the designer followed the grid everywhere.</p><blockquote>“Firstly, by over-communicating. Developers are involved from the very beginning; helping designers to make the right decisions as well as enabling them to explore new opportunities.”</blockquote><p>However, Invision<em> </em>have recently<em> </em><a href="https://www.invisionapp.com/feature/inspect">released<em> </em>Inspect</a><em>,</em> and that means the competition is on! Here’s my list of pros and cons for both tools…</p><h3>Streamlined Process vs Tool Overload</h3><p><a href="https://zeplin.io/"><strong><em>Zeplin</em></strong></a> is amazing but as we’re already using Invision it means we’re employing yet another tool. A new tool we have to educate our clients and contractors on; but also something I’ve had to sell internally (luckily, on this occasion it’s a no brainer as it makes our process quicker).</p><p>Our clients and team are now really used to Invision. We use it throughout our design process, from wires to high definition designs. Everyone is familiar with it and the prototyping helps us to share with our clients, during user testing and so that we can demonstrate to devs how things should behave. But at some point things have to go into Zeplin as well and we can’t maintain both Invision and Zeplin, so Invision often gets left behind.</p><p>The introduction of<em> </em><a href="https://www.invisionapp.com/feature/inspect"><strong><em>Inspect</em></strong></a> will make our design process simpler and more streamlined. Invision will be a centralised place from UX to Build. It will be the truth. No more back and forth between Zeplin/Invision/Sketch. Inspect even integrates with Jira!</p><p>If you’re already using Invision, Inspect will just makes things simpler, especially now that you can upload straight from Sketch. Everything is in one place; clients, producers and developers are all seeing the same thing, which means everyone is on the same page. We all know how frustrating it can be when amends are made and people are left out of the loop.</p><p>Inspect from Invision wins that one for me.</p><blockquote>“If you’re already using Invision, Inspect will just makes things simpler. Everything is in one place; clients, producers and developers are all seeing the same thing, which means everyone is on the same page.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F191321820%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F191321820&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F602293905_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/066ee45b06bb60fbe8a30f56688efe94/href">https://medium.com/media/066ee45b06bb60fbe8a30f56688efe94/href</a></iframe><h3>Old Fart vs Spring Chicken</h3><p>Inspect is good but it’s not as mature as Zeplin. Zeplin let designers set a style guide, which is super powerful because it eliminates guess work for the developer. It’s all there; line-height, colours, font, font-family even gradients. I really like this feature because it also stops the designer from been lazy and forcing us to be consistent with our design rules.</p><p>Zeplin lets you download assets as SVG but also PNGs and Inspect can’t do that (yet). PNGs are great but watch out for image size! Zeplin won’t help you on that one.</p><blockquote>“I really like the style guide feature in Zeplin because it also stops the designer from been lazy and forcing us to be consistent with our design rules.”</blockquote><p><a href="https://zeplin.io/">Zeplin</a> wins that one (but I’m sure Invision is working on it)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FtbKZAGthUgQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtbKZAGthUgQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FtbKZAGthUgQ%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e804be0076bea08958e23fdb00a0a27e/href">https://medium.com/media/e804be0076bea08958e23fdb00a0a27e/href</a></iframe><h3>Dolla Dolla Bill y’all</h3><p>If you are already paying for Invision, well, why pay more? Why not use that money for something else in your studio? Although Invision seemed to say that it will only be available for their enterprise accounts it has now appeared as a feature for everyone. I really hope it stays that way.</p><h3>Conclusion</h3><p>As much I love Zeplin, the reality is that I don’t know how they will find a competitive advantage over Invision. Having everything in Invision is just so much easier, not only for designers and developers but it’s also also useful and accessible to our account managers, project managers and of course our clients too.</p><p>Zeplin gives you measurements, assets and style guides but Invision does (almost) all of that whilst being an excellent prototyping and communication tool.</p><blockquote>“Zeplin gives you measurements, assets and style guides but Invison does (almost) all of that whilst being an excellent prototyping and communication tool.”</blockquote><p>For us, the result is that we are spending more time designing, coding and thinking while crafting our products quicker, which means releasing faster.</p><p><em>Invision Inspect: </em><a href="https://www.invisionapp.com/feature/inspect"><em>https://www.invisionapp.com/feature/inspect</em></a></p><p><em>Zeplin: </em><a href="https://zeplin.io/"><em>https://zeplin.io/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b30ce36d75a" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/will-inspect-from-invision-replace-zeplin-in-your-workflow-9b30ce36d75a">Will Inspect from Invision replace Zeplin in your workflow?</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple and (mostly) free UX and Design setup for your project]]></title>
            <link>https://blog.prototypr.io/simple-and-mostly-free-ux-and-design-setup-for-your-project-b3c088a2168e?source=rss-2c6d17d3381f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3c088a2168e</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[free]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[tools]]></category>
            <dc:creator><![CDATA[Thomas Michalak]]></dc:creator>
            <pubDate>Fri, 29 Jul 2016 15:19:51 GMT</pubDate>
            <atom:updated>2016-12-02T15:23:03.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZbq9f2DBpWeXVojwJiv1A.jpeg" /><figcaption>Illustration by Ryan Phipps Mitchel — <a href="http://rpm-design.co.uk/">http://rpm-design.co.uk/</a></figcaption></figure><p>I was recently asked by a client to share our UX and Design process, part of the exercise was to write down a list of the tools we use.</p><p>I’ve lived through the web revolution, death of flash, Web 2.0, the gold rush to apps, the rise from the aches of jS, etc… and I think that the new revolution is with the tools that are available to designers and developers nowadays. When I started working in Digital we only used to have 2 main tools, Photoshop and Dreamweaver and for the cool kids Fireworks and an open source editor. Designers also had to be specialists, there was your flash designer and your web designer or your graphic designer. Our tools used to be complicated and hard to pick up.</p><p>We now have so much choice it’s sometimes hard to decide which one to pick and dedicate your time training yourself (I mean how many adobe tools got canceled last year? How many new prototyping tool comes out every 3 months?). That’s probably why a lot of designers can’t let go of Photoshop. But people who make those new tools understand this pretty well and it’s now easier to pick up a new product and ditch it when somethings better or more relevant to your project comes up.</p><p>It’s now easier than ever to do your discovery, plan your project, communicate with your team, share your work, get feedback from the people who will interact with your design, test and validate concepts. Less time spent on doing the boring stuff means more time to concentrate on the real work.</p><p>There are many other tools that I won’t mention, things like Axure, UXPin or <a href="https://popapp.in/">Pop Prototyping</a> which let you photograph sketches and make those into a prototype. Seems like every day a new prototyping tool is released (although Pop is actually one of the first!)</p><p>As an only piece of advice I would say:</p><blockquote>Tools are just tools, don’t let them own you, use what ever gives you results and work well for your team and clients. (Pen and paper still wins it all for me)</blockquote><h4>UX &amp; Prototyping</h4><p><em>We’re not selling static images or jpgs and our tools have to reflect our medium. We’re working with dynamic and responsive content, hyper journeys (almost nothing is linear in our world), interactivity, visual feedback and hyperlinks. My teacher used to call this Hypermedia instead of the internet as a medium or digital (that was 15 years ago!).</em></p><p><strong><em>Invision</em></strong> <strong><em>(</em></strong><a href="http://www.invisionapp.com/"><strong><em>www.invisionapp.com</em></strong></a><strong><em> Free)</em></strong> This is my main prototyping tool, it’s quick and easy, that mean we’re not precious with our prototypes. People can comment, live shares, it integrates with sketch and photoshop. You can either use it straight on your phone or on your computer. It’s really great to test user journeys and get a real feel for it. I don’t know how we managed before those prototyping tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U14ECzIen5X39C16w28odw.png" /><figcaption>Hotspots in Invision</figcaption></figure><p><strong><em>Principle</em></strong><em> </em><strong><em>(</em></strong><a href="http://principleformac.com/"><strong><em>principleformac.com</em></strong></a> <strong><em>One off $99)</em></strong> This is to create micro-interactions, transitions and animations, try out ideas. I used to do those kind of things in After Effects (or <a href="http://processing.org/">processing</a> for interaction) but most designers struggled with AE or can’t code. This just made mocking animations easy and sweet, it’s dead easy to pick up, especially if you watch the 5mins tutorial on their website. I wouldn’t use it for the whole thing like Invision but for the details, the delights bits or the things that can’t be represented with a static image, it even support videos. It also integrates with sketch, just click the import button to grab an opened project in Sketch. You can load it on your phone, record a video and even export as a mac app (pretty cool). Check out some great examples at <a href="http://principlerepo.com/">http://principlerepo.com/</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-rSFT42JPeRakN16DuMSKw.gif" /><figcaption><a href="http://principleformac.com/sample_files/date_night.prd">Date Night</a> by <a href="https://dribbble.com/nimasha_sperera">Nimasha Perera</a></figcaption></figure><p><strong>White board</strong>: Our work might be mostly digital but we’re still working with humans too, and the quickest way to communicate ideas between humans is language and drawing. This is certainly not free but such a valuable tool (and slightly off topic). In our previous office I got a whole wall to be made into a white board, this the best tool we have, the quickest way to share ideas and layout complex journeys in front of everyone. We now have white boards in all our meeting rooms. The bigger the better, when your in the flow you don’t want to reach the end of your board. It will also help you putting some distance between you and your ideas as well as having a wider view of all your concepts.</p><h4>Design &amp; Production</h4><p><em>You don’t want to sit on your design for ever and you need to use real data and content to cover real life scenarios. So many beautiful mock ups out there that wouldn’t actually work or even solve a real problem (dribbble is full that sort of none sense)</em></p><p><strong><em>Sketch (</em></strong><a href="https://www.sketchapp.com/"><strong><em>www.sketchapp.com</em></strong></a><strong><em> One off $99 until v4)</em></strong> That’s an obvious one. Not much is needed to be said about it as so much as already been written. I like the constant updates, how they understand trends and listen to their users and the tiny file sizes. the new group sizing feature just nailed working on responsive design, super clever.</p><p><strong><em>Craft plugin (</em></strong><a href="https://www.invisionapp.com/craft"><strong><em>www.invisionapp.com/craft</em></strong></a> <strong><em>Free) </em></strong>One the great things about Sketch is the plugins. Invision has been taken advantage of this feature with their Craft plugin. You can generate content (names, articles titles, dates and even create your own lists), use real data (from the web, api, photo libraries), create and share libraries with the team (symbols, text style, artboards, elements), they even introduce a prototyping tool, that bit is not actually that great (at least it wasn’t in the beta) but I’m sure this will become amazing really quickly.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F153858834%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F153858834&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F554261530_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/6ee67eea166ae966c45908d25008fbf6/href">https://medium.com/media/6ee67eea166ae966c45908d25008fbf6/href</a></iframe><p><strong><em>Zeplin (</em></strong><a href="https://zeplin.io/"><strong><em>zeplin.io/</em></strong></a><strong><em> Free)</em></strong> This tool just simplified the exchange of assets between Designers and Front-end as well as the creation of stylesheets. Remember the crazy spreadsheets, annotated files or pdf that ultimately were either not read or out of date as soon as you were doing updates. Everything sit in one place, the developer can see all measuremts in your design, grab assets, grab colours, fonts, text, export assets as svgs, png, jpgs, they even can get the css out of it formated according to their favourite framework (sass, etc…). This tool makes it easy when getting started or doing quick <em>in-browser</em> prototypes. Designers love it and every Developers I worked with loved it as well.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FtHmzAytSgpI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtHmzAytSgpI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FtHmzAytSgpI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e07c3771009e37c9a6fa56d6473ddb67/href">https://medium.com/media/e07c3771009e37c9a6fa56d6473ddb67/href</a></iframe><h4>Data &amp; User Testing (all for free!)</h4><p><em>You simply just cannot rely on your experience and gut feeling, if you are designing for someone else than yourself you need to understand them. It’s funny how some designers will tell you how much they need to connect with their client to truly understand their needs but will completly ignore the end-user in fear of spoiling their creation. None sense.</em></p><p><strong><em>Hotjar (</em></strong><a href="https://www.hotjar.com/"><strong><em>www.hotjar.com</em></strong></a><strong><em> Free) </em></strong>This is simply amazing, I believe this is closing the gap between user testing and analytics, it will generate heat maps, scroll maps and record people will using your site on mobile and desktop (yes record!). It’s great on an existing live product but also if you’re doing a beta. Absolutely love it. You can also use it to get feedback from visitors with the Polls and monitor funnels. You can trigger recording or tagging using JS and most features can be turned on or off in case one of your client has some tight privacy policies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sPpo9SdmJ2w1Obe42RlWBg.jpeg" /><figcaption>Hotjar is more than just Heatmaps, it records users and let you get feedback straight from your product</figcaption></figure><p><strong><em>Silverback (</em></strong><a href="https://silverbackapp.com/"><strong><em>silverbackapp.com</em></strong></a><strong><em> 2.0 is Free)</em></strong> There’s other we’ve tried (like lookback that comes with invision) but this just the simplest and most effective (and it’s made by clearleft in Brighton). To be honest the advantage of those softwares is that it also films the user. There’s many way to do user testing (one to one, distance, groups, etc…) what ever you want to do you need to understand what and why you’re testing. User testing is simple but making the conclusions out of the testing sessions can be overwhelming. What ever you do, just put your work in front of others.</p><p><strong><em>Typeform (</em></strong><a href="https://www.typeform.com/"><strong><em>www.typeform.com</em></strong></a><strong><em> Free) </em></strong>This is the best survey tool on the planet, if you don’t believe me check out their twitter feed. This is a great way to do interviews and get feedback when people are too busy, not available, or too simply reach out to your customers. It works beautifully on mobile and it’s super easy to create. “Forms for Humans” as the say.</p><h4>Planning &amp; Documentation (Free)</h4><p><em>Those 2 are obvious but worth mentioning as they’re free, straight forward and great for collaborations.</em></p><p><strong><em>Google Tools (Free)</em></strong>: Google tools are the easiest way to get started with documentation, user flows and presentations. It’s free and makes it easy to collaborate with your team and client. Google Drawings is a hidden gem, creating flows is dead easy but most of all it’s easy to update and can look great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*UYMep1TCXIJZfxbJji-c9A.png" /><figcaption>Docs, Slides and Drawings</figcaption></figure><p><strong><em>Trello (</em></strong><a href="https://trello.com/"><strong><em>trello.com</em></strong></a><strong><em> Free)</em></strong>: You probably know about that one too. There’s some pro and cons to Trello, especially compared to something like Jira but it’s also a lot easier to use and it’s lot more team friendly than Jira.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*bBPFBwO_3pNwL5eqDw1zAQ.jpeg" /><figcaption>Simple interface, super straight forward and integrates with products such as slack</figcaption></figure><p>That’s it, it’s my first medium post, if anyone got to the end (which I doubt) leave a comment!</p><p>Check out our work: <a href="http://graphitedigital.com/">http://graphitedigital.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3c088a2168e" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/simple-and-mostly-free-ux-and-design-setup-for-your-project-b3c088a2168e">Simple and (mostly) free UX and Design setup for your project</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>