10. ■ Build and expose core APIs
■ Include adoption as a factor when
prioritising
■ “Innovation” APIs to drive excitement
10
API roadmap
Inside-out
■ Track demand
■ Evangelise to all dev teams to
become a part of SDLC
■ Join/set up steering groups,
architecture boards
Outside-in
14. 14
■ API adoption by both internal and
external consumers is critical
■ APIs need to be easy to find:
catalogue in developer portal
■ APIs need to be easy to access:
ensure self-serve access
■ APIs need to be easy to use:
documentation must exist before
delivery is signed off
Understand the consumption lifecycle
■ Capture and optimise the user journey
for each persona and type of
consumer
■ Consider a pilot or beta programme
with a subset of internal/external
consumers
■ Identify all stakeholders that need to
sign off delivery and invest in ongoing
adoption
Define and document the adoption path
Adoption: turning APIs into value
16. 16
Metric Actual Target Metric Actual Target
Average service uptime 100% 100% Project time to market
7.5
weeks
6 weeks
Number of secured
microservice endpoints
89% 100%
Customer satisfaction
score / NPS
9.8 9.8
Average response time 5 ms < 5 ms
Time to onboard new
partners
15 days 1 week
Time to resolve errors
92
minutes
< 15
minutes
Internal developer
retention
99% 95%
Microservice traffic
growth Q/Q
7% 10%
Revenue growth
through digital
channels
£19
million
£15
million
17. Wrap
1. Are microservices going to add value?
--------
2. Have a plan
3. Avoid analysis paralysis with MVPs and iterative improvement
4. Bring all your stakeholders on the journey with you
5. Understand, measure, and celebrate business impact
6. Constant feedback and course correction
17