STKI Summit 2022 presentation Jimmy

STKI.INFO
1
Copyright@STKI_2022 Do not remove source or attribution from any slide, graph or portion of graph
STKI IT Knowledge Integrators
Company Confidential
Page 1

STKI.INFO
2
Our new website and part of its contents:
Page 2

STKI.INFO
3
Our new website and part of its contents:
Page 3

STKI.INFO
4
examples of our content (video)
Page 4

STKI.INFO
5
Let's start with some definitions:
Page 5

STKI.INFO
6
Page 6

STKI.INFO
7
Product-led
Organization
Digital Transformation Disruption
Xtreme (Post-digital) Adaptation
Page 7

STKI.INFO
8
intro
Page 8

STKI.INFO
9
My 2021-2022 reading list
I recommend the following:
Magazines & Books
(I read all of them)
Page 9

STKI.INFO
10
Product Management Books
Page 10

STKI.INFO
11
Product Management Books
Page 11

STKI.INFO
12
Business Books
Page 12

STKI.INFO
13
Economics Books
Forecasting books
Page 13

STKI.INFO
14
forecasting
Page 14

STKI.INFO
15
WHEN IT RAINS IT POURS:
global & local events affecting business technology in Israel
15
• War between Russia and Ukraine
• Price of oil and gas increases
• Inflation maybe pushing the world into a recession.
• Interest rates increasing after years of “free money”
• “STARTUP” BUBBLE , profit the new name of the game
• Massive layoffs will occur in startups and will get bad, very
quickly, likely sometime mid next year (in Silicon Valley more than 700
start-ups have laid off over 100,000 workers this year)
• Possibility that the health situation deteriorates
• 2022 election’s results & 2023 State Budget
• Several hyperscalers opening Israeli Regions
• Technical Debt low priority in budget allocations
• CEOs pushing IT (again) to be only an enabler
Page 15

STKI.INFO
16
Predictions That Were So Wrong
But I Will Do Some Anyway
Page 16

STKI.INFO
17
Predictions for Israel @ 2023
a year of market challenges, bold decisions, and disruptive innovation.
• Hybrid Workspace & Workers
• Hybrid-cloud Core Technology Stack
• SaaS Enterprise Solutions
• Smart Automation
• (processes, testing, operations, etc.)
• Cloud First Development
• Communication & Knowledge Software
• FinOps services
• Zero-trust SASE
• Product-led organizations
• IT as the Business
• Technology & Products Division
• AI & Data Science
• Ecosystems & Super Apps
• Blockchain
• AR (augmented reality) (not metaverse)
• Israeli-Based Hyper-scalers
• Industry-specific Clouds
• Open Industry Integration (APIs)
• Composable Software (center office)
• Regularly modified & tested BCP
• Self-service Analytics
• Outsourcing
• Staff Augmentation
• Managed Services
• Co-location services
• Low code (citizen developers)
• Metaverse
• CDOs (digital or data) powered by IT
• Software licenses to subscriptions
• CAPEX to OPEX
• Uniting NOC & SOC centers
• Technical Debt is starting to be paid:
• Old on-prem ERP to cloud
• Closing on-prem Data Centers
Page 17

STKI.INFO
18
Predictions for Israel @ 2023
a year of market challenges, bold decisions, and disruptive innovation.
• Hybrid Workspace & Workers
• Hybrid-cloud Core Technology Stack
• Smart Automation
• (processes, testing, operations, etc.)
• Cloud First Development
• Communication & Knowledge Software
• FinOps services
• Zero-trust SASE
• Product-led organizations
• IT as the Business
• Technology & Products Division
• AI & Data Science
• Ecosystems & Super Apps
• Blockchain
• AR (augmented reality) (not metaverse)
• Israeli-Based Hyper-scalers
• Industry-specific Clouds
• Open Industry Integration (APIs)
• Composable Software (center office)
• Regularly modified & tested BCP
• Self-service Analytics
• Outsourcing
• Staff Augmentation
• Managed Services
• Co-location services
• Low code (citizen developers)
• Metaverse
• CDOs (digital or data) powered by IT
• Software licenses to subscriptions
• CAPEX to OPEX
• Uniting NOC & SOC centers
• Technical Debt is starting to be paid:
• Old on-prem ERP to cloud
• Closing on-prem Data Centers
Page 18

STKI.INFO
19
Page 19

STKI.INFO
20
FOURTH INDUSTRIAL REVOLUTION
FOURTH INDUSTRIAL REVOLUTION
Most people don’t realize that
DIGITAL DISRUPTION is the FOURTH INDUSTRIAL REVOLUTION.
Page 20

STKI.INFO
21
First Industrial Revolution: The evolution of society in the eighteenth and nineteenth
centuries from mostly agrarian to industrial and urban, which was mostly driven by
mechanical innovations such as the steam engine.
Second Industrial Revolution: The explosive growth of industries from the late 1800s to
the First World War. This was driven by mass-production techniques, electric power, and the
internal combustion engine.
Third Industrial Revolution: The widespread change (mixing computing & communication
to the masses) beginning in the 1980s with PCs, cellular phones and internet, due to new
electronic technologies.
Fourth Industrial Revolution: Modeling & mixing the physical, digital, and biological worlds
through algorithms (AI) & technologies. The major driver is the availability of massive
computing capacity from Hyperscale Cloud Technology Providers
Page 21

STKI.INFO
22
Availability of Hyperscale Cloud Technology’s massive computing capacity
is one of the biggest technological shifts of our lifetime;
it is going to fundamentally change everything.
Page 22

STKI.INFO
23
• The GOOGLE effect: separation of humans and information
• The WHATSAPP effect: Free communications, death of distance
• The ZOOM effect: Virtualization of family, classroom & business meetings
• The WOLT effect: Virtualization of food delivery experience
• The FACEBOOK effect: Virtualization of human relationships
• The AIRB&B effect: Virtualization of short-term accommodations
• The LINKEDIN effect: Virtualization of specialized knowledge and employment opportunities
• The AMAZON effect: Virtualization of customer experience
• The WAZE effect: Virtualization and crowdsourcing of automobile travel
• The SPOTIFY, APPLE MUSIC effect: Personalization of music consumerist
• The INSTAGRAM, SNAPCHAT, YOUTUBE effect: Virtualization of content sharing
• The YELP, TRIPADVISOR effect: Virtualization of Consumer Reviews
23
Customers loved pandemic-era services and
want them to continue, even if they’d never
used them pre-pandemic.
Page 23

STKI.INFO
24
• The GOOGLE effect: separation of humans and information
• The WHATSAPP effect: Free communications, death of distance
• The ZOOM effect: Virtualization of family, classroom & business meetings
• The WOLT effect: Virtualization of food delivery experience
• The FACEBOOK effect: Virtualization of human relationships
• The AIRB&B effect: Virtualization of short-term accommodations
• The LINKEDIN effect: Virtualization of specialized knowledge and employment opportunities
• The AMAZON effect: Virtualization of customer experience
• The WAZE effect: Virtualization and crowdsourcing of automobile travel
• The SPOTIFY, APPLE MUSIC effect: Personalization of music consumerist
• The INSTAGRAM, SNAPCHAT, YOUTUBE effect: Virtualization of content sharing
• The YELP, TRIPADVISOR effect: Virtualization of Consumer Reviews
24
Page 24

STKI.INFO
25
“every
company
(including
yours)
will be a
software
company”
No matter what industry
a company is in, it relies
on software to plan and
deliver on key business
objectives.
• means through which
we communicate,
collaborate, and
execute.
• factor that shapes
both the employee
and customer
experience.
Page 25

STKI.INFO
26
“every
company
(including
yours)
will be a
software
company”
No matter what industry
a company is in, it relies
on software to plan and
deliver on key business
objectives.
• means through which
we communicate,
collaborate, and
execute.
• factor that shapes
both the employee
and customer
experience.
Page 26

STKI.INFO
27
FinTech:
Software firms that automate the delivery of financial services
Innovation has long been focused on the consumer banking. Business banking
remains stuck in neutral and business services such as real time treasury,
payments and receivables will be available first by FinTechs
Competing directly with TRADITIONAL BANKS & FINANCIAL INSTITUTIONS
InsurTech:
Software firms that make it possible for customers to research and buy insurance
online. Digital tools had made it easy to write auto insurance profitably online, 15 minutes to save
15%.
Competing directly with TRADITIONAL INSURANCE COMPANIES
creative destruction disruptive innovation
Page 27

STKI.INFO
28
FinTech:
Software firms that automate the delivery of financial services
Innovation has long been focused on the consumer banking. Business banking
remains stuck in neutral and business services such as real time treasury,
payments and receivables will be available first by FinTechs
Competing directly with TRADITIONAL BANKS & FINANCIAL INSTITUTIONS
InsurTech:
Software firms that make it possible for customers to research and buy insurance
online. Digital tools had made it easy to write auto insurance profitably online, 15 minutes to save
15%.
Competing directly with TRADITIONAL INSURANCE COMPANIES
creative destruction disruptive innovation
Page 28

STKI.INFO
29
• All of you (today) offer a variety of software
services that make it easier (self service) for
costumers to solve their specific “problem”
• You will offer more and more software
products (as will your traditional and tech
competitors) giving more & more value to
customers
YOUR COMPANY will have to be a
SOFTWARE COMPANY
Page 29

STKI.INFO
30
• All of you (today) offer a variety of software
services that make it easier (self service) for
costumers to solve their specific “problem”
• You will offer more and more software
products (as will your traditional and tech
competitors) giving more & more value to
customers
YOUR COMPANY will have to be a
SOFTWARE COMPANY
Page 30

STKI.INFO
31
DIGITAL DISRUPTION:
Migration from the Third to the Fourth Industrial Revolution Era.
re-defines the value proposition of the business using technology products
that significantly change customer behavior and market conditions.
Most companies will become
product-based software companies
DIGITAL TRANSFORMATION:
Effects of the Fourth Industrial Revolution
Continue transforming business activities, processes & competencies
delivering products that deliver value
drive advantages (impacts) for companies and customers.
Page 31

STKI.INFO
32
distinguishing between:
disruption takeoff and sustained transformation :
• Successful DISRUPTION is the tipping point for successful
operation of the enterprise from one generation of the
industrial revolution to the next,
• TRANSFORMATION during the industrial revolution needs to
sustain the new business model. The disruption is incomplete
if the new business model cannot be built with an eye toward
perpetual evolution.
70% of enterprises fail in the disruption/transformation efforts:
There are two ways in which they can fail.
• first, fail to take off
• second, to maintain momentum, and they end up crashing.
Page 32

STKI.INFO
33
distinguishing between:
disruption takeoff and sustained transformation :
• Successful DISRUPTION is the tipping point for successful
operation of the enterprise from one generation of the
industrial revolution to the next,
• TRANSFORMATION during the industrial revolution needs to
sustain the new business model. The disruption is incomplete
if the new business model cannot be built with an eye toward
perpetual evolution.
70% of enterprises fail in the disruption/transformation efforts:
There are two ways in which they can fail.
• first, fail to take off
• second, to maintain momentum, and they end up crashing.
Page 33

STKI.INFO
34
• Imagine attaching a World War II airplane engine to a modern commercial jet aircraft.
The old engine would not have the power needed for the plane to take off and stay aloft.
• And yet, most enterprises undergoing digital transformation do exactly that ,when they rely on
older versions of IT organizational structures and capabilities to power the change
• The digital enterprise needs a new design of engine (i.e., IT function) to power takeoff and staying aloft,
just as modern aircraft needed a new breed of engines in the 1950s.
• The modern engines for digital are the new “Product Teams” based organization
and cloud-based solutions.
This can be fatal for a fully
synchronized digital transformation.
Page 34

STKI.INFO
35
Is Your IT Function a Piston Engine or a Gas-Turbine Engine?
Different enterprises have different names:
• CIO, ‫מנמ‬
"
‫ר‬ , VP Technologies, CISO
• Chief Data Officer, Chief Digital Officer,
• Chief Business Services, Chief Transformation Officer,
Most enterprises also have or are thinking about multiple organizations
doing these functions.
STKI strongly believes that all these enabling functions need to come
together. That is the major part of the “engine upgrade”
IT technologies, IT scope of operations, and IT skills all have incredibly
short life cycles. What’s new is that the
piston-engine version of IT has reached an inflection point.
IT needs a consciously different engine. We’re no
longer talking evolution; we’re talking about a
dramatically different redesign.
Page 35

STKI.INFO
36
old IT
new IT
Page 36

STKI.INFO
37
• The new IT function is not just about new technology
platforms, a new charter of work, or newer skills; it is
about leading all the other functions and business units
in the company to new product-enabled business models.
• The digital enterprise needs digital to be understood by
every function, but powered by the new IT.
• Which is why STKI believes that the new function needs a
totally new charter and a new name
• Products and Technologies Division .
‫וטכנולוגיות‬ ‫מוצרים‬ ‫חטיבת‬
Products and Technologies Division.
Page 37

STKI.INFO
38
Evolution of software
development
1990 -2022
Over the past 30 years, STKI has seen a rapid evolution in:
• how we ORGANIZE,
• DISCOVERY of what we want TO DO and what
we need NOT TO DO
• DELIVERY of the final product
Page 38

STKI.INFO
39
1990s:
Business leaders owned discovery and a
project manager with programmers tried to
deliver it on schedule and on budget
Page 39

STKI.INFO
40
The Evolution of Modern Software “Discovery & Delivery”
 Discovery happened once a year in an annual budgeting process
 Projects with fixed timelines were assigned to specific development teams.
 A project manager managed the work, budget, and schedule.
 Waterfall project management was used (mapping into distinct, sequential phases).
 Projects were often delivered late and over budget.
 Business needs often trumped customer needs.
 The enormous time lag between business requirements and the delivery of technology
that answered those needs, led to the cancelling of many projects.
 Business requirements, and customer requisites changed during this time, and the
final product did not meet the then current needs.
 Teams learned that many times customers never used it (offered limited value)
1990s: Business leaders owned discovery (they decided what to build)
project manager with programmers tried to deliver it on schedule and on budget
Page 40

STKI.INFO
41
Page 41

STKI.INFO
42
2001: A group of software engineers (in a
mountain retreat) proposed the Agile manifesto.
Page 42

STKI.INFO
43
2001: A group of software engineers (in a mountain retreat)
proposed the Agile manifesto.
 Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software (continuous delivery of value)
 Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
 Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
 Businesspeople and developers must work together daily throughout the
project.
 Build projects around motivated individuals. Give them the environment and
support they need and trust them to get the job done.
 The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
Cont. 2 : Evolution of Modern Software “Discovery & Delivery”
Page 43

STKI.INFO
44
 Working software is the primary measure of progress.
 Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
 Continuous attention to technical excellence and good design enhances agility.
 Simplicity the art of maximizing the amount of work not done.
 The best architectures, requirements, and designs emerge from self-organizing
teams.
 At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly.
Cont: Manifesto for Agile Software Development
Page 44

STKI.INFO
45
2002-2019: Agile in name only
Faking Digital
You aren't Agile or Digital because of what you call yourself.
You are Agile or Digital because of what you do.
Page 45

STKI.INFO
46
2002-2019: partial agile (agile in name only) & faking digital
 Discovery and Delivery are completely separate functions
 Business leaders didn’t give up ownership of “discovery” they kept their original ideas
 Most “delivery” teams weren’t good at estimating unpredictable work (time or budget)
 Biweekly sprints killed any chance of finding a continuously sustainable pace or innovation
ideas
 Continued operating on an annual budgeting cycle, making flexibility nearly impossible.
 Teams measured by features they delivered, not whether anyone used it or if it created any
value
 Very few projects were successful and used by clients for over 5 years (Chaos Report)
 Faking Digital is the practice of implementing technologies for operational & financial
effectiveness and adding new “front-end” applications without changing the business itself.
Page 46

STKI.INFO
47
• The digital age began 75 years ago, (invention of the
transistor)
• Digital calculators & watches introduced 50 years ago
• Internet is more than 50 years old
• First browser created 30 years ago
• IBM PC was introduced 40 years ago.
• Apple is 45 years old
• STKI is 30 years old
• Google is 25 years old
• iPhone is 15 years old
NOW is the time to move beyond the
digital transformation buzzword
Disruptions at the start of a New Industrial Revolution Era
demand a different game plan than simple
transformations of the current business model.
Digital is an “old mantra”
Page 47

STKI.INFO
48
Let’s not confuse
Faking Digital with Digital Disruption
Faking Digital
is the practice of implementing technologies for operational
& financial effectiveness and adding new “front-end”
applications without changing the business itself.
Corporate immune system working at full speed.
DIGITAL DISRUPTION
is the Xtreme Adaptation of the organization’s
business model by changing the
DNA-culture of both the enterprise & industry
digital
disruption
Faking
Digital
Page 48

STKI.INFO
49
The Standish Group
published a study called
the “Chaos Report,” which
cited that
nearly 84 percent
of projects will
either fail or go
over budget.
.
Page 49

STKI.INFO
50
The Chaos Report also
said that
“most features are
rarely or never used.”
During this era, it's not
just that we were not
building software
predictably; we were
not even building the
right things.
Page 50

STKI.INFO
51
2020: Lessons from the
pandemic era and startup
knowledge spillover
Implementing the “real” thing
-”lean and agile development”-
Page 51

STKI.INFO
52
It is time to press ahead with Digital Disruption,
learning from and applying the techniques from Start-ups,
transitioning into a “software company”
Start-ups are all about Xtreme adaptation based on
PRODUCTS and EMPOWERED TEAMS
change change change
large established business
make millions of excuses and obstacles for
not adapting
Page 52

STKI.INFO
53
During the covid-19 era most projects were led by junior managers,
moved fast, didn’t wait for meetings, business & IT merged and gave impressive results
Merging DISCOVERY and DELIVERY into ONE team
PROJECTS moved toward PRODUCTS
(IT moved from enabler of the business to being the business itself) :
• Collective-business wisdom of the zoom IT crowd-cloud
• Business knowledge of most front-line team members
• Comfortable offering non-standard processes and solutions for business outcomes
• Challenged assumptions giving honest and constructive feedback
2020 - : Lessons from the pandemic era
Page 53

STKI.INFO
54
 Questioning how discovery (what to build) decisions were made
 Pushing discovery decisions from business to product managers and the whole product team.
 Rather than just validating ideas, teams are co-creating with customers (from the beginning)
 Combining the team’s knowledge of what’s technically possible with the customer’s knowledge of
their own needs, pain points, and desires to build better products.
 Teams are adapting to changes in the market, in customer needs, and in technology, in real time.
 Adding Lean Practices to Agile Principles
 Include Value Stream Management
 Optimize the whole process. Without having a view of the whole process/system, we won’t know
what to optimize.
 add activities, processes, and automation that validate that the software meets the customer’s
needs.
2020 - : Lessons from startup knowledge spillover (LEAN + AGILE)
Page 54

STKI.INFO
55
The whole PRODUCT team contributes to
Continuous “Discovery & Delivery”
Continuous
Discovery
Continuous
Delivery
Product
life cycle
Design Thinking
The whole team is involved in customer interviews, mapping the customer
journey, ideating on solutions, discussing delivery options, developing the
code, supporting the product and responsible for outcomes
not a one-time activity, it is never
done, it must evolve
build, rebuild, ship & support
Page 55

STKI.INFO
56
Software products today “SHOULD” be conceived, designed, built, and
delivered by a cross-functional team that is part of the value stream
Team’s actors
Page 56

STKI.INFO
57
Team’s actors
Page 57

STKI.INFO
58
Page 58

STKI.INFO
59
Recently, STKI analysts received many questions from teams
chasing frameworks, tools or methodologies,
dreaming that each new innovation will suddenly magically,
effortlessly unlock the door for the
move from project to product based
Page 59

STKI.INFO
60
 OUTCOME ORIENTED mindset (outcomes rather than features / outputs)
 CUSTOMER-CENTRIC mindset places the customer at the center & that the
purpose of every business is to create and serve a customer.
 COLLABORATIVE mindset requires cross-functional nature of product work and
rejects the siloed model
 VISUAL mindset stepping beyond spoken and written language and into the
power of spatial thinkers by drawing, externalizing thinking mapping knowledge.
 EXPERIMENTAL mindset encourages scientific-thinking by identifying assumptions
and gathering evidence.
 EVOLVE FROM A PROJECT MINDSET TO A CONTINUOUS MINDSET infuse
discovery continuously throughout your delivery.
Product Team success
not just tactics or tools but the need to change the mindset.
Page 60

STKI.INFO
61
PROJECT PRODUCT
FUNDING Annual
Continuous with frequent
checkpoints for funding and
resources changes
TIMELINE Formal start and end dates
Continuous, ongoing, no firm end
dates but when not needed it is
retired
TEAMS
Matrix orchestration across
departments and technical
domains (silos)
Multidisciplinary, breaking
functional & specialization silos,
most of the team is full time
METRICS
On-time and on-budget
(sometimes also business
outcomes)
Business centric metrics
(customer satisfaction, profit,
market share, etc)
Page 61

STKI.INFO
62
FEATURE
based
on-prem
“application”
PROJECT
development
cost
OUTCOME based
PRODUCT
development cost
yearly
“USAGE PLUS
SUBSCRIPTION”
variable cost
(SaaS
consumption
model)
yearly usage
variable
expenses cost
on-prem cloud
PROJECT PRODUCT
Page 62

STKI.INFO
63
Three different types of Product Teams
Page 63

STKI.INFO
64
Platform Teams
provide common services to be implemented once but used in
many places, help in managing complexity by encapsulating
particularly difficult or specialized areas of the product.
Pini Cohen
Experience Teams
responsible for how the product is experienced (getting a
solution for the problem) by users in the form of apps, UIs,
solutions, or journeys.
Galit Fein
Data Product Teams
Focus on the process of collecting, organizing, storing, and sharing
data within an organization, they use that data to build a feature
for an experience team or build a whole data product.
(types: output data as a service, data-enhanced products, and data as
insights)
Einat Shimoni
Page 64

STKI.INFO
65
The goals of EXPERIENCE AND DATA TEAMS are
to solve problems for users and customers,
The goals of a PLATFORM TEAM is to enable the
experience and data teams to better solve problems
TEAM OBJECTIVES not the only work that a product
team is responsible for, also “keep‐the‐lights‐on”
We do need to keep an eye on this ongoing work because,
if it spikes, the team won't be able to make much progress
on their team objectives.
Page 65

STKI.INFO
66
STKI.INFO
66
Page 66

STKI.INFO
67
STKI.INFO
67
Page 67

STKI.INFO
68
Page 68

STKI.INFO
69
Beware of
“Group-Think”
Page 69

STKI.INFO
70
Outcomes vs Outputs (features)
Lessons from Top Tech Companies
an OUTCOME is a CHANGE in human
behavior** that DRIVES business results.
** “human behavior” can apply to users’ behavior, customers’
behavior, or staff and employee behavior
Page 70

STKI.INFO
71
• In the old days setting project goals wasn’t that hard.
• If you’re making cars, you’re done when they roll off the
assembly line.
• But when making software products, done is less obvious.
• When is Microsoft word done? When is google done?
• Software systems are never done. We just decide to stop
working on them, or make an endless list of features and ask
our teams to work on that list—forever?
• The problem is that features can be finished and delivered and
“work perfectly” but still deliver NO VALUE
how many of these
buttons do you
use in real life?
Our world is full of “features” that work as specified
and yet deliver no value.
Page 71

STKI.INFO
72
 Starting with outcomes, rather than outputs, is
what lays the foundation for product success.
 By shifting focus to the impact on both
customers and business results (outcomes) the
team is clearly communicating the value it will
create.
 When the businesspeople leave it up to the
team to explore the best outputs that might
drive the outcome, they are giving the team
the latitude they need to create value for the
customer.
from an output (features) mindset to an outcome (business) mindset
Page 72

STKI.INFO
73
Don’t mix
Assumptions with Knowledge
MVP is just a buzzword that
means “experiment”
in order to turn
assumptions into knowledge.
run
experiments
what are the customer
behaviors that drive
business results?
Page 73

STKI.INFO
74
Outcomes (human behaviors that drive business results) is what happens
when you deliver the right features.
You could manage a team by telling them what to make:
that’s called managing outputs. It’s a problem because
features don’t always deliver value.
You could manage a team by asking them to target some
high-level business result That’s called managing
impact. It’s a problem because it’s not specific enough.
What you want is to manage with outcomes: ask
teams ”what is the customer behavior change that we
are looking for?” That allows them to find the right
solution
Page 74

STKI.INFO
75
STKI.INFO
75
Product Manager combines (numerous inputs) into a coherent Product Roadmap
outcome
based
roadmap
Page 75

STKI.INFO
76
Products and Technologies Division
Disruption & Transformation Road Map
Page 76

STKI.INFO
77
Disruption & Transformation Road Map
(where are you?
Page 77

STKI.INFO
78
Traditional IT with steroids
The Digital Disruption & Transformation Road Map
Page 78

STKI.INFO
79
1. Traditional IT with steroids
• Moving from “data processing” to “information technology”
• You’re finally budgeting and prioritizing “technical debt” payment
• You’re trying to upgrade technology to the latest platforms (from
older (on-prem to SaaS applications) including cloud, AI, etc.
• Business (CEO, CFO) don’t see ROI in upgrades (misunderstanding
of technical debt)
• Enterprise applications are not connected
• Infrastructure department is over-staffed (too many technologies)
• No Industrial Engineering group to optimize processes
• You’re not really “transforming the enterprise.”
• You’re “digitalizing” some operations. And seeing benefits.
• You have some fake digital products, customer relations, or
operations.
The Digital Disruption & Transformation Road Map (2)
Page 79

STKI.INFO
80
Page 80

STKI.INFO
81
This is the cost of having to work on:
• Outdated infrastructure (software/ hardware)
• Outdated software (several versions behind latest vendor version or
old onprem versions)
• ERP and/or CRM
• Core systems based on outdated technologies (not in itself broken
systems) but are critical to day-to-day operations
• Outdated data management tools (ETL, DW, BI)
• Upgrading and automating old processes and killing non-necessary
ones
• Inability to integrate applications or processes (in-house or partners)
• Missing documentation
• Un-commented configuration
• Un-documented code changes
Traditional IT with steroids:
Finally paying our “technical debt”?????
Page 81

STKI.INFO
82
This is the cost of having to work on:
• Outdated infrastructure (software/ hardware)
• Outdated software (several versions behind latest vendor version or
old onprem versions)
• ERP and/or CRM
• Core systems based on outdated technologies (not in itself broken
systems) but are critical to day-to-day operations
• Outdated data management tools (ETL, DW, BI)
• Upgrading and automating old processes and killing non-necessary
ones
• Inability to integrate applications or processes (in-house or partners)
• Missing documentation
• Un-commented configuration
• Un-documented code changes
Traditional IT with steroids:
Finally paying our “technical debt”?????
Page 82

STKI.INFO
83
SILOED IT
Page 83

STKI.INFO
84
2. SILOED IT
• Bureaucracy, old processes, technical debt hinder
automation, transformation and disruption at scale
• Parts of the organization are experimenting with
transformational business models and products
• Experimenting with data products
• Moving to best-of-breed enterprise applications
• There is no enterprise-wide product strategy to
completely transform your business model itself.
• Very strong Disruption DNA firewall
Page 84

STKI.INFO
85
Upon returning, had to declare to
customs the items he was
bringing back from the moon:
mainly rock and dust samples.
Aldrin was reimbursed exactly $ 10 for “travel
expenses. Luckily, he was not responsible for
paying for actual transportation from Earth
to the moon—or even to Cape Kennedy,
Florida, where Apollo 11 launched, as he
had a government planes for that.
OLD PROCESSES NEVER DIE:
Bureaucracy, old processes for NASA astronaut Buzz Aldrin when he came back from the moon
Page 85

STKI.INFO
86
IT Dilemma:
managing the middle way
Page 86

STKI.INFO
87
3. IT Dilemma: managing the middle way
• Your enterprise has a mix of old and new digital business
models, processes, and products.
• Implementing
• self-service data services
• Data Science projects
• API gateways and management tools
• All new applications are following a corporate-wide strategy.
• Disruption DNA firewall still exists
• Management is not convinced of the need of disruptive
applications (Parmenides Fallacy)
Page 87

STKI.INFO
88
(especially xxxtech startups)
Page 88

STKI.INFO
89
Enlightened IT
Page 89

STKI.INFO
90
4. Enlightened IT
• You’re delivering industry-leading customer results, innovative
digital products, and best-in-class operational efficiency.
• Implementing enterprise-wide data & digital literacy programs
• Hippo vs data
• Implementing open industry standards
• You’re not winning always
• You’re digitally optimized for the moment.
• Re-organizing the business-technology relationship
by building “PRODUCT TEAMS” and the new
“Products and Technologies Division”
Page 90

STKI.INFO
91
Hippo Dominated Vs Data Obsessed
data literacy programs
Page 91

STKI.INFO
92
Page 92

STKI.INFO
93
5. Products and Technologies Division
• Experience, Data and Platform teams deliver business impacts
• Value as the main outcome with an enterprise-wide product strategy
• Transformation is fully synchronized & disruption is in the DNA
• The organization has transformed into a software company
• The organization is:
• Data-driven
• Cloud first development
• Simplifies business processes using intelligent automation
• Provides personalized concierge value as-a-service
• Experiments with Blockchain and Augmented Reality
• Orchestrates ecosystems in order to build B2B and B2C super apps
• All this powered by the Products and Technologies Division
Page 93

STKI.INFO
94
Any questions
Page 94

STKI Summit 2022 presentation Jimmy

More Related Content

Similar to STKI Summit 2022 presentation Jimmy

More from Dr. Jimmy Schwarzkopf

Recently uploaded

STKI Summit 2022 presentation Jimmy