whole-enterprise architecture

142
How to re-think a business from scratch, with Whole-enterprise architecture Tom Graves, Tetradian Consulting Conferenz IT & Enterprise Architecture Forum Auckland, July 2016

Upload: tetradian-consulting

Post on 25-Jan-2017

1.243 views

Category:

Business


0 download

TRANSCRIPT

Page 1: Whole-enterprise architecture

How to re-think a business from scratch, withWhole-enterprise architecture

Tom Graves, Tetradian ConsultingConferenz IT & Enterprise Architecture Forum

Auckland, July 2016

Page 2: Whole-enterprise architecture

Hi. (That’s all the introductions

that we need!)I’m Tom.

Page 3: Whole-enterprise architecture

Let’s start withthe hard question…

Page 4: Whole-enterprise architecture

What isenterprise-architecture?

(yeah, lots of arguments about this…)

Page 5: Whole-enterprise architecture

Well, yes, IT is a key part of EA…

CC-BY-SA MysteryBee via Flickr

Page 6: Whole-enterprise architecture

all the technologythat’s around IT,

that’s part of EA too…

CC-BY-ND garylerude via Flickr

Page 7: Whole-enterprise architecture

and uses of IT – such as in mobile…

CC-BY Highways Agency via Flickr

Page 8: Whole-enterprise architecture

social (sort-of)…CC-BY artotemsco via Flickr

Page 9: Whole-enterprise architecture

…or just plain daft…CC-BY jimlegans via Flickr

Page 10: Whole-enterprise architecture

Yet what isenterprise-architecture, really?

…it’s the architectureof the enterprise.(yeah, I know, should be kinda obvious…)

Page 11: Whole-enterprise architecture

The aim of all architecture…

Things work betterwhen they work together,

on purpose.(It’s about effectiveness.)

Page 12: Whole-enterprise architecture

…and enterprise is

“a bold endeavour”

(Enterprise as “a large commercial organisation” is valid too,but it’s merely one narrow subset of a broader whole.)

Page 13: Whole-enterprise architecture

So this is EA, too…

Page 14: Whole-enterprise architecture

…and this…

Page 15: Whole-enterprise architecture

…and this…

CC-BY Igor Schwarzmann via Flickr

Page 16: Whole-enterprise architecture

“It’s not not aboutthe technology”

(Andrew McAfee)

(because technology is an enablerthat makes the enterprise possible)

Page 17: Whole-enterprise architecture

…but it’s always about people…

CC-BY AllBrazilian via Wikimedia

(look! – technology in use!)

Page 18: Whole-enterprise architecture

Technology is a meansEnterprise is the ends

Don’t mix them up!

Page 19: Whole-enterprise architecture

What’s the current situationwith our frameworks

for enterprise-architecture?

Page 20: Whole-enterprise architecture

What are we facing in EA?• Cloud and other infrastructure changes• Internet of Things, smart-cities and more• Mobile, wearables, embedded-devices• Technology-disruption, blockchain, materials• Business-disruption, customer-centrism• Spiralling complexity – any scope, any scale

Page 21: Whole-enterprise architecture

What do we need from frameworks?• Agility, speed, adaptability, simplicity• Consistency of methods, models, frames• Consistency across any scope, any scale• Address all forms of complexity, dynamics etc• Address all aspects of context, including human• Practice-oriented, results-oriented

Page 22: Whole-enterprise architecture

…but…

Page 23: Whole-enterprise architecture

What do our EA frameworks give us?• Most are built for classic big-IT only• Cumbersome, inconsistent, needlessly verbose• Most oriented to documentation, not practice• Most require top-down Waterfall-type style• No awareness of people-as-people• No methods (TOGAF is almost the only exception)

Page 24: Whole-enterprise architecture

• Most are built for classic big-IT only• Cumbersome, inconsistent, needlessly verbose• Most oriented to documentation, not practice• Most require top-down Waterfall-type style• No awareness of people-as-people• No methods (TOGAF is almost the only exception)

a great bigclunky

outdated mess…

What do our EA frameworks give us?

Page 25: Whole-enterprise architecture

WAAAAHHH!!!

Page 26: Whole-enterprise architecture

…or, more politely,not much use at all.

Page 27: Whole-enterprise architecture

What do our EA toolsets give us?• Most are built for those big-IT frameworks• Cumbersome, unwieldy, often user-hostile• Most oriented to documentation, not practice• Most assume top-down Waterfall-type style• In most, no awareness of people-as-people• Almost no support for methods (except TOGAF, again)

Page 28: Whole-enterprise architecture

• Most are built for those big-IT frameworks• Cumbersome, unwieldy, often user-hostile• Most oriented to documentation, not practice• Most assume top-down Waterfall-type style• In most, no awareness of people-as-people• Almost no support for methods (except TOGAF, again)

a great bigclunky

outdated mess…

What do our EA toolsets give us?

Page 29: Whole-enterprise architecture

WAAAAHHH!!!

Page 30: Whole-enterprise architecture

…or, more politely,not much use at all.

Page 31: Whole-enterprise architecture

#facepalm…

CC-BY xxdr_zombiexx via Flickr

…they copied the same mistakes “because we thought that’s what the market would want…”

Page 32: Whole-enterprise architecture

(image source not known)

If we can’t fix this…

…our prospectscould be somewhat bleak…

Page 33: Whole-enterprise architecture

What can we do about it?!?

CC-BY Editor B via Flickr

Page 34: Whole-enterprise architecture

Short answer:start again from scratch…

Page 35: Whole-enterprise architecture

…and this time,do it properly, by starting

from a whole-enterprise view.

Page 36: Whole-enterprise architecture

Don’t panic! – it’s not as hard as it sounds…

BY Nate Steiner via Flickr

Page 37: Whole-enterprise architecture

…it’s using what we already know, going back to first-principles,

and applying architectureto architecture itself.

Page 38: Whole-enterprise architecture

‘Whole enterprise’doesn’t need to mean

whole-of-enterprise, every time…

…instead, it’s more about doingevery item of architecture

always in context of the whole.(which means we first need to understand that whole…)

Page 39: Whole-enterprise architecture

Understanding the scope…

‘Classic’ EA covers only the mid-range of abstraction, and often IT-only;for most real-world EA, we need more range – top-down and bottom-up.

Page 40: Whole-enterprise architecture

Linking architecture and design…

Architectureemphasis on

Why and Who

Designemphasis onHow and What / Where / When

Page 41: Whole-enterprise architecture

Understanding the process…

Damien Newman’s ‘the Squiggle’, as a description of the development process

Page 42: Whole-enterprise architecture

About disciplines of sensemaking…

(a favourite book)

Page 43: Whole-enterprise architecture

“The art of scientific investigation”

Preface to WIB Beveridge, The Art of Scientific Investigation, Norton, 1957

“Elaborate apparatus plays an important part in the science of today, but I wonder if we are not inclined to forget that the most important instrument in research is the mind of [the researcher].

https://archive.org/details/artofscientifici00beve

“We need to pay more attention] to the technicalities of making the best use of the [mind] … the practice and mental skills - the art - of scientific investigation.”

Page 44: Whole-enterprise architecture

About structure and story…

(another favourite book)

Page 45: Whole-enterprise architecture

“Two points of view on architecture”• Architecture is an exercise in truth

A proper building is responsible to universal knowledgeand is wholly honest in the expression of its functionsand materials

• Architecture is an exercise in narrativeArchitecture is a vehicle for the telling of stories, a canvas for relaying societal myths, a stage for thetheatre of everyday life

Chapter 84, in Matthew Frederick, 101 Things I Learned In Architecture School, MIT Press, 2007

- architecture is about structure

- architecture is about story

Page 46: Whole-enterprise architecture

Core conceptsfor whole-enterprise architecture

Page 47: Whole-enterprise architecture

From plan to planning,from architecture to architecting…

CC-BY – Paul – via Flickr

Page 48: Whole-enterprise architecture

Enterprise is ecosystem-with-a-purpose…

CC-BY Fretro via Flickr

Page 49: Whole-enterprise architecture

People are always people, themselves…CC-BY andré luís via Flickr

Page 50: Whole-enterprise architecture

…never as mere projections of the machine…CC-BY justin pickard via Flickr

Page 51: Whole-enterprise architecture

Scope is always ‘the everything’…(every context is within a greater context)

CC-BY Matt Brown via Flickr

…yet we get to choose effective scope-boundary…

Page 52: Whole-enterprise architecture

Recursive and fractal…

CC-BY-NC-SA sharman via Flickr

every point describes every other point…

Page 53: Whole-enterprise architecture

VUCA is everywhere…

Volatility, Uncertainty, Complexity, Ambiguity… CC-BY soldiersmediacenter via Flickr

Page 54: Whole-enterprise architecture

Architecture is non-functional first

Two bridges:The function is the

same for both;the non-functionals make the difference

CC-BY-ND ernieski via FlickrCC-BY hansfransen via Flickr

Page 55: Whole-enterprise architecture

There is no ‘The Solution’…

CC-BY art_es_anna via Flickr…every context changes dynamically over time…

Page 56: Whole-enterprise 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)

Page 57: Whole-enterprise architecture

Building a methodfor whole-enterprise architecture

Page 58: Whole-enterprise architecture

Start from a linear project-sequence…

(Tuckman’s classic Group Dynamics project-lifecycle)

Forming(Purpose)

1 2 3 4 5

Performing(Process)

Storming(People)

Norming(Preparation)

Adjourning(Performance)

Page 59: Whole-enterprise architecture

Bring in the Squiggle…

Architecture Design

Page 60: Whole-enterprise architecture

Map phases onto the Squiggle…

Forming(Purpose)

Storming(People)

Norming(Preparation)

Performing(Process)

Adjourning(Performance)

Architecture Design

Page 61: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Reframe as Five Elements cycle…

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Start here

Page 62: Whole-enterprise architecture

WhatProcess

(Performing

…and make it fully fractal

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Page 63: Whole-enterprise architecture

Five Elements as strategy-action cycle

(overall cycle and relationships need to be kept in balance)

Page 64: Whole-enterprise architecture

Use the cycle for any scope, any scale,any duration, any depth of detail,

nested fractally to any depth…

start a new nested iteration anywhere…

but always do the whole cycle(because if not, it will probably fail…)

Page 65: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Fail #1: skip People, go direct to plan…

WhyPurpose(Forming)

HowPreparation

(Norming)

OutcomePerformance

(Adjourning)

Storming!

Page 66: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Fail #2: jump straight into action…

WhyPurpose(Forming)

WhatProcess

(Performing)

Storming!

Page 67: Whole-enterprise architecture

There are good reasons why we dothe Five Elements cycle

always in that sequence…

…don’t try to skip over or avoidany of the phases!

Page 68: Whole-enterprise architecture

More detail on method…

Page 69: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 1: Purpose (Why)

WhyPurpose(Forming)

• Establish, clarify and refine the business-question for review

• Identify applicable scope• Identify underlying vision

and values• Identify success-criteria for

this iteration

Page 70: Whole-enterprise architecture

Why vision and values matter…

NOW!

before

certain uncertain

(depends onpersonal connection,

personal trust)

(depends on sensing, feeling, an often-literal

‘being in touch’)PLAN

ACTION

edge of action

situational awareness(realities – What)

commander’s intent(guidance – Why)

Page 71: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 2: People (Who)Who

People(Storming)

• Identify who is likely to have knowledge we need

• Identify stakeholders for the business-question, and their drivers

• Identify and assess any underlying politics…

Page 72: Whole-enterprise architecture

Who are the stakeholders?A stakeholderis anyonewho can wielda sharp-pointed stakein our direction…

CC-BY-NC-SA evilpeacock via Flickr

(Hint: there are a lot more of them than we might at first think…)

Page 73: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 3: Preparation (How)

HowPreparation

(Norming)

• Identify frames and methods that match criteria for the current business-question

• Create context-specific methods for action

• Build action-plan

Page 74: Whole-enterprise architecture

The Start Anywhere principle:

everything connects toeverything else…

everything depends oneverything else…

- so we can start anywhereand arrive at the same place!

Page 75: Whole-enterprise architecture

Start from context…

Typical visual-checklist:

Holomap(part of EnterpriseCanvas suite)

Page 76: Whole-enterprise architecture

Start from services…

Typical visual-checklist:Enterprise Canvas(and 20+ related maps in the ECanvas suite)

Page 77: Whole-enterprise architecture

Start from complexity…

Typical visual-checklist:

SCAN(with any of its 80+ overlays and crossmaps)

Page 78: Whole-enterprise architecture

Start from capability and strategy…

Typical visual-checklist:

SCORE(and other maps in the strategy suite)

Page 79: Whole-enterprise architecture

Start from structural content…

Typical visual-checklist:

Service Content(and 20+ related maps in the ECanvas suite)

Page 80: Whole-enterprise architecture

Start from value-flows…

Typical visual-checklist:

Service Cycle(and 20+ related maps in the ECanvas suite)

Page 81: Whole-enterprise architecture

Start from story…

Typical visual-checklist:

NOTES(with active narrative / story-exploration)

Page 82: Whole-enterprise architecture

Start from effectiveness…

Typical visual-checklist:

SEMPER(power-dynamics and ‘ability to do work’)

Page 83: Whole-enterprise architecture

Start from governance…

Typical visual-checklist:

Backbone & Edge(dynamics, pace-layering, dependencies and more)

Page 84: Whole-enterprise architecture

Start from architecture-maturity…

Typical visual-checklist:

Maturity Model(recommended tactics at varying maturity-stages)

Page 85: Whole-enterprise architecture

The Start Anywhere principleshows us that ‘where to start’doesn’t matter all that much..

…what does matteris that we do get started!

Page 86: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 4: Process (What / Where / When)

WhatProcess

(Performing)

• Enact the action-plan• Engage with stakeholders

during the action• Apply governance as

needed for the context• Capture architectural

information as required

Page 87: Whole-enterprise architecture

Remember thatenterprise-architecture

is not solution-architecture…

…we need the right toolset for each type of work– but are there any good tools yet for EA?

Page 88: Whole-enterprise architecture

Solution-architect’s toolset

Page 89: Whole-enterprise architecture

Enterprise-architect’s toolset

Page 90: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 5: Performance (Outcome)

OutcomePerformance

(Adjourning)

• Assess benefits-realised and value-delivered from the iteration, as per the criteria from Why-phase

• Assess lessons-learned from the iteration

• Set up for further actions

Page 91: Whole-enterprise architecture

Don’t skimp on this phase!– it’s how we establish and prove

that we’ve delivered real business-value…

and how we build competence, expertiseand maturity in enterprise-architecture

Page 92: Whole-enterprise architecture

A real example:transform organisation’s

operating-model(duration: five weeks elapsed-time)

Page 93: Whole-enterprise architecture

Transformation – 0: Setup• Business question: “How can we

turn round into profitability?”• Refined to: “How do we

enhance operational effectiveness, to become more profitable?”

• Initial enquiry-iteration indicates competence for this resides with operations-staff

Initialenquiry

and setup

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Page 94: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Transformation – 1: Purpose (Why)

WhyPurpose(Forming)

• Business question: Refine business-processes to enhance effectiveness

• Use organisation vision and values as focus-criteria

• Success-criteria: Set of feasible / achievable change-projects

Page 95: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Transformation – 2: People (Who)Who

People(Storming)

• Put out a call for volunteers who have the likely experience, knowledge and commitment

• Engage senior-management in commitment to change

• (but warning-signs of equivocation from some senior managers…)

Page 96: Whole-enterprise architecture

Our volunteers were excited about possibilities…CC-BY-ND alanclarkdesign via Flickr

Page 97: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Transformation – 3: Preparation (How)

HowPreparation

(Norming)

• Run a set of training-workshops with the volunteers, to learn the methods for whole-enterprise architecture and design

• Create context-specific methods for action

• Build action-plans

Page 98: Whole-enterprise architecture

Methods for whole-enterprise architecture…

Page 99: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Transformation – 4: Process (What etc)

WhatProcess

(Performing)

• Volunteers start to enact their action-plans, to develop detailed business-cases

• but senior-managers pull back on support for front-line staff

• Middle-managers bully their staff about ‘wasting time’…

• Volunteers lose their commitment…

Page 100: Whole-enterprise architecture

Our volunteers lost commitment and hope…CC-BY-ND alanclarkdesign via Flickr

Page 101: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Transformation – X: Failure…?• With commitment lost, the

transformation fades to nothing:– “The greatest danger for an

organisation is when its passionate people fall silent”

• There is now neither means nor time for needed transformation – so the blame-games start…

• Right now, the most likely outcome is that the organisation will have to be sold or closed

Storming!

Page 102: Whole-enterprise architecture

We can’t avoid the politics…

Always be careful of the politics – it’s a crucial aspect of EA,but it can kill business-transformation and more if not done well…

Page 103: Whole-enterprise architecture

A real example:assess Gartner’s Bimodal-IT

(duration: two days)

See also: http://weblog.tetradian.com/towards-a-whole-enterprise-architecture-standard-worked-example/

Page 104: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Bimodal-IT – 1: Purpose (Why)

WhyPurpose(Forming)

• Business-question: “should we adopt Bimodal-IT?”

• Refined to “What IT-governance do we need?”

• Success-criteria: clarity on the decision, and guidance on what to do next

Page 105: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Bimodal-IT – 2: People (Who)Who

People(Storming)

• Stakeholders: operations, developers, service-management; also marketing, PMO etc

• IT-vendors, consultancies, trade-journals; also various independent practitioners

• Vendors, consultancies etc have vested interests…

Page 106: Whole-enterprise architecture

Use Holomap to map stakeholders…

(Context-specific version of Holomap instantiated from Holomap metatemplate,to summarise the overall broader context for the business’ IT-organisation)

Page 107: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Bimodal-IT – 3: Preparation (How)

HowPreparation

(Norming)

• Literature-review identifies real doubts…

• Assessment shows deep-complexity in criteria for governance

• Build action-plan to explore ideas on meta-governance

Page 108: Whole-enterprise architecture

Assess with Backbone & Edge…

(Backbone & Edge visual-checklist with crossmap to Simon Wardley’s ‘Pioneers, Settlers, Town-Planners’ model – includes example data-types to illustrate ‘spectrum of governance of governance’)

Page 109: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Bimodal-IT – 4: Process (What etc)

WhatProcess

(Performing)

• Internal stakeholders do acknowledge need for governance – including for shadow-IT

• Complexities of dynamics etc are a real concern

• Many stakeholders openly deride Bimodal-IT as an extreme over-simplification:– “it’s worse than useless…”

Page 110: Whole-enterprise architecture

Stakeholder views on ‘Bimodal-IT’…

“exactly what not to do for viable governance…”

Page 111: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Bimodal-IT – 5: Performance (Outcome)

OutcomePerformance

(Adjourning)

• Benefits-realised: clear advice – some form of meta-governance needed, but not Bimodal-IT

• Value-delivered: probable cost-avoidance of c.$10m-$100m

• Lessons-learned: beware of big-consultancy hype…

• Further actions: explore future needs and criteria for systematic meta-governance

Page 112: Whole-enterprise architecture

The moral of this tale:beware of ‘solutioneering’!

– someone else’s supposed ‘best practice’is rarely an exact best-practicefor our own business-context…

Page 113: Whole-enterprise architecture

A real example:restructure a design-firm’s

business-model(duration: two hours)

See also: http://weblog.tetradian.com/2015/11/30/using-score-to-reframe-the-business-model/

Page 114: Whole-enterprise architecture

“Where do we start?”, he said…

Page 115: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Business-model: Why (Purpose)

WhyPurpose(Forming)

• Refine the business-question to “Finding more and better clients”

• Key value: “Design-work that I like doing”

• Success-criterion: a viable business-model

Page 116: Whole-enterprise architecture

Another view of the Squiggle…

Architecture DesignConcept Visuals

Page 117: Whole-enterprise architecture

Initial idea-sketches…

Page 118: Whole-enterprise architecture

Full concept-sketch…

https://www.behance.net/gallery/34644071/Lotus-2016-Geneva-Motor-Show-concept

Page 119: Whole-enterprise architecture

Preliminary model…

https://www.behance.net/gallery/34644071/Lotus-2016-Geneva-Motor-Show-concept

Page 120: Whole-enterprise architecture

Fully-rendered model…

https://www.behance.net/gallery/34644071/Lotus-2016-Geneva-Motor-Show-concept

Page 121: Whole-enterprise architecture

Fully-rendered model…

Page 122: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Business-model: Who (People)Who

People(Storming)

• Assess feedback from clients and other contacts

• Review of own implicit ‘A/B tests’ on portfolio-sites such as Behance.net

• Look inside oneself for inner knowing…

Page 123: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Business-model: How (Preparation)

HowPreparation

(Norming)

• Need for a simple precursor to Business Model Canvas

• Use SCORE frame for capability/strategy mapping as precursor– http://weblog.tetradian.com/

2013/06/29/checking-the-score/

• Build action-plan

Page 124: Whole-enterprise architecture

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

VersionSCOREstrengthsStrengths / Services / Support(existing capabilities and resources, potential for synergies)

challengesChallenges / Capabilities-needed(‘weaknesses’ indicate needed capabilities and resources)

optionsOptions / Opportunities and risks

(opportunity is also risk, risk is also opportunity)

responsesResponses / Returns / Rewards

(probable or emergent consequences of action or inaction)

effectivenessdefault: efficient, reliable, elegant, appropriate, integrated

focus-question

Page 125: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Business-model: What etc (Process)

WhatProcess

(Performing)

• Enact the action-plan: Use SCORE frame to explore the context, opportunities, challenges etc

• “SWOT is just bits - SCORE is a path, connected, adaptable”

• Continue iterating, to collect Just Enough Detail…

Page 126: Whole-enterprise architecture

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

VersionSCOREstrengthsStrengths / Services / Support(existing capabilities and resources, potential for synergies)

challengesChallenges / Capabilities-needed(‘weaknesses’ indicate needed capabilities and resources)

optionsOptions / Opportunities and risks

(opportunity is also risk, risk is also opportunity)

responsesResponses / Returns / Rewards

(probable or emergent consequences of action or inaction)

effectivenessdefault: efficient, reliable, elegant, appropriate, integrated

“Finding more and better clients”

not enough income;not enough work I like

good at 3D modelling

need more expensive software?

I like doing research

are clients interested in research – I assume not…

jobs with research in them have often gained me new work

research is important to me

I’m good at textures, ‘realness’

is there a market for ‘realness’?

A/B test shows there is a market for ‘realness’

‘realness’ is important to me

not many people do what I do

real business-opportunity for concepts/visualswith research and ‘realness’

my current software is enough

next task: clarify details of new business-model!

JC3DVIS business-model Tetradian

Page 127: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Business-model: Outcome (Performance)

OutcomePerformance

(Adjourning)

• Benefits-realised: Clear preparation and content for Business Model Canvas

• Lessons-learned: “Stuff I’d thought was of no value turns out to be the opposite – things like research, and realness”

• Set up for further actions

Page 128: Whole-enterprise architecture

“Portraying the realness of things…”

Page 129: Whole-enterprise architecture

Revised business-activity model…

“some people just want concept-sketches, others want full visuals,but some clients do want both…”

Page 130: Whole-enterprise architecture

How architecture really works…

“When we started, I wanted a [predefined] framework, but this has given me far more, helped me to think. It’s a lot more exciting, to be honest.”

“What was useful was you set off sparks of thought that got me connecting the dots.”

(And when we do it right, architecture can indeed be exciting!)

Page 131: Whole-enterprise architecture

Your real example:EA in 5 minutes

Page 132: Whole-enterprise architecture

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

Page 133: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 1: Why (Purpose)

WhyPurpose(Forming)

• Establish, clarify and refine the business-question for review

• Identify applicable scope• Identify underlying vision

and values• Identify success-criteria for

this iteration

Page 134: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 2: Who (People)Who

People(Storming)

• Identify who is likely to have knowledge we need

• Identify stakeholders for the business-question, and their drivers

• Identify and assess any underlying politics…

Page 135: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 3: How (Preparation)

HowPreparation

(Norming)

• Identify frames and methods that match criteria for the current business-question

• Create context-specific methods for action

• Build action-plan

Page 136: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 4: What / Where / When (Process)

WhatProcess

(Performing)

• Enact the action-plan• Engage with stakeholders

during the action• Apply governance as

needed for the context• Capture architectural

information as required

Page 137: Whole-enterprise architecture

WhyPurpose(Forming)

WhoPeople

(Storming)

HowPreparation

(Norming)

WhatProcess

(Performing)

OutcomePerformance

(Adjourning)

Phase 5: Outcome (Performance)

OutcomePerformance

(Adjourning)

• Assess benefits-realised and value-delivered from the iteration, as per the criteria from Why-phase

• Assess lessons-learned from the iteration

• Set up for further actions

Page 138: Whole-enterprise architecture

What do we learn from this?

(Quick comments, anyone?)

Page 139: Whole-enterprise architecture

Wrapping up…

Page 140: Whole-enterprise architecture

Summary• Whole-enterprise architecture aims to create

effectiveness, always in context of the whole• Methods and frames are consistent everywhere,

– consistent at every scope, scale and duration– consistent pattern: Why, Who, How, What, Outcomes

• Address all aspects of context, including human• Address all forms of complexity, dynamics etc• Always oriented to real-world practice and results

Page 141: Whole-enterprise architecture

Thank you!

Page 142: Whole-enterprise architecture

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

Books: • Real enterprise architecture: Beyond IT to the whole enterprise (2008)• Bridging the silos: Enterprise architecture for IT architects (2008)• Power and response-ability – the human side of systems (2003/2008)• SEMPER and SCORE: Enhancing enterprise effectiveness (2008)• The service-oriented enterprise: Enterprise architecture and viable services (2009)• Doing enterprise-architecture: process and practice in the real enterprise (2009)• Everyday enterprise-architecture: sensemaking, strategy, structures and solutions (2010)• Mapping the enterprise: modelling the enterprise as services with the Enterprise Canvas (2010)• The enterprise as story: the role of narrative in enterprise-architecture (2012)

Further information: