Jill DaSilva

100% agreement with this statement. When a designer asks questions it shows that they care and desire the necessary context to be effective partners in the work. I have seen this exact same sentiment used as a reason for not including designers. I've heard from Product and Engineering leaders that this slows things down and is an unnecessary friction when decisions have already been made. The cement is dry. Deadlines have been set. Promises have been made to Sales who, in turn, have made commitments to Clients. Product needs the screens designed so Engineering can build. The questions can wait until the next iteration. We can pick up the pieces then. It's a vicious cycle and can be damaging to a product and the organization as a whole. This cycle is rough on the designer, product manager, and engineers because they all want to do their jobs and to do them well. The issue is timing. It's not the questions that the designer is asking that are frustrating. It's WHEN they're being asked. Getting Design injected into the right (read: most effective) part of the process requires advocacy and trust. The best designers build relationships.

4

1 Comment

Such a great post, sharing lessons learned by Akshan Ish. For anybody interviewing for senior design roles, or just presenting a great story, take a look. There aren't many resources helping senior / principal / staff designers prepare for interviews, so sharing 10+ experience from both sides of the table, is gold. https://lnkd.in/d4XprbS2

14

2 Comments

With Outset unlocking new research methodologies comes understanding new UX terminology. Hear Aaron Cannon explain what “tokens” are and how they relate to evaluating generative UX.

5

Codex 5.3 for designers. Claude Opus 4.6 for engineers. Here’s why 👇 They don’t just feel different and they also have a different UX philosophy. • Codex: Plan → Execute • Opus: Plan → Execute → “Want me to walk you through it?” Opus keeps you close to the logic. It’s built to pull you into the why, not just deliver the what. Put it on a truly complex codebase and let's talk afterwards. Codex is the opposite vibe: crisp execution. You decide the plan, it runs it. No extra ceremony. Not better vs worse, just two UX strategies optimized for different kinds of work.

11

Two Checkboxes That Nail Privacy and Promotion 1️⃣ Lets the user decide whether their prompts are stored for system-improvement purposes. 𝗪𝗵𝘆 𝘁𝗵𝗲 𝗰𝗼𝗽𝘆 𝘄𝗼𝗿𝗸𝘀 Transparency first: leads with “By default we collect and process…” so users know what’s happening now before opting out. Plain language: no legalese—“prompts and completions” is the only necessary jargon, and it’s still everyday English for the audience. Benefit framing: “solely to improve inference speed” reassures that the data isn’t for ads or resale. 2️⃣ Classic marketing-promotion opt-in. 𝗪𝗵𝘆 𝘁𝗵𝗲 𝗰𝗼𝗽𝘆 𝘄𝗼𝗿𝗸𝘀 Value-oriented headline: “Partnerships and special offers” sounds exclusive, not spammy. First-person promise: “I’m interested in…” subtly shifts power to the user—feels like their choice, not the company’s agenda. Concrete examples: “new models, features, user research, collaboration” tells users exactly what they’re signing up for. #UXWriting #SaaSDesign #Microcopy #ProductDesign #UserTrust

5