<?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 Mrirani on Medium]]></title>
        <description><![CDATA[Stories by Mrirani on Medium]]></description>
        <link>https://medium.com/@mrirani?source=rss-a7ed9af51a35------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*djzejzTP_jPY7YeIPmNFvA.jpeg</url>
            <title>Stories by Mrirani on Medium</title>
            <link>https://medium.com/@mrirani?source=rss-a7ed9af51a35------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:29:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mrirani/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[From Words to Workflows: UX Content Design at Nutanix]]></title>
            <link>https://medium.com/nutanix-design/from-words-to-workflows-ux-content-design-at-nutanix-cf2df933a902?source=rss-a7ed9af51a35------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf2df933a902</guid>
            <category><![CDATA[nutanix]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[ux-content-design]]></category>
            <dc:creator><![CDATA[Mrirani]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 05:51:47 GMT</pubDate>
            <atom:updated>2025-09-24T03:59:47.989Z</atom:updated>
            <content:encoded><![CDATA[<p>In enterprise tech, clarity isn’t a luxury; it’s survival! When you’re managing hybrid cloud environments, deploying workloads at scale, or troubleshooting infrastructure in real-time, a single ambiguous message, a mislabeled control, or an onboarding text that doesn’t match how people actually work can cost teams hours and dollars. That’s where content design steps in — not as ‘fill in the blanks’ in the UI.</p><p>As a UX content strategist at Nutanix, I’ve observed that when we incorporate content design from the start alongside research, product, and engineering, we ship faster, reduce support reliance by users, and earn more trust where it matters most: in production.</p><h3>What “good content” looks like in practice</h3><ul><li><strong>Involve content at problem framing: </strong>Define <strong>user intent, domain terms, and success states</strong> before you start designing.</li><li><strong>We work on flows together and not just single screens: </strong>Writers, designers, PMs, and engineers co-design state changes (loading, success, empty, error).</li><li><strong>Error handling is key:</strong> Say <strong>what</strong> happened, <strong>why</strong>, and <strong>what</strong> to do next — respecting the user’s effort. Test error copy with the same rigor you test critical flows.</li><li><strong>Build a robust content system:</strong> Work on terminologies, voice, and tone by context, and accessibility rules. Now add these into your design components so teams can ship the right words as much as possible independently.</li><li><strong>Measure/test words and not just the UI: </strong>Track task success and completion time. Check the number of times users resolved queries through help articles without raising tickets, and the top five ticket topics that content can fix. A/B test the copy, not just the color or placement of the button.</li></ul><h3><strong>How we at Nutanix make the most of UX Content</strong></h3><p>By now, you must have gathered that content design at Nutanix isn’t just about polishing words at the end; it’s how we make complex infrastructure feel obvious from the start. In the sections below, we will demonstrate how strategy drives microcopy. Why audits are so important and why writing in active voice, testing our copy along with UI, and prioritizing our error model (“what happened, why it happened, what to do next”) is key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0RCv9wAuk5vhYF-NoWcT5A.png" /><figcaption>Types of content involvement at Nutanix currently</figcaption></figure><h4><strong>A) Content design is not just ‘fill in the blanks’ in the designs</strong></h4><p>Content should be graspable and clearly understood. In this example from our LCM (<em>Life Cycle Manager</em>) screen, users are taken through a guided tour on how to use this section with the help of tooltips. LCM is a tool that automatically keeps clusters up to date by checking, downloading, and applying software upgrades with minimal effort.</p><p><strong>Issues included </strong><em>(see ‘before’ screen below)</em></p><ol><li>The<strong> </strong>header didn’t add value.</li><li>The subtext was clunky, adding to the cognitive load.</li></ol><p><strong>Suggestions included</strong> <em>(see ‘after’ screen below)</em></p><ol><li>Action-oriented header.</li><li>Moved away from a clunky paragraph format and used the clearer bulleted way of showing information.</li><li>Removed redundant information like ‘click the actions button’.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*anUVcj5vk2UAK4DrpionsA.png" /></figure><h4><strong>B) UX Content design is mostly UX Content Strategy</strong></h4><p><strong>UX content design </strong>is largely <strong>content strategy</strong>. We define the exact information users need at each step and then shape the screen around that. For example, we start with a content inventory:</p><ul><li><strong>Required fields</strong></li><li><strong>Defaults</strong></li><li><strong>Warnings</strong></li><li><strong>Remediation (adding clear next steps)</strong></li><li><strong>If the ‘help text’ runs long</strong>, we switch from inline hints to error notification banners to add clarity, but without crowding the UI.</li><li><strong>For long resource names</strong> (labels/identifiers), we partner with design to use flexible columns, smart truncation, or info icons to reduce cognitive load.</li><li><strong>Our error model</strong> -“what happened, why, and how to fix.” Designers and content designers work together to decide where we may need inline messages or where transient toasts may be helpful. It’s always a team effort.</li><li><strong>Progressive disclosure</strong> helps retain the most important information at the forefront, helping users make better-informed decisions in a step-by-step manner.</li></ul><p>Here’s an <strong>example from Move </strong>(<em>Nutanix Move helps users easily transfer their apps and data from one environment to another without disruption</em>), where VMs (<em>Virtual Machines</em>) needed to be migrated. Due to content strategy designs changed, and how:</p><p><strong>Issues include </strong>(s<em>ee ‘before’ screen below</em>)</p><ol><li><strong>No header: </strong>Context was thus missing.</li><li><strong>Disabled primary CTA 1 </strong>on the welcome screen: Users were hence not guided to the first step seamlessly.</li><li><strong>Primary CTA 2</strong> <strong>within the side panel</strong>: Taking away from the primary information of how to migrate VMs.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jotnWt2wnNLn_B6OGnk7yg.png" /></figure><p><strong>As suggestions, </strong>we<strong> </strong>broke the <strong>screen down into 2 steps (<em>Step A and Step B — screens below</em>)</strong> that added better clarity, reduced cognitive load, resulting in a balanced design.</p><ol><li><strong>Informative main header</strong>: Moved away from the basic ones like “Welcome to VM Migration”</li><li>Brought in the very first step of “Add Environment” as the primary CTA</li><li><strong>Step A: </strong>Removed the side panel</li><li><strong>Step B: Primary CTA changed to the core task after at least 1 environment was added</strong> — “Create Migration Plan”</li><li><strong>Step B: Introduced the side panel</strong> only after at least 1 cluster is added.</li><li><strong>Action-oriented headers </strong>+ <strong>explanatory text</strong> is concise, clear, symmetrical, and easy to follow.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAs8DssTZQTW12waTBPMuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAEmrmydNkOEVWz3a0WKdQ.png" /></figure><h4><strong>C) Importance of voice and tone</strong></h4><p>How we speak to our users through our product is key. <strong>Voice</strong> is your product’s consistent personality, and <strong>tone</strong> is how that voice shifts by context, directly influencing comprehension, trust, and user behavior — especially under stress, like error scenarios, outages, billing, and security.</p><p><strong>Why voice and tone matter</strong></p><ul><li><strong>Clarity and speed:</strong> A steady voice with a predictable tone lowers cognitive load.</li><li><strong>Trust during high-stakes moments:</strong> Calm, transparent tone during failures (“what happened + impact + what to do”) reduces panic and support tickets.</li><li><strong>Actionability:</strong> Tone can nudge action. Directive but respectful language (“Update the policy, then retry”) leads to higher task completion than vague information or a copy with a harsh tone.</li><li><strong>Consistency at scale:</strong> In large organisations with multiple teams, a shared voice prevents terminology drift and reduces rework across different teams, like branding and technical writing teams.</li><li><strong>Risk mitigation:</strong> The wrong tone can imply guarantees, minimize risk (which may not be apt for that scenario), or assign blame — creating compliance and brand issues.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pnOffr_VC3JsYRAQR8kXFw.png" /><figcaption>A simple tone matrix example</figcaption></figure><h4><strong>D) Importance of active voice</strong></h4><p>In simple words, in an active voice, the subject does the action, making sentences clear and direct. In UX, that means faster decisions, fewer mistakes, and clearer accountability.</p><p><strong>Why active voice is (usually) better</strong></p><ul><li><strong>Clarity:</strong> The doer is upfront, so users instantly know <em>who</em> does <em>what</em>.<br> <em>Passive:</em> “The request was denied.” This may make the user ask, “Who denied it?” Or “why was the request denied?”<br> <em>Active:</em> “Server failure, request denied.”</li><li><strong>Brevity:</strong> Active sentences are typically shorter and thus quicker to scan.<br> <em>“Session expired. Sign in again.”</em> (Active/imperative) is tighter than <em>“You are required to sign in because your session has expired.”</em></li><li><strong>Actionability:</strong> It pairs naturally with the next steps the user is required to take<br> <em>“Update the policy and retry.”</em> vs <em>“A retry is recommended once the policy is updated.”</em></li><li><strong>Consistency with UI patterns:</strong> Buttons, labels, and system messages work best as commands or subject-verb statements (“Create snapshot,” “Download logs”), which are all “active” in nature.</li><li><strong>Better for localization and accessibility:</strong> Clear subjects and simple syntax reduce translation errors and improve screen-reader output.</li></ul><h4><strong>E) From audits to actionable design</strong></h4><p><strong>We at Nutanix also carry out </strong>regular content audits of our products, standardize terminology, and focus on actionable errors and empty states.</p><p>A couple of years back, our team carried out a Prism Tasks revamp, where the team addressed real admin needs (clearer task hierarchies, copyable error details, better filtering), emphasizing how content and interaction design reduce troubleshooting time at scale.<a href="https://medium.com/nutanix-design/building-ux-writing-guidelines-for-enterprise-design-76c0e800a65e"> Check out our Medium</a> article.</p><h4>F) How content fits inside Nutanix’s design system</h4><ul><li><strong>Foundations:</strong> Teams define voice, tone, terminology, casing, grammar rules, and character count alongside visual tokens. This yields consistent labels (e.g., sentence case), bias-free language, and clear naming conventions across products.</li><li><strong>Component-level guidance:</strong> Each component (button, form field, toast, modal, empty state, banner) includes “microcopy rules”. These include — purpose, dos/don’t examples, character limits, placeholder rules, and error templates. Designers can pull the guidance at the exact point of use with little or no dependency on UX writers.</li><li><strong>Patterns and templates:</strong> We ship system patterns — errors, confirmations, onboarding, permissions with a clear content framework: “what happened, why it happened, and what to do next.” We also add sample strings and slot maps within the design system so designers get the right words in early, during early design, to ensure consistency and speed across teams.</li><li><strong>Reusable strings &amp; A11Y:</strong> Common CTAs and system messages become shared resources, reducing duplication and easing accessibility. Accessibility guidelines and truncation rules can easily live with the components.</li></ul><p>This works well because designers get embedded voice and tone rules and microcopy patterns in components, so they move faster with fewer review cycles. With consistent terminology, character limits, and reusable strings, rework cycles are reduced, which makes handoffs to engineering smoother. Also, actionable error and empty-state templates boost usability and accessibility by default, reducing polish time.</p><h3><strong>How content designers and stakeholders collaborate at Nutanix</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywHOO0gdK7xkd_fu57QaoQ.png" /><figcaption>Stages of UX content involvement end-to-end at Nutanix</figcaption></figure><p>The image above shows how our content team works end-to-end, starting from scoping and flowing into post-ship support. But we also work in-depth to tackle our content debt and legacy content. Legacy content is real — and fixable — if you treat it like product work, and not just cleanup!</p><p>Here are a few effective ways to balance working on new flows alongside addressing legacy —</p><ul><li><strong>Stop the bleed: </strong>Ensure to ship new flows with guardrails — voice/tone, glossary, error patterns, reusable strings, and character limit. Now use them from the first wireframe, thus new flows ship clean.</li><li><strong>Keep a short “content debt” list:</strong> Log anything that trips users. These include confusing screens, walls of text, vague labels, or unhelpful errors. Group by theme (e.g., unclear empty states, inconsistent terms) so you can fix them in batches.</li><li><strong>Prioritize what matters most: </strong>Fix the places users hit most and where mistakes hurt. For example: first-time setup, core actions, and errors.</li><li><strong>Fix by pattern, not page: </strong>Create one good error or empty-state template, then apply it everywhere. Replace outdated terms with the agreed ones. Break long text into clear bullets and headers.</li><li><strong>Work in two lanes: </strong>In every release, reserve a small, fixed slice for legacy fixes (e.g., 20–30%) while the rest goes to new flows. The rhythm matters more than the exact number.</li><li><strong>Ship small but often: </strong>Aim for quick wins you can merge in days. Focus on one component, one message set, one screen. Issues that can be solved quickly, but efficiently, and with minimum dependencies.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9n_btsKjII864rjET8wUCw.png" /><figcaption>Involvement of a UX content strategist for content tasks that don’t require end-to-end ownership</figcaption></figure><p>In conclusion, great products aren’t just engineered — they’re communicated. At Nutanix, content design turns complex infrastructure into clear decisions by shaping flows, defining terms, and engineering for accessibility from day one — the result: great stakeholder management, and products where all teams are aligned with decisions taken. More users could now get their tasks done through the UI itself, thus reducing the need to rely on help articles.</p><p>So, folks, bake content into your design system, bring writers in at problem-framing, and test the words, not just the UI.</p><p><strong>Clear, consistent language is how enterprise software earns adoption!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf2df933a902" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nutanix-design/from-words-to-workflows-ux-content-design-at-nutanix-cf2df933a902">From Words to Workflows: UX Content Design at Nutanix</a> was originally published in <a href="https://medium.com/nutanix-design">Nutanix Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to effectively communicate with India’s small businesses]]></title>
            <link>https://medium.com/meesho-tech/how-to-effectively-communicate-with-indias-small-businesses-b76391fa9e66?source=rss-a7ed9af51a35------2</link>
            <guid isPermaLink="false">https://medium.com/p/b76391fa9e66</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[meesho]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mrirani]]></dc:creator>
            <pubDate>Fri, 01 Jul 2022 04:19:46 GMT</pubDate>
            <atom:updated>2022-07-01T04:19:46.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2TowHbANaPLFL_UpN1SdTg.png" /></figure><p>Even when something’s free, it will cost money.</p><p>At least, that’s what our suppliers thought.Even when we offered our suppliers free credits they thought it would be a liability.</p><p>Why? The usage of the word “cost” and “₹”.</p><p>From “Add to Cart” to “Estimated Delivery Date”, a lot of thought goes into writing every small text on our app. Here is a peek into how our UX team solved a huge gap in our cataloguing problem through effective communication:</p><h3>Problem Identified 🕵️</h3><p>Catalogue uploading is the most critical action our suppliers must take. In fact, for effective selling on Meesho, a suppliers must upload a minimum of 7 catalogues within the first 30 days of creating their account.</p><p>However, we discovered that many of our suppliers did not have the motivation to complete catalogue uploads. These required our suppliers to supply product info such as size, colour, category, etc., which proved to be <strong>too time consuming</strong>. This step was eating into their business hours. Moreover, some suppliers also face technical issues that weren’t promptly addressed.</p><h3>The Solution : Incentive Bundling Project 💰</h3><p>We needed our suppliers to complete catalogue uploading. The obvious solution was to incentivise this step. So, we did.</p><p>We offered monetary credit to suppliers who upload a minimum of 7 catalogues. Suppliers could use this credit to create advertising campaigns on Meesho and boost their business. Additionally, we released other secondary rewards aimed at improving the satisfaction metrics amongst our suppliers.</p><p>We identified two entry points to place the communication banner:</p><ol><li>First, the most obvious real estate… the <strong>home screen</strong></li><li>Second, the <strong>advertisement section</strong> that a supplier could access through their account. This is a high visibility spot which receives ~230,000 visits per day and ~37,000 unique users every month</li></ol><p>Now with the banner placement set, we moved onto creating a content hierarchy that helped weave the ‘Incentive Bundling’ story with intuitive design.</p><blockquote><em>While design grabs the attention of a supplier, content informs them of the value proposition. Design and content (UX copy), thus, go hand-in-hand.</em></blockquote><p>But things went wrong before they got right.</p><h3>The Goof Up 🙈</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_mPDpXHRwQNFVE68" /></figure><p>The above banner was added to the the advertisement section.<strong>What we found:</strong></p><ul><li>Users did not understand the term “<strong>ad credit</strong>” and “<strong>worth</strong>”</li><li>With the word “<strong>free</strong>” and the amount “<strong>1200</strong>” so far apart, our suppliers didn’t realise that we were giving them 1200 ad credits for free</li><li>The usage of <strong>“₹”</strong> confused our users into thinking that we were asking them to spend INR 1200</li></ul><h3>Course correction 💡</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dKKsZoYyH25gOW-o" /></figure><ul><li>We orchestrated intensive User Testing (UT), where we interacted at length with our suppliers to understand the way they speak and comprehend English. This led us to some revelations. We replaced <strong>“Ads Credit”</strong> with <strong>“Advertisement Balance.”</strong> While the word <strong>“balance” </strong>explicitly told our users that <strong>“1200”</strong> is what remains with them, <strong>“advertisement”</strong> was way more comprehensible to our suppliers than <strong>“ads” </strong>or even <strong>“advertising”</strong></li><li>Lastly, we placed 1200 next to “Free.” This removed any remaining confusion and we clearly communicated that it was free balance for ads</li></ul><h3>More Goof Ups 😬</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1de_tGTyPFdcpYwW" /></figure><p>The banner above was placed on the home screen to convey to our users that they were now part of the “Supplier Plus” programme. But…</p><ul><li>Suppliers had no clue about what ‘Supplier Plus’ actually meant.</li><li>They interpreted the phrase “you are now part of” as a membership programme that could be extended after the first 30 days.</li><li>The banner didn’t convey where or how suppliers could “use rewards”.</li></ul><p>Essentially, this banner didn’t reassure our suppliers regarding their business growth. Meanwhile, the rewards screen (aka the page where suppliers see the rewards available to them) was causing more confusion to the suppliers too.<strong>Here’s a sample rewards screen:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z2SxTBxubqmIawtZ" /></figure><ul><li>“Upload 4 more catalogues” was not the right way to communicate with our users</li><li>Our UT showed that the terms such as “advertising,” “returns placed,” “applicable,” “penalty,” and “worth” were incomprehensible to our users</li><li>Our suppliers interpreted “callback within 1 day” in Catalogue Manager Support card as “they would get just one call” from Meesho’s support team.</li><li>Penalty for cancellations was not a point of concern for our suppliers if at least cancellation within the first 30 orders were waived off.</li><li>The ‘days left’ part were repetitive.</li><li>There was no follow up on ‘Boost Your Business’ mentioned in screen 2</li></ul><h3>When we got it right 🙌</h3><p>We changed our language to match the expectation of our users. For example, we explained what “Supplier Plus” is but simply putting it after the key term “Boost your business” in the home page banner. We also added “See Rewards” as the Call To Action, which became an exploratory trigger for the suppliers to see what the reward section is about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nvAErkEQfIV-XgKf" /></figure><p>We also made the following changes to the rewards screen:</p><ul><li>We replaced “4 more” with “4/7” which made the communication about number of catalogues to be uploaded explicit and simple</li><li>We replaced “callback within 1 day” with “receive call back within 24 hours”</li><li>We shortened the subtexts and removed terms that were foreign to our user base and replaced “days left” with “rewards expire on” at the top of the banner, which created a sense of urgency and eliminated repetition</li><li>And finally, we gave a coveted spot to the “Boost your business” buzz phrase.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xtaRV1sfuO-W2Vp7" /></figure><p>UT has been key to our deep understanding of how Bharat’s e-commerce users communicate online. We were sufficiently surprised to learn how the placement of words can completely change the perception of our messaging. We also learnt that not all short, crisp sentences float well with our suppliers. Some occasions call for over communication. Longer sentences = Better comprehension.</p><p>After making these small but incremental changes we found our suppliers starting to feel more comfortable using the various features on the Meesho platform, and finally taking action quicker on our app and website.</p><h3>The Takeaways ⭐</h3><ul><li><strong>Involve:</strong> Work on content at early stages. Content has a big say in the design stages</li><li><strong>Ask:</strong> Talking to users is the best way to gauge what will work and what won’t. This includes terminologies, nomenclatures, etc.</li><li><strong>Evolve:</strong> The order of words, their proximity to other elements in design, their spacing may change the whole meaning for the user. Know what these nitty-kitties are and evolve with your user’s behaviour</li></ul><p>While the impacts metrics of this project pour-in, the user testing and feedback is positive. But there is always leeway to evolve and adapt. After all, we are building for the next billion.</p><p>This project wouldn’t have been possible without the help of <strong>Heli Fajalia (Product Designer) and Avinash Paadhi and Vennela (Product Managers)</strong></p><p>If you want to work on such unique challenges and build for the next billion, check out our <a href="https://meesho.io/jobs?utm_medium=organic_social&amp;utm_source=blog&amp;utm_campaign=blogCTA">careers page</a> for our openings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YyXoabXXLkir_Cax.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b76391fa9e66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/meesho-tech/how-to-effectively-communicate-with-indias-small-businesses-b76391fa9e66">How to effectively communicate with India’s small businesses</a> was originally published in <a href="https://medium.com/meesho-tech">Meesho Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>