Business process digitalisation
summary
Company processes get recast as service boundaries with an API contract style template so teams agree inputs, SLAs and acceptance criteria; projects decompose into themed teams and reusable extensions, capturing 80–90% of scope in contracts; internal services become sellable products; training cycles enforce delivery standards quarterly; result is predictable scaling from a two person start to ~600 people with fast growth years (45% and 60%) and an observed 12× reduction in overtime.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:09Scaling challenges
- 7:22Digitalizing business processes
- 9:56API paradigm in processes
- 15:21Contract-based standardization
- 22:32Scaling efficiency
- 26:37System engineering
- 31:11Productizing services
- 35:32Measuring success
- 38:07Departmental collaboration
- 40:34Closing remarks
related talks
21mPragmatic Strategies for Global API Integration
41mWhy your company needs an internal API and what you should do about it
18mWinning in the API economy
25mMaking microservices a behaviour not a buzzword
08mMicroservices at Scale
26mFrom project to reality let's explore some API
30mMonolith to Microservices
29mProductize Your Services! A Path Towards Effective Microservice Development
