Tamara Alsheikh

Do you need a healthcare background to work in healthcare UX? No, but you do need to rethink how you approach the work. Healthcare UX isn’t just about clean flows or visual polish. It’s about trust, risk, and navigating complex systems. You’ll need to know how to: Work with clinicians and compliance Do research that holds up under HIPAA Factor in patient safety, not just usability Connect design decisions to clinical and operational outcomes That’s what we cover in Transition into UX for Healthcare - a course I built for people making this shift. We don’t just teach the process. We build AI-powered tools, backed by research and grounded in real regulations. If you’re ready to make the move, join us. Details in the comments.

58

12 Kommentare

Engineers and product teams are already achieving unprecedented output with just copilots.  This trend is undeniable and will only accelerate.  Soon, designers won't just use AI tools; they'll orchestrate entire teams of UX Agents. To prepare for this future and stay relevant, I suggest you learn a few things: 1. How to move faster with AI 2. Improve design quality with AI 3. Designing intuitive UX for AI-driven applications. 4. Emerging design patterns and industry standards AI has influenced 5. Navigating the ethical responsibilities and boundaries of AI use. I am adding some classes, notes and guides discussing AI in UX for my students at SJSU. If you want to follow along and get the guide please check out: https://lnkd.in/gQn3n3yh and signup.

34

2 Kommentare

I recently tried connecting 𝗙𝗶𝗴𝗺𝗮 𝗠𝗖𝗣 𝘄𝗶𝘁𝗵 𝗖𝘂𝗿𝘀𝗼𝗿 for some Curo (curohq.com) dev work - and it felt like a real shift in the design-to-code workflow. Honestly, it surprised me how useful it was. Normally, moving from design → code feels clunky: – open Figma – inspect layers – copy spacing, colours, styles – manually rebuild everything in code With MCP, that loop gets tighter. Cursor can pull context directly from Figma files and generate implementation-ready code: ⚡ 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁-𝗹𝗲𝘃𝗲𝗹 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗼𝗻 → Clean React/Tailwind code mapped straight from design structure, no manual copy-paste. ⚡ 𝗗𝗲𝘀𝗶𝗴𝗻 𝘁𝗼𝗸𝗲𝗻 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 → Colors, spacing, typography flow directly into code, reducing mismatch bugs. ⚡ 𝗙𝗮𝘀𝘁𝗲𝗿 𝗶𝘁𝗲𝗿𝗮𝘁𝗶𝗼𝗻 → Prototype and refine in Cursor without constantly jumping back into Figma “dev mode.” It felt like a smoother loop. Instead of translating designs by hand, you spend more time actually building. It’s still early and not perfect, but even in this first try I could see how much friction it removes. As someone who’s usually juggling between design files and dev work, this felt like a glimpse of the future. Trying this out made me appreciate how powerful it feels when AI stitches broken workflows together. That’s exactly the kind of leverage I want Curo to create in learning. try curohq.com 👉 Has anyone else tried Figma MCP yet? Curious if you found the same speed boost.

25

1 Kommentar

Most health apps design for engagement. Women's health apps should design for relief. I said this to a product team last week and the Zoom room went quiet. We'd been reviewing design options for a women's health app - debating layouts, interaction patterns, how many steps it should take to complete a task. Standard UX stuff. But I feared the conversation was missing the point. The perimenopausal woman we're building for is managing a career, aging parents, teenagers who need her, a body that's betraying her in ways she's struggling to wrap her brain around. She code switches all day every day, from meetings to grocery stores to soccer fields. Our app isn't in her top ten priorities, probably not her top twenty. And we want her to use it anyway. So here's what I told the team: every tap matters. Every swipe, every scroll, every extra step between her and the thing she needs is friction she doesn't have bandwidth for. We're not competing with other apps, we're competing with exhaustion. This is true across women's health, but it's especially acute in perimenopause and menopause - life stages where cognitive load is already maxed out, sleep is garbage, and patience is thin. Most health tech products obsess over engagement, but what if we obsessed over effort instead? What if we measured success not by time-in-app but by mental burden relieved? When you design for a tired, overstretched, underslept woman, simplicity isn't a nice-to-have. It builds trust, earns respect, and demonstrates empathy for her reality. And when you nail that, she'll come back. Not because you gamified her experience or sent her smartly timed notifications, but because you gave her something so rare in her life: Easy.

248

69 Kommentare

What happens if you take Figma away from your design team? Would they still create value? Could they reframe a business problem? Run a workshop that aligns stakeholders? Sketch ideas with users, not just polish pixels? Defend why a feature exists? Challenge assumptions in the roadmap? If yes, you've got designers who think beyond tools. If not, they might be great at delivery, but underused when it comes to solving the right problems. In many teams, the gap isn’t talent or tooling it’s timing. Design gets involved too late. When it’s brought in earlier, everything gets sharper: thinking, direction, and decisions. That’s where the real leverage is.

114

60 Kommentare

Can AI Really 10X Your Design Thinking Workshops? Remember when UX workshops meant a room full of people voting with sticky notes and sharpies? Fancy executives acting like kindergartners for a day, everyone feeling creative, but walking away with... just another idea? The frustrating truth: traditional design workshops rarely produced tangible outcomes. Just vague concepts that would take months to materialize (if ever). Those days are over. With AI tools integrated into each stage of the IDEO design thinking process, we can compress months into hours and deliver actual working prototypes: 1️⃣ EMPATHIZE: Use Gemini (by Google or ChatGPT by OpenAI for deep research and user insights in minutes 2️⃣ DEFINE: Let any LLM and AI articulate precise problem statements that hit business and user needs 3️⃣ IDEATE: Generate wireframes with Claude AI while team collaborates in Miro (You can also do it in FIgma, or with sharpies!). Take the image of the sketched wireframe, upload to claude and let it do the code. 4️⃣ PROTOTYPE: Transform concepts into interactive demos with Lovable before lunch (you can even import Figma's sketches at this point) 5️⃣ TEST: Gather immediate feedback and iterate in real-time on your live, coded concept and prototype. I recently ran a workshop at a big bank where we went from vague challenge to working prototype in a single day. The executives weren't playing anymore—they were speechless. This isn't incremental improvement. It's a complete reimagining of the design process. Last week when I said "Figma is dead," people told me that the design process can't be replaced by AI. I never said it would be replaced—I said we should redesign it with AI tools. And that's exactly what's happening.

45

16 Kommentare