Joe Baz

Very useful animation showing automation of Figma designs based on a PRD. The thread talks about the development process from ChatGPT 3.5 to ChatGPT 4o, with visuals that highlight the results. Imagine what will be possible with ChatGPT 5 this summer. https://lnkd.in/dDqj2Dke

14

🍳 Cooking as a UX Challenge 🍳 Hello new friend from #Config! Instead of talking about config, I want to share something ‘Janice Lai, RD + UX designer’ can write about: UX of cooking! Cooking is WAY more than making food edible—it's a complex challenge. Here's a modified user journey map for cooking from my dual perspective: 🔍 Planning: • What should I cook today? • As a dietitian + wife, it's not just about taste; it’s about nutrition balance! • Did I help my husband ‘eat the rainbow’ this week? • Are there enough proteins to help us build muscle after exercising? • Variety: If I cook rice for lunch, I'll opt for a different carb for dinner cause I get bored easily. 🌱 Sourcing: • Finding the right ingredients is tricky! • Making ごぼう鶏めし(Gobo Chicken Rice) means a trip to a Japanese supermarket for gobo/ burdock root—it’s nutritious and delicious! 💵 Buying: • Scouring for the best prices requires planning too. • For 黯然銷魂飯 (Hong Kong BBQ pork fried egg rice), I avoid buying overpriced Chinese broccoli/ bok choy from Western supermarkets. 🔄 First In, First Out: • Using up every leftover ingredient is like managing a mini-inventory system. 👶 🐾 Safety First: • Ensure pets and kids are safe and entertained. • And please wash your hands. #foodsafety 🔪 Preparation: • Cutting and peeling requires patience and fine motor skills—no chopped fingers please! 🧑‍🍳 Cooking: • Juggling multiple dishes feels like playing a real-life version of Overcooked. 🎨 Presentation: • Plating is a visual invitation for ‘users’ to consume it. • For instance, if you are a parent that make Japanese dishes, your kid may really need you to draw a smiley face on their omelet rice in order for them to even start digging into it. 🕒 Time Management: • Struggling to keep all dishes warm? Me too! 🍽️ Eating: • Finally! But are your kids really eating? • As a parent, you may be feeding them by spoon or introducing them to that 1 new food a day. • Then… are YOU eating enough? 🧼 Cleanup: • The dishes won't clean themselves! #dishwasher Cooking isn’t just about culinary skills. It’s project management, a race against time, and an art form all rolled into one. Here’s a salute to all the home chefs who cook for themselves and their loved ones! 🫡 As a dietitian, I want to remind you: your meals don’t have to be perfect every time. It’s okay to order takeout! 💕

 Do you cook for enjoyment or just to keep the hangry at bay? Comment below and share how underrated a home chef's work is! 💬 The photo included is from my Instagram.
 Want me to help with your cooking? I am also taking private patients as a dietitian👩‍⚕️! We can chat about your personal/ kiddo’s challenges with nutrition and find easy ways to eat better with a busy work schedule. 
 #UXDesign #Dietitian #UserExperience #HomeCooking #Nutrition #AppreciationPost

34

12件のコメント

So, I've been posting on twitter and threads (https://lnkd.in/gQy4bC2d) these daily bug logs. I'm at 200 now. At 100 I did an analysis with gpt about these and shared that on linkedIn as well. So here is the next 100s analysis. So, just like at 100, I gave GPT the next 100 bugs and asked it to analyse changes and evolution. Here is what it came up with Evolutions: -Shift from result focus to process focus -Increased depth of reflection -Increased acceptance and resilience Themes & insights: -a greater attunement to emotional states and triggers and their impact -understanding the balance between social interactions and need for solitude -stronger focus on being present and mindful (surprised by this coz I dont have a meditation practice rn) Areas to improve: -long term focus, because the bugs are still very disjointed from each other -more structure around health and wellness -trying to understand more about broader culture and global perspectives

5

I’m kind of tired of takes on Japanese or worse “Asian “ ux, done without understanding context or language, mentioning things that happen both in western design and in the country or region being “analyzed”. Making halfhearted references to badly understood history and religion. Want to understand what japanese people expect from products? Look up Japanese products business cases. Perfect days has just come out, try to catch a brand in the background and then find out about their digital products, then look for a Japanese designer doing a business case and translate that (understanding that especially with llms the translation will be imperfect) This trend borders on cultural appropriation and exoticism.

1

1件のコメント

Etsy was recently seen A/B testing AND eventually shipping a more visible search with the help of a higher contrast orange background button color (instead of a ghost-like icon only approach). Full screenshots: https://lnkd.in/gVJThW3W Now I don't work for Etsy (as much as I'd love to design some experiments for/with them) so we can't see the actual numbers beyond this feint probabilistic residue from the public domain. However, the amazing Andrey Andreev who runs experiments at Metro recently ran a very similar one and shared a solid result on GoodUI - with a positive impact to sales and searches. N = 896,009 SRM Check = Pass p-val on Increased Sales = 0.0139 (I know some people might like this to be even lower for a primary metric; but there is also reinforcing evidence on increased searches with an even lower p value at "ultra stat-sig" levels using Ron Kohavi's language; p < 0.00000001). I inverted the a/b test and categorized it under the Filled Vs Ghost Button pattern - further weakening the ghosts and strengthening the high contrast filled button styles on multiple metrics. https://lnkd.in/gmD8Exvc Thanks Andrey for a somewhat of an unintended replication, as I know your source of inspiration came from somewhere else on this one. :) Have you tested anything similar or different. If so, what did you discover? I'd be super curious to see more examples where increases to search have either ❌ failed or ✅ succeeded. Please share independent of outcome. ps. We also have a handful of similar "visible search" experiments where companies tested adding or hiding search: https://lnkd.in/gvWqzrK5 - further supporting this direction. [EDIT]: Note the additional confounders / variables in the Metro test - a stronger border, a change in background color of the search box as per Jakob Nielsen comment. They may be similar along the lines of the increased visibility theme - but possible additional variables nevertheless. #experimentation #ecommerce #replication #optimization #ui #ux

379

28件のコメント

This is probably the biggest feature we've ever done Knapsack. We're able to take a design from Figma, understand exactly how it related to a set of coded components and patterns, and then have it build that experience in Knapsack. From there you can theme, edit, remix, experiment, save it, and share it. This is how we go from design to code in moments with an incredible degree of accuracy. Soon, this will be a multi-modal experience that will let you use a PRD, user stories, prompts, images, and Figma files to create experiences assembled from your design system components and patterns that will work at enterprise scale. Those experiences will be able to be themed and shipped across a company's entire app ecosystem. Oh yeah, it uses a lot of that trendy AI stuff too! All coming this fall...

38

4件のコメント

Decision Trees For UI Components — Smashing Magazine https://buff.ly/4aGxKJW How do you know what UI component to choose? Decision trees offer a systematic approach for design teams to document their design decisions. Once we’ve decided what UI components we use and when, we can avoid never-ending discussions, confusion, and misunderstanding.Let’s explore a few examples of decision trees for UI components and how we can get the most out of them. Source: Decision Trees For UI Components — Smashing Magazine ()

1

1件のコメント

The many faces of Jen BlatzChatz.... I am working on a video on How to REALLY Use AI in UX Research. If you want to be notified of when that video drops, please subscribe to the BlatzChatz (Youtube) channel. https://lnkd.in/gCBzyXQ2 This video involves: ⛈️ Thunderstorms 🤣 Mistakes 🤬 A few curse words 🤖 Real-world AI use

15

4件のコメント

It’s Thursday! Let’s talk about DESIGN DISCOVERY and how to make it PRACTICAL. Discovery is an essential part of the design process. In discovery, designers build a shared understanding of the problem and the design direction, establishing a foundation for all future design decisions. What does that foundation look like? In PRACTICAL DESIGN DISCOVERY, I describe three kinds of things to put into this foundation: → Principles: Enablers that help you make decisions → Concepts: Ideas that establish a big picture or north star → Models: Representations of the user experience When you draw a conclusion from user research, that’s a principle. When you say “our product is like a concierge for kids activities,” that’s a concept. And when you sketch out a flow chart or wireframe an important screen, that’s a model. Each of these contributes to the foundation that informs further design decisions. You’re not just creating these for yourself. The other people on your team – product managers and business stakeholders and developers – need to contribute to this foundation. These things – principles, concepts, and models – are the way you draw others into the discovery process. Sometimes managers tell designers to cut principles and concepts out of their process. I get it: Models are accessible because they are tangible representations of the final product. Even a flow chart is easier to react to than an unmoored design principle or a big idea. In discovery, however, you can’t model every aspect of a product. The point of discovery is to set the direction. Models provide enough of a view into the final product to get buy-in on that direction. But they’re not the whole picture. Principles provide guidelines for making decisions that the models do not cover. They establish constraints on the design process. Concepts align everyone around the product’s purpose or essence. They paint a picture of what the world looks like with the product in it. Both are helpful for decision-making. You don’t need to break the bank creating principles or concepts, or even models. Use a text file to capture statements as they jump out during the design process, like “never show a data visualization without context or explanation [a principle]” or “this is a mash-up between a to-do list and a calendar [a concept]”. Use models to illustrate principles and concepts. When folks provide feedback on the models, ask them about the concepts and the principles. “You said you were worried about the fields on this screen, but it aligns with our principle of ‘only ask for information when needed.’ Are there circumstances when the principle doesn’t apply?” Every part of the foundation – principles, concepts, and models – is a hook for a conversation with the entire team about the direction of your product. Looking for more ways to refine your discovery practice? Grab a copy of PRACTICAL DESIGN DISCOVERY! https://lnkd.in/dtar-e2

38

2件のコメント

Patterns for implementing human-centric design thinking and UX to GenAI #GenAI #UX #AI

3

Acceptance Sampling plan (Part-2) https://lnkd.in/gdk2a3Wn From the Institute for Quality & Reliability series by Hemant Urdhwareshe. This video explains how to select appropriate sample size using Sampling Plans such as MIL-STd-105E, ANSI/ASQ Z1.4, IS 2500 Part-1 (or ISO2959 -1).

2

Acceptance Sampling plan (Part-2) https://lnkd.in/gdk2a3Wn From the Institute for Quality & Reliability series by Hemant Urdhwareshe. This video explains how to select appropriate sample size using Sampling Plans such as MIL-STd-105E, ANSI/ASQ Z1.4, IS 2500 Part-1 (or ISO2959 -1).

1

How to train your designer 🐉

3

Is simplicity in design overrated? I came across an article by Morgane Peng that calls out this issue perfectly. She makes a bold point: simplicity can be just as harmful as unnecessary complexity—especially in UX. Which makes a ton of sense to me after reading it, and answers the question I asked myself starting out. Why are these huge corporations not investing in better designs? Turns out they didn't need to since it works for their target audience. While working on a suite of internal web apps for a major player in retail automation, I started with a simple goal: streamline a complex tool. But as the project progressed, I realized something crucial—these apps weren’t for mass usage. It was for their internal teams with specific workflows and established mental models. The job is to make their work easier, not our idea of what 'easier' should be. It's sort of a cliche to say 'Design for your users', but it makes a lot of sense looking at it this way. The sweet spot is what Peng calls the “efficient frontier”—not too basic, not too complex, but exactly what the user needs to get the job done.

16

The best designers are systems thinkers in disguise. Systems thinking is crucial for iterative, efficient design improvements. Rather than attempt to design a wholly new, perfect solution, oftentimes it’s better to find leverage points—areas where an incremental, often non-intuitive change will lead to significant renovation in the system. The smallest nudge for the biggest effect. A systems thinker knows surface issues are symptoms of deep systemic structures and patterns. They draw up a holistic view of the entire system and identify leverage points that, if altered, create a more efficient, cohesive design. Point being: you don't need to make sweeping changes every time. One of the most pernicious challenges facing our nation is the need for more affordable housing. And when you factor in the manifold constituents, regulations, and interests, this could be one of the most complex systems to navigate. Which is why I was so encouraged to read about Minneapolis’s recent approval of major zoning reforms to promote housing. The director of City Planning there said, "No single legislative action did more to contribute to housing creation than the elimination of parking minimums." This seemingly small change—removing a vestigial mandate for parking that was not even likely to be used—had an outsized impact on the entire housing ecosystem. By relaxing this one constraint, the city unlocked a cascade of possibilities for new developments, more affordable housing, and vibrant neighborhoods. Sometimes, details distract. But when you widen your aperture and begin to understand how the various parts of a system interact, a small adjustment can lead to a massive unlock. Try to see the whole world at once and make sense of it. Widening your aperture can sharpen your focus. Embrace *Systems Thinking*

63

9件のコメント

I regularly see posts and comments from designers expressing frustration about working with colleagues, stakeholders, or senior leaders who “just don’t get it.” Here is my take: 1. At its core, Design is a process of exchanging information and value. 2. An effective designer understands how people see, perceive, and think about information. 3. This is true for users AND colleagues. So designers, work to understand what’s valuable to those you’re working with, not just the users you’re targeting, and you may witness a shift in their understanding and appreciation of the Design.

14

2件のコメント

Designers should adapt to CMSs, not the other way around. A bold statement coming from “the other side”, i.e. the developers’ side, but, unfortunately for designers, objectively true. Here’s what it means: Designers strive to provide the best possible visual result, often forgetting that they are designing websites that are going to have their content dynamically created or changed on demand sooner or later. So what they do is tweak things around, using specific images, specific copy, and, more often, extremely specific styling. I’ve experienced tons of those cases with designers using images with a specific aspect ratio and/or focal point in places where literally any image could (and should) be utilized, or using specific wording on menus and titles not taking into account things like longer words or sentences, leading to a nightmare with localization and copy modifications. What’s worse, there are designers that tweak the layout to serve their specific needs, forgetting that it’s all dynamic. For example, adjusting a title’s letter spacing letter-by-letter. This is more obvious with designers coming from the printing world, but it’s also present with some designers claiming to be making web templates for a living. Sometimes they’re picked by the client, so the agency can’t have a say, and it’s difficult to challenge their work as doing so may be perceived as hostile by the client. Sometimes they’re just the wrong choice by either the client or the agency itself. Please make sure the designers you’re working with have experience in creating layouts that adapt to dynamic content - especially if they’re your clients’ choice. If that’s not possible, look for hints that they’re not familiar with dynamic content early, and try pointing them to the right direction. Using an ineffective design costs money to you and to your clients. 

40

4件のコメント

The UX sky is not falling in 2025 - shake it off! Yes there were some painful corrections to the 30 year exponential growth of UX over the last 3 years. If you are new to the field I'm sure it felt like the UX sky did fall, and I'm sorry that happened to you. The sun also rises. And whatever we think of the incoming US administration, broad deregulation of the technology sector leads directly to a surge in new capital investments. Which equals massive new hiring in 2025. Get your resumes tailored and your profiles spiffed. Give hiring folks a couple of days to get their 2025 on, and go get your new job!

330

27件のコメント

Really annoyed at Figma's price gouging here. There is no reason other than greed: https://lnkd.in/gfdrEiWH Oh, and I emailed them about it and this line from their reply was particularly poignant: "Additionally the minimum for enterprise is a $5k invoice minimum. 6 enterprise seats or made up with other products." To put that in context... our monthly Adobe bill (for 8 CC, 7 PS, 6 Acrobat licenses) is ~NZ$2k... Amazing how quickly enshittification sets in... #Figma #Design #SoftwareLicensing

8

3件のコメント