<?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 Billy D Stagg on Medium]]></title>
        <description><![CDATA[Stories by Billy D Stagg on Medium]]></description>
        <link>https://medium.com/@billcreative?source=rss-f1394fb8bdd5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ExReOs2M8XrwtnCgdNSS1A.jpeg</url>
            <title>Stories by Billy D Stagg on Medium</title>
            <link>https://medium.com/@billcreative?source=rss-f1394fb8bdd5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:21:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@billcreative/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[Cutting the fat from Product Design]]></title>
            <link>https://uxdesign.cc/cutting-the-fat-from-product-design-5b01b28ff8ed?source=rss-f1394fb8bdd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b01b28ff8ed</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Billy D Stagg]]></dc:creator>
            <pubDate>Sat, 06 Oct 2018 19:52:39 GMT</pubDate>
            <atom:updated>2018-10-10T11:58:04.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyMPpOO5o0S6fay8SduZcw.png" /></figure><p>A few years back I was working on a project for a large organisation redesigning some of their legacy applications. It was the brief designers long for; the opportunity to shape the future UX of a whole family of web-based applications. The first app released would lay the foundations for the others to follow.</p><p>I didn’t waste time and immediately started researching the users to understand the existing software and worked with the product owner and various stakeholders to build a backlog of requirements the team could start working through.</p><p>After a couple of weeks armed with a much better understanding of the challenge at hand, we started workshops to shape the new product. In the meantime, the development team would start laying the essential foundations until we’d validated and detailed requirements and had at least a scribbled wireframe they could work with.</p><p>Fast forward a few months. We’d gone through sketches to wireframes, outlined user flows for the key user journeys, designed UI components along with detailed specifications and even had prototypes that demonstrated how we wanted things to work. We’d been out to customers to test the designs, received great feedback and everything appeared to be heading in the right direction.</p><p>There was one problem. We didn’t have anything built to release and what was built was a million miles away from something we could.</p><p>The problem described above isn’t uncommon. Time and time again we see teams creating designs that don’t get built or get built far from the intended design and experience.</p><p>This is fine for discovery or to validate a proof of concept but in a fast-moving industry, we need release products fast and frequently to stay ahead of the competition.</p><p>Over the past few years, I’ve adjusted my process in order to improve the product development process and wanted to share a few of the key changes which will hopefully help you and your team too.</p><h3>MVP isn’t a buzzword</h3><p>You’ve probably heard “we need an MVP” a thousand times but it shouldn’t just be a buzzword. If you fully understand what makes an acceptable Minimum Viable Product you can help focus the team’s energy and effort towards a release. For a quick release, your team must be willing to release the most basic product. This can be an incredibly hard sell to stakeholders who budget for a fully functional product which delivers all features, but the benefits are plain to see.</p><p>The faster you release, the faster you can get the product out to customers gaining valuable feedback and giving you insights you didn’t anticipate. Also, the sooner you start to acquire users the quicker your user base starts to grow. After a few months of gaining users, you’ll be ahead of the game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lka1F8bgkSRrZT0k_fiN0A.png" /></figure><p>You need to accept the MVP might not be as immediately competitive, but it also doesn’t need to be mass marketed straight away either. The key is to release what you can quickly to pave the way for incremental improvements that deliver ever-increasing value to your users.</p><p>Slack is a great example of a product which relied on the feedback from users to help shape their product. Without having a CMO and mass marketing campaign they won the hearts of their users by listening and incrementally shaping the product.</p><h3>Pop your bubble</h3><p>As individual creatives, we often desire to work in silo with little regard for things outside of our control. Our deliverables are what we’re concerned about and as long as they work and look great we’ve done our job. If the final product doesn’t look or feel like our design then it’s not our fault, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ei3s07Bp1haLv_7lfGVoiw.png" /></figure><p>This is compounded by the fact that humans are emotional beings and visual stimulus speaks volume. It’s easy to wow stakeholders and leave a lasting impression. As creatives, we feed off the opinions of others.</p><p>However, if we disregard high-fidelity mockups and prototypes and are just credited for the results of a released product as opposed to some amazing individual work would we fare as well?</p><p>I’m not suggesting for one minute we stop doing the fantastic, pixel-perfect work. My OCD for perfection stems from the days where 800x600 displays meant an off-pixel design was glaringly obvious and a final product should be perfect. As the Salesforce design team put it:</p><blockquote>“Demonstrate respect for people’s time and attention through thoughtful and elegant craftsmanship”</blockquote><p>A high-fidelity design also enables us to test a realistic product, validate our assumptions and confirm usability. But what’s important is that we don’t waste time creating a portfolio piece that impresses stakeholders but never gets built. Instead, focus on a real-life working product.</p><h3>Find the right cadence</h3><p>To reduce the amount of unused work we need to be aware of everything that’s happening with the product we’re designing. The roadmap, the backlog, what’s planned to be built next and exactly what developers are actively working on at every stage. There’s no point sitting on the outside and hoping that if you show the teamwork you’ve completed it’ll just get built.</p><p>It’s easy and not uncommon for a product team to see design as an afterthought or exclude it completely. As designers we want to problem solve creatively, using our experience and gaining feedback to validate the right solution. We don’t want to be told to “just make it look good”.</p><p>Being aware of everything that’s happening and ensuring the design is an integral part of the product development and release cycle will not only help your designs see the light of day but also bring the rest of the team onboard, which brings me to the next point.</p><h3>Share ownership</h3><p>If you&#39;re fortunate enough to be brought onboard during a product&#39;s inception make sure our ideas involve everyone. It will help the team feel included and give them the opportunity to contribute. Nobody wants to be told what to do so share ownership of ideas and use your expertise and experience to facilitate. The teams desire to deliver a shared idea will be higher and it will also help keep everyone on the same page. You’ll also find the team morale will boost when everyone is in agreement and shares the same goal.</p><h3>Get to code</h3><p>The subject of whether designers should code has been a hot debate for many years. As someone that’s as comfortable as a UI Developer as I am as a UI Designer, I’m probably a bit biased. I understand it’s a luxury and it takes a lot of time investment to learn how to code but the benefits are easy to see. For me, the ability to code gives me a freedom to express ideas in working code. Sometimes it doesn’t need to be production code, it’s quick and messy but nevertheless delivers an experience to the target platform reducing the number of errors interpreting or trying to recreate a design later.</p><p>If designers won’t or can’t code they should at least understand the platform for which they design for. An architect doesn’t design a house without considering the materials and its surroundings.</p><p>How does this help you cut the fat? It should be obvious. The ability to hand over assets that can be used in production will reduce the effort needed to code them. If you understand the platforms or frameworks your designing for it will enable you to design within their constraints.</p><p>Does the table component have column filtering? Can the select component fetch data or are all options preloaded? If component X delivers the same user value as component Y, which is easiest to implement?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzh4lCWPFyKD0crNcSCN1g.png" /></figure><p>A set of reusable components can save a whole world of time so the more you understand those components, the more aware you’ll be of how they can be customised to suit your needs.</p><p>The further your designs are from what’s technically feasible, the more effort you’ll waste correcting designs and the developer will waste trying to meet the expectations your design has set with stakeholders.</p><p>In addition to this, over the past few years, there has been a huge change in how we design and build products. Living style guides, pattern libraries and new design tools have allowed us to be more efficient than ever. Better technical knowledge means you can now really improve your teams’ operational efficiency in ways you weren’t able to before. What are you waiting for?</p><h3>Checklist</h3><p>To summarise, if you’re somebody who wants to cut the fat and release products more efficiently, reducing your effort and that of the developers you work with:</p><ul><li>Understand the bare minimum needed to deliver value to your users and accept that releasing quickly, obtaining feedback and validating small incremental changes is better than releasing a ton of unused features.</li><li>Avoid working in silo for your own benefits or to “wow” stakeholders. If your work isn’t going to be released into a real product, or help shape the real product, your effort is wasted. Your goal is to release a product not just a portfolio piece.</li><li>Synchronise yourself with the product team. Know what’s planned and what will be delivered at every stage, so you can provide just the right amount of assets as and when needed.</li><li>Work as a team, involve everyone in ideation and use your expertise and experience to steer and facilitate. You’ll learn from them, they’ll learn from you and everyone will be aligned and focused on the same goal.</li><li>Understand the platforms and frameworks you are designing for. If you can’t code then work as close to code as possible. The smaller the gap between your designs at the final product, the less movement they’ll be when developers interpret them.</li><li>Work closely with developers. Establish or identify components and create a living style guide embracing reusability. This will also strengthen consistency across your product.</li><li>Embrace advances in design tooling and optimise your workflow.</li></ul><p>It would be great to hear about your experiences and how you’ve managed to speed up your product releases. Let us know in the comments below and reach out if you have any questions.</p><p>Thanks for reading!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b01b28ff8ed" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/cutting-the-fat-from-product-design-5b01b28ff8ed">Cutting the fat from Product Design</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>
    </channel>
</rss>