<?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 Darren Bennett on Medium]]></title>
        <description><![CDATA[Stories by Darren Bennett on Medium]]></description>
        <link>https://medium.com/@protopilot?source=rss-fb3cb03411b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*59hqSS5R8p7BJkH3n5lAnQ.png</url>
            <title>Stories by Darren Bennett on Medium</title>
            <link>https://medium.com/@protopilot?source=rss-fb3cb03411b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:58:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@protopilot/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[What is a design pipeline and why does it matter]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@protopilot/what-is-a-design-pipeline-and-why-does-it-matter-21bca01629ad?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/1536/1*hg1cRsO29SwPJpgB8YMBFw.png" width="1536"></a></p><p class="medium-feed-snippet">All product features start with an idea and follow a sequence of steps to delivery. This is called the design pipeline but for most teams&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@protopilot/what-is-a-design-pipeline-and-why-does-it-matter-21bca01629ad?source=rss-fb3cb03411b6------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@protopilot/what-is-a-design-pipeline-and-why-does-it-matter-21bca01629ad?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/21bca01629ad</guid>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 09:48:55 GMT</pubDate>
            <atom:updated>2025-09-23T09:48:55.653Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How designers can help prioritise product features]]></title>
            <link>https://medium.com/@protopilot/how-designers-can-help-prioritise-product-features-db6d1a08f6b1?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/db6d1a08f6b1</guid>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Sun, 13 Jul 2025 22:32:39 GMT</pubDate>
            <atom:updated>2025-07-13T22:32:39.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yTRkcq-fK2XKDYpgOO2vEA.png" /></figure><p>In the fast-paced world of product development, it’s easy to get swamped with feature requests from all directions. Product teams often bring a flood of ideas inspired by other apps, without knowing if those features will truly resonate with our users.</p><p>By up-skilling your team in advanced prototyping, you can quickly transform these ideas into tangible, testable prototypes. This not only helps you share and socialise these concepts with stakeholders but also allows you to test them with real users. The result? You receive a reality check on what truly adds value and what might be mere noise.</p><p>Ultimately, this means that your prioritised feature list is driven by real user insights, not just internal assumptions.</p><p>Here are some tips on approaches I have used to determine what tools work best for teams when testing ideas for prioritisation:</p><ul><li>Spend some time researching the tooling landscape, follow top voices in the world of advanced interaction tools and AI, to get their take.</li><li>Seek out people who are using these tools and processes. There’s a lot of noise out there right now so find the ones applying it to real projects.</li><li>Discuss with your team to determine what they have tried. Create a regular meeting or section in your design meeting to chat.</li><li>Set a task for each team member to try out a tool and then report back. How easy was it to pick up? Was it useful for your context? Did it solve any problems you have?</li><li>Look out for experts you can bring in and talk to your team in a lunch ’n’ learn style talks.</li><li>Look out for free webinars that you can join as these give you the ability to ask questions and get a wider impression from people in other companies.</li></ul><p>Here are some tools you should have a look at to see if they’re a good fit:</p><p><a href="https://www.protopie.io/">ProtoPie</a> — My go-to tool for prototyping. Create realistic prototypes with this no-code tool, and you’ll dazzle your stakeholders. They’ll think you’ve built the real thing. Import your Figma designs and start adding triggers and responses. Use conditional logic, device sensors like the camera, text-to-speech for voice UI, variables, keyboard input, video, and connect multiple prototypes for multi-device functionality. Create software/hardware prototypes with ProtoPie and Arduino, and utilise real APIs.</p><p><a href="https://createwithplay.com/">Play</a> — If you want to create native iOS prototypes, take a look at Play. No code/low-code tool. Uses iOS core animation. Has native components like Apple Maps, import from Figma, use real API’s, and design with real layout constraints.</p><p>Prototyping your ideas and creating tangible objects that people can use is the key to identifying the valuable from the less valuable. It helps you follow an evidence-driven process rather than an opinion-based one, and gets you to the good ideas you would never have thought of, just by using Figma.</p><p>To find out more about advanced interaction tools, check out <a href="https://protopilot.co.uk/">https://protopilot.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db6d1a08f6b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a Product Design A-Team]]></title>
            <link>https://medium.com/@protopilot/how-to-create-a-product-design-a-team-398bc72c3020?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/398bc72c3020</guid>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Sat, 21 Jun 2025 12:00:03 GMT</pubDate>
            <atom:updated>2025-06-21T12:00:03.473Z</atom:updated>
            <content:encoded><![CDATA[<p>In a world where headcounts are being reduced but the workload isn’t, how do you achieve more with less?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oltHuDj5keGKNb0BgzjhMQ.png" /></figure><p>We are at a time in our industry where many design teams have reduced headcounts, yet the workload itself isn’t changing. Furthermore, many of the feature requests received appear to be invaluable and unvalidated. So, if you are a lead designer or Head of UX, how can you skill up your team to meet this challenge head-on?</p><p>I’ve worked with many teams, helping them upskill and embrace new tools and methods. Over the thirty years I’ve been doing this, I’ve found some key things that’ve worked for me in delivering the best results. So in this article, I wanted to share what those are:</p><h3>Use research and your team’s experience</h3><p>Think critically about what will make a difference to your customers and stop features before they’ve started by using a solid test-and-learn strategy. There have been many occasions where I’ve stopped useless features in their tracks. These are things that often come from other apps that stakeholders have seen. Ensuring a feature is right for your service and audience is crucial and requires thorough research. From there, you can build prototypes up to super realistic ones and test with real people before you’ve written a line of code.</p><h3>Prototype early and at a high level of realism</h3><p>Create tangible prototypes that you can use and test with. Our brains are wired for play, which makes designing with high fidelity (visual + interaction and motion) prototypes the best way to truly see if an idea is useful or not. Designing interactively helps your team generate ideas they would never have thought of if they had designed statically.</p><h3>Upskill your team to a crack unit of generalists</h3><p>Many people eschew design generalism, citing the fact that being a jack of all trades makes you the master of none, but the truth is you don’t have to be the master of any one skill. Remember, all of these skills add up to making you a specialist designer or maker of products, and that’s where your real value is.</p><h3>Use AI in the right way</h3><p>AI is a powerful ally when used correctly. Use it to automate repetitive tasks and to augment your team’s weaker skills. Identify candidates on your team who are open and even excited to level up their skills. One of the long-standing debates is whether designers should code. I’ve always had a deep fascination for code and delivered many products, having designed and coded them all myself, but I made a decision a while back to focus on being a designer rather than a coder. Now, with AI by my side, I can be both.</p><p>If you have team members with an aptitude for code at a theoretical level, you can now augment them with tools like Cursor or V0. Another great way is to use AI as a learning tool. I routinely chat with ChatGPT about how to solve advanced logic problems when prototyping, both when using tools like ProtoPie and in real code. Utilising AI in this manner is a clever approach to upskilling your team.</p><p>Another approach is to invest in specialist trainers to come in; this works exceptionally well when you need to turn things around quickly, especially if you find one who has real industry experience as well. This is something I’ve done many times within the teams I’ve worked with.</p><h3>Stay aligned</h3><p>I’ve seen so many teams lose their way mid-project because they don’t implement guardrails to help them stay aligned. Using a vision prototype as a single source of truth prevents teams from wasting time reinventing the wheel over and over, and helps them think critically about what they’ve designed. Of course, having a vision prototype also makes it insanely easy to test with customers at the drop of a hat. Being in a constant test-and-learn mode helps teams iterate.</p><p>I recently read about an interesting study where an experiment was conducted with two groups. Each group was tasked with creating a ceramic cup. Team one had to make a single perfect cup while the other team could make as many as they liked. The outcome? The iterative team created a better cup, and in fact, they produced multiple amazing cups, while the other team spent most of their time at the drawing board trying to plan the perfect cup. You can think of a vision prototype as the iterative cup that’s constantly being changed and refined.</p><h3>Size matters, but not in the way that you think</h3><p>The truth is that smaller teams can outperform bigger ones and often create better solutions because they are highly skilled and they have a more intimate relationship. The core design team at Apple for the design of the Macintosh was only 16. Adding more headcount never translates into increased productivity, just more debate; however, with a highly skilled and multifunctional team, you can 10X both the quality of their output and productivity.</p><p>So, if you’re struggling with reducing headcount and too many feature requests, most of which have no value, then try the steps above to turn your team into an A-Team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=398bc72c3020" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The #nocode revolution has begun — which will you choose?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/interact-magazine/the-nocode-revolution-has-begun-which-will-you-choose-2082ea051974?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/1920/1*xVq_Yu8231P_YG1LWOMjmQ.png" width="1920"></a></p><p class="medium-feed-snippet">Hello and welcome to the first ever issue of interact, the newsletter dedicated to the world of interaction and motion design tools.</p><p class="medium-feed-link"><a href="https://medium.com/interact-magazine/the-nocode-revolution-has-begun-which-will-you-choose-2082ea051974?source=rss-fb3cb03411b6------2">Continue reading on Interact Magazine »</a></p></div>]]></description>
            <link>https://medium.com/interact-magazine/the-nocode-revolution-has-begun-which-will-you-choose-2082ea051974?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2082ea051974</guid>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Wed, 10 Jul 2024 16:40:27 GMT</pubDate>
            <atom:updated>2024-07-10T16:40:27.349Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A tale of misplaced value]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@protopilot/a-tale-of-misplaced-value-3239f64d5a25?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/1280/1*8UQ5YVEiNLvbiU-FWsK8aQ.png" width="1280"></a></p><p class="medium-feed-snippet">Let me tell you a true story about the misplaced value of saving costs on a project. For this story, I&#x2019;m going to take you back in time&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@protopilot/a-tale-of-misplaced-value-3239f64d5a25?source=rss-fb3cb03411b6------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@protopilot/a-tale-of-misplaced-value-3239f64d5a25?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3239f64d5a25</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[loss]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Sun, 12 May 2024 15:16:41 GMT</pubDate>
            <atom:updated>2024-05-12T15:16:41.141Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why prototyping is crucial to designing successful digital products]]></title>
            <link>https://medium.com/@protopilot/why-prototyping-is-crucial-to-designing-successful-digital-products-9e8bcf15e2f4?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e8bcf15e2f4</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[motion-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Wed, 19 Apr 2023 15:10:36 GMT</pubDate>
            <atom:updated>2023-05-12T22:32:22.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tools like Figma are great for designing UI graphics, but if you’re only using Figma your only designing half the experience. Here are 8 things prototyping can help you do to deliver a complete product experience.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FfVqpefS26hn3fnYJPTqOQ.png" /></figure><p>If you walk into any product design studio today you’ll probably see designers using a UI graphics app, most likely Figma.</p><p>Figma’s main focus is the graphic design of user interfaces. Figma does, of course, have the ability to prototype, but its capabilities for the most part sit at the low-fidelity end.</p><p>Figma is also great and handing off graphic design to development teams but it doesn&#39;t have any capability of handing off anything else. These facts mixed with the fact that most designers live in the sandbox of Figma UI creation has resulted in interaction and motion design to not be considered thoroughly enough in the design of products.</p><p>So if you’re sitting there creating a design at high fidelity from a set of Figma libraries, laying out frames in a user flow ready to add that Figma link to a JIRA ticket then you’ve left out half of the design of the feature you are about to deliver. More than that, you’ve missed out on all the benefits prototyping gives you through the ideation stage.</p><p>It’s time to stop relying on any single tool for design and re-embrace the process of designing. To do that you need to be prototyping in all different ways and for all different reasons.</p><p>To get started let’s define something very important.</p><h3>What is prototyping?</h3><p>Here’s what The Interaction Design Foundation says prototyping is:</p><blockquote><strong>“Prototyping is an experimental process where design teams implement ideas into tangible forms from paper to digital.”</strong></blockquote><p>This definition gives us what prototyping is but not the why. It’s worth also separating in your head prototyping from interaction and motion design. While they can all exist together they don’t necessarily have to, and they definitely should also exit apart. This may sound a bit cryptic but bear with me!</p><p>Let me define another principle for you:</p><blockquote>Interaction and motion should be mandatory considerations in both the ideation process and a deliverable for handover.</blockquote><p>Ok, so we need to be creating prototypes as well as interactions and motion. What could this new prototyping sandbox look like?</p><h3>Forms of prototyping</h3><p>We can make prototypes in many ways using lots of different tools. The point of a prototype is to validate an idea in reality.</p><p>Until you have something that you can touch and use it’s just an idea.</p><p>Tom Chi, a designer on the Google Glass team talked about this in his <a href="https://youtu.be/DkyMCCnNI3Q">TEDX</a> talk. The Google Glass team was debating what colour the overlay text should be. Without testing various colours everyone’s suggestion was just their opinion. So they built a prototype to test what colour would actually work the best.</p><p>Tom defines the first rule of rapid prototyping as <strong>Direct Experience. </strong>Direct Experience<strong> </strong>is a way to uncover real problems and to get to those problems we need to get to something tangible as quickly as possible. Only by experiencing our concept directly can we uncover the real problems we need to solve.</p><p>The best way to prototype a concept does depend on what you are designing but for digital products, the most common forms are:</p><p><strong>Paper </strong>— An analog process where you are making something from paper. The interactions are created usually using a human as the computer e.g you press a button and someone orchestrates the motion. Other more elaborate executions delve into the realms of paper mechanics similar to what is used in the creation of pop-up books and paper theatre kits.</p><p><strong>Low/Low fidelity</strong> — Low fidelity visuals and low fidelity motion. This is otherwise known as the click-through popularised by InVision. Here you are creating very crude interactions devoid of true motion. A button is clicked and the next screen instantly appears.</p><p><strong>Low/Mid fidelity</strong> — We don’t need a high-fidelity UI to test high-fidelity motion. We can mix the two at different fidelities. Here I’m using ProtoPie and its ability to access the camera on my device to test the UI. I can validate the crude visuals first before increasing the visual fidelity.</p><p><strong>High/High fidelity </strong>— This is as close to the real product as I can get. Again using ProtoPie I can create a prototype that uses high-fidelity visuals and motion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JwZeIpD4UT2Z2Bc7qtp1A.png" /><figcaption>Types of prototyping — download the ProtoPie player and scan the QR codes to try them out!</figcaption></figure><h3><strong>Where can prototyping help you in the design process?</strong></h3><p>Now we know what you can create, let&#39;s talk about why you should. Here are eight reasons why I think you should be prototyping more and where prototyping can help solve some problems I’ve seen teams come up against when they only design static comps.</p><h3>1. Encourages you to play with ideas</h3><p>Digital experiences exist beyond the 2 dimensions of our sketchbooks or Figma. Prototyping enables us to play with ideas in a tangible form in any or all of the ways explained above. But why is making things tangible important?</p><h4>The Science of Play</h4><p>It turns out that there is a special part of the brain dedicated to playing known as the Play Circuits. You can read all about the scientific research that’s been done at the <a href="https://www.nifplay.org/what-is-play/biological-drive-to-play/">National Institute for Play</a> which highlights some key points as to why play is intrinsic to us as humans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*JxuEWuiPT0zf2PMA5UmdDw.png" /><figcaption>Play Circuits in our Midbrain</figcaption></figure><p>Play Circuits are a key part of how we assess and interact with the world around us. When we are presented with something interactive such as a prototype our play circuits are activated which in turn motivates us to interact.</p><p>The Play Circuits exist in our midbrain with neural pathways that connect to all of our higher brain functions such as communication and creativity.</p><p>Play is key for us in a couple of ways:</p><ol><li>It enables us to connect to our creative brain functions which helps us think of more ideas</li><li>It facilitates communication with stakeholders and allows them to tap into their creativity when they are feeding back.</li></ol><h3>2. Prototyping forces you to design for interaction</h3><p>Whether we are sketching or designing in Figma we are predominantly designing the way our concept looks rather than how it works.</p><p>We’ll have an idea in our heads as to how we think the interface will be interacted with and how it will behave but it’s likely to be a crude hypothesis in our heads and needs to be validated by building it into something tangible.</p><p>In creating a prototype we are forced to apply interactions just as a developer is required to when building a real app. Having to do them forces us to think about and consider them.</p><p>Often when I start prototyping my ideas it will cause me to make different UI decisions. Interaction and motion bring context as I join the dots and a narrative start to form in front of me. I’m slowly bringing my concept to life.</p><p>The great Don Norman talks about Feed Forward and Feed Back in the legendary <a href="https://www.goodreads.com/en/book/show/840">The Design of Everyday Things</a>. Prototyping Allows us to take the role of the system and decide what affordances are interactive and how they will behave when interacted with. Only the prototyping process allows us to do this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wJd8gpvfg5uPpHx3cZIV1w.png" /><figcaption>A crude sketch that needs to be validated with a prototype</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i-eVY0Y1c2p0F9JYgQL4IA.png" /><figcaption>A working prototype. Scan the QR code and try it out for yourself in ProtoPie Player on your phone</figcaption></figure><h3>3. Prototyping enables you to design for motion</h3><p>When I think of interaction design I actually see it as having two parts.</p><ol><li>The trigger that you choose for a person to use to interface with your product e.g a tap</li><li>The translation of your interfaces properties over time</li></ol><p>Point one refers to interaction design which we covered in the previous section. In this section, we’ll cover point 2, Motion Design. So what is Motion Design?</p><p>In the most simplistic terms, motion is the change of a property (or properties) over time. For example, opacity is a property that has a value range of 0–100 with 0 being transparent and 100 being opaque. If I want an interface element to fade out I’m changing the opacity property over time. So motion isn’t just the movement of an object from one place to another, it’s the gradual change of an object’s property.</p><p>Considering motion is important for a number of reasons:</p><h4>Physics of the real world</h4><p>We, humans, assume that the products we use obey the same physical laws that we do. If I drag an object on my phone screen it should move the same as if I was moving a cup from one side of my desk to the other.</p><p>When something works the way we expect it to we say that it fits our <a href="https://en.wikipedia.org/wiki/Mental_model">mental model</a>.</p><h4>Brand Personality</h4><p>Motion design is a key mechanism to help imbue your product with <a href="https://blog.hubspot.com/marketing/what-is-brand-personality">Brand Personality</a>. Motion is as important a lever for your brand as Tone of Voice is. If ToV is the way your brand speaks, Motion is your brand&#39;s body language.</p><h4>Usability</h4><p>Usability is what we are all striving for. We want our product to be usable, accessible, and inclusive. Motion can play a key role in all of these.</p><p>If you think about motion in terms of wayfinding, having a sense of where you’ve been and your direction of travel is key. An example of this is the way the interface moves. In iOS when you tap a button and then tap the back chevron the view moves first from right to left and then back again. If it instantly jumped from one to the other it would be a lot harder to understand what had happened.</p><p>Because motion is part of the overall experience of a product it can impact <a href="https://www.nngroup.com/articles/aesthetic-usability-effect/"><strong>The aesthetic-usability effect</strong></a><strong>.</strong></p><p>In fact, I would argue that great motion design is more important than great visual design. It comes back to the aesthetic-usability effect—we expect something that looks great to feel great but when it doesn’t, it leaves us with a sour feeling.</p><h3>4. Prototyping helps uncover things that you have forgotten to design</h3><p>When we design in Figma we design our products as static interfaces or storyboards. Each frame will be a snapshot of a point in time but what happens between the frames we don’t consider. This has the result of leaving parts of the experience either undesigned and conversely risks some of what has been designed to be undesirable.</p><p>In the example below the Figma design shows two frames in a storyboard. The first shows the login screen unfilled and the next frame shows the person successfully logged in.</p><p>If we look at the prototype below we can see a number of extra things happening that hadn’t been considered such as the keyboard coming up, causing the primary CTA to move, and the need for a loading animation while the API call is made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oeYqUdu0VBNJC91dc3NetA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*pirvXuuLzUtqRzPiYWcrzg.gif" /></figure><h3>5. Helps you to communicate with stakeholders</h3><p>When designing in static comps in Figma, the only way to communicate the design is by whizzing around a Figma file explaining our design as we go.</p><p>I refer to this activity as ‘telling the design’. Apart from giving me motion sickness this way of communicating is confusing and hard to follow. It relies on the designer to remember every interaction and motion detail and the ability to communicate it through words effectively. Without something tangible to share people interpret the experience differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*d5PEA49bYHuRsfLa40EdeQ.gif" /></figure><p>Showing a prototype conveys a narrative that can be easily followed. With a prototype, we are showing rather than telling our design.</p><p>The added benefit is that we can share the prototype with stakeholders to allow for some playful experimentation ( see Section 1 — Encourages Play).</p><p>When I deliver a design to be estimated by a dev team I deliver a high-fidelity prototype and not a Figma link. Prototyping is a great way to show exactly the experience they want to be built and a dev team can now use that to estimate accurately.</p><p>If we only show a static Figma comp the dev team won’t take into account anything but the most basic motion. which with apps might be basic transitions and for websites probably no motion at all.</p><p>On top of that, we’re likely to get a plethora of ‘what happens when…’ questions which normally come at the point the feature is being built.</p><p>The outcome here is normally not great for a couple of reasons. The designer will be under pressure to come up with a solution quickly and any solution they provide will need to either be basic so it can be built or pushed as a feature to a future sprint or release.</p><h3>6. Helps you to consider real device features and constraints</h3><p>Prototyping allows us, to put our design on the target device, whether it be a Phone, Tablet, or TV. In fact, any hardware with a screen can run your prototype.</p><p>Referring back to Tom Chi and his Google Glass story, we need to get to a direct experience as fast as possible and that means experiencing a concept where the final product will exist.</p><p>In a way, this point is a cumulation of all the others as to the ‘why do it’ question. People will engage more with a prototype on a real device. You can test real hardware features on a device. You can understand the ergonomics of a device.</p><p>When I was at Microsoft I worked within the interaction design team responsible for the <a href="https://www.microsoft.com/en-us/d/surface-duo-2/9408kgxp4xjl?activetab=undefined">Surface Duo</a>. The Duo has eight postures. That’s eight different ways of using it. It would have been very hard to design for such a device without being able to run prototypes on it. We used ProtoPie as our tool of choice with a little help from the dev team we overrode the native Android OS and full-screened prototypes to make it feel as real as possible.</p><h3>7. Helps you test for usability and accessibility</h3><p>I worked with Sainsbury’s on the brand-new <a href="https://apps.apple.com/gb/app/nectar-shop-collect-points/id385266473">Nectar app</a>. This app launch was very high profile and needed to be delivered to a tight schedule. We worked in design sprints, testing prototypes in regular lab sessions every two weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*IChoqpyYjSc5OJ1FiCk53A.gif" /><figcaption>Prototyping in multiple fidelities</figcaption></figure><p>We used the low/low fidelity prototypes initially and then moved the fidelity all the way up to High/High. If we hadn’t had that buy-in from the business and capability we wouldn’t have been able to deliver such a great product but more than that, we wouldn’t have been able to test all the playful interesting ideas we had.</p><p>Not only could we test the usability of our ideas we could also test their accessibility for people with a range of disabilities such as sight, mobility, and Autism. It is so important to design inclusively and prototyping direct experiences and testing them with a range of people is crucial for success.</p><h3>8. Enables you to handover motion design</h3><p>Prototypes are a great way of communicating interaction design to a developer. Most prototyping tools enable you to export videos but one tool, in particular, goes that extra mile.</p><p>ProtoPie has a feature called <a href="https://www.protopie.io/learn/docs/interaction-recordings/getting-started">interaction recordings</a>. These recordings can be shared with the dev team allowing them to get to all the important values they need, to replicate the design in code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35SAGRaKgDQQJ1DWIKN1vg.png" /></figure><p>ProtoPie can show the easing curves, durations, and delay values that make up the motion.</p><p>I’ve used interaction recordings to great success on multiple projects. Having an app gives access to dynamic documentation has the benefit of not constraining me in the complexity of the motion I create or the confusion of trying to articulate that manually.</p><h3>In Summary</h3><p>We should all be designing interactively rather than statically. Of course, we need to design the visual interface in Figma but it shouldn’t stop there. That’s only half the design.</p><p>Prototyping is just another word for interaction and motion design. It’s important to prototype for validation but we also must not forget to deisgn and hand off interaction and motion as well.</p><p>Remember Tom Chi’s words. Validate experiences directly on the device rather than having pointless arguments which are just a clash of people&#39;s opinions.</p><p>Finally, embrace interaction design with all of your senses and in all the dimensions that the world has to offer. Don’t get institutionalized inside of Figma (or any tool for that matter) as it will make your designs stale and your creativity blunt. Keep things shiny and sharp by exploring new ways to create experiences that challenge the status quo and change the world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e8bcf15e2f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Figma’s Smart Animate versus ProtoPie’s Smart Jump]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@protopilot/figmas-smart-animate-versus-protopie-s-smart-jump-4ae54cfd534c?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/1920/1*WqAzLJoRuKk2iyqRBxIg6A.jpeg" width="1920"></a></p><p class="medium-feed-snippet">ProtoPie has added Figma&#x2019;s Smart Animate feature to its animation capabilities, but how do the features compare and how does it change&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@protopilot/figmas-smart-animate-versus-protopie-s-smart-jump-4ae54cfd534c?source=rss-fb3cb03411b6------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@protopilot/figmas-smart-animate-versus-protopie-s-smart-jump-4ae54cfd534c?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ae54cfd534c</guid>
            <category><![CDATA[protopie]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 22:03:15 GMT</pubDate>
            <atom:updated>2023-01-03T22:20:42.147Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ProtoPilot in 2023]]></title>
            <link>https://medium.com/@protopilot/protopilot-in-2023-9f585cb1a8ca?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f585cb1a8ca</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[protopie]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 10:36:12 GMT</pubDate>
            <atom:updated>2023-01-03T10:36:12.745Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here’s what to expect from ProtoPilot in terms of new content in 2023 here on Medium and other channels like Patreon, YouTube, and Udemy.</h4><p>First off, the good news is I will be posting a lot more content than you’ve seen in 2022! This is my commitment to you so thanks for those of you sticking with me. Here’s a rundown of the content that will be coming your way, together with some ideas for new content you haven’t seen before.</p><h4><strong>Weekly posts</strong></h4><p>This year I’m going to be posting a weekly video demystifying the prototyping of various design patterns for apps of all kinds but I need your help. If there’s a problem you’ve hit or a thing you want me to show you how to prototype then message me and let me know. At the end of the day, I want the content to be relevant to you. I’m a practicing designer with a full-time job so I’ll always have some things to share, but it’s always nice to be able to help you out with things you’re working on as well.</p><h4><strong>How-to articles</strong></h4><p>Medium is a great platform to share how-tos. If that’s something you like then let me know. There’s nothing worse than creating content no one wants to read, especially here!</p><h4><strong>ProtoPie Connect / Arduino</strong></h4><p>Are you aware that ProtoPie has a whole other product called Connect? Connect allows you to prototype with hardware that you create with Arduino and any peripheral that supports <a href="http://socket.io/">socket.io</a>. I’ve been thinking about creating content for this but it’s quite a niche area. If it’s something you want me to look into and create, let me know.</p><h4><strong>Prototyping games</strong></h4><p>Here’s another idea for content. I’ve seen a few game designers starting to pick up ProtoPie to prototype rudimentary 2D mobile games. If that’s something you want to see some content about then send me a message.</p><h4><strong>Product design and interaction design techniques</strong></h4><p>Moving focus slightly, I’m thinking of creating content teaching UX and IXD fundamentals through examples created in ProtoPie and Figma. So this type of content will be less about how to create in ProtoPie (although I’ll still do that) and more about the types of skills and techniques designers should have to be successful in Product design in 2023.</p><h4><strong>Not just ProtoPie</strong></h4><p>Finally, I’ll be looking into creating content in apps other than ProtoPie. I always have my beady eye on the design landscape so you may see content in other apps popping up.</p><p>That about wraps up my thoughts for 2023 for ProtoPilot here on Medium. If there’s anything in the world of interaction design in terms of content you would like me to take a look at then let me know.</p><p><em>Darren @ ProtoPilot</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f585cb1a8ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A better way to communicate and deliver product design to the dev .]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/protopilot/a-better-way-to-communicate-and-deliver-product-design-to-the-dev-3f0c25eceea9?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/2600/1*1bS7IuCGVUhddmC9Z52mAA.png" width="2732"></a></p><p class="medium-feed-snippet">There&apos;s more to communicating designs with your development team than handing over a Figma link. Here are my top tips on communicating&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/protopilot/a-better-way-to-communicate-and-deliver-product-design-to-the-dev-3f0c25eceea9?source=rss-fb3cb03411b6------2">Continue reading on ProtoPilot »</a></p></div>]]></description>
            <link>https://medium.com/protopilot/a-better-way-to-communicate-and-deliver-product-design-to-the-dev-3f0c25eceea9?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f0c25eceea9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 19:14:21 GMT</pubDate>
            <atom:updated>2022-09-18T19:14:21.341Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ProtoPie formula fundamentals: Layer properties]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@protopilot/protopie-formula-fundamentals-layer-properties-cf480052358b?source=rss-fb3cb03411b6------2"><img src="https://cdn-images-1.medium.com/max/1600/1*KA14XwmsnxUbpuPLYvchlg.png" width="1600"></a></p><p class="medium-feed-snippet">In part two of this series we will look at the first building block of formulas, layer properties.</p><p class="medium-feed-link"><a href="https://medium.com/@protopilot/protopie-formula-fundamentals-layer-properties-cf480052358b?source=rss-fb3cb03411b6------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@protopilot/protopie-formula-fundamentals-layer-properties-cf480052358b?source=rss-fb3cb03411b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf480052358b</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[protopie]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Darren Bennett]]></dc:creator>
            <pubDate>Sun, 23 Jan 2022 10:31:14 GMT</pubDate>
            <atom:updated>2022-01-23T10:31:14.920Z</atom:updated>
        </item>
    </channel>
</rss>