About the project
To create a pitch to a potential client on how our design services could help them design an impactful API portal
Results
We got the deal eventually and a 2 year contract to launch the product
Role
Lead designer
Planning the pitch
Problem framing to set the stage
A key part of design thinking is also problem framing. To help clients see the problem clearer to why they needed design services, I framed the problem and opportunity to start the pitch.
Specifically, I aligned the outcome that design could achieve with their specific goals which is
- Publicise their APIs for other developers to use and
- Cement their position as a forward-thinking leader in the banking industry
Design strategy
We treat the documentation and content organisation as the key user experience. That meant that while the design isn’t as UI heavy (no fancy components, just plain ol’ text), we still believe that organising and designing documentation is key to ensuring the success of the adoption of an API portal.
UI matters, too
A teaser of what the product could look like
Reducing friction to onboard
Interviews with users revealed that the common barriers to using a new API is the messy documentation, and not knowing where exactly to start.
We propose to reduce friction in a few ways
- A quick-start guide
- Feature use cases to resolve the cold start problem
