Developer Portal
There was no portal. Everything went through tickets. I created a self-service portal to take that queue off support.
The context
The Developer Portal is one of Sensedia's products: in it, users create and customize their own developer portal.
The problem
The portal did not exist. The path was to open a ticket, and a support team created and updated the portal. Every delivery depended on that team, and every change became one more ticket.
The decisions
- I interviewed Sensedia's own developers to inform the design.
- I created the portal from scratch as a self-service platform, where users update and customize the portal whenever they want, without opening a ticket.
- I presented a full-scope proposal, which caused real friction with leadership because of the deadline. I decided to reduce the scope to a viable version.
Left out of the first delivery: more customizable screens, documentation with better filters and a sidebar.
Screens and artifacts
Current state
Portal delivered with reduced scope, without more customizable screens, without documentation with better filters and without a sidebar. The goal was to eliminate support tickets, but no formal metric was measured after launch.
What I would do differently
Align scope expectations with leadership before deepening the proposal, not after.