User Experience for Non-Technical Users

👩🦰 Designing Accessibility Personas (https://lnkd.in/evVnB4hd). How to embed accessibility and test for it early in the design process ↓ We often assume that digital products are merely that — products. They either work or don’t work. That they help people meet their needs or fail on their path to get there. But every product has its own embedded personality. It can be helpful or dull, fragile or reliable, supportive or misleading. When we design it, willingly or unwillingly, we embed our values, views and perspectives into it. Sometimes it’s meticulously shaped and refined. And sometimes it’s simply random. And when that happens, users assign their perception of the product’s personality to the product instead. Products are rarely accessible by accident. There must be an intent that captures and drives accessibility efforts in a product. And the best way to do that is by involving people with temporary, situational and permanent disabilities into the design process. One simple way of achieving that is by inviting people with disabilities in the design process. For that, we could recruit people via tools like Access Works or UserTesting, ask admins of groups and channels on accessibility to help, or drop an email to non-profits that work in accessibility space. Another way is establishing accessibility personas for user journeys. Consider them as user profiles that highlight common barriers faced by people with particular conditions and provide guidelines for designers and engineers on how to design and build for them. E.g. Simone, a dyslexic user, or Chris, a user with rheumatoid arthritis. For each, we document known challenges and notable considerations, designing training tasks for designers and developers and instructions to simulate experience through the lens of these personas. By no means does it replace proper accessibility testing, but it creates a shared understanding about what the experiences are like. You can build on top of Gov.uk’s profound research project (https://lnkd.in/evVnB4hd) — it also explains how to set up devices and browsers, so that each persona has their own browser profile. Once you do, you can always switch between them and simulate an experience, without changing settings every single time. All Accessibility Personas (+ Tasks, Research, Setup) https://lnkd.in/evVnB4hd Accessibility doesn’t have to be challenging if it’s considered early. No digital product is neutral. Accessibility is a deliberate decision, and a commitment. Not only does it help everyone; it also shows what a company believes in and values. And once you do have a commitment, and it will be much easier to retain accessibility, rather than adding it last minute as a crutch — because that’s where it’s way too late to do it right, and way too expensive to make it well. [Useful pointers in the comments ↓] #ux #accessibility

Most AI ideas die before they even get off the ground. Why? Because teams get stuck in endless debates instead of building something tangible. The best way to get leadership buy-in, align teams, and validate your AI concept? Prototyping. But here’s the secret—you don’t need to code to prototype AI effectively. Instead of diving into AI coding tools like Cursor or Replit, you can use no-code AI prototyping tools like Notion AI, UX Pilot, CustomGPTs, and Voiceflow to move even faster. In our latest AI Community Learning Series, Polly M Allen (Ex-Principal PM, Alexa AI) and Rupa Chaturvedi (AI UX Leader, ex-Amazon, Google, Uber) shared how to: ✅ Align teams faster with interactive AI prototypes (instead of lengthy PRDs) ✅ Use no-code tools to build AI-powered experiences—without writing a single line of code ✅ Pick the right AI use cases and avoid overcomplicating solutions Plus, they demoed how to build a Shopping AI Assistant live—showing exactly how to structure, test, and refine AI interactions in minutes. Curious how they did it? Full recap + session replay 👇 Have you built an AI prototype before? What worked (or didn’t)? Share your thoughts below! #ProductManagement #AI #Design #Prototyping

While auditing content for an Entrepreneurship course at UNSW Arts, Design & Architecture I discovered a secret. The secret to enhanced user-centric innovation: We often get "stuck" with what we're taught, and this sometimes affects how we think. We all learn about Design Thinking as a standalone tool, but there's MUCH MORE to it. Integrating Design Thinking, Lean UX, and Agile methodologies creates a powerful framework for driving user-centric innovation. Here's how it works: → Design Thinking: for deep empathy and problem definition → Lean UX: for rapid prototyping and validation → Agile: for iterative development and delivery ... And what happens when each is missing? • Without Design Thinking = "Misunderstanding" • Without Lean UX = "Wasted Effort" • Without Agile = "Stagnation" Combining these methodologies offers a holistic approach. Concept Exploration + Iterative Experimentation = Needs-and-Pain-point Discovery The initial stages emphasize brainstorming and prioritizing insights, leading to hypothesis formation that guides subsequent experiments. Continuous experimentation allows for the revision of hypotheses based on real user feedback, creating a dynamic loop of learning and adaptation. Here's how to integrate them: 1/ Design Thinking: Start with empathy. Understand your users deeply before defining the problem. 2/ Lean UX: Prototype quickly. Validate your ideas with real users early and often. 3/ Agile: Iterate. Develop in short cycles and adapt based on feedback. As teams build and explore new ideas, they foster collaboration across disciplines, leveraging diverse perspectives to refine solutions. This integrated framework not only enhances the customer experience but also drives sustainable growth. This helps founders ensure they remain competitive and relevant in their respective industries. George Dr. Kelsey Burton Yenni 👀 LESSGO!

Imagine this: you’re filling out a survey and come across a question instructing you to answer 1 for Yes and 0 for No. As if that wasn't bad enough, the instructions are at the top of the page, and when you scroll to answer some of the questions, you’ve lost sight of what 1 and 0 means. Why is this an accessibility fail? Memory Burden: Not everyone can remember instructions after scrolling, especially those with cognitive disabilities or short-term memory challenges. Screen Readers: For people using assistive technologies, the separation between the instructions and the input field creates confusion. By the time they navigate to the input, the context might be lost. Universal Design: It’s frustrating and time-consuming to repeatedly scroll up and down to confirm what the numbers mean. You can improve this type of survey by: 1. Placing clear labels next to each input (e.g., "1 = Yes, 0 = No"). 2. Better yet, use intuitive design and replace numbers with a combo box or radio buttons labeled "Yes" and "No." 3. Group the questions by topic. 4. Use headers and field groups to break them up for screen reader users. 5. Only display five or six at a time so people don't get overwhelmed and bail out. 6. Ensure instructions remain visible or are repeated near the question for easy reference. Accessibility isn’t just a "nice to have." It’s critical to ensure everyone can participate. Don’t let bad design create barriers and invalidate your survey results. Alt: A screen shot of a survey containing numerous questions with an instructing you to answer 1 for Yes and 0 for No. The instruction is written at the top and it gets lost when you scroll down to answer other questions. #AccessibilityFailFriday #AccessibilityMatters #InclusiveDesign #UXBestPractices #DigitalAccessibility

🚫 Not every problem needs a tech solution. Came across this 𝘣𝘳𝘪𝘭𝘭𝘪𝘢𝘯𝘵𝘭𝘺 𝘴𝘪𝘮𝘱𝘭𝘦 fix in a largely manual, paper-heavy environment in an organisation still finding its feet with digital transformation. Without touching the existing process, this small tweak made file clearances faster and helped set up a priority queue. No tech, no tools — just thoughtful design. Sometimes, the best solutions don’t come from coding or automation, but from truly observing people, their challenges, and the context they operate in. 🔍 Design thinking at its core is: Understand the user, observe the environment, and solve for them in the most efficient way possible. Have you come across a low-tech or no-tech solution that made a big impact? I would love to hear about it. #DesignThinking #ProblemSolving #Innovation #ProcessImprovement #NoCode #UserCentricDesign

Question: If you had a bad experience with a company or product, would you buy from them again? The answer is "no" right? For disabled people, 75-80% of customer experiences are failures. That means that 75-80% of transactions for our community aren't repeated. That's pretty bad right? The impact of a negative experience resonates far beyond a single transaction. It can influence a customer's decision-making process and brand loyalty for the long term. In striving for improvement, businesses must recognise the importance of inclusivity and accessibility. By investing in accessible design, empathetic customer service, and continuous feedback loops, we can create an environment where every customer feels valued and understood. Here are some actionable steps to enhance the customer experience for everyone: * Prioritise accessibility: Ensure your physical and digital spaces are accessible to disabled people. This includes wheelchair ramps, accessible websites, and accommodating customer service practices. * Educate your team: Educate your staff to the diverse needs of customers. Training programmes that emphasise empathy and understanding can go a long way in fostering a positive and inclusive customer experience. * Feedback mechanisms: Establish channels for customers to provide feedback easily. Actively seek input from disabled people to understand our unique challenges and implement necessary improvements. * Adopt universal design: From product packaging to online interfaces, adopt a design philosophy that considers the diverse needs of all customers. Universal design benefits everyone and creates a more positive overall experience. * Transparent communication: Be transparent about your commitment to inclusivity. Communicate the steps you are taking to improve accessibility, both internally and externally. This fosters trust and demonstrates your dedication to positive customer experiences. Remember, creating a truly inclusive business environment not only improves the lives of disabled people but also enhances the overall customer experience for everyone. It's a win-win strategy that builds lasting connections and fosters brand loyalty. #InclusiveBusiness #CustomerExperience #AccessibilityMatters

Lyft knew they had a problem. Only 5.6% of its users are over 65, and those users are 57% more likely to miss the ride they ordered. So, Lyft created Silver – a special app version for seniors. But why create a separate app when these improvements would benefit all users? The curb-cut effect is real. Features designed for wheelchair users ended up helping parents with strollers, travelers with luggage, and delivery workers with carts. The features in Lyft's senior-friendly app wouldn't only benefit older riders: 💡The 1.4x larger font option? Great for bright sunlight, rough rides. 💡Simplified interface? Less cognitive load for all of us. 💡Live help operators? Great for anyone when there's a problem. 💡Select preference for easy entry/exit vehicles? Not everyone likes pickup trucks. What started as an accommodation should became a universal improvement. The most powerful insight? Designing for seniors forced Lyft to prioritize what truly matters: simplicity and ease of use. Will they leverage this for all their users? The next time someone suggests adding another button to your interface or feature to your product, consider this approach instead: sometimes the most innovative design is the one that works for everyone. Rather than creating separate "accessible" versions, what if we just built our core products to be usable by all? This is the paradox of inclusive design - what works better for some almost always works better for all. What "accessibility" feature have you encountered that actually made life better for all users? #UniversalDesign #ProductThinking #CustomerExperience

🙈🙊🙉 Inclusive Design = Better UX Did you know that over 1 billion people worldwide live with a disability? That is about 16% of the global population. 😱 Yet, 98% of websites still fail basic accessibility standards. Even more concerning, 68% of users with disabilities leave websites because of design barriers. Microsoft Inclusive Design https://lnkd.in/gxx_CXp9 💡 What is Inclusive Design? Inclusive design is a methodology that considers the full range of human diversity. Abilities, languages, cultures, genders, ages, and different life situations. It is not only about accessibility for people with disabilities. It is about creating better experiences for everyone. 🛠️ Examples of inclusive design in real life: 🚪 Automatic doors Originally created for wheelchair users. Now convenient for everyone. 📃 Subtitles Essential for deaf and hard of hearing users. Also useful in noisy places or when sound is off. 🎮 Xbox Adaptive Controller Designed for gamers with limited mobility. Fully customizable for many user needs. 🎯 Why does it matter? When we design for diverse needs, we build products that work for a wider audience. ✅ How to get started: 1️⃣ Explore Microsoft’s Inclusive Design toolkit https://lnkd.in/gxx_CXp9 2️⃣ Use accessibility checklists W3C Web Accessibility Guidelines https://lnkd.in/dAjpu_8R 3️⃣ Apply WCAG principles in your projects https://lnkd.in/dSVbFjXi 4️⃣ Involve users with different needs in your design process. Let’s design products that are accessible, inclusive, and useful for all. #InclusiveDesign #UXDesign #Accessibility #DesignForAll #MicrosoftDesign

You’ve been sitting on that app idea for months. Maybe years. But when it’s finally time to build, you freeze. What tool do I use? What if I mess it up? Where do I even start? You’re staring at a blank screen. But what if you didn’t need to “build an app”? What if you just needed a prototype that works, and tells you if your idea even has legs? That’s what we did last Friday inside Mighty AI Lab. Here’s the 4-step process we used to go from idea to live prototype in 60 minutes: 1. Start with the Problem–Solution–User Triangle Before building anything, clarify three things: 1. The problem you’re solving (e.g. “Salespeople procrastinate on high-value tasks”) 2. The user you’re solving it for (e.g. “B2B sales reps who work remotely and feel isolated”) 3. The outcome that defines success (e.g. “Help them start difficult tasks in under 2 minutes”) Without this triangle, your app will drift. With it, every feature decision becomes obvious. 2. Use the IDEA Template A simple framework for structuring the app concept: - Intent: What is the core transformation this app enables? → “Reduce friction and resistance so users take action faster.” - Data: What info does the app work with or generate? → “User check-ins, emotional states, task history, time of day.” - Experience: How should it feel to use this? → “Supportive, low-pressure, playful. Like having a coach, not a critic.” - Actions: What tasks should the user be able to perform? → “Log resistance, get tailored nudges, track progress over time.” This turns vague ideas into a real architecture, without writing a single line of code. 3. Build in Claude Artifacts Instead of using 5 tools to cobble something together, we use Claude’s Artifact mode to: - Generate a UI (forms, logic, layout) through natural language prompts - Link intent to interaction—e.g., “When user selects ‘resisting outreach’, show mindset nudge.” - Iterate live while thinking out loud, which unlocks creativity and flow. You’re not coding. You’re designing with language. 4. Test. Adjust. Ship. Don’t wait for “done.” Start with usable. - Share the prototype with 2–3 target users - Ask: “Would this actually help you do the thing you’re avoiding?” - Based on real feedback, make small tweaks that move the needle - Only then consider porting it to something like Lovable or Retool This step saves founders weeks of wasted effort and gives clarity faster than any brainstorm ever could. Here's a real example: Holly came to the session with an idea: A tool that helps salespeople overcome procrastination. In less than an hour, she had a working prototype. Complete with resistance check-ins, mindset coaching, and game-like progress tracking. Not just imagined. Built. We build real prototypes live, every week, inside Mighty AI Lab. Interested? Join here: https://lnkd.in/gjah4Yen

I watched a designer turn a 12-page PRD into a user flow in 43 seconds. Not a sketch. Not a rough draft. An editable, team-ready flowchart in FigJam. The Claude + FigmaJam integration launched last month, and it's changing how product teams work. Here's what I'm seeing: → Teams creating diagrams earlier in the process — not after decisions are made, but as a way to make them → Designers with zero coding background turning flowcharts into working HTML prototypes in under 5 minutes → PMs catching edge cases in sprint planning that used to surface in QA three weeks later Three workflows worth trying this week: 1. PRD to user flows Upload your requirements doc. Get an editable flow diagram. Your team reviews it before standup ends. 2. Flowcharts to working code Draw logic in FigJam. Claude Code reads it and builds a functional prototype. Designer Felix Lee calls this "vibe coding." 3. Screenshots to prototypes Screenshot any UI. Get a clickable HTML version. Test five navigation patterns in an afternoon. The shift isn't faster diagrams. It's collapsing the time between understanding a problem and visualizing it with your team. Setup takes 2 minutes: Claude �� Settings → Connectors → Figma. What's your biggest friction point right now — alignment between specs and flows, or getting testable prototypes without engineering time? #ai #product #productdesign #ux #design