Three places to read. Longer essays when something needs the space, short notes from the week, and a running list of what's currently holding my attention. Published when it feels worth writing down, not on a schedule.
When a question needs more room than a note allows. Drafted slowly, published when the thesis holds together on re-read.
The hardest part of regulated design isn't the regulation itself. It's the translation layer between legal requirements, product logic, and human comprehension. Most of the visible design work is downstream of it.
Short observations from live client work and conversations. The things that don't need a full essay, but are worth writing down so I can find them again when a similar problem shows up.
If the rules aren't legible to the person being asked to follow them, the product isn't trustworthy. Which means compliance is upstream of copy, layout, and flow, not downstream. Most compliance failures I have worked on were translation failures, not adherence failures.
Not a transaction outcome. Every declined transaction has a specific person on the other side of it, a specific reason in some back-office system, and a specific gap between the two. The design is in the gap, not in the UI that shows the gap.
Almost every engagement has a gap between the written brief and the actual business risk underneath it. Scoping conversations that only read the brief skip the work. The first week is usually spent clarifying what the organization is actually asking for.
A workshop is an instrument for producing a specific artifact with a specific group of people in a specific time window. If the artifact is vague, the time is porous, or the group is wrong, it is a meeting with post-its. The prep is most of the design work.
A small running list of what has my attention this month. Some of it is directly useful to the work, most of it is just good company. Books, courses, and the occasional event worth crossing a city for.
Book
On picking the one metric that matters, and ignoring the rest until you've moved it. Translates well to studio work, where scope is the enemy.
Course
A refresher on service blueprinting with a public-sector lens. The exercises on cross-functional stakeholder mapping are the reason I signed up.
Event
Mostly for the hallway conversations. A quiet notebook, a full calendar of one-on-ones, and one strong cold brew a day is the plan.
Best for project inquiries, scoping conversations, and workshop requests. I answer within two business days.
A low-pressure intro call. Bring the system you're stuck on; I'll bring questions.