- The document discusses the complex systems approach to benefit impact analysis and digital transformation.
- It argues that digital transformation is about more than just technology and involves many stakeholders across and outside the organization.
- The key is to take a whole-enterprise perspective and focus on values, not just money, to ensure all stakeholders benefit and trust is maintained.
digital marketing , introduction of digital marketing
ICS/IASA Conference 'How I learned to stop worrying...'
1. Benefit Impact Analysis
– Complex Systems Approach
(or: ‘How I Learned To Stop Worrying
And Love All This Big Scary
Digital-Transformation Stuff’)
Tom Graves, Tetradian Consulting
IASA, Dublin, June 2017
4. This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0).
To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/
Tetradian www.tetradian.com
Project By Date
VersionHolomap
shared-enterprise / indirect-context
includes community, government, non-clients, anticlients, others
includes investors, beneficiaries
market / direct-context
includes competitors, regulators, recruiters, trainers, journals, others
transactional-context
includes suppliers / providers, customers / consumers, transactional partners
prospect prospectsupplier / provider
partner
client / consumer
partner
organisation
service-in-focus
…such as this…
36. Digital transformation:
“It’s not not about the technology”
...but it’s also mostly not about
the technology.
See post ‘Digital-transformation – it’s about (much) more than just digital’:
http://weblog.tetradian.com/digital-transformation-its-about-much-more-than-just-digital/
– Andrew McAfee
37. Everyone wants to sell us
ready-made answers...
...yet the real challenge is in
finding the right questions
...“solutions!”
38. Finding the right questions
can be even more important
than finding the right answers
(in part because questions
tend to stay the same,
whereas answers will change
with time and context)
40. A business is a construct, an association of
human beings combining capital and labor
to make something.
That business has precisely the same social
responsibilities as the people it consists of.
The responsibility to play fairly ... and to
create value for all those it engages with.
– Seth Godin
Seth Godin: ‘Off the hook with Milton Friedman’
http://sethgodin.typepad.com/seths_blog/2017/06/off-the-hook-with-milton-friedman.html
41. “An organisation is bounded by
rules, roles and responsibilities;
an enterprise is bounded by
vision, values and commitments.”
“An organisation is bounded by
rules, roles and responsibilities;
an enterprise is bounded by
vision, values and commitments.”
Tom Graves, Mapping the Enterprise, Tetradian,
2010
Enterprise as story
Organisation aligns with structure, enterprise with story.
We need a balance of both for the architecture to work.
42. Perspectives across the boundary
We need to understand each of these perspectives
See post ‘Digital-transformation – it’s about (much) more than just digital’:
http://weblog.tetradian.com/digital-transformation-its-about-much-more-than-just-digital/
43. Outside-in…
CC-BY Fretro via Flickr
“Customers
do not appear
in our processes,
we appear in
their experiences.”
Chris Potts, recrEAtion, Technics, 2010
44. ‘User experience’
is more than the behavior
of your product or service;
it covers all interactions
your customers have
with your company.
– Bard Papegaaij
See post ‘The whole experience’ http://weblog.tetradian.com/the-whole-experience/
45. If the organisation says it ‘is’ the enterprise,
there’s no shared-story - and often, no story at all.
Whose story?
46. The minimum real enterprise is the supply-chain
- a story of shared interactions and transactions.
Whose story?
47. The organisation and enterprise of the supply-chain take
place within a broader organisation of the market.
Whose story?
48. The market itself exists within a context of ‘intangible’
interactions with the broader shared-enterprise story.
Whose story?
54. A stakeholder
is anyone
who can wield
a sharp-pointed
stake
in our direction…
CC-BY-NC-SA evilpeacock via Flickr
Who are the stakeholders?
(Hint: there are a lot
more of them than we
might at first think…)
56. Boundary of identity vs control
Outsourcing does not outsource responsibility!
See post ‘Boundary of identity, boundary of control’: http://weblog.tetradian.com/boundary-of-identity-vs-control/
57. The boundary-of-control
delimits what the managers
think the organisation is…
the boundary-of-identity
delimits what everyone else
thinks the organisation is.
See post ‘More on boundary of identity versus control’: http://weblog.tetradian.com/more-on-identity-versus-control/
Outsourcing does not outsource responsibility!
58. ...we need a whole-context model like this.
To make sense of GDPR...
61. ‘Business-model mechanics’
Strategyzer: ‘Why Some Business Models Are Better Than Others’
http://blog.strategyzer.com/posts/2015/4/7/why-are-some-business-models-better-than-others
62. (includes Value Proposition Canvas to link organisation and customer)
Business Model Canvas
supplier stuff stuff we do customer stuff
money stuff
Strategyzer: https://strategyzer.com/canvas/business-model-canvas
66. “Real-world detail can break
the best-looking business-model
without even breaking out a sweat.
“We need to have a better sense
of that detail before committing
ourselves to a lot of hard work
and ultimate heartache.”
See post ‘Hidden risks in business-model design’
http://weblog.tetradian.com/hidden-risks-in-business-model-design/
67. Market rules and interactions impact on customer-relations
Need to expand out to market...
70. Don’t try to ‘boil the ocean’!
Always aim for ‘Just Enough Detail’
71. And remember, it’s fractal…
…fractality provides simplicity, protection against overload
CC-BY-NC-SA gjshepherd via Flickr
72. Enterprise
as a system
...or, to be more pedantic,
system-of-systems interacting and intersecting
with other systems-as-systems-of-systems,
but we won’t worry about that just yet...
73. Start with an assertion:
Everything in the enterprise
is or represents a service.
(If so, we can describe everything
in the same consistent way.)
74. A tension exists between what is, and what we want.
The vision describes the desired-ends for action;
values guide action, describing how success would feel.
Why anything happens
75. A service represents a means toward an end
– ultimately, the desired-ends of the enterprise-vision.
The nature of service
76. Services serve.
(That’s why they’re called ‘services’…)
What they serve is the story,
via exchange of value.
(And if we get that right,
they can sometimes make money, too.)
77. Services exchange value with each other, to help each
service reach toward their respective vision and outcome.
Relations between services
78. Value-flow is ‘horizontal’, but connection is first made by
‘vertical’ connection to shared-value and value-proposition
How connection happens
79. Each service sits at an intersection of values (vertical)
and exchanges of value (horizontal)
Values and value
80. Each service sits at an intersection of values (vertical)
and exchanges of value (horizontal)
Values and value-flow
81. Services link together in chains or webs, as structured
and/or unstructured processes, to deliver more complex and
versatile composite-services.
Supply-chain or value-web
82. Many different forms of
value, investment, benefit
– where the meaning of ‘value’
arises from the enterprise-story
84. No distinct dimension for money?
No need: money is a composite of
‘conceptual + aspirational’
– an arbitrary number
associated with a brand
(Money-as-cash is ‘physical + conceptual + aspirational’
– but that’s another whole story...)
88. Value-proposition is not
“the fancy name
for your product or service”
– it’s how you
propose to deliver value
to the entire shared-enterprise.
(Value-proposition provides the link
between why, how and with-what.)
89. Keeping on-track: value-balance
See post ‘Services and Enterprise Canvas review – 3D: Investors’
http://weblog.tetradian.com/services-and-ecanvas-3d-investors/
90. We need to consider
investments and returns
of every applicable type,
to and from
every type of stakeholder.
(‘Applicable type’ is determined
by the shared-enterprise values.)
91. Keeping on-track: validation
See post ‘Services and Enterprise Canvas review – 3C: Validation’
http://weblog.tetradian.com/services-and-ecanvas-review-3c-validation/
93. How does value flow across
the shared-enterprise?
What drives value-transitions
and value-transforms?
How does each interaction help
to build and maintain trust?
95. Identify the elements that help to pull from one phase to the next
Five Elements and service-cycle
Performance
Purpose
People
Preparation
Process
PoliciesValues
Events
Completions
Success
(start here)
Trust /
Commitment
(Initiating-Events)
(Completion-Events)
97. Every instance of service is also a project in its own right
Project-cycle and service-cycle
Performance
(adjourning)
reporting etc
Purpose
(forming)
strategy etc
People
(storming)
HR etc
Preparation
(norming)
scheduling etc
Process
(performing)
production etc
99. The service-cycle applies across all of these connections
Enterprise and service-cycles
shared-enterprise
market
procurement
product-
development
+ marketing
receive
materials to
inventory
make shoes
store and
ready shoes
for shipment
sales and
service
accounts
payable
manage
budget,
operations
accounts
receivable
identify and
support
suppliers
obtain
materials
pay for
materials
identify and
support
customers
deliver
shoes
be paid for
shoes
supplier customer
gain supplier
respect
gain customer
respect
verify supplier
satisfaction
verify customer
satisfaction
gain / maintain market respect
gain / maintain enterprise reputation
verify market satisfaction
verify enterprise satisfaction
100. BUT…
if we try to take short-cuts,
the cycles will break down…
(short-cuts give seemingly-better results in short-term,
guaranteed-failure in the longer-term…)
105. Yes, we need to get it right
on managing the money
– yet also on managing
all other forms of value as well
106. “The NHS, though it needs to
run efficiently, is not a business.
“It is about diagnosing, treating and
caring for patients in the best way.
See post ‘The Demoralised Man’ http://weblog.tetradian.com/the-demoralised-man/
“All its other functions should be
subservient to that.”
– Heather Wood
107. “The NHS, though it needs to
run efficiently, is not a business”
...neither are most businesses!
See post ‘The Demoralised Man’ http://weblog.tetradian.com/the-demoralised-man/
Always start from the values,
not the money
111. The core metric
of all business is
trust
Trust that we will keep our promises
Trust that we will keep on-track to our values
112. Making money
is a side-effect of
staying on-track to values
Simple.
(though rarely easy...)
Saving money
is a side-effect of
being effective on-purpose
113. If we focus too much on money,
we lose track of value.
If we focus on the ‘how’ of value,
we lose track of the ‘why’ of values.
Always start from the values.
(Not the money.)
116. Contact: Tom Graves
Company: Tetradian Consulting
Email: tom@tetradian.com
Twitter: @tetradian ( http://twitter.com/tetradian )
Weblog: http://weblog.tetradian.com
Slidedecks: http://www.slideshare.net/tetradian
Publications: http://tetradianbooks.com and http://leanpub.com/u/tetradian
Books: • The enterprise as story: the role of narrative in enterprise-
architecture (2012)
• Mapping the enterprise: modelling the enterprise as
services with the Enterprise Canvas (2010)
• Everyday enterprise-architecture: sensemaking, strategy,
structures and solutions (2010)
• Doing enterprise-architecture: process and practice in the
real enterprise (2009)
Further information: