The internal site rebuild is still in testing, and I'm writing its formal documentation now, the work that has to happen before something built in three days is safe to call finished. Showing what was possible got me handed something bigger: I'm the lead on a new design system for the team.
What "design system" means here
Take our most modern system, strip it into reusable components, and document each one so pages stop reinventing their own button or table. Same instinct as the reusable CSS classes and tokenized colors from the rebuild, formalized into something the team can reference instead of something that lives in my head.
Why now
I didn't ask for it, and it didn't come from the internal rollout directly. It came from the EMR product waiting on contract acceptance: with that stuck, the plan became to use the time building the design page instead of waiting on legal. Same pattern as the ADA agent: the more the results are concrete and demoable, the more I get handed the next piece that used to be nobody's job. It's also bigger than anything I've led on my own, with two junior developers assigned to help and two weeks to the first demo.
Where it stands
There's a working prototype now, and the plan is to reveal it to clients rather than roll it out internally first. It isn't a broadly adopted internal system yet. The test is the same as the agents: not whether I can build it, but whether the documentation is good enough that someone who wasn't in the room, including the two junior developers helping on it, can use the components correctly.