Week 12_Lecture 12
Week 12_Lecture 12
W12
Tertulia:…
2
3
4
• Your Workforce Is More Adaptable Than You Think
by Joseph B. Fuller, Judith K. Wallenstein, Manjari Raman, and Alice de Chalendar
5
Brazil China France
7
Accelerating Technological Change
Growing Demand for Skills
Changing Employee Expectations
Shifting Labor Demographics
Transitioning Work Models
Evolving Business Environment
8
Accelerating Technological Change
New technologies New technologies that Sudden technology- Technology-enabled
that replace human augment or supplement based shifts in opportunities to monetize free
labor human labor customer needs services or underutilized assets
General increase in the skills, technical knowledge, Growing shortage of workers with the skills for
and formal education required to perform work rapidly evolving jobs
14
Don’t just set up training programs—create a learning culture
15
16
• Implementation in Digital Transformation
17
OF DATA SCIENCE
Success PROJECTS NEVER
MAKE IT TO
13%
PRODUCTION!
Failure
87%
19
https://blog.nuclino.com/two-pizza-teams-the-
science-behind-jeff-bezos-rule
21
Project
Manager
Product Engineering
Design Team
Team Team
22
You as the entrepreneur
Workload
Product Team
Project timeline
23
24
Tech
teams
and
maximum
velocity
Gothelf, J. (2017). Lean vs. Agile vs. Design thinking: what you really need to know
25
to build high-performing digital product teams. Sense & Respond Press LLC.
Designers
Accurate description
of customer’s need
AND EACH
TIME WE Timely,
Useful,
HAVE NEW Product and Useable
CHALLENGES! Managers
On-time Product
Product
26
AGILE
LANDSCAPE
BY DELOITTE
27
Manifesto for Agile
Software Development
28
Agile Development values:
29
GOAL: Highest Quality, Lowest Cost, Shortest Lead Time
Just In Time High Quality Jidohka
Minimum resource required Mudi Muri Mura
to constantly deliver: Process • Detect abnormality
• Just what is needed min input max output • Stop and Respond
• In just the required amount • Harmonize humans and
• Just where it is needed Method machines
• Just when it is needed Minimum Lead Time
26 Shots 12 6 Shots 12
9 Shots on target 4 3 Shots on target 5
74% Possession 26% 17% Possession 83%
771 Passes 269 228 Passes 1,058
88% Pass accuracy 70% 67% Pass accuracy 91%
6 Fouls 14 9 Fouls 6
The secondary question is: Can we build a sustainable business model around the product?
Work in short cycles to choose whether to Continue, Pivot, Or Kill, based on customer feedback.
Ries, E. (2011). The lean startup: How today's entrepreneurs use continuous innovation to create radically 32
successful businesses. Currency.
Because of the force from
A tool of Lean Startup, which
tech team and demand for
clarifies two things:
high velocity
• What is the most critical • MVP has been transformed
things we must learn first on into product phase one
the project? (fewest number of features
• What is the least amount of for being ready to be
work we must do to learn it? shipped)
33
DESIGN THINKING
• Design thinking is a human-
centered approach to innovation
that draws from the designer’s
toolkit to integrate the needs of
people, the possibilities of
technology, and the requirements
for business success.
• TIM BROWN, EXECUTIVE CHAIR OF
IDEO
34
Design a (series
Clearly articulate
of) prototype(s) to
the problem you
test all or part of
want to solve
your solution Engage in
continuous short-
cycle innovation
Empathize Ideate process to
continually
improve your
design
Define Prototype
Brainstorm
Develop a deep
potential solutions;
understanding of
select and develop Test
the challenge
your solution
35
Integrate the
principles
Do not integrate
the processes
Gothelf, J. (2017). Lean vs. Agile vs. Design thinking: what you really need to know 36
to build high-performing digital product teams. Sense & Respond Press LLC.
PRINCIPLE ONE:
ALWAYS WORK IN SHORT CYCLES
Evidence based decision making.
Constant feedback and adjustment.
What is the next minimum viable product?
PRINCIPLE TWO:
HOLD REGULAR RETROSPECTIVE
Continuous process improvement.
What did you Like, Learn, Lack, and Long for?
PRINCIPLE THREE:
CUSTOMER VALUES ARE THE SAME AS BUSINESS
VALUES
Take user-centered perspective
You are done when your customer is done
PRINCIPLE FOUR:
GO AND SEE
Managing by walking around
Managing by facilitating the good pattern
PRINCIPLE FIVE:
ONLY TEST HIGH-RISK AND HIGH-VALUE
HYPOTHESES
Balancing product discovery with delivery work
Strategic
Easy wins
High
initiatives?
MATRIX Low
Business Value
Low Value Low Value
Low Complexity High Complexity
Low
Maybe Later! Deprioritize
42
PRINCIPLE SIX:
DO LESS, MORE OFTEN
Traditional research can become wasteful
Find the fastest way to learn the most important thing.
PRINCIPLE SEVEN:
WORK AS ONE BALANCED TEAM
Small (six to ten people), Dedicated (working on one thing at a time), Co-located,
Cross-functional, Autonomous, empowered teams
PRINCIPLE EIGHT:
RADICAL TRANSPARENCY
What is the project, why does the team work on it, How the work should be done, What
is the success look like.
Access to customer
Access to data
PRINCIPLE NINE:
REVIEW INCENTIVE STRUCTURE AND
PERFORMANCE MANAGEMENT CRITERIA
What are you being asked to do? vs. What are you incentivized to do?
PRINCIPLE TEN:
MAKE LEARNING A FIRST-CLASS CITIZEN OF
YOUR BACKLOG
Prioritize learning over delivery
48
•Domain expertise and statistics •Software engineering
•Familiarity with programming •Developing models and data pipelines
•Creating insight from data Project •Working with Software engineering
•Making decisions on Machine Manager team on model integration and
Learning approach & prototyping deployment
Machine
System Product Product Data Software Data
Learning
Architect Owner Manager Scientist Engineer Engineer
Engineer
49
Workload
Product Team
Project timeline
50
What does the What data do we How do we
business need? have / need? Is it organize the data
clean? for modeling?
Business Data
Understanding Understanding Business Data Data
Understanding Understanding Preparation
Data
Deployment Preparation
What modeling Which model How do
Evaluation Modeling techniques best meets the stakeholders
should we apply? business access the
objectives? results?
51
52
53
To increase from To position as the To optimize
12.7% to more than healthy diet competitive prices
20%. promoting grocery and boost revenue. Business Data
store. Understanding Understanding
54
Per capita consumption of vegetables
Business Data
Understanding Understanding
155.92
Data
155.8
Deployment Preparation
148.8
142.1
140.4
Evaluation Modeling
139.8
56
Store’s Masterfile Transaction database
17,774 food items 1.5B transactions
• Item name • Item code
• Class (fruit, vegetables, • Amount purchased Business Data
Understanding Understanding
meat, …) • Unit (weight, volume, …)
• Type (Spinach, Kale, …) • Price Data
• Form (fresh, frozen, …) • Customer code Deployment Preparation
• Unit of measurement • Date of purchase
Evaluation Modeling
FNDDS 13,829 Customers
• Demographics
• Food description •
Food and Nutrient Database
Socioeconomic condition
for Dietary Studies
• Nutrients (vitamins, • Size of household
protein, minerals, …) • Contact information
• Address 57
Selecting Data
Cleaning Data
Constructing New
Data
Integrating Data
Formatting Data
58
Store’s Masterfile Transaction database
17,774 food items 1.5B transactions
• Item name • Item code
• Class (fruit, vegetables, • Amount purchased Business Data
Understanding Understanding
meat, …) • Price
• Type (Spinach, Kale, …) • Customer code Data
• Form (fresh, frozen, …) • Date of purchase Deployment Preparation
• Unit of measurement • Store Code
Evaluation Modeling
FNDDS 13,829 Customers
• Demographics
• Food description • Socioeconomic condition
• Nutrients (vitamins, • Size of household
protein, minerals, …) • Contact information
• Address 59
Selecting Modeling Generating a Test
Techniques Design
60
Evaluating the Results Review Process
61
Customers with annual per capita vegetable
consumption
More than Between 240lb Business Data
Less than 80lb Understanding Understanding
240lb and 80lb
Data
Deployment Preparation
60 association rules for
different vegetables
Evaluation Modeling
• Min support = 30%
• Min Confidence = 90%
• Min Lift = 4
62
Business Data
Increase in vegetable sales per Understanding Understanding
customer (compared to previous year)
Data
Deployment Preparation
Store one:1.2% Store two: 1.4%
Evaluation Modeling
Store three: 1.9% Store four: 0.8%
63
THE SCIENCE OF
EVALUATION: A
REALIST
MANIFESTO
BY RAY PAWSON
64
Context Mechanism
1 •
•
Current situation
Resources and infrastructures
3 • Emerging challenges and
opportunities
• Stakeholders • Change management
• Culture • Ethical considerations
Program
2 • Design
• Development
• Right problem
• Right data
• Right value
• Right process
• Right deployment
strategy
• Implementation
65
Context
The question is not: what Population
works, or does it work? Program Black Box Outcome
Mechanism
The question is: what works,
for whom, why, under what
circumstances, and how? Context Mechanism Outcome
CMO Configuration
66
SO, SOME OF US
ARE NOT THATWhat do you think?
INTO Why do people eat less vegetables?
VEGETABLES??!
67
THE HEART OF
CHANGE
REAL-LIFE
STORIES OF HOW
PEOPLE CHANGE
THEIR
ORGANIZATIONS
BY JOHN P. KOTTER
68
Vegetables are too expensive.
69
Planning for Deployment
70
Customers with annual per capita vegetable Customers with annual per capita vegetable
consumption consumption
More than Between 240lb More than Between 240lb
Less than 80lb Less than 80lb
240lb and 80lb 240lb and 80lb
Annual household income more than $24K Annual household income less than $24K
Store one: 1.2% Store two: 1.4% Store one: 2.3% Store two: 2.4%
Store three: 1.9% Store four: 0.8% Store three: 2.1% Store four: 2.1%
72
Intended
Strategy • No Learning
Unrealized • No Control
Strategy
Learning
(Strategy as a Pattern)
74
STRATEGY
SAFARI A GUIDED
TOUR THROUGH
THE WILDS OF
STRATEGIC
MANAGEMENT
BY HENRY MINTZBERG
75
DIGITAL TRANSFORMATION
COMES DOWN TO TALENT
IN FOUR KEY AREAS
By: Thomos H. Davenport and Thomas C. Redman
76
Technology Data Process Change
77
• Emerging technologies like IoT,
blockchain, AI, and data lakes hold
transformative potential.
• Companies face challenges from
legacy systems (technical debt)
and skepticism about IT
departments' ability to lead
change.
Technology • Leaders need technical depth,
strategic foresight, and strong
Data Process Change
78
• Data quality is often poor, and
companies need to address this for
transformation to succeed.
• Transformation requires managing
new types of data (e.g.,
unstructured data) and integrating
massive amounts of proprietary
and external data.
Technology Data • Employees at all levels must
embrace roles as data creators and
Process Change
79
• Transformation requires rethinking
end-to-end customer processes
and breaking down silos.
• Effective process management
demands the ability to align teams,
improve workflows, and know
when to pursue radical change
versus incremental improvements.
Technology Data Process Change
80
• Leadership, teamwork, emotional
intelligence, and change
management are crucial for
navigating transformations.
• Teams must integrate "purple
people"—those who can bridge
technical and human-centric
elements—to ensure alignment.
Technology Data Process Change
81
Module THREE: Module TWO: Module TWO: Module ONE:
• Database • Data Strategy • Data Strategy • Social Impact of
• Big Data • Data and Bias Technology
• IoT • Data visualization Module FIVE: • Digital Transformation
• Cybersecurity and Organizational
• Cloud Computing Module THREE: • Data-Driven Strategy Culture
• 3D Printing • Digital Strategy
• Database • Platform Strategy Module SIX:
•
Technology
Blockchain
Data
• Big Data Process •
Change
Design Thinking
Module FOUR: Module SIX:
• Agile Development
Module FOUR:
• Machine Learning • Implementation • Lean
• Artificial Intelligence • Machine Learning • CRISP-DM • Context, Mechanism,
• Artificial Intelligence and Strategy
82
`
ANY QUESTION? W12