<?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 Pranay Sute on Medium]]></title>
        <description><![CDATA[Stories by Pranay Sute on Medium]]></description>
        <link>https://medium.com/@pranay.sute_2112?source=rss-42af7462fb64------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ngStuMwSnSBLBqWnSNmOhw@2x.jpeg</url>
            <title>Stories by Pranay Sute on Medium</title>
            <link>https://medium.com/@pranay.sute_2112?source=rss-42af7462fb64------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:13:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pranay.sute_2112/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[4 Lessons Product Designers can Learn from Ironman]]></title>
            <link>https://medium.com/swlh/4-lessons-product-designers-can-learn-from-iron-man-ad7b038751e5?source=rss-42af7462fb64------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad7b038751e5</guid>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[marvel]]></category>
            <category><![CDATA[ironman]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Pranay Sute]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 05:57:20 GMT</pubDate>
            <atom:updated>2020-06-20T05:58:34.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>4 Lessons Product Designers can Learn from Iron Man</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QXzcz-sOtl3FwtjLYyF_g.jpeg" /></figure><p>If you are reading this article, I can safely assume you are a huge fan of the Da Vinci of MCU, <strong>TONY STARK,</strong> and who wouldn’t be, right? That flamboyant personality, beautiful ladies by his side, riches that make Forbes’ most-affluent look like paupers. So much so that even Elon Musk must secretly be aspiring to be like Tony Stark.</p><p>But, take that all away and what is he?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*6A7oaoBrHVvnJje6qMCbyA.jpeg" /></figure><p>Keeping aside his enormous wealth &amp; the armour suit, what sets Tony Stark apart is the fact that he is also the <strong>Ultimate Designer. </strong>So<strong>, </strong>let’s look at the few elements from Iron Man’s life on-screen and draw a real-life analogy for us product designers to learn from</p><h3>№ 1. Mark 1 was terrible, but it does the job</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*FJeUeOBRmELUdhPrpAeLIQ.jpeg" /></figure><p><strong>Reel Life:</strong> Remember Mark 1? The armour suit built by Stark by recycling missile scraps in a cave, with metal plates barely qualifying for something that could be called as protection and mechanical parts falling all over the place. Mark 1 wasn’t the most refined of the armour suits, but the important thing about it is: it <strong><em>gets the job done</em>.</strong> It is built for only one specific purpose which is to thrust power for at least 15 minutes so that Tony Stark can escape from his tormentors.</p><p><strong>Real Life:</strong> So, how is the above example relevant to product design? The answer is that product designers, often, succumb to the pitfall of solving too many problems in one go.</p><blockquote>Designer: “I will design for, better conversion, &amp; personalisation, &amp; brand loyalty, &amp; usability, &amp; customer delight”.</blockquote><p>But the trick is to just pick one and design for that. Design it as <strong><em>fast</em></strong> as you can, as <strong><em>frugally</em></strong> as you can. Sometimes, that might even mean steering clear of extensive and time-consuming user research. But if you have a basic understanding of user needs &amp; problems, proceed ahead with designing a solution for that. The philosophy here is, to have a swift &amp; frugal approach in shipping out the product and get rich feedback by conducting usability analysis.</p><p>The important thing to remember while designing a product with this approach is to have a plan for assessing design viability. Conducting multiple usability tests helps to get rich qualitative insights from real users, so you can learn from your mistakes (and trust me, it’s totally okay to be wrong) and build on top of it in the next phase.</p><h3>№ 2. J.A.R.V.I.S does most of the work.</h3><p>Have you ever had a feeling that you are always running behind schedule &amp; are barely able to finish the project in time? Fast-paced product design cycles always force designers to keep an eye on the clock, and in the haste of doing so, they overlook some design flaws or usability issues.</p><p><strong>Reel Life: </strong>Whenever I watch a scene from the Iron Man movie where Tony Stark is building his iron suits, I always tend to think <strong><em>“How is he even doing it?”</em></strong>. That is like MCU equivalent of doing user research, brainstorming, wire-framing, prototyping and running usability, for multiple projects and just by one guy at that.</p><p>How Tony Stark is able to build such intricate machinery, all by himself, is because over the years, he has developed different systems that help him build his suits ever so rapidly. Majorly this is done by automating the time-consuming and recurring activities like fabricating, running calculations and simulations etc. Most of this is done by J.A.R.V.I.S., Stark’s AI assistant, so that he can concentrate on the one, major task, i.e. — innovating.</p><p><strong>Real Life:</strong> In this fast-paced design world, it has become ever more necessary for designers to have a design system. Having a library of UI components, interaction patterns, templates and visual assets in place can go a long way in speeding up the design process. With this, the professionals can focus on the critical task of designing creative solutions rather than spending their energies on crafting pixel-perfect UI.</p><p>Having a design system in place helps to conceptualise quickly, speed-up development, and assist in an accelerated iterative process. Automating the process by having a design system is in a way similar to having an AI assistant to do the mundane tasks for you.</p><h3>№ 3. Re-discover a new element</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*cYtQGVf6I5vnnQhhRRvBAQ.jpeg" /></figure><p><strong>Reel Life:</strong> At the start of the second Iron Man movie, Tony Stark is facing a grave problem. Palladium, which is integral for the functioning of the arc-reactor powering his suit, is also poisoning his blood. Tony is running out of time and options to find a replacement for palladium.</p><p>However, like any master designer would do, he goes back to the drawing board, looks at the core of the problem from an entirely new perspective and creates a new element altogether. Thus, making the armour all the more powerful.</p><p><strong>Real Life: </strong>Many a time, it so happens that designers reach a dead-end while designing. It may be an application or a fancy looking screen that you have spent weeks polishing, only to realise post-launch that the number of visits on the screen is much lower than expected <em>(I have experienced this first-hand).</em> Now, you are stuck and are not able to figure out despite all the efforts as to why users aren’t finding your design relevant.</p><p>Rather than choosing to do minor tweaks in the existing design, what has helped me in such situations is to go back to the drawing board and analyse the problem at its fundamental level. This might mean, revisiting the problem statements and understanding the core of the problem. Often, this approach will help in re-discovering that aspect of the product which is the most impactful for the user.</p><h3>№ 4. Tony Stark is a polymath, and you should aim to be one too</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*iK2w3zxZ1UpLUJtnv_3C2A@2x.jpeg" /></figure><blockquote><strong>Polymath</strong> (noun): a person of wide knowledge or learning.</blockquote><p><strong>Reel Life: </strong>In the above scene, though Tony replies to Maria Hill’s question with “last night” in his signature cocky, pompous way, he does become an expert on the subject after reading Erik Selvig’s notes. Not just thermonuclear astrophysics, Tony Stark is also an expert on a variety of complex topics. He isn’t merely a mechanical engineer or an electrical engineer but also an expert in computer science, robotics, propulsion, quantum mechanics, molecular physics, weapons design, nano-tech &amp; bending space-time. Ha!</p><p>Another person, from our real world, who shares such expertise across multiple disciplines is Elon Musk. Both Stark &amp; Musk can apply fundamentals of one discipline to the others and come up with path-breaking, innovative solutions. Elon Musk himself has been vocal about the benefits of having <strong>cross-discipline knowledge</strong>. Being a fan of Iron Man myself, I cannot help but think: if there is a product design equivalent of being a polymath?</p><p><strong>Real Life: </strong>Product designers often limit their understanding to a few disciplines like user research or UI design and rarely try to venture beyond these areas. Don’t get me wrong here; there is absolutely nothing wrong with having mastery in one discipline. Still, if we are able to look at our designs from a front-end developer’s perspective or from the point of view of data analysts, animators, game designers, it might bare some interesting facets of the product which haven’t been noticed yet.</p><p>That being said, you do not have to be a thorough expert in all these disciplines but having a brief understanding will help you while collaborating with the engineers, data analysts or get buy-in from the business. This is what will set you a band apart from the herd of other designers and tip the scale in your favour when you are applying for a job, or even applying yourselves at work.</p><p>Movies have the power to transport us to a new, unexplored world of fantasy. In the end, viewers have a sense of being inspired to do something better, create something more meaningful. Just take a look at technological inventions like the wireless tech, touchscreen phones, AI assistant that are so commonplace today and were inspired by movies like <strong>Star Trek</strong>, <strong>Star Wars</strong> <strong>2001: A Space Odyssey</strong> and so on. Inventors have been able to draw a connection from the field of our imagination &amp; craft something new and exciting in the real world.</p><p>Similarly, if we can derive inspiration from the intriguing universe of cinema and apply it to our own design philosophy, we will be able to exercise it better while solving the real-world problems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad7b038751e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/4-lessons-product-designers-can-learn-from-iron-man-ad7b038751e5">4 Lessons Product Designers can Learn from Ironman</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>