Simplifying Complex Interfaces

🔎 How To Redesign Complex Navigation: How We Restructured Intercom’s IA (https://lnkd.in/ezbHUYyU), a practical case study on how the Intercom team fixed the maze of features, settings, workflows and navigation labels. Neatly put together by Pranava Tandra. 🚫 Customers can’t use features they can’t discover. ✅ Simplifying is about bringing order to complexity. ✅ First, map out the flow of customers and their needs. ✅ Study how people navigate and where they get stuck. ✅ Spot recurring friction points that resonate across tasks. 🚫 Don’t group features based on how they are built. ✅ Group features based on how users think and work. ✅ Bring similar things together (e.g. Help, Knowledge). ✅ Establish dedicated hubs for key parts of the product. ✅ Relocate low-priority features to workflows/settings. 🤔 People don’t use products in predictable ways. 🤔 Users often struggle with cryptic icons and labels. ✅ Show labels in a collapsible nav drawer, not on hover. ✅ Use content testing to track if users understand icons. ✅ Allow users to pin/unpin items in their navigation drawer. One of the helpful ways to prioritize sections in navigation is by layering customer journeys on top of each other to identify most frequent areas of use. The busy “hubs” of user interactions typically require faster and easier access across the product. Instead of using AI or designer’s mental model to reorganize navigation, invite users and run a card sorting session with them. People are usually not very good at naming things, but very good at grouping and organizing them. And once you have a new navigation, test and refine it with tree testing. As Pranava writes, real people don’t use products in perfectly predictable ways. They come in with an infinite variety of needs, assumptions, and goals. Our job is to address friction points for their realities — by reducing confusion and maximizing clarity. Good IA work and UX research can do just that. [Useful resources in the comments ↓] #ux #IA

📱 Mastering Complexity in UX: Lessons from a Book Tracking App Today, I want to share a brilliant example of managing complexity in user interface design. This book-tracking app demonstrates how to present rich functionality without overwhelming users. Key takeaways: - Information Hierarchy: Organize content by importance. Here, user profile and reading progress take centre stage. - Progressive Disclosure: Hide advanced features until needed. "Adjust goal" is available but not intrusive. - Visual Cohesion: A consistent dark theme keeps the interface clean despite dense information. - Functional Grouping: Distinct sections for progress, streaks, and book lists create logical flow. - Glanceable Data: The circular progress bar instantly communicates daily reading status. - Efficient List Design: Book history shows essential info without clutter. The result? An interface that's: - Information-rich yet uncluttered - Accessible for casual users, deep enough for power users - Intuitive for basic tasks, with room for advanced features This exemplifies how thoughtful design can make complex systems feel effortlessly simple. What's your favourite example of well-managed complexity in design? Share below! #UXDesign #UserExperience #DesignThinking

*Simplify your product design — borrow familiar patterns* Last week I wrote that simplicity is a competitive advantage. But what does it mean for a product to be simple? Simple products are immediately familiar and usable. When I pick up a knife or a cup, I never have to think to myself, “how do I use this?”. That sense of familiarity is what we wanted for WhatsApp too. We wanted to make sure our users wouldn’t feel like they needed to learn how to use the app, but could just start calling and messaging. We had to ask ourselves — what will make this product familiar to billions of very different people around the world? Well, the only thing we really knew about all those potential users is that they had a phone. So we matched the patterns of the phone’s operating system, because we knew the user would know them. If Android normally had an floating action button in the bottom right, that’s where WhatsApp would put its button. This meant WhatsApp would feel familiar even if you've never actually used the app before. We also used consistent patterns throughout the app. I’m not talking about anything fancy — just things like “triangle button = you’re going to send a message; arrow = not going to send yet.” That consistency quickly built a sense of predictability and control for users. Of course, this was really limiting in lots of ways! There were lots of interesting interaction patterns that we couldn’t use because they weren’t already intuitive to all our users. The question I always asked was “where would the user naturally put their thumb? Put the button there.” If you’re watching a Hotjar recording, you can see where someone pulls their mouse, or where someone’s eyes track in qualitative research. Users are telling us where they expect to find something — put the button there! For another industry example of how familiar patterns make hard things feel easy, think about all the new genAI chat bots. This is wildly complicated frontier technology. How is it possible that hundreds of millions of consumers could pick it up overnight? Because even though these AI systems are built on complex foundations, they borrow a messaging interface that we’ve all been using for decades. That familiar interface means that everyone can use this amazing tech without needing to learn anything new. One shortcut I always think of when designing a new product is: what other apps or physical products are my users likely to be using? Are there any patterns I can borrow from those to make a new product automatically intuitive? If a user normally swipes right to dismiss notifications, can swiping right dismiss new alerts inside my product instead of making the user find an “x” to tap on? Making these small gestures familiar can add up to making a whole product feel more simple and intuitive, instead of like yet another new thing to learn. (For regular updates in this ongoing series about product, leadership, and scaling, subscribe to amivora.substack.com!)

Our app was in English. Our customers spoke English. But when I spent time in the field, I realized we weren’t speaking the same English. The English in our app was formal. Technical. Institutional. So we simplified. By aligning language to lived reality. ❌ “Transaction failed” ✅ “Payment didn’t go through” ❌ “Retry” ✅ “Try again” ❌ “Verify your identity” ✅ “Confirm it’s really you” ❌ “Authentication required” ✅ “Please sign in” Small changes. Meaningful difference. Less cognitive effort. Fewer clarifying questions in the field. A more human product experience. What I learned: #inclusive #design isn’t just about supporting multiple languages. It’s about writing in the language people actually think in. Conversational fluency ≠ comfort with technical English. If users have to mentally translate your interface into something familiar, you’ve already introduced friction. Now when I review customer-facing content, I ask: “Is this how a real person would say it?” If not, we rewrite it.  #InclusiveDesign #CustomerExperience #Communication Adeniyi Fagbemi Alvin Mwendia Karla Silvas Abraham Inyaka Antonio Dominguez Andy Holloway Steven Peirce Marc Talary Simon Vane

Is your digital experience simple to use and easy to navigate, or does it add to patients' stress and anxiety? If you can’t recall the last time you tested it with real patients, you might be surprised by the outcome. Recently, I highlighted three core qualities patients value in digital healthcare experiences: Impact, Simplicity, and Confidence – measured by our Patient Experience (PX) Scale. Now, let's take a deeper dive into SIMPLICITY and how creating easy-to-use digital healthcare experiences can reduce stress and help patients navigate the complexities of healthcare. SIMPLICITY is measured using the following patient-centric criteria: 𝟭. 𝗡𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 𝟮. 𝗘𝗮𝘀𝗲 𝗼𝗳 𝗨𝘀𝗲 𝟯. 𝗚𝘂𝗶𝗱𝗮𝗻𝗰𝗲 𝟰. 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 So, how can we design digital experiences that avoid overwhelming patients and ensure effective outcomes? Here are some actionable tips: → Improve Information Scent Use card sorting and tree testing with real patients to organize content in a way that aligns with their journeys and terminology. → Reduce Interaction Cost Minimize the number of clicks (or taps on mobile) required to access essential information or complete tasks. → Don’t Make Them Think Create intuitive and self-explanatory interfaces that are intuitive and don’t require extra effort. → Use Familiar Patterns Stick to familiar and widely used patterns and avoid asking users to learn something new. → Offer Live Support Option Provide easy access to human support when needed, including clear hours of availability. → Offer Additional Resources Provide explainer videos, FAQs, tooltips, or guides for those who need extra help but still prefer self-service. → Use Plain Language Avoid medical jargon, technical terms, or complex phrasing. If jargon is necessary, provide simple explanations and relevant context. → Incorporate Visual Aids Diagrams and images can help convey complex information and improve recall. Simplicity is essential for all patients. As healthcare UX professionals, it’s our responsibility to create effortless digital experiences for real humans from all walks of life. To evaluate and enhance your digital patient experience for simplicity (and beyond), download the open-access framework: Patient Experience (PX) Scale toolkit (linked in comments.)

Creating a simple dashboard is one of the most complex tasks. Most developers focus on simplifying the interface. Although this is notable, it is not the right place to start. The priority should be user research and deeply understanding the needs. Before starting development, you have to know: • Their habits and hesitations • Their daily challenges • Their environment • Their context... Using a template like the Empathy Map can be very helpful in these situations. It always helps me to ask questions to humans, not users. And I think this is key. You'll find incredible information when you talk to people with empathy. Here are some examples of questions I ask during my interviews: • Which chart or dashboard have confused you in the past? • What context would make data-driven decisions easier for you? • What outcome or feeling do you seek from using a great dashboard? • Can you share a good or bad experience with a dashboard? What caused it? To achieve simplicity, you must face chaos such as: • Extreme users • Tough debates • Attempt to discredit data • Attempt to discredit the tool or process • Disagreements during workshops But at the end, I'm convinced this is the only way to reach true simplicity. By exposing yourself to complexity intentionally (with a framework), it becomes easier to create the simplest solution. Trust yourself. Keep asking questions... Until it clicks. Think about it today and start developing the skill I've developed the last 10 years by using Design methods in Data Visualization with my free newsletter: Join 5000+ Data Professionals here : https://lnkd.in/evwikjCE+Vautier&utm_campaign=publer #dataanalytics #datavisualization #businessintelligence

The Beauty of Simplicity: What the Super Bowl Score Bug Teaches Us About Great Design 🎨 🏈 If you watched the Super Bowl last night, you may have noticed something different on your screen: Fox Corporation and FOX Sports debuted a new minimalist score bug—and I have to say, I’m a fan. Traditionally, score bugs in sports broadcasts try to do too much at once. They cram in scores, time, down and distance, possession indicators, play clocks, timeouts, and more—all at the same time. It’s information overload. But this new design? It showed the right information at the right time. When a flag was thrown, the graphic adapted. When the down and distance changed, the display shifted seamlessly. No clutter. No distractions. Just what the viewer needed, exactly when they needed it. And that’s the mark of great design. 🎯 Apple Gets It—And More Industries Should Too 🍏 Apple mastered this approach. The iPhone, Mac, and Apple Watch succeed because their interfaces strip away complexity, making every interaction feel effortless. When you pick up an iPhone, there’s no manual needed—it just makes sense. Every design decision reduces cognitive load, ensuring clarity and ease of use. From slide-to-unlock to the Apple Watch’s Glanceable UI, Apple’s best innovations mirror what we saw in last night’s game: remove the unnecessary, emphasize the essential. What Businesses Can Learn from This Whether you’re designing a new app, improving a restaurant ordering system, or even refining how you communicate information to your team, less is often more. Clarity wins over complexity. A well-designed UI—whether digital or operational—reduces friction, improves engagement, and enhances the overall experience. ✨ This same principle drives our work at Wendy’s. With FreshAI, our goal isn’t just adding AI—it’s making ordering feel effortless, keeping things simple for customers and crew alike. So next time you’re designing something—whether it’s a piece of software, a customer experience, or even a PowerPoint presentation—ask yourself: 🔹 Am I giving people the right information at the right time? 🔹 Is there anything I can remove to make this clearer? 🔹 Does this make the experience feel seamless and intuitive? That’s the power of thoughtful, minimalist design. The Super Bowl’s new score bug is just one small example, but it’s a reminder that good design isn’t about how much you can show—it’s about how well you can show what matters most. What’s a great example of minimalist design that you love? Let me know in the comments! 👇 #design #simplicity #UX #innovation #Apple #SuperBowl #UserExperience

EV charging networks. Building energy management systems. Smart grids. Brilliant climate solutions are failing. Not because they don’t work—but because the end users are an afterthought. Here are 5 smart design principles that turn complex climate tech into tools people actually use. 1. Simplify the complex Look at carbon reporting dashboards – the good ones don't drown procurement teams in emission factors. They make it clear: here are your top emission sources, and here's what to tackle first. Suddenly, action feels possible (with detailed analytics a click away). 2.Keep it consistent Facility managers juggle desktop monitoring, mobile alerts, and on-site controls for energy systems. When the interface stays identical everywhere — same terms, same buttons, same flow — your adoption soars. Nobody has time to learn three systems. 3.Design for your entire ecosystem The best sustainability platforms work for both the ESG director and the data entry clerk. They can connect different workflows without forcing everyone to wade through features they'll never use. 4.Make troubleshooting obvious When a factory's energy optimization system flags an issue, error codes aren't enough. Clear next steps make all the difference: "Compressor 3 is running inefficiently. Check: 1) Air pressure settings 2) Filter status." 5.Show impact clearly Monthly sustainability reports shouldn't need a PhD. The most effective ones translate complex metrics into business impact, making it easier for decision-makers to see the return on their investment: "Process changes reduced Scope 1 emissions by 175 tonnes CO2e this quarter, putting you at 68% of the 2024 reduction target." Great design isn't just about making climate tech look good — it's about making it work in the real world, where time is short and stakes are high. What challenges have you faced in making sustainability tools more user-friendly? -- I run a design agency to scale climate impact by building trust-worthy brands and seamless user experiences. Reach out to know how we can help!

𝐀𝐟𝐭𝐞𝐫 𝐟𝐚𝐢𝐥𝐢𝐧𝐠 10+ 𝐇𝐋𝐃 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬 𝐭𝐡𝐢𝐬 𝐢𝐬 𝐭𝐡𝐞 𝐨𝐧𝐞 𝐭𝐡𝐢𝐧𝐠 𝐭𝐡𝐚𝐭 𝐈 𝐡𝐚𝐯𝐞 𝐫𝐞𝐚𝐥𝐢𝐬𝐞𝐝. 𝐌𝐨𝐬𝐭 𝐨𝐟 𝐭𝐡𝐞 𝐜𝐨𝐦𝐩𝐥𝐞𝐱-𝐬𝐨𝐮𝐧𝐝𝐢𝐧𝐠 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐡𝐚𝐯𝐞 𝐭𝐡𝐞 𝐬𝐢𝐦𝐩𝐥𝐞𝐬𝐭 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐩𝐨𝐬𝐬𝐢𝐛𝐥𝐞. The reason is simple. 𝐈, 𝐥𝐢𝐤𝐞 𝐦𝐨𝐬𝐭 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬, 𝐰𝐚𝐬 𝐨𝐯𝐞𝐫𝐜𝐨𝐦𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐧𝐠 𝐞𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠. In interviews, when they asked me to design a chat application, I would jump straight into microservices, event sourcing, and complex architectures. I thought complexity would impress them. But here's what I learned the hard way - the best engineers start simple and scale up, not the other way around. Take WhatsApp. At its core, it's just message storage and delivery. The magic isn't in the complexity - it's in solving the right problems at the right time. During my recent interview, when asked to design a URL shortener, I started with a simple hash function and a database. Then I gradually added caching, load balancing, and analytics only when asked about scale. The interviewer loved it. Start with the simplest solution that works. Add complexity only when you can justify why it's needed. That's why simple designs win. Because deep down, we all know that if you can't explain it simply, you don't understand it well enough. What do you think? Have you also fallen into the overengineering trap? hashtag #SystemDesign #TechInterviews #SoftwareEngineering #KISS #TechCareers

Complex Apps Demand Smarter UX Healthcare, finance, logistics- expert users High stakes. Nonlinear workflows Normal UX won’t cut it You need to design for the work, not just the user The Design Lifecycle: 3 Phases to Guide Complex UX 1️⃣ Understand: Research the work, not just the user 2️⃣ Explore: Prototype within real-world constraints 3️⃣ Materialize: Test and refine in realistic environments Understand Phase: Research the Work, Not Just the User Expert users operate in layered, high-stakes systems. ✅ Immerse in their environment ✅ Learn domain rules, jargon, and workflows ✅ Include multiple roles for a full picture Understand Strategies: 1️⃣ Study the domain independently 2️⃣ Observe work in context 3️⃣ Triangulate insights across roles and methods Explore Phase: Generate Ideas Within Real Constraints Complex systems have rules, integrations, and safety concerns. ✅ Ideate with constraints in mind ✅ Prototype at the right fidelity ✅ Co-create with domain experts Explore Strategies: 1️⃣ Frame ideation around feasibility and regulations 2️⃣ Use low-fidelity prototypes for early testing 3️⃣ Collaborate with experts to validate solutions Materialize Phase: Test and Refine in the Real World Expert workflows are complex and variable ✅ Adapt evaluation methods to reveal reasoning, not just task success ✅ Bring domain experts into testing ✅ Break traditional rules when needed to gather feedback Materialize Strategies: 1️⃣ Scenario-based testing for real-world decisions 2️⃣ Workshops and informal reviews with experts 3️⃣ Pragmatic early testing using knowledgeable internal staff Key Takeaways: Designing for complex domains requires: ✅ Research grounded in real work ✅ Idea generation within meaningful constraints ✅ Evaluation methods tailored to expert reasoning ✅ Collaboration with domain experts at every step Complex UX Isn’t New UX- It’s Smarter UX Adapt your familiar methods thoughtfully, and your designs will support expert users in high-stakes environments 👇 Comment: Which complex domain have you designed for?