Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Everett

Learn how to create websites, apps, and AI experiences in the real world at your own pace.

Learn how to create websites 💻, apps📱, and AI products 🔮 in the real world from professionals.

68 contributions to UXD Academy Mastermind
Do-With-You Session – November 16, 2026
⬇️ Tonight's Session ⬇️ https://us06web.zoom.us/rec/share/GDIGlz-9N1O3QI4gxtwNDR4y6_rkUMfsQjLtDrPXbNlFg-SAjA5N_8at9PQukaWo.9kdoSR_J_afBno3W Passcode: =Ib+@+z4 We discussed: 1. What a two-week sprint really looks like for a designer in a Scaled Agile (SAFe) org, plus the book I keep pointing to, Org Design for Design Orgs 2. PI planning and Big Room Planning: how 8 to 10 weeks breaks into sprints, and why you mostly listen in the kickoff 3. Stand-ups, Jira tickets, and how a ticket actually gets closed: side conversations, heads-down time, a walkthrough with your PM and then your devs, then handoff 4. Protect your maker time: block at least 2 hours, and Tuesdays and Thursdays are your friend 5. How handoff is changing now that we can build what we design with Claude Code 📅 The sprint calendar I walked through (click any meeting to see what it is and what's expected of you): https://claude.ai/artifact/QDebADGYopjGiLsmq3AU6x Prompts to try this week: 1. Translate my work into sprint language: turn a past project into interview answers that sound like you've worked in a sprint team 2. Write my stand-up in two sentences: go into stand-up with what you did, what's next, and what's blocking you 3. Let Claude play the PM first: find the holes in your design before the real walkthrough 4. Protect my heads-down time: find the two-hour blocks your meeting-heavy week is hiding 5. Rehearse a PM sync: practice the weekly PM conversation before your first real one #1 in full: I'm interviewing for [role title] roles at companies that run Agile or the Scaled Agile Framework (SAFe). Here is a description of a past project: [paste project write-up]. Map what I did onto sprint vocabulary: requirements gathering, stand-ups, tickets, walkthroughs with PMs and developers, handoff. Only use what's actually in my write-up, and when something is missing, ask me instead of inventing it. Then write two answers I could say out loud for "Tell me about working on a cross-functional team," each under 90 seconds, one plain and one more detailed.
0
0
📱 A prototype that looks finished isn't a decision
Hey family. This week I sat with three pieces by Herajeng Gustiayu, a product designer who leads a team in travel tech. I think they're the clearest writing I've seen on what our job turns into when prototypes get cheap. I think about it like a walkthrough at practice. A play can look perfect at half speed with nobody guarding it. That doesn't make it the play you call in the game. Her first point: how finished a prototype looks and how decided the team is used to move together. They don't anymore. An AI flow can look ready for engineering before anyone has actually chosen it. Her fix is one question in every review: what would make us abandon this direction? If the room shrugs, nobody wrote the assumption down. Her second: AI made exploring cheap, so the skill moved from making options to choosing them. Bring two or three to a review, not six. And when a stakeholder asks for something you disagree with, build their version plus two alternatives, then say which one you'd run and why. Her third hit me hardest. Her team built a tool that turns a brief into a first-draft screen that fits their design system in under 30 minutes, no designer needed. The list of places where designers still had to be involved turned out to be a list of where judgment lives. In her words, "Some people who thought they were senior will realise they were just fast." Fast at half speed isn't the same as knowing which play to call. That's the side of the line I want all of you on. Try this. Next prototype you share, yours or one an AI made, put one line under it: "We're assuming ___. We'd drop this if ___." Do it three times this week and post your favorite in the comments. Her three pieces: AI prototypes are getting ahead of product decisions AI gave me more room to explore as a product designer
0
0
🚨 No Session Tonight But...
In the meantime, join the a16z Speedrun talent network! a16z is a venture capital firm that invests in and scales some of today's most popular tech companies. They scale companies through a 12-week growth program called Speedrun. Here’s what they are offering: - 300+ a16z Speedrun startups are hiring - Joining takes about a minute - A Speedrun partner introduces you to founders - It’s free for candidates - Open roles include Founding Engineer, ML Engineer, Product Designer, GTM Lead, Platform Engineer, and Design Engineer If you’ve been building with Claude, this is a good place to put that work in front of people. Founding teams at early startups want people who already work with AI every day. --- Before you sign up: 1. Update your portfolio or LinkedIn so the link you share shows your best AI work. 2. Pick the one or two roles you’d actually want. 3. Sign up here: a16z speedrun talent network A warm intro is not a job offer, so treat it as a door that opens. I haven’t vetted every startup on the list, so do your own homework on each one. If you join, tell us in the comments.
DWY Session – October 19, 2026
⬇️ Tonight's Session ⬇️ https://us06web.zoom.us/rec/share/ZAdYcK3f5M7DjYwPscz8Zo6ZPchWnfyLL0UHZPzZVaKkaDJ54dreB9RdaQR9TV1z.S0zw39rm4cEclZjt Passcode: !Q8xM4A% --- We discussed: 1. Why I'm moving my presentations to Claude Slides: comment mode, custom fonts and logos, and export to HTML or PDF 2. Portfolio mindset: show what you built end to end, with AI as your thinking partner 3. How I'm using Claude to run a client engagement from first email to free lunch and learn to paid assessment 4. The pre-work checklist and personal context doc that get a client ready before we ever meet 5. Building plugins so Claude does the paperwork, and I just teach Prompts to try this week: 1. Build a branded deck in Claude Slides: a presentation in your fonts, logo, and style without screenshot ping-pong 2. Retell your case study around the decisions: show the problem, the calls you made, and how fast you shipped 3. Find who you forgot to follow up with: unanswered emails surfaced, follow-ups waiting as drafts 4. Let Claude interview you, once: a personal context document so you never re-explain yourself 5. Build a pre-work checklist before the meeting: show up to a discovery meeting with real examples, not guesses #1 in full: Let's create a Claude artifact: a presentation for [audience] about [topic]. I'm attaching my logo ([SVG or PNG]), a PDF of a deck whose look I want to match, and this Google Fonts link for the typeface: [font URL]. Place my logo in the top-left corner of every slide and follow the attached deck's colors and spacing. Keep it to [number] slides. Before you build, describe the style you'll follow in a few lines so I can correct it. Then build it, and I'll use comment mode to fix individual slides. All 5 prompts in one PDF, attached below 👇🏾 Which prompt are you running first? Drop the number below 🚀
0
0
DWY Session – October 12, 2026
⬇️ Last Night's Session ⬇️ https://us06web.zoom.us/rec/share/h3EHztQM9H8Cm5qFA0v9MD2EqDOrn153BoKgmaGLV_Lxg-JCkDA3QpyGItiaq-lu.0Vhv7Aa4KggZncCO Passcode: y82kMvQ= --- We discussed: 1. BreAnn rebuilt her marketing site with Claude-powered animations 2. Motion design and micro-interactions that create real delight for Njeri's project 3. New model drops from Anthropic, OpenAI, and Meta, plus when to use Opus vs. Sonnet vs. Haiku 4. My AI Opportunity Assessment process: interviews, rubric, roadmap, governance policy, and prompt studio Prompts to try this week: 1. Sketch it, then direct it: get the motion you pictured instead of the one Claude guessed 2. Design the feeling first: turn "make it less clinical" into five concrete micro-interactions 3. Two versions, two branches: compare design directions without risking the version that works 4. Content calendar on autopilot: a monthly calendar, a nightly status sweep, and email drafts you review 5. From interviews to a ranked roadmap: turn a pile of "I wish AI could do this" into a plan a client can act on #1 in full: I'm attaching a rough sketch of [page or section name]. Here's what's on it: [list the pieces, e.g. logo, photo, headline]. Here's how I want them to move: [piece 1] should [start where, move how, end where], then [piece 2] should [start where, move how, end where]. Keep [layout / colors / fonts] exactly as they are. Before you build anything, restate the movement as numbered steps so I can correct it. Then build it. All 5 prompts in one PDF, attached below 👇🏾 Which prompt are you running first? Drop the number below 🚀
0
0
1-10 of 68
Everett Swain
3
39 points to level up
@everett-swain-7025
I began my design career 12 years ago. Now I teach people how to become designers without degrees.

Active 7h ago
Joined Feb 7, 2024
Powered by