Convene
2,400 designers who actually answer.
A private Slack room for mid-career product designers — teardowns, salary threads, and the second opinion you needed yesterday.
You're not reading about a community.
You're eavesdropping on one.
Three threads from this week. You can see them. You just can't reply yet.
The Emoji Poll
Thirty seconds of your time. Fourteen opinions in six minutes.
quick gut check before I push this to eng — onboarding final step, user has just connected their first integration. button label: "Finish setup" vs "Start exploring". which one do you ship?
"Start exploring" — "Finish" frames it as a chore you just survived. "Start exploring" reframes the moment as a beginning, not an ending. tiny copy change, big psychological shift.
Depends. If your activation metric is "first action taken" then "Start exploring" points forward. If it's "setup complete" you want "Finish setup" for the confirmation dopamine. what's your north star metric here?
The Teardown
Four screens. Forty-three replies. One design lead changed her entire IA approach.
Did anyone else catch what Stripe did in their new merchant onboarding? They're hiding 60% of the form fields behind a "Tell us more" expansion — but the expansion is pre-triggered by your business type selection. So it feels like the form is getting shorter as you go, even though you're entering more data. Classic progressive disclosure but inverted. I've been staring at this for 20 min. 🧵
This is the "shrinking form" pattern — Intercom used it in 2019 but Stripe's implementation is cleaner because they're using the business type as a routing signal, not just a filter. The user thinks they're filling out less; they're actually providing more qualified data. Genuinely clever.
I just rebuilt our entire account creation flow based on this thread. Moved from a 12-field linear form to a 4-field adaptive one. Took two days. Our PM is going to think I'm a wizard.
The Salary Thread
The thread that made three people renegotiate. Numbers redacted. Context preserved.
Starting this thread because I just got an offer that felt low and had no idea if it was. Format: [years exp] / [city] / [role level] / [total comp range] / [equity %]. I'll go first: 6yr / Austin / Senior IC / ████████ / 0.08% — feels below market but hard to tell. Anyone?
8yr / NYC / Staff / ████████ / 0.12%. Your number is low for Austin at 6yr Senior. I'd counter at minimum ██████ and push on the equity band — 0.08 is pre-Series B language for a Series C company.
Update: I shared this thread with my manager and asked to revisit my comp. We're having the conversation Thursday. Never would have had the data to do this before.
The conversation you needed
was already happening.
These are first names only. Roles and situations are real.
Senior Product Designer
Series B health-tech startup
"I posted a half-baked onboarding flow at 11pm on a Tuesday. By 7am I had twelve replies, two Figma comments, and a job lead from someone who'd solved the exact same problem at Duolingo."
What they needed
Needed: Second opinion on a 5-step onboarding before Thursday's eng handoff
Freelance UX Consultant
Independent · Austin, TX
"I was about to price a discovery sprint at $4,800. Someone in #real-talk told me the going rate for my experience level in my market was $7,200–$9,000. I went back to the client that afternoon."
What they needed
Needed: Pricing sanity check for a 3-week discovery sprint with a mid-size retail brand
Design Lead
Enterprise SaaS · 400-person team
"I rehearsed my entire design system proposal in #presentations before the board meeting. People asked the hard questions — "why not Radix?", "what's the migration cost?" — so when my CPO asked the same things, I didn't flinch."
What they needed
Needed: Stakeholder rehearsal for a $200K design system investment proposal
The room is full.
You're at the door.
Four threads from the last 24 hours. You can read the first line. The rest is inside.
Just got a DM from the design director at Linear — they're building out their mobile team and want someone who's done 0-to-1 on iOS. Not posted publicly yet. Who's interested? Reply in thread 👇
This is the worst checkout flow I've seen in production in 2025 and I can't stop analyzing it. Six required fields before you can even see the price. Attaching annotated screenshots — tell me I'm not insane.
Hot take: design systems are a trap for IC designers who should be building product intuition instead. Change my mind. I'll start: I've met more senior designers who are great at tokens and terrible at decisions than the reverse.
Sharing my entire discovery sprint contract template — SOW, payment schedule, IP clause, and the "scope creep escalation" language that saved me $8k last year. DM me if you want the editable version.
The chairs are already
arranged in a circle.
Someone saved you a seat. The coffee is already poured. There are three conversations happening right now that you would have something to say about.
Curated membership · No spam · You can leave anytime