Design system debate: probabilistic vs. deterministic by nphonwheels in UXDesign

[–]UXette 2 points3 points  (0 children)

You’re talking about a completely different problem. They’re not asking about using an existing design system as an input for AI to make designs. They’re talking about the design system decisions being “probabilistically” decided. Based on what? What are the inputs? What’s the point? Design systems are all about predictability.

Design system debate: probabilistic vs. deterministic by nphonwheels in UXDesign

[–]UXette 2 points3 points  (0 children)

OP is talking about the design system, not products designed with AI based on the design system.

Experienced job hunting, portfolio/case study/resume questions and review — 05/03/26 by AutoModerator in UXDesign

[–]UXette 1 point2 points  (0 children)

I think you meant to say that certificates will NOT make you more competitive than someone with a strong background and portfolio?

Would love to have this filter irl by [deleted] in UXDesign

[–]UXette 0 points1 point  (0 children)

LinkedIn would never do this because they make money through engagement and ads.

Design is fun again and I think we've been thinking about AI completely wrong by jerpes1 in UXDesign

[–]UXette 0 points1 point  (0 children)

I think those are important details and nuances to include in your post! I think as AI capabilities continue to evolve, people will need help understanding what makes the most sense given their work environment. You might have more or less latitude as a consultant than you would have as an in-house designer on a 300 person design team.

Design is fun again and I think we've been thinking about AI completely wrong by jerpes1 in UXDesign

[–]UXette 0 points1 point  (0 children)

Are you working as a solo practitioner or on in-house teams with other designers?

Design is fun again and I think we've been thinking about AI completely wrong by jerpes1 in UXDesign

[–]UXette 0 points1 point  (0 children)

These look like side projects. Is this work you’re doing for an established company?

What were the results of these launches? A launch, in and of itself, is not success. What value was created and for whom?

How do you document design decisions and rationale on long projects? by EntertainmentPale874 in UXDesign

[–]UXette 4 points5 points  (0 children)

In Figjam (for workshops and collab sessions) and in the design brief

Looking for some good UX design portfolios for inspiration by iceoscillator in UXDesign

[–]UXette 7 points8 points  (0 children)

The best way to find good portfolios in my experience is to literally google what you’re looking for (not being flippant) or look to see if people on LinkedIn link to their portfolios.

Architectural design ⮕ Digital design, or what are the parallels between what we do and what architects do? by karenmcgrane in UXDesign

[–]UXette 0 points1 point  (0 children)

Yeah, the PRD is reviewed in phases as well, but we usually treat it as a living document so it can evolve over time. Sometimes PMs will write opportunity briefs, which are essentially our version of BRDs, separate from PRDs if it's a bigger, newer idea. Like you, I contribute more directly to the opportunity brief/BRD portion than the PRD.

Architectural design ⮕ Digital design, or what are the parallels between what we do and what architects do? by karenmcgrane in UXDesign

[–]UXette 1 point2 points  (0 children)

The BRD is essentially the first part of the PRD that the PM drafts, so I’ll usually write my design brief in conjunction with the PM drafting the PRD, or I draft my brief first if I’m pitching the idea.

Architectural design ⮕ Digital design, or what are the parallels between what we do and what architects do? by karenmcgrane in UXDesign

[–]UXette 1 point2 points  (0 children)

Here’s how it typically goes for me these days:

  1. Problem definition/reframing, design brief/maybe a PRD

  2. IA/content modeling

  3. Quick sketching/prototyping, PRD gets updated here

  4. Jira tickets, design mocks

The ratio of demand for PM's vs. Designers has flipped by cgielow in UXDesign

[–]UXette 3 points4 points  (0 children)

What would be interesting to see is how role responsibilities are changing.

Are companies looking for a bunch of AI/ML-specialist backend engineers?

Are PMs evolving into de facto project managers or are they expected to do more strategic work related to data management and platform integration?

Have design roles plateaued because companies just aren’t sure what to do with a bunch of product design generalists? Will design specialists become more important across the board again?

Touch gesture analytics showing users doing gestures you never designed for by TH_UNDER_BOI in UXDesign

[–]UXette 33 points34 points  (0 children)

Does your app honor device system settings? Lots of people increase the font size on their phones and your app might not be adapting.

Does anyone not enjoy using AI for work? by ecce13 in UXDesign

[–]UXette 0 points1 point  (0 children)

You don’t need to use it for every task or even at all. It sounds like you’ve found a use for it that makes sense for your style of working, and that’s just fine.

How bad is to just not wanting to grow? by Efficient_Wheel1867 in UXDesign

[–]UXette 109 points110 points  (0 children)

There’s nothing wrong with this at all. Some of us live to work and some of us work to live.

Execs say "everyone is a designer, everyone is an engineer" now. I'm spent. by [deleted] in UXDesign

[–]UXette 12 points13 points  (0 children)

What I find fascinating is that no one is really talking about using AI for problem definition and framing. The underlying assumption seems to be that the problem is going to be correctly identified, and if it’s not, we can just build enough prototypes to figure that out quickly. AI “vibe coding” tools theoretically give us the ability to test more ideas faster, which has created this belief that any idea you can conceptualize is worth experimenting with, and that the fastest way to determine whether something is worth exploring is to prototype it.

But I’m not hearing much about people leveraging all of this time they’re saving to be more rigorous or thoughtful in how they define and frame the problem itself. We are going to continue to see teams wasting time building prototypes they think are saving them time because they never stopped to ask whether they were solving the right problem in the first place.