Diego Faria

I have reviewed hundreds of UX case studies in my career. Most of them suffer from: - Lack of polish - Poor scannability - No engaging narrative - Failing to show the impact - Focusing too much on the process The solution is quite simple: 1. Create a story 2. Lead with the impact 3. Share your process at a high level 4. Keep it short and polished; optimize it for scanning 5. Share it in a format that is easily accessible and shareable The following cheatsheet will help you structure your case studies in a concise, engaging, and impactful manner. If you found this useful, consider reposting to your network ♻️ -- Bonus tip: You can't always measure the impact of an initiative, and that's totally ok. Here is what you can do instead: - Show the metrics you expected to move, even if you don't have the numbers - Did it have a strategic impact for the team/business? - Did you test the new flow/feature? Show the results #productdesign #uxdesign #uiux

927

40 Kommentare

Figma is skipping the traditional IPO roadshow and going public via direct listing. And it's 40x oversubscribed. Most companies avoid direct listings. In a traditional IPO, investment banks buy shares at a discount and then sell them to institutional investors. The banks act as underwriters, which means they guarantee a minimum price and provide stability. Direct listings are different. No underwriters. No discount. No roadshow presentations to convince investors. Existing shares just start trading on the exchange at whatever price the market decides. This creates volatility risk as there's no price floor. But Figma doesn't need to worry about that. There's massive demand already baked in. When Spotify went direct in 2018, everyone predicted chaos. Instead, it traded relatively smoothly. Same with Slack in 2019. But why does this really matter for Figma? They capture the full market value instead of giving banks a discount. In traditional IPOs, banks often price shares 10-20% below market value to ensure a successful launch. That's money left on the table. Why give away value when you don't have to?

115

1 Kommentar

Design Systems should evolve — but with intention. I just published a new article about the Design System Contribution Process — how to propose new components, avoid duplication, and keep consistency intact across products. Start with the problem Reuse before reinventing Propose non-breaking, well-documented changes I also included a great visual flowchart from Helsinki Design System that helps teams make better decisions. 👉 Read it here:https://lnkd.in/d9agFNpQ #DesignSystems #UXDesign #ProductDesign #DesignOps #ComponentLibrary #DesignProcess #MediumArticle

80

1 Kommentar

Want to see what a strong portfolio foundation looks like? Mitchell Zeller recently redesigned his portfolio — and it’s a great example of how to get the core ingredients right (which is like 80% of the job). He’s a product designer and front-end developer based in Australia, and what stood out to me immediately was how intentional everything feels: → Smooth interactions that support the content → Clear, well-structured case studies with just enough motion and annotation → A clever toggle that separates the design and dev sides of a project — without making either feel like an afterthought There’s still some refinement to be done. But Mitchell’s already nailed the hardest part: building a portfolio that feels considered from the first scroll. This week’s portfolio review goes into the details — what he’s doing well, and what needs to be addressed still too. Read the full review + check out his portfolio at the link in the comments. And if you want more breakdowns like this each week: the newsletter is the place to be. 👇

84

25 Kommentare

Atomic Design by Brad Frost (https://lnkd.in/d3HQ7EK6 )is a brilliant methodology that helps UX/UI specialists construct robust, modular design systems—not just isolated pages. The hierarchical stages are: Atoms: Fundamental UI elements like buttons, labels, and inputs. Molecules: Simple assemblies of atoms—e.g. a search field with label, input, and button. Organisms: Distinct interface sections built from molecules and atoms, such as headers or cards. Templates: Layout structures that organize organisms and molecules, shaping content hierarchy. Pages: Fully realized templates filled with real content—this is where the user experience is validated. This methodology allows us to navigate between the abstract and the concrete, ensuring consistency, scalability, and a shared vocabulary across design and development teams. It’s a mental model—not a rigid, linear process—and remains highly relevant for building modern, collaborative design systems. #UXDesign #UIDesign #AtomicDesign #DesignSystems #ScalableUI #ComponentDesign #AtomicDesignMethodology

2.580

42 Kommentare