Design Authority Isn't About Title. It's About Pattern Recognition.
I spent years watching people with "Senior" in their job title lose arguments to junior designers who just happened to show up with the right context at the right time. William Eric Richmond's work on design authority cuts through that noise because it treats influence as something you accumulate through repeated, predictable behavior rather than something you request from management. It's more boring than it sounds. That's why it works. Richmond's central idea is that design authority operates on a rhythm. You establish it by showing up consistently with well-reasoned positions, then letting that track record do the heavy lifting. Most people try to manufacture authority through assertiveness or framing. Richmond flips that: authority emerges when your decisions become legible to stakeholders over time. They start anticipating your input because your past input was consistently useful. The practical mechanism is simpler than the name implies. You pick a domain—let's say component library governance or accessibility compliance—and you become the person who ships clear, documented decisions in that space. Not opinions. Decisions with reasoning attached. After three or four cycles of this, engineers and product managers stop asking you for permission and start asking you for input. That shift is the pulse. That's the authority materializing.
I ran into this directly last year when we were restructuring our design token architecture. I had just joined, my title was middling, and half the engineering leads didn't know who I was. I picked one narrow problem: the naming convention for spacing tokens was creating merge conflicts across three repos. I wrote a single decision record, laid out the tradeoffs, linked it to our existing design system documentation, and posted it where people actually worked. No meeting. No slide deck. Just the thing. Two weeks later, someone else on the team hit the same problem in a different area and referenced my decision record without being asked. That's the rhythm kicking in. You don't build authority by volunteering for cross-functional meetings. You build it by making your reasoning visible so that when the next similar situation arises, people follow the path you already paved. Here's what most people get wrong about this approach. They treat it as passive. It's not. You're actively curating a body of public reasoning. The difference matters because passivity means you wait for problems to come to you. The rhythmic approach means you identify recurring friction points and publicly resolve them before they become arguments. There's a window where this strategy is extremely powerful, which is before the organization has established norms around a given problem space. Once norms exist, your decision records just reinforce what's already there, and the authority-building effect diminishes.
Another counter-intuitive thing: the narrower your domain, the faster the rhythm establishes. I watched a colleague try to build authority across five different problem areas simultaneously. She published good work in all of them but never crossed the threshold where anyone treated her as *the* person. Meanwhile, another designer who owned just the color system—nothing else—was consulted on decisions she never asked about because her name kept appearing in the same context. Depth beats breadth for authority accumulation. Always has. There are real limitations to this model that Richmond doesn't always emphasize enough. It doesn't work in organizations where decisions are made by fiat from the top down. If your leadership makes choices without referencing design reasoning, your decision records become archival documents rather than operational tools. I saw this happen at a company where the CPO would announce features on Slack and expect design to execute. No amount of well-documented token decisions changed that dynamic. In those environments, authority has to be negotiated through informal relationships, not published reasoning. Another failure mode is pace. The rhythmic approach requires you to publish decisions faster than the organization needs them. If you're spending three weeks crafting a single decision record while the team is already working around the problem, you've missed the window. My workaround was to adopt a tiered documentation system. Quick decisions got a single paragraph with a link to context. Complex decisions got the full record. Most of my decision output was tier one. The rhythm depended on volume, not perfection.
Get the Full Details
The terminology Richmond uses sometimes obscures how mechanical this actually is. "Design authority" sounds like a philosophical concept. It's really just reputation compounding through visible decision-making. The moment you strip away the abstraction, it's a productivity system with social consequences. You ship reasoning. People adapt to it. Your influence grows proportionally to how many people have adapted. If you're trying to apply this, start by auditing where decisions currently get made in your organization without design input. Not the big strategic decisions. The small ones. The ones that repeat. Pick one of those recurring decision types and publish your reasoning for it. Do it in a format your colleagues actually read. Then do it again when the same decision surface comes up three months later. The consistency is what converts from activity into authority. The alternative is the more common path where designers wait for meetings to matter. That path works fine until it doesn't, usually right when you need influence the most and have none banked. Richmond's framework just makes the bank account visible.
