Скачать или смотреть Inside a CIO’s Playbook: No-Code, ERP & 2-Week Sprints in a 73-Year-Old Public Transit Enterprise

Most CIOs inherit 6- to 12-month IT backlogs.
This CIO promised to deliver in 2 weeks; and used no-code + ERP + field empathy to make it real.
Here’s how it happened inside a 73-year-old transportation business with 600+ buses.

When Mark Brown joined Dyson Group as CIO, he walked into a classic enterprise scenario:

✔ Oracle JD Edwards as the ERP
✔ Oracle Integration Cloud as middleware
✔ proprietary operational systems running in silos
✔ safety + compliance + regulatory constraints
✔ a multi-year backlog of projects
✔ no unified transformation owner

But instead of requesting more budget, more developers, or multi-year cycles, Mark declared a different mandate:

“Give me two weeks.”

The boardroom couldn’t believe it.
The industry didn’t expect it.
And the delivery model had to change dramatically for it to work.

WHAT ENABLED THE SHIFT

Mark brought in a CIO playbook rooted in:

✓ people, process, technology - in that order
✓ field immersion — riding buses, shadowing drivers, working workshops
✓ architecture-first mindset — leverage before replace
✓ no-code as the rapid app delivery layer
✓ iteration over perfection - 2-week demos vs year-long releases

This eliminated the “Software Development Death Cycle” in favor of empowered subject-matter experts and faster business feedback loops.

WHY NO-CODE MATTERED

No-code allowed the IT team to:

✔ build apps without long dev cycles
✔ expose ERP data without custom code
✔ unify systems without rip-and-replace
✔ deliver visible wins quickly
✔ involve SMEs directly in shaping solutions

The first quick wins created trust, then momentum — the currency of transformation.

KEY THEMES COVERED

● CIO transformation strategy
● No-code for enterprise & ERP
● 2-week sprint model in a legacy org
● People - process - tech approach
● ERP + middleware + proprietary systems
● Field empathy as leadership tool
● Safety + compliance constraints
● Architecture vs backlog thinking
● Leveraging existing tech before buying new

WHO THIS EPISODE IS FOR

✔ CIOs & CTOs
✔ Enterprise Architects
✔ Transformation Leaders
✔ No-Code & Platform Teams
✔ ERP Leaders - Oracle / SAP / JDE
✔ Operations & Compliance Teams
✔ Product & Innovation Offices