The Founding — No. 001

I run a 25-person design practice with four managers. I also run a constellation of AI agents that handles research, editing, critique, and daily triage. The site you’re reading was supposed to be a portfolio. Today I changed my mind about what it should be — and I want to write down how that happened, because the way a practice decides something is part of what I’m trying to document.

The research phase that led here ran in a single day. The Librarian mapped the territory — thirteen voices, checked against what they’d actually published in 2026. The Researcher read demand data: eight questions design leaders are asking right now, scored against the evidence I already have. A third pass tore down the sites of Simon Willison, Maggie Appleton, Linus Lee, and Addy Osmani to understand what the builder-in-public genre actually does and whether it transfers to someone running a team rather than building tools alone.

What do I do with the time AI gives back?25 / 25

How do I stay credible when AI makes me feel early-career again?20 / 25

How do I maintain craft standards when AI lowers the average bar?16 / 25

Fig.01 — The top three of eight questions design leaders are asking, scored demand × lived evidence out of 25. The highest-scoring question already had a finished essay against it. Demand brief, 7 Jul 2026.

All three sessions arrived at the same finding. Nobody is publishing from inside a running, inspectable AI-augmented design practice at team-leadership scale. The commentators describe where design teams should go. The researchers survey what teams are doing. The individual practitioners document their own changed workflows. The seat for someone showing the practice itself — the decisions, the system, the ongoing evidence of what held and what broke — is empty. That’s the agency vantage, specifically. The gap is even narrower: no creative director at a design consultancy, publishing the re-architecture of their team in real time, with proof.

Coiners

Frameworks, from altitude

Advisors

Counsel, from outside

Builders

Practice, personal scale

The empty seat

Practice, team scale

Fig.02 — Thirteen voices, three occupied positions, one empty seat. Territory map, 7 Jul 2026.

I’ve been sitting on that material for weeks. Essays drafted. Cases built. A production system running daily. And a site that presents it as finished work, as credential, as evidence of things already resolved. That framing was defensible. Hiring decision-makers need something to inspect, and finished cases give them that. But the research found something else: the leaders who get the roles they want are known through their published thinking before they’re hired. The portfolio confirms; it doesn’t introduce. That meant a site built only as proof was already behind. The real work — the interesting work, the work nobody else is doing — is the search itself.

So the site shifts. The credential layer stays: cases, verified metrics, plates that demonstrate the hands still work. But the expedition log leads. The typeset record of a running practice, published as it runs.

Searched for

A design director or creative director publishing an ongoing record of AI-augmented team practice. Four targeted searches.

Found

No example. The genre runs in engineering leadership and among individual practitioners. In design leadership, the ground is empty.

Fig.03 — The genre absence. Closest structural analog: an engineering leader, not a designer — the altitude exists, the domain doesn’t. Builder-in-public teardowns, 7 Jul 2026.

The decision has a cost I priced in before making it. A log that stops reads as an abandoned practice — worse than no log. And every note requires an editorial gate: publish the reasoning, not the client; the system, not the specifics. That gate has no expiration date. I accepted it because the bought side of the trade is structural: the site, the OS, and the positioning stop being three separate projects. Every week the practice runs, the site gets truer.

Cost

A cadence obligation with a sharper failure mode — a stopped log reads as an abandoned practice. A per-piece editorial gate, no expiration date.

Bought

The site, the OS, and the positioning stop being three projects. The differentiator compounds in public instead of decaying in private. The empty seat, claimed while it’s still empty.

Fig.04 — The decision’s accounting, written before the decision was made. Decision record, 7 Jul 2026.

One thing corrected itself mid-process. A first draft of this system overengineered the cadence — weekly notes, aggressive publication targets, the kind of velocity that sounds rigorous on paper and produces thin work in practice. I pushed back. A monthly note that says something true beats a weekly note that says something thin. The log serves the practice; it doesn’t chase it. The cadence landed at monthly-grade: every note carries proof, at the Wattenberger bar — records the reader can inspect, not decoration beside prose.

This note is the first instance of that. The log begins by logging its own founding — the research that found the whitespace, the decision that chose to fill it, and the correction that kept the system from becoming another thing that needs managing. That’s the practice deciding — research, pattern recognition, a redirect when the evidence says so.

The seat was empty. I sat down.

Researched by the Librarian and the Researcher; drafted with the Editor; decided and passed by my eye.