<?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 Vinod Abraham on Medium]]></title>
        <description><![CDATA[Stories by Vinod Abraham on Medium]]></description>
        <link>https://medium.com/@vinodabraham?source=rss-256f2bcdb5c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WITu2GuQnSTpsRSZTn97fQ.png</url>
            <title>Stories by Vinod Abraham on Medium</title>
            <link>https://medium.com/@vinodabraham?source=rss-256f2bcdb5c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:55:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinodabraham/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[Designing the Shift: A Case Study in UX Leadership at a Legacy MNC]]></title>
            <link>https://medium.com/@vinodabraham/designing-the-shift-a-case-study-in-ux-leadership-at-a-legacy-mnc-5df2eb99d837?source=rss-256f2bcdb5c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5df2eb99d837</guid>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[designshift]]></category>
            <category><![CDATA[ux-leadership]]></category>
            <category><![CDATA[new-to-old]]></category>
            <dc:creator><![CDATA[Vinod Abraham]]></dc:creator>
            <pubDate>Mon, 28 Jul 2025 07:39:24 GMT</pubDate>
            <atom:updated>2025-07-29T15:50:29.553Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrfCkgLD1kzapI7RFbGAbg.jpeg" /></figure><p>When I joined a global food and environmental testing MNC with over 30 years of legacy, I stepped into a company that had never formally embraced UX. With more than 100 programme in active use — built by teams focused heavily on functionality — I was the first UX expert ever hired.</p><p>In early 2018, the UX team was hired to enhance the next generation of the <strong>Lab Information Management System (LIMS)</strong>. As the first UX designer, I focused on bringing user-centred thinking into this mission-critical platform, aiming to improve usability and streamline lab workflows.</p><p>This presented a rare and exciting opportunity: to lay the foundation for UX in a company of this scale and complexity. From defining what UX even meant in our context to aligning it with legacy systems and stakeholder mindsets, my role was to introduce a user-centred design culture from scratch.</p><p>This case study details how I:</p><ul><li>Established UX practices and workflows compatible with existing processes</li><li>Collaborated across departments to integrate UX thinking into product lifecycles</li><li>Created the company’s first UX Design Principles and documentation</li><li>Advocated for scalable, repeatable approaches to research and design</li></ul><p>Setting up UX in an environment that had never known it wasn’t just a design challenge — it was a strategic one.</p><blockquote>Intuitive Design — Modular Architecture — Quicker Releases.</blockquote><h3>My Role</h3><p>As the first UX hire in a 30+-year-old global organisation, I led the effort to establish UX as a core function within the company. My role extended beyond design execution — I was responsible for building the UX foundation from the ground up. This included setting up design practices, driving stakeholder collaboration, and delivering hands-on work such as research, wireframing, prototyping, and user testing. Additionally, I played a key role in hiring and mentoring the design team, scoping UX initiatives, and budgeting for tools and resources to scale the function sustainably.</p><h3>Key Responsibilities</h3><p><strong>Customer Insights &amp; Ideation<br></strong>Initiated user research across global teams to surface hidden pain points, identify unmet needs, and spark idea generation rooted in real user challenges.</p><p><strong>Planning &amp; Scope Definition<br></strong> Scoped UX efforts in alignment with existing development cycles and business priorities, helping teams shift from ad-hoc feature building to user-driven roadmaps.</p><p><strong>Design Execution &amp; Validation<br></strong> Delivered low- to high-fidelity wireframes and interactive prototypes; validated solutions through usability testing and feedback loops across regions.</p><p><strong>Strategy &amp; Vision<br></strong> Defined a UX vision aligned with the company’s transformation goals; introduced the first UX Design Principles to guide future design decisions.</p><p><strong>Oversight &amp; Coordination<br></strong> Integrated UX into existing workflows and delivery pipelines, working across functions to ensure design quality and consistency at scale.</p><p><strong>Leadership &amp; Team Building<br></strong> Built the UX function from scratch — hiring the first team members, setting up collaborative rituals, and evangelizing user-centered thinking across the organization.</p><blockquote><strong>Design Philosophy</strong></blockquote><blockquote>“A perfect product is a fine balance between the user’s need and the product’s requirement; neither can survive alone.” — Vinod Abraham</blockquote><h3>The Challenge</h3><p>As the first UX hire, one of the biggest hurdles was that the business didn’t yet understand where UX fit within the existing product development process. UX was not part of any formal workflow, and user-centric thinking had never been integrated into decision-making.</p><p>The product suite consisted of over 20 standalone .NET applications — each built in isolation with no shared design language or system integration. Wireframes were owned by Business Analysts (BAs), based solely on requirements handed over by business stakeholders. Developers implemented changes in an ad hoc manner, often piling new features onto existing screens without considering layout, flow, or usability.</p><p>This led to several critical issues:</p><blockquote><strong><em>Inconsistent and cluttered interfaces</em></strong><em>, making navigation difficult and unintuitive</em></blockquote><blockquote><strong><em>Low user acceptance</em></strong><em>, with less than 50% of users adopting new features</em></blockquote><blockquote><strong><em>Solution-first mindset</em></strong><em>, where BAs and business leads proposed UI changes without defining the underlying user problem</em></blockquote><blockquote><strong><em>Lack of design planning</em></strong><em>, resulting in screens overloaded with functionality and poor user flow</em></blockquote><p>Introducing UX into this environment required not just design interventions but also a cultural and structural shift in how problems were approached and solutions were crafted.</p><p>Here’s how I approached it.</p><h3>Understanding the Current State</h3><h4>Information Architecture Review</h4><p>To begin, I conducted a comprehensive knowledge transfer (KT) to understand the existing application landscape and how the LIMS system functions end-to-end. Based on this deep dive, I created an <strong>Information Architecture (IA)</strong> map of the current system. This helped visualize how modules were structured, where overlaps existed, and how users navigated across 20+ disconnected .NET applications.</p><h3>User Research</h3><p>To validate assumptions and gain a ground-level view, I visited <strong>six labs </strong>across<strong> five countries</strong>, conducting in-depth interviews with <strong>100+ users</strong> — including lab technicians, supervisors, and data reviewers.</p><p>The goals were clear:</p><ul><li>Understand real-world workflows inside the lab</li><li>Identify user pain points and unmet needs</li><li>Map functional gaps and UX breakdowns in the current system</li></ul><h4>Key Research Findings</h4><ul><li><strong>Broken Navigation:</strong> Users found it difficult to move within and across applications, leading to frequent errors and inefficiencies.</li><li><strong>No Feedback Loop:</strong> There was no formal mechanism for users to provide feedback or request improvements.</li><li><strong>Inconsistent UI:</strong> Each application looked and behaved differently, creating a fragmented experience.</li><li><strong>Lack of Discoverability:</strong> Users often requested features that already existed — highlighting unintuitive layouts and poor information hierarchy.</li><li><strong>Poor CTA Prioritisation:</strong> Primary and secondary actions weren’t clearly defined; some screens had up to <strong>10 competing CTAs</strong>, overwhelming users and slowing down tasks.</li><li><strong>Need for Hardware-Integrated Workflows<br></strong> Users expressed a preference for hardware like barcode scanners to streamline data entry and minimise manual effort.</li><li><strong>User Frustration with Dead Ends<br></strong> Research revealed that users often encountered screens with no clear next step, leading to confusion and dropped tasks.</li></ul><h3>Laying the Foundation for UX</h3><p>Based on these findings, I proposed a strategic UX foundation built on <strong>three key pillars</strong>:</p><ol><li><strong>Design Principles Document:</strong> Established a shared language and philosophy for consistent, user-centred design across teams.</li><li><strong>Design System:</strong> Began the creation of a modular, reusable component library to ensure UI consistency and speed up development.</li><li><strong>Seed Application:</strong> Designed and delivered a reference product (Seed App) to demonstrate UX best practices in action — setting a benchmark for future builds.</li></ol><p>This work culminated in defining the <strong>UX process</strong> — how UX integrates with product, BA, and development teams, ensuring collaboration at every stage of the product lifecycle.</p><h3>Design Tenets</h3><p>Given that our<strong> primary users</strong> were <strong>lab technicians and analysts</strong> working in high-focus environments, our design approach <strong>prioritized clarity, simplicity, and speed</strong>. The goal was to reduce cognitive load and help users make quick, confident decisions without distraction.</p><p><strong>Key design principles included:</strong></p><ul><li><strong>Keep it simple: </strong>Interfaces were stripped of visual clutter to ensure users could focus on the task at hand.</li><li><strong>Right Focus: </strong>Screens were structured to guide attention to primary actions and critical information.</li><li><strong>Lightweight UI: </strong>We avoided heavy visual elements, opting instead for clean layouts, minimal styling, and efficient interactions to support fast-paced lab workflows.</li></ul><p>These principles shaped every aspect of the design system, from typography and layout to interaction patterns and feedback mechanisms.</p><p><strong>Defining the UX Process</strong></p><p>Given the small UX team managing a suite of 20+ applications, we introduced a custom, efficient UX process tailored to our environment. Since research had already been conducted, the UX Process Breakdown given below</p><h3>UX Process Breakdown</h3><p>Below is a step-by-step breakdown of the UX process we implemented post-research:</p><ul><li><strong>Requirement Gathering<br></strong> Requirements were collected through Business Analysts (BA) or Functional Analysts (FA), via documentation or direct discussions with stakeholders.</li><li><strong>Information Architecture (IA)<br></strong> A new IA was created based on gathered requirements and earlier research. This directly addressed the broken navigation across applications.</li><li><strong>Wireframing<br></strong> Low-fidelity wireframes were developed through multiple discussions, focusing on functionality. Functional approval was secured at this stage, separating layout logic from visual design to reduce rework later.</li><li><strong>Visual Design<br></strong> High-fidelity screens were designed using the established design system and principles, ensuring consistency and usability across all interfaces.</li><li><strong>Prototyping<br></strong> Interactive prototypes were built to simulate end-to-end user flows and demonstrated to business stakeholders for validation.</li><li><strong>Usability Testing<br></strong> Designs were validated through focused usability tests — task-based sessions with actual users — before handing off to development.</li><li><strong>Gap Analysis<br></strong> If new components were required, they were added to the Seed Application to avoid future development delays. Alternate design solutions were provided for any technical constraints.</li><li><strong>Visual QA<br></strong> This step ensured the final implementation matched designs pixel-perfectly. It also guaranteed that all UI changes passed through UX, preventing inconsistent or unintuitive interfaces.</li><li><strong>Enhancements<br></strong> Post-rollout, further research was conducted to identify areas for improvement and guide future iterations.</li></ul><p>This streamlined, repeatable approach helped align all stakeholders and drastically improved user acceptance — rising from under <strong>50%</strong> to an average of <strong>98%</strong>.</p><h3>Impact Report</h3><p>The introduction of UX as a formal discipline within a 30+ year-old legacy organisation had a transformative effect — not just on design outputs, but on product thinking, development workflows, and end-user satisfaction.</p><h4>User Experience Transformation</h4><ul><li><strong>User Adoption Jumped from &lt;50% to 98%<br></strong> Systematic UX involvement in planning, wireframing, and validation led to dramatically higher user acceptance across multiple applications.</li><li><strong>Streamlined Navigation Across 20+ Applications<br></strong> Revamped information architecture and consistent UI patterns reduced errors and improved task completion efficiency in daily lab operations.</li><li><strong>Significant Drop in Usability Complaints<br></strong> Direct usability testing and feedback loops helped resolve long-standing user frustrations and eliminated redundant features and flows.</li></ul><h4>Process &amp; Workflow Improvements</h4><ul><li><strong>Formalized UX Process Integrated into SDLC<br></strong> UX became a structured part of the delivery pipeline — ensuring every feature was user-validated and visually consistent before release.</li><li><strong>Established First-Ever Design System<br></strong> A modular, scalable design system improved delivery speed and enabled reusability across teams and applications.</li><li><strong>Cross-Functional Alignment with BAs and Developers<br></strong> Collaborative rituals improved clarity, minimized rework, and ensured functional alignment before any development started.</li></ul><h4>Organizational Impact</h4><ul><li><strong>Culture Shift Toward User-Centered Thinking<br></strong> UX moved from a “nice-to-have” to a strategic pillar, influencing decision-making at the product and leadership level.</li><li><strong>Built a Scalable UX Team &amp; Practice<br></strong> From a one-person team to a structured CoE with hiring, mentoring, tooling, and training frameworks in place.</li><li><strong>Design-Led Benchmarking Through Seed Application<br></strong> The Seed App served as a tangible example of design excellence — used to onboard new developers, guide architecture choices, and evangelise UX best practices internally.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5df2eb99d837" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>