Surviving the hyperautomation low code bubble
summary
Banks take weeks to open an account even though competitors do it in minutes, so the concrete fix is end-to-end orchestration not point‑to‑point scripts: use BPMN executable XML plugged into a workflow engine (example code as a Spring Boot app on GitHub), add reusable REST/Twilio connectors and DMN decision tables, and expose those via a SaaS/platform or a process automation Centre of Excellence so business users stitch yellow‑bucket flows while developers handle red‑bucket complexity following a golden path.
AI-written summary · about
chapters (13)
- 0:00Hyperautomation and low-code intro
- 2:27Spaghetti integrations break automation
- 5:13Process orchestration explained
- 9:42Hyperautomation goals and talent gap
- 13:10Roles and process complexity
- 17:42Process complexity and criticality
- 20:34Low-code for developers
- 26:16Business user connectors
- 30:50Team topologies for automation
- 34:00Microservices and cognitive load
- 38:18Pro-code vs low-code summary
- 41:47Goldman Sachs low-code case
- 42:11Q&A: Target audience and lock-in
related talks
45mPro-Code vs Low-Code in Microservice Orchestration
25mDevelop Automated Workflows in Seconds
53m5 tips on how to deliver software effectively by aligning coding and business best practices
23mThe New Neobanking Stack
35mAgentic Workflows: Stories from the Engine Room
24mAutomating Access to Development
41mRethinking Low-code
24mBizDevOps