Hey again 👋
Just incase you missed the update of the Unicorn Club going forward here's a TLDR;
New structure:
🏗️ Build - actionable UX and interface craft you can use now
🧩 Shape - shared foundations and ways of working
🚀 Ship - release habits, measurement and iterate
The aim is simple, turn reading into progress in the same week. Same 4-6 minute skim, just with more momentum.
- Adam at Unicorn Club 🦄
Sponsored by Kinsta
Adapting Social struggled with 50+ client sites spread across multiple hosting providers. After moving to Kinsta , they achieved 33% faster page loads and 767% increase in site traffic .
Automated workflows saved them 250+ hours annually . Now they manage everything from one dashboard on Google Cloud Platform with centralized site management. Performance and efficiency transformed their agency .
Read the Full Story →
🏗️ Build
Make better interfaces.
A clear catalogue of inline patterns (chips, dropdowns, sliders, ghost text) that refine user intent as they type across search, uploads and creation.
Why it matters: Reduces prompt burden and time‑to‑value, turning vague asks into higher‑quality outputs without chat back‑and‑forth.
Try this: Add two contextual preset chips and one inline hint to your most‑used search or upload field.
Design onboarding as a motivational, personalised pre‑signup flow that pays off immediately with a tailored promise and a real result.
Why it matters: Personalisation plus visible progress lifts activation and reduces drop‑off. Users continue when value is felt, not explained.
Adopt this week: Replace one generic step with a 3‑question branch and rewrite the CTA to “promise + next step”.
Modern HTML/CSS (nesting, :has(), @starting-style, light‑dark(), lvh/svh/dvh, native validation) covers many interactions faster and smoother than JS.
Why it matters: Fewer scripts mean faster, more reliable interfaces with better accessibility and less maintenance.
Try this: Swap one JS accordion/toast for details/@starting-style plus :has(); keep the native input to drive state.
🧩 Shape
Shared foundations across teams.
Outputs without shared problem‑framing look productive but dodge the social work that makes solutions credible and stick.
Why it matters: You burn trust and slow delivery when you “print receipts” (artifacts) without alignment; fixes get rolled back.
Adopt this week: Add a 30‑minute pre‑solution session to frame the problem, success metrics, and stakeholders before any mocks or code.
Cutler separates where hours go from what teams can actually deliver, surfacing the hidden drains (interruptions, rework, dependencies).
Why it matters: Treating time as capacity misguides investment and reporting; you optimise calendars, not outcomes.
First step: Split your weekly report into “time allocation” vs “capacity factors”. Capture the top three drains per team and one fix to try.
🚀 Ship
Release, measure, iterate.
A field guide to Google’s load paths (Speculation Rules, SXG, AMP, edge/cache/redirect variants) plus robust client/server detection to tag real‑world visits.
Why it matters: Segmenting by load type removes noise in LCP/engagement, revealing what Google‑referred users actually experience.
Adopt this week: Tag Google‑referred, first‑visit, same‑tab sessions with a load‑type flag and start reporting LCP by type (e.g., SXG prefetch vs server load).
Last week, what was the one area you found most challenging or rewarding in your work?
- 🌐 Interaction Design - 🎨 Visual Hierarchy - 🔄 Component Behaviour - ♿️ Accessibility Compliance
This is the question we've asked the Unicorn club this week.
We're shaping our focus together - every reaction counts. You can reply or jump over to the community Slack to share your thoughts!
Cast your vote - and share your insights
Get our "7 Positioning Sins That Cost B2B Brands Millions" guide when you join. It's free, join 10,000+ B2B executives.
Daily rundown of what's happening in tech and what you shouldn't miss. Read by 200,000+ professionals from Google, Apple, OpenAI...
🎲 Also worth a look
A few extras we've found.
Why curation beats “Homer Simpson car” building in an AI‑cheap world; define criteria and say no.
AI engineering demand is surging; roles cluster in SF; public tech hires more; remote is down.
Nine org archetypes (from “Game of Thrones” to “Thoughtful Transformation”) and how to navigate them.
Other ways I can help...
Here’s how I can help you tackle your next challenge:
🎯 1:1 Mentorship – Personalised advice on portfolios, career moves, or challenges you're facing.
💡 Hire Me – Let’s work together to launch your vision, get expert guidance and make an impact.
Thanks for reading ❤️
Adam from Unicorn Club
Follow me on X or BlueSky
Connect on LinkedIn