16. │
2. Event Storm the system
Highly collaborative modeling tornado!
Make sense of a complex business domain
with a common language for different tribes.
Identify trouble spots & starting points.
3. Select “Thin Slice(s)” of functionalities
Cut the monolithic business cake and pick a sweet
piece to start the modernization work.
1. Define Objectives & Key Results
Decide on direction for outcomes &
approach. Agree on objectives and refine
key results to measure those.
6. Produce tested and working code
Take low-level design decisions, select patterns to use, and
implement user stories. Time-bounded set of 1-week iterations.
4. Drafts the desired notional architecture
Model the process & data flows connecting the
business capabilities in sequence.
5. Fill the backlog
Craft actionable user stories.
Identify APIs, data & connections. API DATA
PUB / SUB EXT
STORIES UI RISKS
SERVICE A
7. Cloud Modernization Patterns
Reuse and document the learned modernization
patterns as recipes in a “cookbook” (e.g. wiki).
Consolidate knowledge and accelerate team
velocity.
100% Enablement Focus 🙌
Our team pairs with your’s throughout the process
keeping a tight feedback loop, constant knowledge
transfer and maximum shared learning
18. │
Facilitated workshop
with a cross-section of
business and IT people
Use stickies to roughly
define the logical flow
of a system or process
Talk it through!
Discover underlying
risks and opportunities
Discover the business flow
and find ideas on where to
start - in a few hours
19. │
Here is what it looks
like (Pre-COVID)
Decompose Online
Commerce Monolith -
Mapping Boundaries,
Identifying Risk, etc.
20. │ 20
Here is what it looks
like (Remote-Only)
Pharmacy Benefits
System for US
Insurer - 60m lines of
code on Mainframe
Why? Domain
mapping, API
boundary definition,
risk and opportunity
identification
Informs Future State
Architecture Design
and How to Move
the Needle Quickly
31. │
Small product team that markets
to internal customers while
automating everything
PLATFORM AS PRODUCT
A mixture of on-the-job and
classroom enablement, along
with maximum pattern reuse
CxO metrics, coordination and
oversight across all parallel work
teams, coordinated by OKRs
Independent teams maximizing
automation and moving quickly
toward parallel outcomes
EXECUTION AT
SCALE
EDUCATION &
ENABLEMENT
PROGRAM &
MEASUREMENT
Navigator
Understand root
cause and get
consensus on a
path forward. Get
hands on ASAP!
Platform
Automation
Platform team
automates more,
reducing toil
A Few Projects
Targeting progressively
more complex business
problems, build and
modernize slices of
existing system
Enablement
Create program to
build and support a
learning
organisation
Scale
Scale practices,
methodologies and
culture across the
organisation
BIG Wins
Measurement starts
on day 1 but is
magnified as
workload increases
(as driven by the
Transformation
Program)