a Fortune 100 developer platform had powerful infrastructure but a fragmented experience: legacy tools, inconsistent workflows, and documentation that made routine work harder to learn.
i led the product-design effort to unify the dashboard, information model, and supporting guidance around the way developers actually work.
how it works
- organize by developer intent
navigation follows the task—build, test, ship, and monitor—instead of internal systems. - make status comparable
services use one visual language for health, ownership, and required action. - bring guidance into the workflow
documentation and examples appear where decisions are made.
product outcome
the system reduced relearning across tools and gave teams a consistent foundation for adding new developer workflows.
designed for learnability
- research shaped the structure
interviews and task analysis revealed where platform language diverged from user language. - consistency carries meaning
shared patterns are tied to shared behavior, not decoration. - documentation is part of the product
examples, defaults, and recovery paths complete each workflow.
the work made a complex internal platform feel less like a collection of systems and more like one coherent developer product.