<?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 Gray Holland  on Medium]]></title>
        <description><![CDATA[Stories by Gray Holland  on Medium]]></description>
        <link>https://medium.com/@uxflo?source=rss-8c5bfb36f9f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HLVaJg6UnJ5DNwFyi99GgQ.png</url>
            <title>Stories by Gray Holland  on Medium</title>
            <link>https://medium.com/@uxflo?source=rss-8c5bfb36f9f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:26:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uxflo/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[The uncomfortable truth about UX testing]]></title>
            <link>https://medium.com/@uxflo/the-uncomfortable-truth-about-ux-testing-9dad0a8633d2?source=rss-8c5bfb36f9f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dad0a8633d2</guid>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Gray Holland ]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 14:45:31 GMT</pubDate>
            <atom:updated>2025-03-30T20:05:26.865Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Uncomfortable Truth about UX Testing</strong></h3><h4>Exploring the gap between UX testing theory and practice</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Po4thLXPKrmb9b1_FIuyQ.jpeg" /></figure><h4><strong>The Testing Disconnect</strong></h4><p>When did your team last conduct a real user test? Not just gathering analytics or collecting survey feedback — but a structured test where actual users interact with your product. That moment of hesitation you’re feeling reveals the gap between what we preach and what we practice.</p><p>As UX professionals, we’ve mastered the art of advocating for user testing. We fill slides with compelling arguments for early validation, testing plans, and champion user-centered design principles in every kickoff. Yet when timelines compress and resources tighten, testing is inevitably the first thing we sacrifice. I’d like to confronted this disconnect head-on.</p><p>Having led design teams for over two decades, I’ve seen this pattern repeatedly — and I’m not immune. We fully understand the value of testing, yet that understanding rarely leads to consistent action. Decades of research show that fixing problems becomes exponentially more expensive as development progresses, and those figures don’t even capture lost user trust or missed market opportunities. Still, we push testing aside, settling for reactive fixes rather than proactive intervention. We never have time to do it right the first time — but we always seem to find time to do it twice.</p><blockquote>User testing isn’t just a nice-to-have — it’s the foundation for sustainable UX improvements and product success, yet we consistently sideline it — why?</blockquote><p><strong>A Series on Measuring the Difference in User Experiences</strong></p><p><em>This series takes a practical journey through the user testing landscape. In Part One, we confront uncomfortable truths about our testing practices. Part Two will introduce a pragmatic approach that works within real-world constraints. Later installments will showcase tools and </em><a href="https://medium.com/@uxflo/how-we-made-complex-software-21x-easier-to-use-0df0a7fd8375"><em>case studies</em></a><em> demonstrating these approaches in action. Throughout, we’ll focus on bridging the gap between theory and reality — helping teams measure meaningful differences in user experience.</em></p><h4><strong>The High Cost of Skipping Testing</strong></h4><p>While the gap between what we advocate and what we practice is glaring, neglecting user testing comes at a steep price. Let’s first examine the high cost of skipping this essential step:</p><ul><li>Only 55% of companies conduct any type of online usability testing for their websites [<a href="https://uxeria.com/en/15-statistics-that-will-convince-your-boss-to-invest-in-ux/">1</a>][<a href="https://uxcam.com/blog/ux-statistics/">2</a>].</li><li>Only 23% of UX teams conduct usability benchmarking [<a href="https://www.nngroup.com/articles/quantitative-user-research-methods/">3</a>].</li><li>94% of a user’s first impressions are design-related [<a href="https://uxeria.com/en/15-statistics-that-will-convince-your-boss-to-invest-in-ux/">1</a>].</li></ul><p>Despite the proven ROI of high-impact design changes, the 2022 UserTesting State of UX Report exposes a troubling disconnect: 70% of organizations report increased demand for testing, yet budgets remain unchanged. Moreover, 43% lack processes to base design decisions on user feedback, and 45% fail to integrate user research throughout the product development lifecycle [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>].</p><p>The business impact couldn’t be clearer: teams that integrate user research consistently outperform those that don’t by 2X on critical metrics like retention, conversion, and revenue. UX insights represent one of the biggest available levers for growth, yet they remain chronically underutilized [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>].</p><p>The paradox is striking — we all know testing is valuable, yet we consistently avoid it. This pattern mirrors how we approach other beneficial practices in life — exercise, nutritious eating, adequate sleep — where intellectual understanding rarely translates to consistent action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDHpKf0FPY5LtxvSePoF2A.jpeg" /></figure><h4><strong>Unpacking Our Resistance</strong></h4><p>Even though we know testing is so valuable, we can consistently neglect it — just as we often skip eating our broccoli. So, what holds us back? Let’s now unpack our key barriers of resistance:</p><ul><li><strong>Time &amp; Resource Constraints:</strong> Limited time and budgets force teams to skip testing, leading to costly fixes later [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>]. We never have time to do it right the first time — yet always find time to do it twice.</li><li><strong>Logistical Complexity:</strong> Designing valid scenarios, recruiting participants, analyzing data and presenting results can feel overwhelming — so we never get started.</li><li><strong>Organizational Resistance:</strong> The common assumption that “we already know our users,” combined with lack of buy-in, entrenched processes and fear of change, often leads to sidelining testing.</li><li><strong>Analysis Paralysis:</strong> When testing data reveals problems, teams often freeze — uncertain how to address all issues — problems get backlogged. An IBM study shows that delays from backlogging have an exponential cost impact [<a href="https://www.researchgate.net/figure/BM-System-Science-Institute-Relative-Cost-of-Fixing-Defects_fig1_255965523">5</a>].</li><li><strong>Lack of Preparedness &amp; Support:</strong> Many teams feel under-equipped due to a lack of tools (24%), team collaboration (24%), and research experience (22%), making it difficult to conduct tests and translate findings into actionable insights [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>][<a href="https://www.testingtime.com/en/blog/5-common-challenges-in-uxr-analysis-and-how-to-overcome-them/">6</a>].</li><li><strong>Project Momentum:</strong> The “too late to change now” mentality reflects a sunk cost fallacy that grows as development progresses, further increasing resistance to necessary changes [<a href="https://www.ibm.com/design/thinking/static/Enterprise-Design-Thinking-Report-8ab1e9e1622899654844a5fe1d760ed5.pdf">7</a>].</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B69b5rXvcXPd3LB--vw57w.jpeg" /></figure><p>User testing is disruptive because it challenges groupthink, exposes uncomfortable truths, and demands necessary change before moving forward. The more insightful the discovery, the bigger the change, the more difficult the revelation is to face. Yet avoiding this process only drives up costs, erodes user trust, and results in missed market opportunities.</p><h4><strong>The Practical Challenges of User Testing</strong></h4><p>Even when companies champion user testing, real-world challenges persist. The logistical nuts and bolts of testing cannot be avoided. Let’s examine what it takes to run a basic usability test:</p><p><strong>Testable Product or Prototype</strong></p><p>You need something concrete for users to interact with — either a functioning product version or a realistic prototype that covers the intended workflow. This requires coordination with at least design, possibly development, often both with tight timeline constraints ever looming.</p><p><strong>Clear Success Metrics</strong></p><p>Effective testing begins with a hypothesis and specific success metrics. What exactly are you trying to learn? How will you measure success? You need the test itself — a carefully designed set of tasks or goal that will yield meaningful evidence.</p><p><strong>Testing Infrastructure</strong></p><p>Whether in-person or remote, you need specific tools and materials to conduct and record sessions. Remote testing demands reliable video conferencing, screen recording capabilities, and often specialized software for capturing interactions. The test instructions must be crystal clear, with all necessary supporting materials prepared in advance.</p><p><strong>User Testers</strong></p><p>Finding appropriate test participants consistently ranks as one of testing’s biggest hurdles. You need participants who represent your target users, available during your testing window, that will provide honest, unfiltered feedback. The UserZoom report confirms this challenge, with 34% of researchers citing participant recruitment as their primary obstacle [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>].</p><p><strong>Data Collection and Analysis</strong></p><p>Gathering data is just the beginning. You need systematic methods to organize, analyze, and compare observations, identify meaningful patterns, and distinguish signal from noise. This requires both analytical skill, domain expertise, and time to interpret user behavior correctly.</p><p><strong>Reporting and Comparison</strong></p><p>Findings must become actionable insights, communicated effectively to decision-makers, in a timely fashion. This typically involves creating compelling visualizations and reports that benchmark results against previous iterations or competitor experiences. The best reports transform raw data into clear recommendations.</p><p><strong>Stakeholder Buy-in</strong></p><p>Perhaps most challenging is securing organizational commitment to act on the findings. Without this foundation, even the most rigorous testing becomes an academic exercise. Alarmingly, the State of UX Report found that 43% of organizations lack processes to make decisions based on user feedback [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>].</p><p><strong>Time and Bandwidth</strong></p><p>Orchestrating all these elements demands dedicated focus — a precious resource on most teams. Many organizations struggle with consistent testing because the coordination effort alone becomes overwhelming among competing priorities.</p><p>These list illustrates why, despite its recognized value, testing remains more an aspiration than a reality for many teams. Yet organizations that overcome these challenges gain a significant competitive advantage — consistently delivering products that users genuinely love. The New Research Landscape report found companies with mature user research practices achieve significant improvements in reduced time-to-market (4.3x), increased revenue (4.2x), and improved brand perception (3x) [<a href="https://maze.co/resources/research-maturity-report/">8</a>].</p><h4><strong>The Limits of Surveys and Analytics</strong></h4><p>Even with the clear benefits of user testing, its logistical hurdles remain daunting. Its not surprising that many organizations lean on surveys and analytics as the de facto alternative. Let’s explore why these methods fall short of capturing true user behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8DxGcEF9HuTBEoW35lVv9A.jpeg" /></figure><p><strong>Market Analytics</strong></p><p>Business Intelligence metrics like trial conversion rates, active users, growth rate and churn statistics are frequently used as stand-ins for UX validation. Often leadership substitutes business analytics because of familiarity, and rely on incomplete UX metrics, without actionable insights [<a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">4</a>]. While these metrics are critical for monitoring business health, they represent outcomes rather than causes.</p><p>The fundamental limitation: market metrics tell you <em>that</em> something is happening, not <em>what, why,</em> or <em>how</em> to address it. When conversion rates drop or engagement decreases, these metrics alert you to a problem but provide no insight into what is the source or cause. Without observing actual user behavior, teams are left guessing at solutions relying on assumptions — precisely what user testing and research is designed to eliminate.</p><blockquote>OKRs measure what the company cares about; Experiences what the customer cares about.</blockquote><p><strong>Customer Interviews &amp; Surveys</strong></p><p>Interviews and surveys provide valuable qualitative insights into user opinions, perceptions, and preferences. However, this subjective feedback can fly in the face of actual observed behavior.</p><p>This “Say-Do” gap is well-documented: consumers consistently claim they want to buy sustainable, environmentally friendly products, but their actual purchasing behavior reveals different priorities [<a href="https://www.ipsos.com/en-us/how-beat-say-do-gap-sustainable-products-and-unlock-growth">9</a>]. This pattern plays out in digital experiences — users tell us they value certain features during interviews, but observation often tells a completely different story. This disparity stems from cognitive biases that affect self-reporting:</p><ul><li>Social desirability bias (wanting to please the interviewer)</li><li>Recall bias (inaccurately remembering past interactions)</li><li>Hypothetical bias (inability to predict one’s own future behavior)</li></ul><p><strong>The Missing Evidence</strong></p><p>True user testing — observing and objectively measuring what people do with your product — provides the missing empirical evidence behind what the market indicates and what customers say. While business metrics tell you outcomes and interviews tell you perceptions, only direct observation reveals actual behavior.</p><p>Business metrics and customer interviews are valuable layers of a comprehensive research strategy, with user testing forming the foundation. Only through measured observation can a quantitative baseline of user performance track improvements over time. When we understand the value and limits of each layer, we can appreciate how they all contribute to user-centered design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atlYDo9RZ4pNkVOvWZBN1g.png" /><figcaption><a href="https://www.reddit.com/user/loopdeloop00/">loopdeloop00</a></figcaption></figure><h4><strong>Closing the Gap: Building a Sustainable Process</strong></h4><p>Despite its proven benefits, user testing remains more occasional than continuous. Psychological, organizational, and logistical hurdles create a perfect storm that forces organizations to rely on an incomplete view. This isn’t merely about dollars; it’s about preventing the erosion of user trust and stifling innovation. The data is clear: organizations that overcome these barriers and implement systematic user testing gain substantial competitive advantages — faster time-to-market, increased revenue, and stronger customer loyalty. The real question isn’t whether testing matters, but how to integrate it practically and consistently within real-world constraints. User testing is essential, and we can’t afford to sideline it any longer.</p><p><strong>Where Are You?</strong></p><p>While testing may seem disruptive in the short term, the true disruption comes from launching products that users won’t or can’t use — a far more expensive misstep. Consider these questions:</p><ul><li>Are you avoiding user testing entirely?</li><li>Relying solely on market metrics and surveys?</li><li>Testing only occasionally, with inconsistent results?</li></ul><p><strong>Practical Next Steps</strong></p><p>The disconnects we’ve explored reveal a clear path forward. By understanding why consistent testing is so challenging, we can develop targeted strategies to overcome each barrier. In Part 2 of this series, I’ll share my lean, pragmatic approach to continuous testing — demonstrating how teams of any size can integrate user testing into their workflow without disrupting timelines or exhausting resources. Get ready for a set of practical steps that deliver the insights you need, without the overwhelming overhead.</p><p><strong>References</strong></p><p>[1] <a href="https://uxeria.com/en/15-statistics-that-will-convince-your-boss-to-invest-in-ux/">https://uxeria.com/en/15-statistics-that-will-convince-your-boss-to-invest-in-ux/</a></p><p>[2] <a href="https://uxcam.com/blog/ux-statistics/">https://uxcam.com/blog/ux-statistics/</a></p><p>[3] <a href="https://www.nngroup.com/articles/quantitative-user-research-methods/">https://www.nngroup.com/articles/quantitative-user-research-methods/</a></p><p>[4] <a href="https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf">https://www.usertesting.com/sites/default/files/2023-08/The%20State%20of%20UX%202022.pdf</a></p><p>[5] <a href="https://www.researchgate.net/figure/BM-System-Science-Institute-Relative-Cost-of-Fixing-Defects_fig1_255965523">https://www.researchgate.net/figure/BM-System-Science-Institute-Relative-Cost-of-Fixing-Defects_fig1_255965523</a></p><p>[6] <a href="https://www.testingtime.com/en/blog/5-common-challenges-in-uxr-analysis-and-how-to-overcome-them/">https://www.testingtime.com/en/blog/5-common-challenges-in-uxr-analysis-and-how-to-overcome-them/</a></p><p>[7] <a href="https://www.ibm.com/design/thinking/static/Enterprise-Design-Thinking-Report-8ab1e9e1622899654844a5fe1d760ed5.pdf">https://www.ibm.com/design/thinking/static/Enterprise-Design-Thinking-Report-8ab1e9e1622899654844a5fe1d760ed5.pdf</a></p><p>[8] <a href="https://maze.co/resources/research-maturity-report/">https://maze.co/resources/research-maturity-report/</a></p><p>[9] <a href="https://www.ipsos.com/en-us/how-beat-say-do-gap-sustainable-products-and-unlock-growth">https://www.ipsos.com/en-us/how-beat-say-do-gap-sustainable-products-and-unlock-growth</a></p><p>[10] <a href="https://www.reddit.com/user/loopdeloop00/">https://www.reddit.com/user/loopdeloop00/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dad0a8633d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Made Complex Software 21X Easier to Use]]></title>
            <link>https://medium.com/@uxflo/how-we-made-complex-software-21x-easier-to-use-0df0a7fd8375?source=rss-8c5bfb36f9f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0df0a7fd8375</guid>
            <category><![CDATA[ux-metrics]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[qt]]></category>
            <dc:creator><![CDATA[Gray Holland ]]></dc:creator>
            <pubDate>Fri, 14 Feb 2025 15:41:06 GMT</pubDate>
            <atom:updated>2025-03-05T15:25:09.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPbYYQu_pmMFdX5S13CksQ.png" /></figure><h4>Part 4 in a Series where I ask the questions “How do we <strong>Measure the Difference of UX</strong>? How do we compare our new designs with the old?”</h4><p><em>Throughout this series, we’ve explored the challenge of measuring user experience improvements objectively. We’ve looked at </em><a href="https://medium.com/@uxflo/the-uncomfortable-truth-about-ux-testing-9dad0a8633d2"><em>why teams often skip testing</em></a><em>, examined methods and available tools, and introduced new approaches to UX measurement. Now, let’s see how these principles work in practice with a real-world transformation that delivered dramatic, measurable results.</em></p><h3><strong>Cutting Through Complexity: Arcturus Case Study</strong></h3><p>For startups, every customer counts. When user adoption and active engagement are essential, every lost user represents missed growth and potential funding. A streamlined, intuitive user experience isn’t just nice to have — it’s mission-critical.</p><p>For Arcturus, a startup pioneering streaming volumetric video, this challenge manifested in their core processing tool, HoloEdit. It was highly capable but technically demanding, with frequent user errors in process setup and configuration. Despite being the industry’s most powerful processing tool, it created a barrier to customer acquisition and retention.</p><p>This case study examines how <a href="https://ux-flo.com/">UX-FLO</a> distilled that complexity into clarity through a metrics-driven redesign. The transformation delivered measurable results: a 21X reduction in workflow effort and the complete elimination of user errors. By objectively validating these improvements — from initial design to final implementation — we empowered Arcturus to confidently invest in its transformation.</p><h3><strong>The Technology Trap: The HoloEdit Challenge</strong></h3><p>Technology development at the cutting edge often creates a familiar problem: interfaces designed by the same engineers and mathematicians developing the underlying algorithms. The result prioritizes technical capability over user experience, and volumetric video processing at Arcturus was no exception.</p><p>HoloEdit’s “job to be done” is deceptively simple — process raw volumetric captures into streamable content. However, achieving this requires a precise sequence of processing stages, each performing specific algorithmic functions to clean, reorganize, and compress data. The challenge isn’t just the complexity of individual stages, but their interdependency. One stage out of order can cause the entire process to fail. Users faced a daunting cognitive load, needing to understand not just what each stage did, but how stages interacted and their precise ordering requirements. Even with comprehensive documentation, both newcomers and experts struggled with these technical setup workflows.</p><h4><strong>Better Training or Better Design?</strong></h4><p>For Arcturus, this technical friction was directly impacting growth. Complex workflows and heavy cognitive loads had become barriers to customer acquisition and retention, particularly affecting trial users attempting to evaluate HoloEdit’s capabilities. Despite having the industry’s most powerful processing engine for volumetric, they were losing potential customers during evaluation.</p><p>The solution required more than additional training or documentation. It demanded a fundamental reimagining of how users interact with powerful processing capabilities. The challenge was clear: create an intuitive interface that reduced errors and accelerated adoption, while preserving HoloEdit’s advanced functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*45UdwK8ElzRnfx4yGJXCew.jpeg" /></figure><h3><strong>Design: The JumpStart Concept</strong></h3><p>JumpStart emerged as a practical solution to HoloEdit’s complex workflow challenge. By breaking the process into three clear modes — Import, Processing, and Export — we guided users through each phase while automating routine setups. This approach minimized cognitive load and potential errors while keeping users informed and in control of critical decisions.</p><p>End-to-End UX testing played a crucial role in validating the design. Using Figma mockups, we compared the JumpStart concept against the existing 2022 interface, engaging both internal stakeholders and external customers. This dual perspective balanced technical expertise with real-world usage patterns, revealing important gaps between internal and customer knowledge / expectations.</p><h4><strong>Focus on What They Do</strong></h4><p>DCipher provided objective measurement of the concept’s effectiveness. We created structured testing scenarios with clear instructions, concept introduction, and standardized datasets. Users completed identical outcomes in both the 2022 HoloEdit interface and the JumpStart Figma prototype. DCipher recorded all user interactions, generating comparative metrics and visual Flowmaps of each experience.</p><p>The results validated our approach: JumpStart achieved a 10X reduction in workflow effort and 12X increase in processing speed, while significantly reducing user errors. DCipher’s side-by-side Flowmap comparisons visually demonstrated how users navigated more efficiently and effectively through the new interface. These visualizations also highlighted remaining friction points, guiding further refinements on the new concept.</p><p>While JumpStart proved transformative for both new and expert users, implementing the full redesign in one release cycle wasn’t feasible. The next challenge became identifying which new components would deliver the most immediate value to customers while laying groundwork for future enhancements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a32eNxcfAfNgU4Gc49LWHQ.gif" /><figcaption>Accelerated demonstration — approximately <strong>two seconds</strong> equal <strong>one minute</strong>.</figcaption></figure><h3><strong>Develop: Implementing the Preset System</strong></h3><p>The Preset system emerged as JumpStart’s most valuable and foundational component, offering immediate impact as a standalone feature. At its core, Presets automate complex stage configurations to match predefined outcomes. Operating at two levels — Stage Presets control individual processing parameters, while Track Presets manage entire ordered stacks of stages — users can now configure complete processing workflows with a single click.</p><p>This approach effectively captures expert knowledge within the product. Instead of manually configuring multiple parameters, users select pre-configured options based on their specific desired outcomes. Whether optimizing for low-bandwidth 5G mobile streaming or high-resolution VFX pre-viz, the appropriate configuration is just one click away. These “Factory” Presets evolve with each release, while allowing customers to save and manage their own local Preset configurations as well.</p><p>The UI implementation focused on the Timeline’s Composition panel, requiring a complete rethink of Track and Stage layer management. The challenge was integrating these new Preset UI capabilities without disrupting familiar interface that users depended on.</p><h4><strong>Designer in the DEV Loop</strong></h4><p>Limiting implementation changes to a single panel created flexibility challenges. New UI components needed enhanced capabilities while maintaining visual consistency with the legacy interface. Our solution was “Retro-Style” design system — custom Qt-based components that matched the existing Qt Quick visuals, yet incorporated a new MVVM design structure. This approach enabled seamless integration of new functionality within the established look and feel while laying the groundwork for future UI vision.</p><p>Follow-up testing with stakeholders compared the new v2023 production software against the 2022 version. Despite the compressed release cycle and small test group, results exceeded expectations: a 21X reduction in workflow effort, 10X increase in processing speed, and complete elimination of user errors. DCipher’s Flowmap visualizations provided clear validation of these improvements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mm95mqE8m9MpzbrzueoKtw.jpeg" /></figure><h3><strong>Results with Impact</strong></h3><p>The Preset system implementation delivered clear, measurable results — dramatically streamlining onboarding for new users while empowering experts with intuitive, outcome-based controls. Presets serve as learning examples with built-in safety nets, encouraging Stage setup exploration without risk. DCipher’s instruments measured order-of-magnitude reductions in speed and effort, along with the complete elimination of user errors. Most importantly, we achieved this without compromising HoloEdit’s powerful capabilities. More than another UI update, JumpStart Presets represents a fundamental shift in how users interact with complex technical software.</p><p>The system continues to evolve, capturing new expert knowledge with Preset updates, growing smarter with each release. Plus this success lays the foundation for broader improvements:</p><ul><li>Extending the Preset approach into Import and Export areas</li><li>Implementing JumpStart’s three-mode guided structure</li><li>Gradually replacing legacy components with MVVM-based alternatives following our “Retro-Style” strategy</li></ul><p>The MVVM design system’s inherent flexibility enables rapid adaptation. This methodical replacement approach maintains UI familiarity while modernizing components, building toward a comprehensive interface refresh.</p><p>The Arcturus project demonstrates a key principle: objective measurement throughout the product cycle — from initial design through final implementation — enables confident, data-driven UX decisions. When you can <strong>measure the difference</strong>, you can make a difference.</p><p>I’d love to hear about your experiences with complex interfaces, user testing, and validation methods. How do you measure UX improvements in your projects? Connect with me to continue the conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0df0a7fd8375" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>