Jakub Skonieczny

Most designers focus on UI. 2 years ago, I decided to focus on problems, Design systems, and polish UI instead. I worked on a design project in the construction sector - a space full of complexity, inefficiencies, and real user pain points. but....... Instead of jumping into screens, I broke down : 1. What’s the actual problem? 2. Who is struggling and why? 3. How can design improve both user experience and business KPIs? This video is just a whiteboard-style intro to that thinking. And this is not the full case study - that’s coming soon. But this is exactly how I approach of any design project :- Clarity - Problem - System - Outcome And I would love to hear your thoughts and feedback in the comments 🙌 #ProductDesign #UXDesign #UserExperience #DesignThinking #ProductDesigner #Startup #Tech #Innovation #DigitalProduct #BuildInPublic

11

Senior designers rarely burn out from the craft itself. They burn out from: • politics • constant justification • fighting the same battles in different forms After 8+ years, the hardest problems aren’t design problems anymore. They’re: • decision problems • people problems • power problems What keeps the work sustainable • Clear decision frameworks that reduce negotiation • Shared understanding of UX, accessibility, and user needs • Less persuasion, more structure and trust The craft isn’t the issue. The environment is. 👉 What drains your energy more than the work itself?

155

25 komentarzy

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 In terms of formats, use something you are comfortable creating: - A custom website (preferred) - A vibe-coded website - A Figma deck or PDF - A simple Notion page 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

733

18 komentarzy

I designed an entire interactive prototype in record time ⚡ …and didn’t start with a hi-fi design tool. As designers, we’re constantly spotting tiny UX improvements. But let’s be real: - We all have competing priorities - Not every idea gets hours of polish - Some concepts get a “no” in 5 seconds So I tried a faster approach. I opened up Miro and: - Dropped in screenshots of the current experience - Brain-dumped ideas, notes, and “what ifs” - Let Miro’s AI make sense of the chaos 🧠 From there, it was a few clicks to get mockups and a fully clickable flow. Just like that I had an interactive prototype ready for stakeholders! If you’ve got an idea but need to move quickly, try out Miro to turn messy thoughts into conversation starters with your team. 💬 #miro #productdesign #miropartner

64

6 komentarzy

With LLMs, designers started to ship front-end. That is where much of accessibility actually needs to be handled, not in Figma prototypes where color, contrast and size mostly cover it on a static canvas. Keyboard use, focus, semantics, screen readers, motion, zoom and actual interface behaviour are now part of our daily practice. Surprisingly, I don't see LLMs generating accessible interfaces by default. You would think standards are the kind of things machines should be good at following. Relying on 3rd-party Skills feels like patchwork. At least, LLMs are good at pointing out what is missing, so you can do the job for them.

35

28 komentarzy

In order to communicate reusable concepts through design tokens, sometimes we need more than just the tokens themselves — not just resources that support the tokens, but new ideas and mental models that are instead supported *by* the tokens.

60

5 komentarzy

🌱 Understanding Atomic Design Brad Frost’s Atomic Design introduces a clear and scalable approach to building consistent interfaces, from atoms to entire pages. If you’re designing or maintaining a design system, this chapter is an essential read to understand how every component fits into a cohesive ecosystem. https://lnkd.in/dzDM92kT ✨ Credits: Brad Frost #DesignSystems #AtomicDesign #UXUIDesign #ProductDesign #DesignThinking #ComponentDrivenDesign #UXStrategy

7

🌧️ How To Consolidate Design Systems (https://lnkd.in/ehZd-UGQ), a practical guide with strategies, potential benefits and quick wins for merging existing design systems. Shared by Evgeny Khoroshilov, heavily inspired by Nathan Curtis's thorough article on Consolidating Design System (https://lnkd.in/dCZHZikx). 🚫 In many companies, not every design system is the same. ✅ Design teams have different needs, budgets, size, skills. ✅ They often see “design system” projects very differently. ✅ It could be a style guide, UI kit, product, process or service. ✅ Audit what kinds of “design systems” your company has. ✅ A: Keep all systems as is, but add a shared practices layer. 🤔 Each brand maintains its main focus, but duplication is likely. ↳ Set up community of practice without changing structure. ↳ Useful when teams have very different needs and priorities. ✅ B: Identify shared practices and move them into subsystems. 🤔 Priorities might be misaligned, risk of poor collaboration. ↳ Involve all teams to shape subsystem for efficiency gains. ↳ Helpful when shared practices are duplicated or differ a bit. ✅ C: Slowly retire old systems and launch a shiny new one. 🤔 Very expensive, with a risk of disruption and poor adoption. ↳ Run a pilot to test and refine, involving key stakeholders. ↳ Good choice with a legacy system that’s falling apart. ✅ D: One system stays and others gradually retire. 🤔 Streamlines operations, but requires re-training + retooling. ↳ Respect needs and work by other teams, and migrate them. ↳ Helpful if one system can be extended to meet all needs. Often the main reason for consolidation of design systems is the need of consistency. It is of course important, but sometimes the cost of enforcing consistency might be very high, disrupting everything from workflows and tooling to culture and team spirit. Consistency for the sake of consistency is a dangerous path to take. There are exceptions, "snowflake" scenarios and specific use cases that often require a particular level of complexity that can’t be avoided or reduced — it must match the complexity of decisions in real life. I always try to keep in mind that in the end a design system is just a product that we use to build the actual product across teams and brands. It doesn't have to be perfect or comprehensive. It must be useful and easy to use. So consolidate design systems if you must, but always involve and support teams behind them as much as you can — just to make sure no core functionality is left behind, and that the team has a clear path and goals to move forward. [Useful resources in the comments due to LinkedIn linking rules ↓] #ux #DesignSystems

362

9 komentarzy