Enterprise Architecture: Perspectives, conflicts and how to resolve them

Enterprise Architecture:
Perspectives, conflicts and how to resolve them
Tom Graves, Principal Consultant, Tetradian

Hi.
(maybe I should update
my profile-photo...?)
I’m Tom.
I’ve been around
the EA scene
for a while now.

These days
I’d describe myself as
a maker of tools for change
– all sorts of tools...

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…

Sales-
pitch!
https://leanpub.com/tb-changes/
New
book!

…enough of an intro?
Okay, let’s get on with the show!

To make sense of
perspectives...
...we’ll need to go
back to the basics
...question our assumptions

Important questions to ask:
What’s the point?
What’s the purpose?
What are we striving for?

Why architecture?
What is its real purpose?

The aim of all architecture...
Things work better
when they work together,
on purpose.
(It’s about effectiveness.)

What are the keys to
architecture?

The Architect’s Mantra…
I don’t know…
(but I know someone who does, or how to find out)
It depends…
(and I know what it depends on, and why)
Just enough detail…
(and I know what the right level of detail would be)

Everyone wants to sell us
ready-made answers...
...yet the real challenge is
to find the right questions
...“solutions!”

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)

Mainstream
‘enterprise’-architecture is:
- relentlessly IT-centric
- riddled with inconsistencies
- riddled with
hidden assumptions...

A matter of perspective
...in reality, the BDAT-stack is an arbitrary special-case

...further confused by misframed ‘Business Architecture’

...and even worse at whole-enterprise scope

In short,
it’s a mess...
...which may be why
management keep yelling at us?

So how do we
get out of this mess?

Expose the assumptions...
If we change the perspective,
we can expose, explore and highlight
the hidden assumptions

People,
Process,
Technology!
Maybe the real problem
is our usual approach:

Technology
CC-BY-SA xdxd_vs_xdxd via Flickr
Process
People
The usual architecture view

…“can I go to sleep now, please?”

So how do we find these
‘missing perspectives’?
- and maybe have some fun doing it, too…

Short answer:
Raid the kids’ toy-box!

https://www.amazon.co.uk/Viga-Wooden-Train-Set-49-Piece/dp/B00486QD0S/

Toy-train as
service-metaphor…

…who or what are the various
uses / users of the service?

…how do those uses intersect?

…how might those uses conflict?

…what decisions
need to be made?

…what scheduling /
prioritisation do you need?

…what infrastructure
tolerances do you need?

…how does it interconnect
with other services?

…what disruptions
could careless
users cause?

…what disruptions could the
service cause for others?

…how, where, with what must it
intersect without connecting?

…how might others impact
your infrastructure?

…what impacts could that
have on service-delivery?

…what are the hazards,
potential sources of disruption?

…what happens
when
external risks
eventuate?

…what happens when
the service itself fails?

…what disruptions
could failures cause?

…which brings us back to…
a matter
of perspective!
- yeah, which way we look at things does kinda matter here…

Perspectives and journeys
Service-delivery is a journey of interactions
where ‘inside-out’ (the organisation’s perspective)
touches ‘outside-in’ (the customer’s / supplier’s perspective)

Outside-in…
CC-BY Fretro via Flickr
“Customers
do not appear
in our processes,
we appear in
their experiences”
Chris Potts, recrEAtion, Technics, 2010

Every service has its own myriad of stakeholders
Whose story?

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…)

Will stakeholders defend us...?
CC-BY dspender via Flickr
...or work against us?

How can we explore this
with execs and others?

Short answer:
CC-BY-SA Tetradian
back to the toy-box!

To make sense of this,
we need first to
map out the context

The entirety of architecture?
business
architecture
information-
systems
architecture
infrastructure
architecture
“enterprise
architecture”
organisation

organisation
The idea that IT is all is... odd...

organisation
A myriad of other services...

organisationsupplier customer
Links with suppliers, customers...

transaction
across the supply-websupplier-
prospects
customer-
prospects
supplier’s
supplier
customer’s
customer
The overall transaction-web...

market
(direct-interaction)
includes competitors, regulators, recruiters, trainers, journalists, analysts, others
transaction
prospects
customer-
prospects
supplier’s
supplier
customer’s
customer
Outward to the market...

...and beyondshared-enterprise
(indirect-interaction)
includes community, government, investors, non-clients, anti-clients, others
market
(direct-interaction)
includes competitors, regulators, recruiters, trainers, journalists, analysts, others
transaction
prospects
customer-
prospects
supplier’s
supplier
customer’s
customer

In generic form, for any service...
services implemented by any appropriate mix of people, machines, IT
indirect-interaction
direct-interaction
transaction
service-in-
focus
partner partner

So far, so abstract.
And so yawn, too…
Instead, let’s make it come alive,
via the human dimension
– just with simple mini-figures

Stakeholders we already know...
CC-BY-SA Tetradian
...such as managers and execs
Manager

The immediate supply-chain...
CC-BY-SA Tetradian
...suppliers, customers and more
ManagerSupplier Customer

Also other internal services...
CC-BY-SA Tetradian
...any number of these!
Facilities Accounts
IT
Production
Planning
Engineering

Internal stakeholders
CC-BY-SA Tetradian
(These may be under direction,
but never truly under control!)
ManagerFacilities Accounts Production Planning Engineering

Supply-chain extends further...
CC-BY-SA Tetradian
...to almost any distance
Supplier’s
supplier
Customer’s
customer

Then there are our prospects...
CC-BY-SA Tetradian
...for suppliers, customers etc
Supplier prospect
Customer
prospect

Transaction stakeholders
CC-BY-SA Tetradian
Supplier Customer
Supplier prospect
Customer
prospect
Supplier’s
supplier
Customer’s
customer
‘Us’

Outward to the next layer...
CC-BY-SA Tetradian
...direct-interactions in the market
Competitor
s
Regulators Recruiter Journalist Analyst

Market stakeholders
CC-BY-SA Tetradian
Competitor
s
Regulators Recruiter Journalist Analyst
(These interact with us, but do not
transact for products/services)

Outward to shared-enterprise...
CC-BY-SA Tetradian
Other services Families
Governmen
t
Big-picture
Anticlient
s
Criminals
...indirect-interactions of all kinds

Enterprise stakeholders
CC-BY-SA Tetradian
(These interact only indirectly,
but sometimes with major impacts)
Infrastructure
and other
‘broad scope’
services
Families,
community
and more
Government,
politics, other
countries
Big-picture,
observers of
‘big-story’
Anticlients
– inherent,
betrayal
Hackers
and other
criminals

That’s a lot of stakeholders...
CC-BY-SA Tetradian

Each transaction or interaction
will tend to follow the same
consistent pattern
Using the human dimension
makes it easier to follow
how the pattern unfolds

A cyclical pattern...
(Start here)
5.
Complete
(closure)
payments etc
1.
Purpose
(trust)
brand etc
2.
Relations
(respect)
marketing etc
3.
Contract
(agreement)
planning etc
4.
Transact
(action)
delivery etc

Here’s the overall pattern...
transaction
shared-purpose
relations / policy
conversation / contract
transaction / interaction
(delivery of service)
(completion of actions)
(completion for provider)
(completion for consumer)
(completion for enterprise)
(reaffirmed trust)provider consumer
(each step of the pattern will be supported by distinct services
– marketing, sales, delivery, accounts, customer-service etc)

A simple transaction-example...
CC-BY-SA Tetradian
service-provider, service-consumer

Step 1: Shared-purpose...
(in other words, establish a common story,
a shared reason to connect and interact with each other)

Establish an initial connection...
CC-BY-SA Tetradian
such as via reputation and brand

Step 2: Make a connection...
(the same principle of ‘who are you? do we trust each other
enough to proceed?’ applies to human and machine alike)

Establish personal connection...
CC-BY-SA Tetradian
provides basis for interaction rules

transaction
shared-purpose
relations / policy
provider consumer
Step 3: Agree a plan of action...
(this settles the details of what will be exchanged in each
direction – information, services, products, payments etc)

Establish / confirm agreement...
CC-BY-SA Tetradian
‘handshake’ on agreed plan of action

transaction
shared-purpose
relations / policy
provider consumer
Step 4: Enact the transaction...
(the content for the transaction / interaction depends on all of
the previous stages – don’t over-focus on this stage alone!)

Set up and run the transaction...
CC-BY-SA Tetradian
take action on the agreed plan

transaction
shared-purpose
relations / policy
(delivery of service)provider consumer
Service or product delivery...
(this is what we would map out in all the fine-detail of
conventional process-modelling and suchlike)

Engage the internal services...
CC-BY-SA Tetradian
others may do the actual work!

transaction
shared-purpose
relations / policy
provider consumer
Step 5A: Complete the actions...
(completion has several distinct sub-stages, of which the first,
here, is to ensure that there is a clear end-event or marker)

Establish that work is complete...
CC-BY-SA Tetradian
typically in terms of a contract

transaction
shared-purpose
relations / policy
provider consumer
Step 5B: Complete for provider...
(in a commercial context, this typically occurs when the
customer/consumer pays the supplier/provider)

Support-service for completion...
CC-BY-SA Tetradian
role of accounts-department etc

transaction
shared-purpose
relations / policy
provider consumer
Step 5C: Complete for consumer...
(for consumer, completion may often occur some time after
completion of action – e.g. bought-food is eaten)

Completions may be different...
CC-BY-SA Tetradian
customer must satisfy their customer

transaction
shared-purpose
relations / policy
(reaffirmed trust)provider consumer
Step 5D: Complete for enterprise
(for long-term viability, all interactions must be seen as fair
and balanced, by all enterprise players – not just transactors)

Always about whole-enterprise...
CC-BY-SA Tetradian
always about overall shared-story

Warning:
Don’t try to short-cut
that sequence or cycle!

A broken cycle...
(Start here?)
5.
Complete
(closure)
payments etc
1.
Purpose
(trust)
brand etc
2.
Relations
(respect)
marketing etc
3.
Contract
(agreement)
planning etc
4.
Transact
(action)
delivery etc
PoliciesValues
Trust

transaction
shared-purpose
relations / policy
(trust ignored) consumerconsumer
(maximise
short-term
profit)
consumerprovider
The quick-profit trap...
(we may get better results in the short-term by focussing
only on our own needs – but we risk longer-term viability)

Ignoring others’ outcomes...
CC-BY-SA Tetradian
...will awaken angry regulators!

All in full view of stakeholders...
CC-BY-SA Tetradian
...a quick way to create anticlients!

Remember, everyone’s watching!
CC-BY-SA Tetradian

In short…
…we must pay attention
to the story as a whole!
- not just the easy bits…
Context, context, context…

It’s easier to engage people
in exploring perspectives
of the architecture
if we can include
the human dimension!
The punchline for this story:

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:
Support our work! – become a patron on Patreon:
https://www.patreon.com/tetradian

Enterprise Architecture: Perspectives, conflicts and how to resolve them

More Related Content

Similar to Enterprise Architecture: Perspectives, conflicts and how to resolve them

More from Tetradian Consulting

Recently uploaded

Enterprise Architecture: Perspectives, conflicts and how to resolve them