How a stalled internal tool became infrastructure
The project had no budget, no clear owner, and a codebase frozen for eight months. Within one quarter, it had a funded roadmap and a new product identity.
The team believed they needed a better UI. They had a dependency management tool developers found confusing — too many states, unclear ownership indicators, a workflow that assumed context no one had.
But the interface wasn't the problem. The problem was upstream: no shared definition of "done," two teams with different mental models of what the tool was for, and a product goal set before actual users were consulted.
I spent the first three weeks not touching Figma.
SDLC Journey Map · 5 research sessions · 3 team contexts
I ran five contextual inquiry sessions with developers across three teams. Not usability tests — I wanted to watch how people moved through their actual work.
Three fractures emerged: two handoff points where context reliably evaporated, one governance gap where no one was accountable for a class of decisions, and a silent dependency that nobody had mapped.
The most important discovery wasn't in the data. It was in the room: nobody had ever seen all the steps together before.
Product positioning doc · Stakeholder alignment sessions
The existing framing positioned the tool as "a dependency checker." That framing explained why it had no budget — it was a utility, not a product.
I worked with the product owner to reframe it as a Dependability Framework: something that gave the whole engineering organization shared language and a single source of truth for software health.
"Dependability" was the word that made everyone nod in the same meeting for the first time.
MUI design system · Component library · Journey map governance doc
The MUI-based design system I built wasn't about visual consistency. It was about transferability. Every component was documented with the decision behind it, not just the spec.
The test of a good handoff isn't whether it's legible. It's whether the team uses it without you.
I was done when I could be wrong in a decision and the team would catch it.
Project moved from "paused" to active roadmap with budget
Clear product owner established across two previously siloed teams
Design system adopted as standard across 3 developer tool products
"The biggest leverage point wasn't the design. It was naming the thing correctly. "Dependability Framework" was doing work that no UI could do — it aligned people who had never agreed on what they were building."