<?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 Arun Jacob on Medium]]></title>
        <description><![CDATA[Stories by Arun Jacob on Medium]]></description>
        <link>https://medium.com/@productnatives?source=rss-bff724d2b337------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7RleNkFdNfhS4MBZZsyD9w.png</url>
            <title>Stories by Arun Jacob on Medium</title>
            <link>https://medium.com/@productnatives?source=rss-bff724d2b337------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:37:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productnatives/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[AI compressed the build cycle. Now your team has nowhere to hide.]]></title>
            <link>https://productnatives.medium.com/ai-compressed-the-build-cycle-now-your-team-has-nowhere-to-hide-c880af0db3b6?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/c880af0db3b6</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-team]]></category>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Mon, 25 May 2026 05:05:31 GMT</pubDate>
            <atom:updated>2026-05-25T05:05:31.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pY3hhVcjP-0-Jxs1" /></figure><p>Every product team I have watched closely in the last eighteen months has gotten faster. About a third of them have gotten better. The other two-thirds have gotten faster at producing the wrong thing, and they are now producing it more frequently than ever.</p><p>This is not a story about AI. It is a story about what AI revealed.</p><p>For the last decade, the build cycle was slow enough that teams could maintain comfortable fictions about what they were building. The fictions could be six weeks long. By the time the feature shipped, the original assumption underneath it had aged out, the context had drifted, and nobody on the team had the appetite to ask whether the thing they were about to release still solved the problem they had originally set out to solve.</p><p>But AI compressed that cycle to two days. And two days is not enough time to maintain a fiction.</p><h3>A SaaS roadmap that worked exactly as planned and still failed</h3><p>I want to tell you about a SaaS company in Bangalore. This was years before any of the AI conversation started, which is the point. The pattern was already there. Speed just made it loud.</p><p>We had five enterprise clients whose logos went on our homepage. They asked, we shipped. The roadmap was essentially a list of their requests, prioritized by contract value. Story points up. Cycle time down. Every quarter looked excellent.</p><p>Eighteen months in, three of those five clients churned.</p><p>But the features were not bad. They worked exactly as specified. The problem was that the underlying job those clients were hiring our product to do had shifted, and we had not noticed because we were so good at executing what they asked for.</p><p>The PM and I did a post-mortem. We could trace, almost month by month, the moment the misalignment had started. Around month seven, one of the clients had asked for something that did not quite fit our model. We built it anyway. By month fourteen, we were a custom development shop with a SaaS pricing model. None of us had said it out loud. But we all knew.</p><p>The slow build cycle gave us a place to hide. Every quarter, the question “are we still building the right product?” got buried under the question “did we ship what we committed to?” The second question is easier to answer. So we kept answering it.</p><h3>Speed did not cause this. Speed made it visible.</h3><p>Here is what AI did. It removed the laundering.</p><p>When a feature took six weeks to ship, the team had time to forget why it was being built in the first place. By the time it was in production, the original premise had aged out. Nobody wanted to relitigate. Process, in this version, is a kind of amnesia.</p><p>But when a feature takes two days to ship, the premise is still warm. The assumption you made on Monday is sitting in front of you, fully rendered, on Wednesday. You can see whether it survived contact with reality. You either confront the gap, or you ship anyway, and the wrongness compounds at the new speed.</p><p>This is what I see across teams in 2026. The fast teams are not the winning teams. The winning teams are the ones whose internal honesty caught up with their build velocity. But the losing teams are the ones whose velocity ran ahead of their truthfulness, and who are now producing wrongness at industrial scale.</p><p>A friend of mine runs design at a Series B startup. She told me her most useful meeting is now a thirty-minute conversation on Friday afternoon where the team looks at what they shipped that week and asks one question. Not “did it ship on time” or “did the metrics move.” The question is: “is this what we said we were building three weeks ago, and if not, when did it stop being that?” She said it took four months for the team to answer the question honestly. The first three months, everyone hedged.</p><h3>The most important person in the kitchen does not cook</h3><p>I keep coming back to a professional kitchen during dinner service. Watch one for ten minutes and you will see something that maps almost perfectly onto a product team in 2026.</p><p>The line cooks are fast. They have to be. But the speed of the kitchen is not set by the fastest cook. It is set by the slowest correct dish on the table. If the steak is ready and the fish is not, the steak waits. If the steak goes out without the fish, the table eats badly.</p><p>The expediter, who does not cook, is the most important person in the room. They call the order. They hold the plates. They send food back when it is wrong. But their real job is to ask, before the food goes out, whether this is what the table actually ordered.</p><p>A kitchen without an expediter does not get faster. It gets messier. The cooks ship dishes at their own pace. The diners do not return.</p><p>Most product teams in 2026 are kitchens without expediters. They have replaced the expediter with velocity charts and AI agents that can plate faster. But they have not replaced the expediter with anyone willing to hold the pass and ask the question.</p><h3>What the honest teams do differently</h3><p>I do not have a model for you. I have a description of what I see in the teams that have figured this out.</p><p>They have made the act of looking at the work faster than the act of building it. The premise gets tested against reality on the same timeline as the feature gets shipped. There is no six-week gap where the question can quietly disappear.</p><p>They have stopped confusing client satisfaction with product correctness. The clients who keep asking for features are not necessarily telling you the truth about what they need. The Bangalore team I was on had five very satisfied clients who were halfway out the door.</p><p>And they treat the speed as a stress test, not a goal. The build cycle in 2026 is not a competitive advantage. It is the floor. Everyone is fast now. But the advantage is in what the speed reveals, and whether the team is willing to look at it.</p><h3>Holding the pass</h3><p>The product question in 2026 is not whether your team is fast enough or adaptive enough. It is whether your team can survive seeing itself clearly.</p><p>The Bangalore team I was on lost three clients before we were willing to look. We were not slow. We were not unadaptive. But we were unwilling, for fourteen months, to ask each other a question we already knew the answer to.</p><p>The expediter, in the end, is the person willing to hold the pass and ask it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c880af0db3b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your onboarding is your product.]]></title>
            <link>https://productnatives.medium.com/your-onboarding-is-your-product-6f0c3bfc3ba5?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f0c3bfc3ba5</guid>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Wed, 20 May 2026 05:16:39 GMT</pubDate>
            <atom:updated>2026-05-20T05:16:39.681Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jedUIeZbXrCHrPVYOT1iXw.png" /></figure><p>Nobody ever fell in love on a second date that almost didn’t happen.</p><p>First dates are brutal, efficient sorting machines. Research on speed dating shows that people form a judgement within the first four minutes. Not an impression. A judgement. The rest of the evening is mostly spent confirming what they already decided while the appetisers were arriving.</p><p>And here’s the part that matters for anyone building a product: the people who fail on first dates almost always fail for the same reason. They spend the whole time talking about themselves.</p><p>Their job. Their hobbies. Their impressive marathon time. Their opinions on craft beer. They treat the date like a presentation. Forty-five minutes of “let me tell you about me” and then genuine surprise when there’s no second date.</p><p>But your product’s onboarding does the same thing. And it’s just as unattractive.</p><p>Most onboarding flows are designed as introductions. “Welcome to our product. Here’s what we do. Here’s how it works. Here’s a tour of the features. Here’s a tooltip pointing at a button you’ll never click. Now please fill out this form so we can personalise your experience, which really means so we can segment you for marketing emails.”</p><p>I’ve sat in rooms where teams spent weeks designing these flows. Beautiful illustrations. Smooth animations. A friendly mascot who waves at you. Genuinely impressive craft, all in service of answering a question the user never asked.</p><p>But the user didn’t open your product wondering “what does this do?” They opened it wondering “does this understand my problem?”</p><p>That’s a fundamentally different question. But the gap between those two questions is where most products quietly die. Not with a dramatic failure. Not with a crash or an error message. With a shrug. A closed tab. A user who signed up, looked around for ninety seconds, felt nothing, and left.</p><p>I wrote recently about the shift from MVP to MVE, from minimum viable product to minimum viable experience. This is where that shift lives or dies. Not in your feature set. Not in your roadmap. In the first ninety seconds after someone gives you a chance.</p><p>At a SaaS company I worked with a few years ago, we had what the team proudly called a “comprehensive onboarding experience.” Four screens of setup. A welcome video. A guided tour that walked you through every major feature before you could touch anything. The team had spent an entire quarter building it.</p><p>Our completion rate on the onboarding flow was 73%. The team celebrated.</p><p>But here’s what they didn’t celebrate: of the users who completed the full onboarding, fewer than 30% came back the next day. They’d sat through the entire presentation, nodded politely, and never returned.</p><p>We’d built the equivalent of a first date where one person delivers a TED talk about themselves for twenty minutes and then says, “So, should we do this again?” The other person smiles, says “definitely,” and then blocks your number in the car park.</p><p>The onboarding wasn’t broken. It was thorough. It was polished. It was entirely about us.</p><p>The turnaround, when it came, was almost embarrassingly simple.</p><p>A junior designer on the team, someone who’d been at the company for maybe four months, asked a question in a review meeting that nobody had thought to ask: “What if the first thing the user sees is their own data instead of our features?”</p><p>That’s it. That was the whole insight.</p><p>Instead of opening with a tour, we opened with an import. Instead of showing users what the product could do, we showed them what the product could do with their stuff. The first screen after signup became a single prompt: bring in your existing work. No tour. No tooltips. No mascot.</p><p>The user’s first experience went from “let us tell you about ourselves” to “we already know why you’re here.”</p><p>Retention after day one nearly doubled. Not because we’d added a feature. Because we’d subtracted everything between the user and the moment they felt the product understood their problem.</p><p>The best first dates are the ones where someone asks you a genuinely good question in the first two minutes. Not because asking questions is a technique. Because it signals something rare and specific: this person is paying attention to me, not performing for me.</p><p>I’ve spent twenty years designing products across startups and enterprises, and in almost every case, the pattern is the same. The teams that obsess over their onboarding as a feature tour are solving for comprehensiveness. The teams that obsess over the first moment of recognition are solving for retention.</p><p>Comprehensiveness feels responsible. It feels like good product management. You’re being thorough. You’re educating the user. You’re reducing support tickets.</p><p>But thoroughness is not the same as care. Showing someone every room in the house is not the same as making them feel welcome at the door.</p><p>The metric that actually predicts whether someone stays is not “did they complete the onboarding?” It’s something much simpler and much harder to measure: did they feel, within ninety seconds, that this product was built for someone like them?</p><p>I’ve started calling this the recognition moment. The point where a user stops evaluating and starts using. Where the internal question shifts from “what is this?” to “oh, this is for me.” Everything before that moment is friction. Everything after it is momentum.</p><p>Most products never reach it. But not because they’re bad products. Because they buried the recognition moment under a welcome video and a four-step setup wizard.</p><p>The teams getting this right are not building better onboarding. They’re eliminating the distance between signup and recognition. They’re asking: what’s the fastest path to showing this user that we understand why they’re here? And then they’re cutting everything that sits between the user and that moment.</p><p>Sometimes that means showing real data on the first screen instead of sample data. Sometimes it means asking one smart question instead of ten. Sometimes it means doing less on purpose so the user can feel more on arrival.</p><p>It’s the same instinct that makes a great first date great. Not the performance. Not the rehearsed stories. The moment where someone makes you feel like they actually showed up to meet you, not just to be seen.</p><p>Your onboarding is not an introduction to your product.</p><p>It’s your product’s first answer to the only question that matters: do you understand why I’m here?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f0c3bfc3ba5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Persuasive Disagreements]]></title>
            <link>https://productnatives.medium.com/the-art-of-persuasive-disagreements-a0f11bcd2604?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0f11bcd2604</guid>
            <category><![CDATA[product-team]]></category>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Fri, 15 May 2026 03:56:58 GMT</pubDate>
            <atom:updated>2026-05-15T03:56:58.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2JOKF3Ke3-OSQekD.png" /></figure><p>After twenty years in my career, I’ve learned that knowing <strong>how to disagree</strong> is a skill. Not just a skill, but an art.</p><p>Knowing how to bring up a disagreement, being persuasive about it, holding the room while you make your case, and actually moving the decision is, more than anything, an art. And it’s one of the biggest reasons some careers compound and others don’t.</p><p>This isn’t only about work, by the way. The same thing plays out at home. With your partner, your parents, the friend who keeps making the wrong call. Most of us never learn how to do this well in any room. We pick up the technical stuff at work. PRDs, sprints, presentations. We pick up the relationship stuff at home through trial and a lot of error. But the actual moment of disagreement, the one where something real is on the line, mostly gets left to instinct.</p><p>And instinct gives you three default ways to handle it. None of them work very well. I know because I’ve used all three. Then there’s a fourth way, which is the one this piece is about.</p><h3>Being Silent (everyone’s favourite)</h3><p>The first default is silence. You have a take, but you don’t say it. The meeting ends, and later you tell a colleague what you really thought. Maybe you complain about it on Slack. The decision moves on without your input.</p><p>I did this for years when I was younger. I would sit in a room, watch something I disagreed with, and just not bring it up. Sometimes I told myself I wasn’t sure enough. Sometimes I told myself it wasn’t my place. Mostly I just didn’t want the friction. And here is the part nobody warns you about: you don’t grow out of this. Senior people still do it. They<strong> just hide it better</strong>.</p><p>The same thing happens at home. Your partner suggests something, you have a real concern, and you go “yeah, sounds good.” A week later you’re annoyed about it, and the annoyance has nothing to do with the actual decision anymore. It’s about the fact that you didn’t speak up. The decision is just where the resentment found a place to land.</p><p>What does silence cost you? Your sharpest read of the situation. The team hired you because of how you think. Your partner chose you because of how you think. But if that thinking stays in your head, what was the point.</p><p>The hardest thing about silence is that nobody else knows it’s happening. From the outside, you look like someone who agreed. So the next time something similar comes up, the people in the room, or at the dinner table, assume you’re on board. And the gap between what you actually think and what they think you think gets a little wider every time.</p><h3>Being aggresive and loud</h3><p>The second default is the opposite. You do bring the disagreement into the room, but with too much heat. The argument turns into <strong>who’s right</strong> instead of <strong>what’s right</strong>. Even when your point is solid, what people remember later is how you sounded.</p><p>I’ve done this one too. Mostly in my early thirties, when I confused having strong opinions with being effective. I would walk out of meetings thinking I’d made the case clearly. Then I’d hear, second-hand, that I’d been “a lot” in the meeting. That’s the polite way of saying you’re now the problem. Nobody was talking about my point anymore. They were talking about me.</p><p>It happens at home too. The argument with your partner where <strong>you won the point but lost the evening</strong>. The fight with a parent where you were right about the thing, but the rightness didn’t matter because of how you got there. Years later, nobody remembers what the argument was about. They just remember that it was bad.</p><p>The cost of being loud is bigger than losing one argument. People stop bringing things up around you. They route conversations away from you. Your partner stops mentioning the small stuff because the small stuff sometimes turns into a big thing. Your team starts pre-aligning before meetings so you don’t have surprises in the room. But you don’t even see any of this happening. From your side, you just notice that fewer interesting conversations are coming your way. You assume the room got quieter. The room didn’t. It just got quieter around you.</p><p>And here’s the part that took me longest to learn. <strong>Being loud is rarely about caring more</strong>. Most of the time, being loud is about being less comfortable holding a disagreement quietly. The volume is a tell that you haven’t figured out how to make the case without it.</p><h3>You fake it!</h3><p>From the outside, this one looks like you’re handling things well. You raise the concern. Someone acknowledges it. The decision moves on, and to anyone watching, the system worked.</p><p>I call this concern theatre. At work it sounds like, “I just want to flag a concern about the timeline.” Someone says, “noted, let’s track it.” It goes into a doc somewhere. Then the team ships on the original timeline anyway.</p><p>You didn’t disagree. You went on the record. Those are not the same thing.</p><p>There’s a real difference between being heard and being logged. <strong>Being heard changes the decision</strong>, or at least changes how the room thinks about it afterwards. <strong>Being logged just gets your concern written down somewhere</strong>, so later, when things go sideways, you can scroll back to the doc, point at it, and feel like you did your part.</p><p>The home version of this is even more familiar. Your partner asks where you want to go for dinner. You say “I’m fine with whatever,” knowing full well you’re not fine with whatever. They pick a place. You go. You don’t enjoy it. And later, the thing you didn’t say comes out somewhere else. You snap at them about something small. You bring up something from last week. The dinner wasn’t really the issue. The silence was.</p><p>I’ve done this at work, in both directions. I’ve raised concerns I knew weren’t going anywhere, just so I’d be on record when things broke. And I’ve been the senior person nodding and saying “good point” because I didn’t have the energy to push, or because I’d already decided and just wanted the meeting to end.</p><p>This is the worst of the three because it can run for years without anyone catching it. From the outside, it looks like a healthy team. Or a healthy relationship. People are talking. Concerns are being raised. Nothing is being suppressed. But nothing is being changed either.</p><p>And when the concern turns out to be right, you don’t get credit for being right. You just get the receipt. The receipt feels like vindication for about a day. After that, it just feels like you watched the thing happen and chose to be on file instead of in the way.</p><h3>What is the right way?</h3><p>Here’s the part that took me years to figure out. Disagreeing well is not a personality thing. It’s a few habits. I’ll give you four.</p><h3>Say what you’re disagreeing about, before you start arguing.</h3><p>Before you make your case, name the specific thing you’re pushing back on. Something like: “Before I disagree, I want to make sure I’m disagreeing with the right thing. The part I have a problem with is the timeline. Is that the bit we’re deciding right now?”</p><p>What this does is enormous. It pulls the room’s attention to the exact piece you’re going after, so your case doesn’t get lost in a wider conversation. It tells the people across from you that you’ve thought about this, which softens them. And it forces you to be precise. You can’t hide behind a vague “I have concerns.” You have to commit to a specific thing.</p><p>Same move works at home. Instead of “we need to talk about the dishes,” try “I want to talk about how chores get split. The dishes are just where I’m noticing it.” Now you’re not arguing about dishes. You’re talking about the actual thing.</p><p>The reason this habit works is that most disagreements lose energy by being aimed at the wrong target. Naming the target first means everything you say after lands on the thing you actually care about.</p><h3>Make the other person’s point before you make yours.</h3><p>Before you say why you disagree, say why <em>they</em> think what they think. Out loud. In your own words. As well as they could say it themselves, ideally better.</p><p>Here’s what that sounds like in a meeting. Your PM wants to ship in two weeks and you think it’s a bad idea. Instead of starting with “I don’t think we should ship in two weeks,” you start with: “I get why two weeks makes sense. We’ve already announced the date, the team’s tired of this project, and pushing it back makes us look indecisive in front of leadership. So shipping fast has real upside. But here’s why I’m still nervous about it…” Now you make your case.</p><p>What this does is change the temperature of the conversation. The person you’re disagreeing with is no longer defending themselves, because you just made their argument for them. Their guard drops. They start listening to your side instead of preparing their next response. And when you do disagree, your case lands harder, because you’ve already shown you understand what you’re pushing back on.</p><p>Same thing at home. Before saying “I don’t think we should visit your parents this weekend,” try “I know it’s been a while since you’ve seen them, and you’ve been wanting to introduce them to the new place. So this weekend isn’t random. But I’m wiped, and I think I’d be bad company. Can we look at next weekend instead?” Same disagreement. Completely different conversation.</p><p>This is the move that turns loud people into persuasive people. Loud people argue with the weakest version of the other side, because it’s easier to win against. Persuasive people argue with the strongest version, because that’s the one that actually has to be answered.</p><h3>Sleep on it before you make your full case.</h3><p>This one is not about staying quiet. Staying quiet is the silence problem we already covered. This is about timing.</p><p>When you feel a disagreement land in the moment, your instinct is to win it right there. Don’t. The version of you arguing in the meeting is dealing with the temperature of the room, the sting of being overruled in front of people, the ego of the person across from you. That version is loud, defensive, and rarely persuasive.</p><p>So flag it live, but don’t argue it live. Something like: “I want to sit with this one before I’m fully on board. Can I come back to you on it tomorrow?” That’s it. Now you’ve gone on the record without going to war. You haven’t gone silent. You’ve bought yourself a night.</p><p>Then sleep on it. The next morning, two things will be clearer. Whether the disagreement still feels real, and what the strongest version of your case actually is. Some of what felt urgent will be gone, and that’s fine. Those weren’t the real disagreements. The ones that survive the night are the ones worth bringing back. And the version of you bringing them back, calm, with a clean argument, is much more persuasive than the version that would have argued it hot.</p><p>This works the same at home. Most fights that feel huge at 11pm are not the same fight at 9am. The move isn’t to swallow the disagreement at 11pm and pretend it didn’t happen. The move is to say “I don’t want to get into this now, but I want to talk about it tomorrow morning.” Then actually do it.</p><p>The reason this habit works is that disagreements raised hot get answered hot. Disagreements raised cool get answered cool. You control which one happens by controlling when you make your real case.</p><h3>Disagree, then commit.</h3><p>When the decision goes the other way, you have a choice. You can keep arguing. Or you can switch to making the chosen path woaggressiverk.</p><p>Switch. That’s the move.</p><p>Not by going quiet. Not by sulking. By actively trying to make the thing succeed. The first one keeps you arguing past the point where it helps. The second one earns you trust the next time you bring something up. This is true at work. It is also true in any relationship that lasts.</p><p>But if you commit before you’ve made your case, you’ve just done concern theatre.</p><h3>The compounding effect</h3><p>Twenty years in, I’ve come to think of <strong>disagreement as one of the few things that compounds</strong>. Every time you do it well, the next one is a little easier. Every time you do it badly, the next one is a little harder. The people I’ve watched build real influence at work, and real trust at home, are not the loudest in the room or the calmest. They’re the ones who treated this as something to learn, not something to survive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0f11bcd2604" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When your user and your customer are different people]]></title>
            <link>https://productnatives.medium.com/when-your-user-and-your-customer-are-different-people-11c9458a3aac?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c9458a3aac</guid>
            <category><![CDATA[organization-dynamics]]></category>
            <category><![CDATA[product-team]]></category>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Wed, 13 May 2026 17:14:45 GMT</pubDate>
            <atom:updated>2026-05-13T17:14:45.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CGABNT96kC-EdHF1" /></figure><p>A tenant lives in an apartment. They care about whether the hot water works, whether the walls are thin enough to hear every argument next door, whether the heating actually turns on in December. They care about the things you care about when you live somewhere.</p><p>The landlord owns the apartment. They care about the yield, the property value, the lease renewal rate. They care about the things you care about when you own something.</p><p>Both have a relationship with the building. But when the landlord decides to renovate, they’re not fixing the plumbing for the current tenant’s comfort. They’re upgrading the kitchen so they can charge the next tenant more.</p><p>And if you’ve ever lived through a renovation you didn’t ask for, contractors showing up at 8am, your hot water vanishing for a week, the hallway smelling like paint for a month, you know exactly what it feels like to be a user of a product that’s being optimised for someone else. The building is changing around you. But not for you.</p><p>Most digital products work this way. The user lives in the product. They navigate it every day. They develop habits, preferences, workarounds. But the product is being renovated for someone else entirely. And until you understand who that someone else is, nothing about the product’s decisions will make sense.</p><p>In most products, the person using it and the person the company is optimising for are not the same person. This isn’t a bug. It’s the business model.</p><h3>1. Paying customers can be the product too</h3><p>“If you’re not paying, you’re the product.” Everyone knows this line. It’s become the default explanation for why ad-supported platforms feel hostile. Social media, free email, free search: your attention is sold to advertisers. You are the inventory. Fine.</p><p>But the split goes much deeper than free-versus-paid.</p><p>Enterprise SaaS is the clearest example. The person using the CRM eight hours a day is not the person who bought it. The sales rep needs the tool to not waste their time. The VP of Sales who signed the contract needs reporting dashboards, forecasting accuracy, and a sense of control. These are different needs. They look similar in a pitch deck. They are not similar in daily use.</p><p>But when they conflict, the signature on the contract wins. Every single time. Not because anyone sat in a room and said “the user doesn’t matter.” But because the incentive structure already made that decision before the meeting started.</p><p>I watched this play out at a SaaS company I worked at. The product team had two options for a dashboard redesign. Option A was faster, cleaner, and users loved it in testing. Option B had more executive-facing analytics widgets. Option B shipped. Not because anyone disliked Option A. Because the renewal conversation happened with the VP, not the sales rep sitting in the product every day.</p><p>The product roadmap follows the signature on the contract. If that’s not the person using your product, you’ve already chosen sides.</p><h3>2. Your business model decides who your user is before your product team does</h3><p>There are three dominant models in digital products, and each one defines “user” differently. It’s worth seeing them side by side, because the pattern becomes obvious once you do.</p><p><strong>Ad-supported products</strong> (social media, search, free tools): The user is the inventory. The advertiser is the customer. The product’s job is to maximise time-on-platform so there’s more inventory to sell. Every design decision that increases engagement is rational under this model, even if it comes at the user’s expense. The outrage algorithm isn’t a failure of values. It’s a success of economics.</p><p><strong>Enterprise SaaS</strong> (B2B, procurement-driven): The user is the operator. The buyer is the customer. The product’s job is to make the buyer look smart for purchasing it. Features that impress in a quarterly review get prioritised over features that reduce the daily friction of the person actually clicking the buttons.</p><p><strong>Platforms and marketplaces</strong> (ride-sharing, delivery, freelance): Neither side is the customer in the traditional sense. The platform optimises for the transaction itself. Drivers, riders, restaurants, couriers: all are inputs being optimised, not people being served. Everyone thinks the platform works for them. But the platform works for the platform.</p><p>It’s like a football stadium. The fans came for the match. But the sightlines are optimised for camera angles, the breaks in play are timed for ad slots, and the premium seats face the broadcast cameras, not the pitch. The fans are the atmosphere. The broadcaster is the customer. The fans just don’t know it, because they’re too busy enjoying the game to notice who the building was actually designed for.</p><p>Your business model doesn’t just determine how you make money. It determines who your product actually serves. Everything else is a story you tell yourself.</p><h3>3. The ride-sharing test that tells you everything</h3><p>Here’s where this gets personal for anyone who builds products.</p><p>At a ride-sharing company I worked with, the product team ran an experiment that measurably improved driver satisfaction. Better route suggestions, fewer forced pickups, slightly more control over their shift. Drivers loved it. But rider conversion dipped by a small margin. The experiment was killed in the next sprint review.</p><p>The comment in the meeting was revealing: “We don’t optimise for supply happiness. We optimise for transaction completion.”</p><p>Nobody in that room was being cruel. The PM wasn’t a villain. The data team wasn’t heartless. The business model had already decided who mattered. The drivers were users. The transaction was the customer. And the experiment, no matter how good the outcomes were for drivers, was never going to survive a framework that didn’t have a row for “supply happiness.”</p><p>But this dynamic isn’t exclusive to Big Tech. It’s in your product too. The founder who builds for investors instead of users during fundraising season. The PM who ships the feature that demos well over the one that works well. The designer who optimises the signup flow for conversion rate, not user comprehension. The startup that redesigns its pricing page to maximise enterprise upsells while making the free tier progressively harder to find.</p><p>I’ve spent 20 years across startups and enterprises, from Adobe to Freshworks to early-stage companies with five people in a room, and in nearly every case, the user/customer split exists. The shape changes. The severity varies. But the split is always there. The only difference is whether the team has named it or not.</p><p>Nobody in the room is being cruel. The business model has already decided who matters.</p><h3>4. User advocacy isn’t about always choosing the user. It’s about always knowing when you’re not.</h3><p>Here’s the part where I’m supposed to tell you how to fix this. I can’t. Not in the way you’d want.</p><p>The user/customer split isn’t something you eliminate. Ad-supported products have advertisers. Enterprise products have buyers who aren’t users. Platforms have transaction economics. That’s reality. Pretending otherwise doesn’t make you ethical. It makes you confused.</p><p>But you can be honest about where the split lives. And that honesty changes everything about how you build.</p><p>The best product teams I’ve worked with didn’t pretend they were building for the user when they were building for the buyer. They made the trade-off visible. They said it out loud in the room: “This decision serves the buyer. Here’s what we’re giving up on the user side. Here’s how we’ll rebalance next quarter.” No theatre. No pretending the quarterly analytics dashboard was really about “empowering” the sales rep.</p><p>That’s not cynicism. That’s clarity. And it’s the difference between a product team that slowly loses its users’ trust without understanding why, and one that makes hard trade-offs with its eyes open.</p><p>User advocacy isn’t about always choosing the user. It’s about always knowing when you’re not. And saying so.</p><p>The tenant never stops caring about the plumbing. The landlord never stops caring about the yield.</p><p>The best products aren’t the ones that pretend there’s no split. They’re the ones that know exactly where it lives and make the trade-off on purpose. Not by accident. Not by org chart. Not by pretending the tenant and the landlord want the same thing.</p><p>They never do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c9458a3aac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Padding in Adobe XD]]></title>
            <link>https://productnatives.medium.com/padding-in-adobe-xd-a2654e5a62e4?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2654e5a62e4</guid>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Mon, 19 Jul 2021 10:41:32 GMT</pubDate>
            <atom:updated>2021-09-06T15:04:21.710Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Padding in Adobe XD enables the ability to define the spacing between the contents of a group and the background layer, reducing the time spent ensuring buttons and other UI elements have consistent padding in each instance.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YlXOYBgq3SG5_v7vtj9GYw.gif" /><figcaption><em>Usage of padding to create the content-aware layout</em></figcaption></figure><h4>Content-Aware Layout (CAL)</h4><p><strong>The padding feature was part of the Content-Aware Layout properties suggested for Adobe XD.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*qoiNZduq7Sr-2h6a6nKvRQ.png" /></figure><p>Content-Aware Layout (CAL) is a family of features that aim to reduce the complexity of the changes caused by small adjustments in the design process. The users will be able to design and edit components without nudging or tinkering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/190/1*hNOrZLwSpnINbSHQmzW2VQ.png" /></figure><p>Structuring and laying out content in Adobe XD was a very manual and tedious process. It was time-consuming from an end-user perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhBgOfLWjqPNtqTYeWFGwg.gif" /><figcaption>It was complicated and time-consuming it is to restructure the button here when the content inside changes.</figcaption></figure><blockquote>How can Adobe XD provide a seamless experience to create extra space around an element’s content inside any defined borders?</blockquote><blockquote>And how can the developers inspect and extract the values added to the design to integrate the design into code efficiently?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/162/1*yS4oSsN60m0QDWVDL_LVWA.png" /></figure><p>My role was to strategise and structure an experience to enable padding in XD, considering the CAL ecosystem.</p><p>I (with the help of the PM) took up the research and user testing responsibilities along with designing the experience. <strong>We owned all the experiences associated with developer handoff and design specs in XD (both prototype and design specs).</strong></p><p>The PM was new to the role, and I had to help him understand the design processes and the steps to go through while executing a project/story.</p><blockquote>We structured both the experience for designers and developers (the design specs UI while they inspect and integrate code.)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/186/1*AbMtyXingZXM5KRZ9k8gnQ.png" /></figure><p>The strategy was to provide a solution by allowing certain elements to be flexible based on the content and enabling designers to set the layout settings to maintain specific spacing around items in a group.</p><p>It should reduce friction in the design process and save time. Padding will also enable the definition of flexible layouts to structure components and curate a design system properly.</p><blockquote>The Padding feature should reduce many manual steps designers need to take while laying out content groups such as sections, lists, cards, buttons etc.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*GQIBXLRHIj0UbBHOomkS2w.png" /></figure><p>Padding is a term closely associated with front-end developers no matter which platform they are integrating for. So I first checked with the designers whether they are aware of the concept of padding.</p><p><strong>The first intricacy was settled immediately; everyone was aware of the term padding and its application and how it differs from margins and other layout properties.</strong></p><h3>Results</h3><p>My next task was to understand how the designers pass on the padding values to the developers. Do they even do that or let the developers perceive it by examining the designs.</p><p>Most of the designers create a redline document to detail out all the measurements in the designs. I went through some of the redlines to understand how they indicate the padding values in the redline document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*eBBcyx2TW1sPiVBXls-53Q.png" /><figcaption>An example of a redline document.</figcaption></figure><h4>For Developers</h4><p>Even though the developers rely on the redline document, this was difficult and tedious for them to always check through the redline document for minor details.</p><p>Some of them use Invision and Zeplin to inspect the design. They use the selection and mouse over interaction to figure out the relative distances.</p><p><strong>Inspecting and Fixing (the common factor)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*m15xKf5Y01Y3OI_Eo8RrMA.png" /><figcaption>Chrome DevTools</figcaption></figure><p>The developers (both web and mobile) had a similar pattern to inspect and fix any layout property changes.</p><p>The web developers are well versed with the ‘developer tool’ extension provided by the browser. For mobile developers, they have layout inspectors in the apps like Android Studio, XCode etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*jGjp3peVlybIxy3YfKNePA.png" /></figure><p>My primary task was to detail and design the experience for the XD desktop app.</p><h4>Pain points</h4><p>The foremost challenge that the designer faced was that they had to manually adjust the spacing (both margin and padding) if any change happens inside the component or a group.</p><p>The main questions we derived from the user research were:</p><blockquote>How should Adobe XD introduce a pattern which will very clearly convince the designers to add padding to an object?</blockquote><blockquote>How should the user set equal padding for all the sides and different values for all four sides?</blockquote><blockquote>Should the user add padding to a layer or a group?</blockquote><blockquote>How can we create a comparable experience for the developer in design specs consistent with the current inspection pattern?</blockquote><blockquote>What all details can we provide to the developers?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*8CYPYlQtgZUZ64dIsYaCGg.png" /></figure><h3>Wireframe and Prototyping</h3><p>They should enable padding first and then set the values. Once the value is set, the content should be responsive and should adapt to any modifications.</p><blockquote>One main factor under consideration was structuring the padding experience similar to how content is organised inside code — like structuring content inside a &lt;div&gt; or &lt;section&gt;in HTML.</blockquote><h4>Padding will be applied to groups only.</h4><p>After initial brainstorming, we decided that padding can be applied to groups and not to a single layer. And the size of the group will be responsive with the content added inside it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*V9jP1IrwS_G4zKsj_gRvtw.gif" /><figcaption>The group will be responsive based on the padding added to it.</figcaption></figure><h4>Visual representation of Padding</h4><p>As stated before, how can a user set equal padding for all sides and different values for all four sides? We should represent these features within the properties panel and give a clear clue to the user regarding these interactive elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/1*poTI0TNhlFVXFjzIIzFZiA.png" /></figure><p>I worked with the <strong>icons team</strong> to design the padding representation icons for XD.</p><p>Another pain point was to represent padding (added to a group) on the canvas. After going through many options and keeping the standard patterns (developer tools) in mind, we decided to show a semi-transparent indication on the groups to which padding is present in the design upon selection and making changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hl1seUf-HbxMI7qjSJUVvQ.png" /><figcaption>on-canvas padding representation in XD</figcaption></figure><h4>Micro-interactions</h4><p>There were many micro-interactions included in the experience.</p><p>When the user changes padding for a particular side, the icon representation will also change and shows the same side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*GtSIe5oKMhLPCSOfOBadkw.gif" /><figcaption>Interaction to represent the sides.</figcaption></figure><p>Another interaction was to adjust the padding on-canvas itself by dragging the padding indication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*-aFcrAs8pQR8RjPio2nRsQ.gif" /><figcaption>Drag interaction to edit the padding.</figcaption></figure><h4>Responsive background layer.</h4><p>In HTML, when the padding is added to a &lt;div&gt;, the width and height of the div increases, and if there is a background image or colour associated with it, it will also increase based on the padding added to it.</p><p>But in XD the construction model was different, so after many deliberations, we decided that if there is an underlying shape layer present inside the group that fills the entire group, it will act as the background layer and grow or shrink based on the content inside the group.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSIrPHzevLRj8bt4krV%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FSIrPHzevLRj8bt4krV&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2FSIrPHzevLRj8bt4krV%2Fgiphy.gif%3Fcid%3D790b761127505941599ef346b70feb6469952b3a005f4c8c%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="190" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d376e71ac9c362c99e7b24f9b53d4ef/href">https://medium.com/media/8d376e71ac9c362c99e7b24f9b53d4ef/href</a></iframe><h3>User testing</h3><p>Once I finalised the designs and prototype experience, we shared it with fellow in-house designers to work with and review the experience. Once we got positive feedback, I approached the engineering team to create a POC to test the padding experience with designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j9CjRXvigt_w_mQ6XQOmpQ.png" /></figure><p>We shared the POC with designers who work on different platforms. The response was excellent. The padding settings were quickly discoverable, and the micro-interactions assisted the users in contriving the padding feature better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*UAKGi9CZjCwH0-RUtJLA7Q.png" /></figure><h4>What is Design Specs?</h4><p>With Adobe XD <strong>design specs</strong>, designers can share the exact specifications of the design files with front-end developers.</p><p>Developers can easily acquire accurate information about the design elements like object height, width, size, alignment, spacing, colours, typography specs etc.</p><blockquote>Go from design to code, without the guesswork.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*FtK7Wwl2_OhsYrhPzDf9tw.png" /></figure><h4>Inspect for padding — UX</h4><p>Once the designers add padding in their designs, we should represent the values in design specs to help developers implement the same values in their code.</p><p>The developers needed the padding values while integrating the code and constructing the UI components. From an interaction point of view, the developers were already well-versed with the developer tool or layout inspection interactions.</p><h4>The main challenges</h4><p>I wanted to understand whether the developers needed an intuitive experience while inspecting the design specs. Or just the padding info on the properties inspector is enough.</p><p>In XD Design specs — from a technical feasibility perspective — padding values can be obtained upon selecting the group since padding is applied to a group in the design document.</p><p>We wanted to determine whether the developers wanted any on-canvas indication of padding while inspecting the group and its children layers.</p><h4>Testing options for validation</h4><p>I structured three different options for user testing and prototyped them. We wanted to illustrate the real-life experience to receive accurate feedback.</p><p><strong>Option 1</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fembed%3Fid%3D1sEdX6ML-qAEwTQTkmVvUF_alo2oWRimqZ7Y7hKx-_zU%26size%3Dl&amp;display_name=Google+Docs&amp;url=https%3A%2F%2Faccounts.google.com%2FServiceLogin%3Fservice%3Dwise%26passive%3D1209600%26continue%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1sEdX6ML-qAEwTQTkmVvUF_alo2oWRimqZ7Y7hKx-_zU%2Fedit%3Fusp%253Dsharing%26followup%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1sEdX6ML-qAEwTQTkmVvUF_alo2oWRimqZ7Y7hKx-_zU%2Fedit%3Fusp%253Dsharing%26ltmpl%3Dslides&amp;image=https%3A%2F%2Fssl.gstatic.com%2Faccounts%2Fui%2Favatar_2x.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=google" width="700" height="559" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b4276f558c28769697b4c4e1ad98db2/href">https://medium.com/media/2b4276f558c28769697b4c4e1ad98db2/href</a></iframe><p><strong>Option 2</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fembed%3Fid%3D1tjZB13hSqIZe83taiNJC3OGr6z-oRKf4Vv-54R1Qwvg%26size%3Dl&amp;display_name=Google+Docs&amp;url=https%3A%2F%2Faccounts.google.com%2FServiceLogin%3Fservice%3Dwise%26passive%3D1209600%26continue%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1tjZB13hSqIZe83taiNJC3OGr6z-oRKf4Vv-54R1Qwvg%2Fedit%3Fusp%253Dsharing%26followup%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1tjZB13hSqIZe83taiNJC3OGr6z-oRKf4Vv-54R1Qwvg%2Fedit%3Fusp%253Dsharing%26ltmpl%3Dslides&amp;image=https%3A%2F%2Fssl.gstatic.com%2Faccounts%2Fui%2Favatar_2x.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=google" width="700" height="559" frameborder="0" scrolling="no"><a href="https://medium.com/media/279ae6d8aa097678f017512207889ba2/href">https://medium.com/media/279ae6d8aa097678f017512207889ba2/href</a></iframe><p><strong>Option 3</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fembed%3Fid%3D1ei84zZTJjXdZz26HwXW_1M2F4ZSuEBCiymHxf08xJmA%26size%3Dl&amp;display_name=Google+Docs&amp;url=https%3A%2F%2Faccounts.google.com%2FServiceLogin%3Fservice%3Dwise%26passive%3D1209600%26continue%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1ei84zZTJjXdZz26HwXW_1M2F4ZSuEBCiymHxf08xJmA%2Fedit%3Fusp%253Dsharing%26followup%3Dhttps%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1ei84zZTJjXdZz26HwXW_1M2F4ZSuEBCiymHxf08xJmA%2Fedit%3Fusp%253Dsharing%26ltmpl%3Dslides&amp;image=https%3A%2F%2Fssl.gstatic.com%2Faccounts%2Fui%2Favatar_2x.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=google" width="700" height="559" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa64abd267d8d0972308592ae78687ee/href">https://medium.com/media/aa64abd267d8d0972308592ae78687ee/href</a></iframe><p>We went out to real developers and asked them to go through the prototypes to interact and review the experience.</p><p><strong>We received mixed feedback from the developers and was unclear about how to proceed and determine the experience.</strong></p><p>I decided to reach out to the larger design team and the product team to get more recommendations. And based on the discussions and weighing all the feedback, we decided to test the experience with a selected group of users and go for A/B testing (with selected customers) to get more feedback and draw a conclusion.</p><p>After letting the users work on it for almost a month and personally reaching out to the real users with scenario-based stories, I got a better viewpoint about it, validate the experience and make a decision.</p><blockquote>We decided to go with the first option, as the developers wanted to view the padding values when they select the group. The extra on-canvas indications upon child selection were confusing, and they can view the relative distance with the help of selection and mouse-hover interaction.</blockquote><p><em>(Padding in Design Specs is yet to be released)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*xDcEQmvHh9en1XPdCgJbyQ.png" /></figure><p>Once I documented the designs and the user testing outcomes, we approached the leadership team for design approval. They appreciated the outcome and were happy with the user responses.</p><p>The main highlight was the responsive behaviour of the content group once padding is added to the layout. All the feedbacks were positive, considering the full interactivity model and the UI experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bjSdaWEOdLiLKaLsSyNoSQ.gif" /></figure><blockquote>Padding reduced design friction and cognitive overload while creating buttons, drop-downs, tooltips, and other UI components.</blockquote><p>Padding, along with other layout features like stacks and responsive resize, became a powerful feature in XD. It helped designers to structure their designs better. It became an easier task for the designers to make modifications to components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2654e5a62e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Components and States in Adobe XD]]></title>
            <link>https://productnatives.medium.com/component-states-in-xd-bc6c30e198ff?source=rss-bff724d2b337------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc6c30e198ff</guid>
            <dc:creator><![CDATA[Arun Jacob]]></dc:creator>
            <pubDate>Mon, 19 Jul 2021 07:55:34 GMT</pubDate>
            <atom:updated>2021-11-09T05:23:09.030Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“The little details can make a big difference in how a human experiences an application or a product.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*k3BjgUJtiWo7Dgw6BI2eVA.png" /></figure><p>In the world of prototyping, creating dynamic elements make the difference between a prototype that feels real and one that interacts like a slideshow of static imagery.</p><blockquote>Component States in Adobe XD was released in 2019 and it equipped designers with the right tools to build these dynamic elements and micro-interactions in prototypes by creating multiple states on a single component.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/1*KSdJbtNGJ7SHl18JmDWKGA.png" /></figure><p>Adobe XD had the capability to add reusable symbols to the designs. The product required an effective way to restructure ‘symbols’ to ‘components’ to support additional variants called ‘states’.</p><p>It aimed to help the designer structure the design system or a framework from an integration viewpoint. And also help them present the prototypes in a lively manner with the help of auto-animation.</p><h4>What is a Component and its States?</h4><p><strong>Components</strong> serve intuitively to push modifications across designs or documents instantly. Designers can make changes simultaneously by only modifying one instance, thereby spending less time duplicating and more time to design efficiently.</p><blockquote>The fundamental idea of a component is ‘Design once, reuse everywhere.’</blockquote><p>Adding <strong>States</strong> are a method of defining various visual formats for a single component. The states can be linked together in XD’s prototype mode to navigate between these states with transitions and animation support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*uEAtGBezLw8T9lTFSB5aYw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/162/1*yS4oSsN60m0QDWVDL_LVWA.png" /></figure><p>I was the lead designer and was responsible for <strong>defining the experience for the Components States from an end to end — design to developer handoff — perspective</strong>.</p><p>I worked closely with the researcher, product managers and the engineering team to construct the component states into reality. I teamed up with another designer working remotely from the US, who helped me assemble and test the experience on a global scale.</p><p>Adobe wanted the feature to be one of the highlights of the Adobe MAX 2019 event. The project was timebound, and we had a short time to finish the initial explorations and to present the leadership with a plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*2GEjt_ck6NLXqf8mYEeJ0w.png" /></figure><p>First, we looked at the existing end to end workflow of designing a symbol in various design tools and how it gets integrated into code.</p><p>A competitive audit comparing Sketch, Figma, Invision Studio and other popular prototyping tools like Principle App, Framer etc., was done in parallel. <strong>None of them had the direct capability to create states to the components and add prototype settings or animations together.</strong></p><p>We also reached out to the enterprise users to see how they design symbols/components. Since the ‘components and states’ capability helps both the designers and developers make their work easy and convenient, we interviewed them together.</p><p>In addition, I shared the wireframes and prototypes with the engineering team — from an initial stage, to see if the experience will be feasible and estimate all the implementation-related factors associated with it — especially the time frame to achieve it technically.</p><p>I sat with the product manager and started defining the main objectives. We derived a strategy very fast from the research.</p><h4>The Overview</h4><p>How can Adobe XD help a designer keep the UI structured and consistent across different platforms and frameworks by providing a feature that is based on the three main principles.</p><blockquote>- Create it once and reuse it everywhere.</blockquote><blockquote>- It should work intuitively to push changes across designs or documents, instantly.</blockquote><blockquote>- Spend less time duplicating and get back to iterating.</blockquote><p>As an initial target, I considered the essential components in a UI framework like — buttons, input fields, navigation, layout components etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ANQPgRA84zyGR1V3csKtEw.png" /></figure><blockquote>So as an example, the designer is creating an input item (a layer or a group) and he wants to add different states associated with it — hover, active, focussed, disabled etc.</blockquote><blockquote>How can the designer convert the input to a component and add states, then reuse it in different artboards and later modify it. The modificaitons should reflect in all the reused instances across the artboards.</blockquote><h4>The Approach</h4><p>I decide to work on the components and states interaction model for a week of whiteboarding and prototyping with the team. Three main goals were determined to be achieved with the experience.</p><blockquote>it should be easily discoverable.<br>it should be easy to interact with.<br>fewer UI impressions to reach the end-goal.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qC9pLpc-Zkx_Vh5t1JeK4w.jpeg" /></figure><h4>Editing the Components (Master vs Instance and overrides)</h4><p>The idea is to make the primary item the master component in the design. When you edit a Master Component, all instances are updated unless they contain overrides for that specific property. Thus the user can save time and effort in making changes to reused design items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*NVfLUIKrWp7jw5e0_77FnA.gif" /><figcaption>Modifications on the master will reflect on its instances.</figcaption></figure><p>Some conclusions were traced out after a week of whiteboarding. Now it was time to validate the ideas by taking them to the real users.</p><p>The engineering team was briefed about the ideas, and I worked with the UX engineer to prepare a POC to gather better test results. The POC was ready in two weeks, and I could now simulate the real experience of our idea to the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*f1Sy_giQdzxQXHSbAmpLDA.png" /></figure><p>The user testing results were surprising. Given the components and states functionalities, the designers were taking it to a different level. They started to create whole UIs with the help of these functionalities.</p><p>For example — in the POC, with minimal functionalities, <strong>a designer created an entire audio playlist and the player interaction</strong> with the help of components, states and prototyping capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*qoHUDnhxYItcPrkBthS0lQ.gif" /></figure><p>To conclude — more than 60% of the designers created UI’s, and they didn’t consider the idea of traditional components — from a design system or UI framework point of view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*SPcPWmrDXFqeNJaQ74d5oA.png" /></figure><p>The POC test unfolded the predicament that the designers will be using components and state features to create typical reusable components like buttons, navigation, toggle switches, etc., but also to design entire UIs and interactive elements.</p><p>This forced a revision in strategy; still, the priority was to let the user design reusable components — add states to them. And we considered a diverse vision to enable user design and create UIs with components and support states.</p><p><strong>There was a plan for the future to be considered — the support for ‘Libraries and Design Systems’. The experience should be scalable too.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58xysmn87cnWjCdXVFIMUA.png" /></figure><p>We stepped up the pace and I started cruising through the designs, interactions, and prototyping. The engineering team was also kept in the loop to identify any technical feasibility issues.</p><p>The ‘<strong>create component</strong>’ action was placed on the properties panel — so that the options are visible all the time. The user can now convert a layer or a group into a component. Once the component is added — they can add ‘states’ to it.</p><p>And for the states — a default option called ‘<strong>hover state’ </strong>was added to support the mouse hover interaction and to introduce the auto-animate and prototyping capability in Adobe XD. <strong><em>(the decision was made based on the research and user testing analytics — 85% of the users added a hover state to the components they created.)</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*hxb5AZRdWXmav9LKtFeAsA.png" /></figure><p>After spending hours of whiteboard sessions, sketching and prototyping, we finally ended up with a solid user flow to perceive the metamorphosis of components and states.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JnojNXW2C3Glx-W01CZbuw.png" /></figure><blockquote>The structured user flow was very simple.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibjQD2Wl4OXVvOc6zy5boA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*L-IPw-0eQlzsTSG64VIxjQ.png" /></figure><p>While going through the user research, brainstorming and prototyping — many challenges and pain points surfaced.</p><h4><strong>1. Discoverability</strong></h4><p>During the user research — the main question for the designers was, <strong><em>“How do you make a layer or a group in the design to a component?”</em>.</strong></p><p>Mixed reviews came up. Some of them wanted a CTA, some of them wanted it in the contextual menu. Another suggestion was to add it in the layer panel etc.</p><p>And for states, initially, I had the idea of showing pre-defined states — when the user creates a component — the app prompts a list of states preloaded like hover, active, focussed, disabled etc. And the users can pick from each and then make changes to the component. I had to drop the idea, as the users converted more than a regular button to a component, as I mentioned before.</p><p>After going through numerous iterations, user testing and prototyping, the decision was made to go with a prominent CTA in the properties panel and combined various other interaction points in the app to ‘make a component’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8_AKpDLmPASObWBt6PRGQ.png" /><figcaption>Make a component CTA options.</figcaption></figure><h4><strong>2. Onboarding</strong></h4><p>Onboarding the users was another main challenge.</p><p>Different patterns like tooltips, coach marks, toast etc., were under consideration. I went out to the real users to test every possible option and defined the onboarding experience, which was consistent with the standards of the <a href="https://spectrum.adobe.com/">Spectrum design system</a> (Adobe’s official design system)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*BPb8TEqwnzcirTTCxWNbpA.gif" /></figure><p>I collaborated with the content team to structure fitting content for onboarding and composed an animation to represent components and their features.</p><h4><strong>3. Visual representations and interactions</strong></h4><p>Components and states should be easy to work with and should self-educate the users with a visual pattern.</p><p>E.g., visual cues in the canvas to differentiate between the Master component and its instances and any overrides made to the instances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*cCCM3ye-Xn61JGjW_iIjXg.png" /><figcaption>Visual indications for Master, instance and instance with overrides</figcaption></figure><h4><strong>4. Technical constraints</strong></h4><p>There were many technical constraints while exploring the interaction model for components &amp; states.</p><p>One example was — when I defined the scenario of connection and syncing auto-animate with states (in prototype), it was hard for the developers to connect the functionality. But they understood the demand for this experience and the impact it will make, and we worked as a team and solved it.</p><h4><strong>5. Scalability</strong></h4><p>Another main factor I had considered was keeping the components &amp; states interoperable with the related features like colours and character styles.</p><p>Also, the experience should be well connected to future innovations like XD libraries, Design system integration etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*GAPb9pAp9WaASPf-hBPzrA.png" /></figure><p>Connecting the states and adding different interactive modes between the states was the next step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*h2QAAAi4_s4xTtTIoOF6Wg.gif" /></figure><p>To keep the consistency, the experience of adding interactions between component states was kept similar to the UX of wiring interactions between artboards.</p><p>When connecting interactions between component states, the main difference was that <strong>the designer chooses a state as a destination instead of an artboard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*zmlWG4TypAuW5ia0q_XJ0Q.png" /></figure><p>Auto-Animate breathes life into interactions.</p><p>States combined with Auto-Animate took prototypes to a new level, well beyond simple transitions and allows you to move and transform elements between artboards or states intelligently — this helps users create rich transitions that feel more realistic.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F573593862%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F573593862&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1186327677_295x166&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="636" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/de7857a36dfd3a38dd67630647302ef6/href">https://medium.com/media/de7857a36dfd3a38dd67630647302ef6/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*LzDXEgqKDhZtbqwvtt6HCQ.png" /></figure><p>Even though the engineering team had some technical challenges implementing the desired experience within a limited time frame, they pulled out a brilliant job in shipping out a full-featured build.</p><p>We reached out to users in multiple geographies and invited them to interact with the UI. It worked flawlessly, and they were able to create and execute the features beyond our expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVozoQF8bWZSMplb_ux_Zw.gif" /></figure><p>It was fascinating to see how they creatively used the Component States properties to manage the entire UI and its prototype capabilities. The reviews from the user testing were all positive.</p><blockquote>They were able to share the story efficiently with the stakeholders, and also the developer handoff was so explicit and impeccable.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*2MFWGOkwcIGedsyuu-Lbrg.png" /></figure><p>Components and States was one of the most highlighted features in the MAX release. Khoi Vinh (Director of XD Design) elaborated and presented the demo of the Components &amp; States. He explained the relationship between the Master components and their instances, prototyping capabilities and the auto animate feature.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FI5y0zmk8TzA%3Fstart%3D360&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DI5y0zmk8TzA&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FI5y0zmk8TzA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0291bed0bc2818fac752cc1c2a751579/href">https://medium.com/media/0291bed0bc2818fac752cc1c2a751579/href</a></iframe><p>XD Evangelist Howard Pinsky shared a UI Kit exploring the feature — it turned out to be a big hit among the designers. You can <a href="https://xd.adobe.com/view/fd309164-eeec-4f03-a974-a9d7a7c2c4bc-a863/">view the prototype</a> and download the file from the <a href="https://www.behance.net/gallery/87411019/Component-States-UI-Kit-for-Adobe-XD">Behance page</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*OiPY8nDvi5myOo6nqqlEvw.png" /></figure><p>After the release, the design world embraced the feature with both their hands. Blogger and Youtuber <a href="https://www.behance.net/forever-dansky">Daniel White (Dansky)</a> said,</p><blockquote>“States enable me as a designer to keep the entire UI kit as streamlined as possible, without the addition of extra artboards that are purely there to facilitate Auto-Animate effects or to toggle the on/off state of a switch.”</blockquote><p>He also mentioned</p><blockquote>“The addition of Component Overrides, now coupled together with States, enables me to design a large and complex UI kit while keeping the management and usage of the UI kit (by someone else) as simple as possible.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/27/1*ny82VGCWHunrpbrgF0S5lA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*NVqMI2I_UHDPeWqboeumag.png" /></figure><p>Components and States revolutionised the way designers treated their designs. The States feature combined with the Auto-animate and other prototyping features became a benchmark and helped the designer present their story better.</p><blockquote>When Components &amp; States were introduced in 2019 — it became the most used feature in XD.</blockquote><blockquote>In a span of 6 months, we added additional prototyping settings and toggle interaction to states. Now, as per the analytics, more than 92% of the users create Components and add States in their designs.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FhhL7f6uhg6qDkMfaSQ%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FhhL7f6uhg6qDkMfaSQ%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FhhL7f6uhg6qDkMfaSQ%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="324" frameborder="0" scrolling="no"><a href="https://medium.com/media/f1b063ed84ef81ea9d7d7f4f1c0d9889/href">https://medium.com/media/f1b063ed84ef81ea9d7d7f4f1c0d9889/href</a></iframe><p>More features have been added to XD now, like — voice triggers, scroll transitions, drag interaction and additional prototyping features. The designers use the Component States to create diverse designs and interactions in their designs.</p><blockquote>Prototypes help tell a story, bring static designs to life and demonstrate how a user will experience a product. Prototypes are also an essential part of the design process for communicating to development teams and other stakeholders.</blockquote><blockquote>Components and States combination in Adobe XD made it easy to prototype a design, from basic transitions to more advanced interactions.</blockquote><p>-</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc6c30e198ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>