Drag & Drop Website BuilderOut of date documentation leading to handholding without outside in approach to APIs while small support team supporting 3 disjointed portal experiences. In need of self serve by improving flows and removing friction to onboarding
Design Sprint Framework to follow for Sprint 0
The current process Map revealed a lot of manual steps in supporting the Sell side and Buy side partners. Challenges we have today can be summarized in 3 points:
# Very manual onboarding/handholding process with partners. Very few self serve capabilities on the portal available today (e.g. finding if partners are hitting a tier limit, or clean set of documentation, or simple onboarding process). Thus simplest of the questions partners have need to go to API support team which is understaffed thus causing delays in responses resulting in poor Partner satisfaction.
# No clear decision making/process on which APIs should be exposed to which partners, as we dont have support APIs as real products, and we dont have approval flows for granting access. This results in us losing control over who has access to which data and leads to us losing sensitive sales data.
# Our APIs are complex for partners to comprehend, and have a lot of business rules that partners need to learn without adequate documentation. This leads in loss of inventory... approximately 1% of unique inventory (monthly approx $6-7M) doesnt make it to the site due to these complexities in rules/policies.
Working session with stakeholders
During the 'Ask The Experts' brainstorming, the team came up with the following business workflow journey a broker goes through. We identified these in order to find out where our sell side partners have a role to play. The types of partners and the areas they serve are highlighted in blue.
Entire team worked together to use postit notes to write out individual HMW and sticked them on the all to gather the most ideas out and to share. We were all energized to participate in the HMW excercise and we all felt everyone contributed, voiced and heard.
Various challenges and questions around how might we fix them in the ideal world.
Team members are located in the same conference room and working closely together throughout the day.
Finally we narrowed down on the target set for Sprint 0 and for Sprint 3. This will get refreshed as we go along the discovery process through Sprint 0 and subsequent sprints.
Friday Prototype
- registration workflow using paper prototyping
- Exposing APIs via OpenAPI spec + creating a product
End-State 3 Sprint
- Dev Portal MVP?
- Expose MVP set of APIs + Products
Create listing API
Pricing Management API
Outdated Developer Portal
Created wireframe E2E process to complete not only MVP during the design sprint phase but also to deliever the entire API program.
Drag & Drop Website Builder