lessons-learnt in ea articulation
DESCRIPTION
A 'mini-workshop' on insights from current developments and practice in enterprise-architecture (BCS-EA conference, London, October 2012) The main part of the presentation is split into eight 'chunks', each tackling a single 'lesson-learnt' from trying to explain EA themes to others in real-world EA practice. Each 'chunk' is timed as around two minutes of background and overview (the bulk of the slides, between the respective 'Challenge' and 'Practice'), and then four minutes pair-discussion around the questions summarised on the respective 'Practice' slide. With two minutes at the start for overall lead-in, and ten minutes at the end for general discussion about what came up for participants during the Practice sections, this fits exactly into a one-hour time-slot. (See http://www.slideshare.net/tetradian/lessonslearnt-in-ea-articulation-worksheet for the associated worksheet.)TRANSCRIPT
Lessons learnt in EA articulation
strategies, services, senses and story
Tom Graves, Tetradian ConsultingBCS EA Conference, London, October 2012
the futures of business
Inviting insight:Eight real-world
challengesfrom EA practice
“It’s all about service”
#1
Challenge:Change business focus
from productto service
Product
CC-BY Kiran Kodoru via Flickr
Product is static…
Service
CC-BY Igor Schwarzmann via Flickr
Serviceimpliesaction… …action
impliesservice
CC-BY AllBrazilian via Wikimedia
It’s always about people…
…‘service’ means thatsomeone’s needs are served
Practice: Service
Products always imply a service…
•Whom do you serve, and how?
•How will you know you’ve served?
•How will you know you’ve served well?
•Who decides?
How do you move from product to service?
“Which point of view?”
#2
Challenge:Use the architectureto help strategists
to break out ofthe self-centric box
Inside-in…
CC-BY Myrmi via Flickr
always at risk of
drowning in the detail…
Inside-out…
CC-BY – Paul – via Flickr
We create an architecturefor an organisation,but about a broader
enterprise.
Outside-in…
CC-BY Fretro via Flickr
“Customers do not appear
in our processes,we appear in
their experiences.”Chris Potts, recrEAtion, Technics, 2010
CC-BY Matt Brown via Flickr
Outside-out…
There’s always a larger scope…
Practice: PerspectiveWhat changes as you change perspective?
•Inside-in
•Inside-out
•Outside-in
•Outside-out
What do these differences imply? To whom?
“It depends…”
#3
Challenge:Create consistencyand awareness of interdependence
across the architecture
CC-BY codiferous via Flickr
In an ecosystem of services,everything depends on everything
else
For ecosystem viability,everything needs to support everything
else
Interdependence
(which is where this guy comes into the picture…)
Everything’s a service
(focus on some service in a chosen value-flow)
Everything’s a service
(interactions occur before and after the main transactions)
Everything’s a service
(identify subsidiary services to manage interactions)
Everything’s a service
(identify inbound and outbound partners for the interactions)
Everything’s a service
(include links with services to direct, coordinate and validate)
Everything’s a service
(include relationships with investors and beneficiaries)
Everything’s a service
(this ‘robot’ is the Enterprise Canvas service-template)
Keep it simple…
…build the (human) story
Practice: InterdependenceHow do the services serve each other?
•Service-consumption (before, during, after)
•Service-provision (before, during, after)
•Direction, coordination, validation
• Investor, beneficiary, governance
How do the services talk with each other? What stories do they exchange? And why?
“Everything changes”
#4
Challenge:Expect change
in the architecture
There is no ‘state’…
- no certain ‘as-is’ or ‘to-be’…
everything’s moving…
…thereis only
the ‘now’
CC-BY Webb Zahn via Flickr
…and when we get there…
…it’s not the ‘there’ we expected.
CC-BY Miguel Vieira via Flickr
What stays the same on the journey?
…how will we know we’ve arrived?
CC-BY Gordon Hunter via Flickr
Practice: Change
If everything’s changing,how can you know
that you’ve arrived?
What map can you useif ‘there’ isn’t there
when you get there?
“Where are we headed?”
#5
Challenge:Create a stable anchor-
directionfor the architecture
A myriad of ‘guiding stars’ out there…
…choose one that looks right to you.
Use it as your guiding-star. Everywhere.
Example (TED conferences): “Ideas worth spreading”
Concern: the focus of interest to everyone in the shared-enterprise
“Ideas worth
spreading”
CC-BY UK DFID via Flickr
“Ideas worth spreading”
Action: what is being done to or with or aboutthe concern
CC-BY US Army Africa via Flickr
“Ideas worth spreading”
Qualifier:the emotivedriver for actionon the concern
CC-BY HDTPCAR via Flickr
Practice: Direction
What guiding-star for the enterprise?
•Focus
•Action
•Qualifier
How to link organisation with enterprise?How to use it as your guiding-star?
“Share the story”
#6
Challenge:Create awareness
of architectureas a shared responsibility
for and of everyone
Nice view of structure, but…
…where are the people?
…where’s the story?
So start with a structure…
…include the human story
Practice: EngagementHow can you include people in the story?
•Engage everyone in building the story
•Make it personal: anecdotes, images, photos
•Support conversation and communication
•Make it their story
What else can you do to share the story?
“Embrace the senses”
#7
Challenge:Create stronger
engagementin the architecture
Texture…
CC-BY Mike Baird via Flickr
CC-BY Franco Follini via Flickr
Shape…
Sound…
CC-BY Angelo Cesare via Flickr
Aroma…CC-BY Andy Tyler via Flickr
Taste…
CC-BY Ian Armstrong via Flickr
Tangibility…
Practice: SensesWhat can you do to engage the senses?
•Texture
•Shape
•Sound
•Scent
•Taste
How to make the architecture tangible?
“Architecture as story”
#8
Challenge:Describe relationships between
structure and story,
organisation and enterprise,
the human aspects of architecture,
to enterprise-architects and othersfrom the defence-industry
Here’s part of a text-based version,
nicely generic, nicely abstract –
the usual way we’d do this…
“An architecturedescribes structure
to support a shared-story.”
“An architecturedescribes structure
to support a shared-story.”
Whose architecture?
Organisation aligns with structure, enterprise with story.
We need a balance of both for the architecture to work.
Tom Graves, The Enterprise As Story, Tetradian, 2012
“An organisation is bounded byrules, roles and responsibilities;
an enterprise is bounded byvision, values and commitments.”
“An organisation is bounded byrules, roles and responsibilities;
an enterprise is bounded byvision, values and commitments.”Tom Graves, Mapping the Enterprise,
Tetradian, 2010
Whose architecture?
Organisation aligns with structure, enterprise with story.
We need a balance of both for the architecture to work.
(yawn…)
Here’s another way to do it,
for that specific audience…
Current EA emphasises structure...
So, here’s a structure...
CC-BY Avodrocc via Flickr
It’s called the Sambadromo...Which doesn’t really tell us anything.To make sense of a structure,we need the story here...
CC-BY Boban021 via Flickr
…the story of Carnaval.
CC-BY sfmission via Flickr
Here, in Rio, a huge shared-story...
CC-BY sfmission via Flickr
Full of colour, sound, spectacle...
CC-BY sfmission via Flickr
...and occasional extremes...
CC-BY sfmission via Flickr
But it’s more aboutexuberance, and pride...
CC-BY sfmission via Flickr
The young(er)...
CC-BY sfmission via Flickr
The old(er)...
CC-BY sfmission via Flickr
The whole community…
CC-BY sfmission via Flickr
And if a line-up like this...
CC-BY bobaliciouslondon via Flickr
might remind you of this...
CC-BY sfmission via Flickr
do rememberto keep trackof the story!
CC-BY sfmission via Flickr
Yet when the party’s over,and it’s time to head home...
CC-BY otubo via Flickr
Someone must be there to clean up...- because that’s part of the story too.
CC-BY jorgeBRAZIL via Flickr
Process, assets, data, locations....- all the usual structure-stuff......all those necessary details of organisation.
CC-BY Avodrocc via Flickr
Organisation focusses on structure…
CC-BY Boban021 via Flickr
yet the enterprise is the story.
The structure happens because of the story.
CC-BY SheilaTostes via Flickr
A key task of enterprise-architectureis to rememberand design for that fact,
Architecture is about structure.Architecture is also about story.We need both, to make it all happen.
maintaining the balancebetween structure and story.
Practice: Story
Use a story to explain an abstract idea
•Make it visual, vibrant, engaging
•Make it personal, human, ‘real-world’
• Include all of the senses
•Make it their story – their terms, their jokes
What else to engage your audience in the story?
“What’s the story?”“What next?”
What did you discover in doing this?
What will you do different on Monday morning?
Practice: Your insights
•Service
•Interdependence
•Direction
•Senses
•Perspective
•Change
•Engagement
•Story
Thank you!
the futures of business
Contact: Tom Graves
Company: Tetradian Consulting
Email: [email protected]
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: