Plain answers to hard questions about design, access, and trust.
I write about accessibility, trust and safety, and AI-native product research and design. Every article opens plainly for the leaders who make the call and then goes deep for the people who do the work.
They arrive in your inbox as an EPUB for your phone, tablet, or e-reader, and you hear the day Accounted For can be ordered.
Check your email. Your first chapters are on their way.
While you wait, here are three good places to go next.
- Accessibility and inclusive design
- Trust and safety
- AI-native product research and design
- Digital life management
- History of design, science, and technology
- Accessibility and inclusive design
- Trust and safety
- AI-native product research and design
- Digital life management
- History of design, science, and technology
The articles I would hand you first.
- Trust and safetyWhen a design tricks people out of their money or their data, you can report it.Submitting Dark Patterns to the Federal Trade CommissionRead the article
- AI-native product research and design · Skillshare classClaude stays on brand when your brief says what to write, with a reason, and not only what to avoid.How to make Claude stay on brandRead the article
- Accessibility and inclusive designAccessibility is where good design starts, not a box to tick the week before launch.Why accessibility comes firstRead the article
Everything I write serves one goal: products people can trust.
Build it so everyone can use it.
Audits, testing, and design that work for disabled people, written for the leaders who fund the work and the teams who do it.
Keep people safe and help them recover.
Fraud, scams, and the recovery paths that fail people, plus how to organize, protect, and prepare your own digital life.
Design with AI and keep your standards.
How I research, design, and prototype with AI, and the rules that keep the work honest and on brand.
Organize, protect, and prepare your digital life.
Plain steps for your accounts, passwords, photos, and records, so the people you love can find what they need.
Learn from the people who built it first.
Stories from the history of design, science, and technology, and what they teach the teams who build products today.
Take the first chapters of Accounted For with you, free.
The Switch That Taught Us to Stop Blaming Pilots
B-17 crews kept retracting their landing gear on the runway. The fix was a knob shape, and the lesson still applies to AI products today.
The Challenger Launch Decision as a Design Lesson
The engineers had the data that predicted the Challenger seal failure. Here is how the charts hid the danger, and what that teaches anyone who builds dashboards.
What Three Mile Island Taught Control Room Design
A panel light showed a valve as closed while the valve was stuck open. Here is how Three Mile Island changed control room design, and what the accident teaches software teams.
Why Accessibility Comes First
Accessibility is where good design starts, not a box to check the week before launch. Here is why starting early pays off, and what to do at each stage of the work.
How to Make Claude Stay on Brand
Claude stays closer to your brand voice when the brief says what to write, shows real examples, and sits where Claude reads the brief before every draft.
Submitting Dark Patterns to the Federal Trade Commission
When a design tricks people out of their money or their data, you can report it. Here is how to report dark patterns to the FTC and what happens next.
Your Digital Systems Need to Work When Life Does Not Go as Planned
Use the Return Path Test to make deadlines, documents, accounts, responsibilities, and trusted help recoverable.
Your Family Needs a Tech-Help Rule Before Someone Gets Scammed
How to choose trusted helpers, verify requests through known contacts, and make unexpected remote-access and tech-support scams harder to fall for.