Thinking, in public
Field notes on design, engineering and growth — written by the people who ship the work. No thought leadership, just lessons with receipts.
Onboarding that activates: patterns we keep, patterns we've banned
Activation-focused onboarding: value-first flows, honest commitment devices, the checklist patterns that still work, and the seven anti-patterns we refuse to ship.
Dashboard design: answer first, chart second
Most dashboards are chart galleries that answer nothing. The question-first method: decision inventories, alert thresholds, and the five-element view that wins.
Getting the most from a remote studio
Hiring a distributed agency shouldn't mean slower decisions or lonelier projects. A buyer's guide to async rituals, time zones and demo cadence.
Empty, loading, error: the states that carry your trust
A field guide to the 20% of screens that carry 80% of trust: zero-data dashboards, skeletons vs spinners, and error copy that admits fault without over-apologising.
Your changelog is a marketing channel
Release notes that sell: segmented announcements, the in-product/email/SEO triple-duty, mining changelogs for case-study fodder, and cadence that signals momentum.
Discovery sprints: two weeks that de-risk six months
Our discovery sprint format, published: inputs, the ten days, the decision memo output, who must attend, and when discovery is a stall dressed as diligence.
Rebrand rollouts: the unglamorous crucial middle
Launch day is the easy part. The rebrand rollout plan: asset census, coexistence windows, internal enablement and honest measurement long after the applause.
Type pairing for brand systems: two voices, one argument
How we pair display and text faces in identity work: contrast logic, superfamilies vs strangers, the third-face rule, and testing in the ugliest context first.
The footer is a sitemap with manners
Footers are the most neglected designed surface on the web. A taxonomy of trustworthy footer patterns — navigation, reassurance, colophons — and what each one earns.
Feature flags without the graveyard
Flag discipline for product squads: lifecycle stages, a naming grammar, expiry automation, analytics hooks, and the monthly flag funeral that keeps codebases young.
How to design case study pages that win work
A case study page is a sales conversation in disguise. The anatomy we use: narrative arc, proof placement, honest metrics, and a CTA that never begs.
Design handoff that doesn't decay in a sprint
Why handoffs rot and how we stop it: living tokens, component specs over pixel mocks, motion specs with real easing values, annotations that survive sprints.