Same and different - architectures for mass-uniqueness

109
Same and different architectures for mass-uniqueness Tom Graves, Tetradian Consulting Open Group London, October 2013 the futures of business

description

My presentation for Open Group London #ogLON enterprise-architecture conference, October 2013 Classic enterprise-architectures seem to focus mainly on IT and replicable IT-based processes. By contrast, many business-contexts such as healthcare, recruitment, education, customer-service and retail, all need to emphasise 'mass-uniqueness' - individual difference or uniqueness at scale. This slidedeck explores some of the themes and techniques that can be used to develop enterprise-architectures with appropriate balance between 'same' and 'different'.

Transcript of Same and different - architectures for mass-uniqueness

Page 1: Same and different - architectures for mass-uniqueness

Same and differentarchitectures for mass-uniqueness

Tom Graves, Tetradian ConsultingOpen Group London, October 2013

the futures of business

Page 2: Same and different - architectures for mass-uniqueness

Hi.

(let’s not bother with the PR-stuff?)

Page 3: Same and different - architectures for mass-uniqueness

It begins with a pin, perhaps…

CC-BY Creativity103 via Flickr

Page 4: Same and different - architectures for mass-uniqueness

…or maybe some dust?

CC-BY storebrukkebruse via Flickr

Page 5: Same and different - architectures for mass-uniqueness

What isenterprise-architecture?

But perhaps better start witha much-argued question:

Maybe more to the point –

why enterprise-architecture?

Page 6: Same and different - architectures for mass-uniqueness

– it’s because

things work betterwhen they work together,

on purpose

Why enterprise-architecture?

Page 7: Same and different - architectures for mass-uniqueness

Why enterprise-architecture?…which implies further questions:

•Things – what things? and who decides?

•Work – ‘work’ in what sense? what work?

•Better – ‘better’ for what? or who? who decides?

•Together – what kind of ‘together’? how? why?

•On purpose – who chooses the purpose? for what?

One place to look for clues is in the enterprise’s balance between same and different…

Page 8: Same and different - architectures for mass-uniqueness

Into practice…

(Each ‘Into practice…’ sectionprovides a brief moment to exploreimplications of the preceding ideas.

Use the text on the slide to guidea quick review of related design-themes

in your business-context.)

Page 9: Same and different - architectures for mass-uniqueness

“What’s the story?”A quest for productivity

Page 10: Same and different - architectures for mass-uniqueness

Let’s go back to an earlier time…

Page 11: Same and different - architectures for mass-uniqueness

there’s not much technology…

Page 12: Same and different - architectures for mass-uniqueness

maybe some of it a bit strange…

Page 13: Same and different - architectures for mass-uniqueness

everything made by hand…

Page 14: Same and different - architectures for mass-uniqueness

everything different, unique…

Page 15: Same and different - architectures for mass-uniqueness

almost nothing standardised…

Page 16: Same and different - architectures for mass-uniqueness

until this guy, in this book…

Page 17: Same and different - architectures for mass-uniqueness

looked at how pins were made…

CC-BY Creativity103 via Flickr

Page 18: Same and different - architectures for mass-uniqueness

applied it to other industries…

Page 19: Same and different - architectures for mass-uniqueness

via sameness…

CC-BY toktokkie via Flickr

Page 20: Same and different - architectures for mass-uniqueness

more sameness…

Page 21: Same and different - architectures for mass-uniqueness

a lot more sameness…

Page 22: Same and different - architectures for mass-uniqueness

then applied to work itself…Richard Arkwright’s Cromford Mill

CC-BY-SA CaptainScarlet via Wikimedia

Page 23: Same and different - architectures for mass-uniqueness

mass-sameness…

Page 24: Same and different - architectures for mass-uniqueness

mass-sameness…

CC-BY aleutia via Flickr

Page 25: Same and different - architectures for mass-uniqueness

mass-sameness…

CC-BY Vlima.com via Flickr

Page 26: Same and different - architectures for mass-uniqueness

mass-sameness everywhere.

CC-BY-SA MysteryBee via Flickr

Page 27: Same and different - architectures for mass-uniqueness

the real value of samenessis that it’s easy to scale

and easy to make efficient- creating huge productivity

Why sameness?

Page 28: Same and different - architectures for mass-uniqueness

But there’s a catch…

Page 29: Same and different - architectures for mass-uniqueness

the differencesnever went away…

Page 30: Same and different - architectures for mass-uniqueness

and if we pretendthat everythingis sameness…

Page 31: Same and different - architectures for mass-uniqueness

we court disaster…

Page 32: Same and different - architectures for mass-uniqueness

Into practice…

In what ways do your systemsdepend on sameness?

What would happenif the sameness wasn’t there

to depend on?

What happens with anythingthat won’t fit those expectations?

Page 33: Same and different - architectures for mass-uniqueness

“What’s the story?”There’s always an exception…

Page 34: Same and different - architectures for mass-uniqueness

What name in your system?

Typical UK-style name-structure for database:

•Title (mandatory: select from picklist)

•Forename (mandatory: 30 characters max)

•Middle-name (optional: 30 characters max)

•Surname (mandatory: 30 characters max)

•Suffix (optional: select from picklist)

Easy, right? – well, let’s take a real example…

Page 35: Same and different - architectures for mass-uniqueness

What name in your system?

UK-style name:

•Mr Pablo Diego Ruiz

Page 36: Same and different - architectures for mass-uniqueness

What name in your system?

UK-style name:

•Mr Pablo Diego Ruiz

Full legal birth-name:

•Pablo Diego José Francisco de Paula Juan Nepomuceno María de los Remedios Cipriano de la Santísima Trinidad Ruiz y Picasso

Page 37: Same and different - architectures for mass-uniqueness

What name in your system?

UK-style name:

•Mr Pablo Diego Ruiz

Full legal birth-name:

•Pablo Diego José Francisco de Paula Juan Nepomuceno María de los Remedios Cipriano de la Santísima Trinidad Ruiz y Picasso

You probably know him as:

Page 38: Same and different - architectures for mass-uniqueness

Driver’s licence, please?

Real simple, right?

Hmm… maybe not so simpleafter all?

The same for everyone, surely?

Hensel twins’ driver-licences >>

Page 39: Same and different - architectures for mass-uniqueness

Driver’s licence, please?On the flight: One ticket, one seat, two passengers, two passports

In the car: Two drivers behind the wheel, each legally liable

Page 40: Same and different - architectures for mass-uniqueness

What keeps executives awake at night?

And here’s a real casefrom my own consultancy-work

in enterprise-architecture…

Page 41: Same and different - architectures for mass-uniqueness

Executive #1: PR disastersGovernment department

(in social-work sector)

Real (if unofficial) business metric:

Number of daysbetween bad headlines

in the newspaper

Page 42: Same and different - architectures for mass-uniqueness

Executive #1: PR disasters

Real newspaper headline:

Department fails again!

Ten life-critical incidentsin just one suburbstill not resolvedin 2½ months!

Page 43: Same and different - architectures for mass-uniqueness

Answer: architecture of the enterprise

What actually happened?

Incident

for one incidentReport

Report

Report

ReportReport Report

Report

Report

Report

Report

Ten incident-reports

Key-field: Date of Birth(for unborn child…)

Page 44: Same and different - architectures for mass-uniqueness

Executive #1: PR disasters

Moral of this story:

Every automated systemneeds an option for manual override

Page 45: Same and different - architectures for mass-uniqueness

Into practice…

What exceptions are therethat could break

your current systems?

How do you find out about thembefore they break your systems?

What workarounds would you needto keep your systems going?

Page 46: Same and different - architectures for mass-uniqueness

“What’s the story?”A bit of theoryon uniqueness…

Page 47: Same and different - architectures for mass-uniqueness

…dust is everywhere…

CC-BY storebrukkebruse via Flickr

Page 48: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Start with everything-different

Page 49: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Find an area of samenesswithin all of that uniqueness

Page 50: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Within each remaining block of difference,find another region of sameness

Page 51: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Within each remaining block of difference,find another region of sameness

Page 52: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Within each remaining block of difference,find another region of sameness

Page 53: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Within each remaining block of difference,find another region of sameness

Page 54: Same and different - architectures for mass-uniqueness

‘Cantor Dust’

Repeat the same processall the way to infinity…

Page 55: Same and different - architectures for mass-uniqueness

no matter how far down we go,there will always be uniqueness…

…and every one of thoseapparent ‘samenesses’ we found

is also different from every other…

- uniqueness in the sameness…

Page 56: Same and different - architectures for mass-uniqueness

Into practice…

How much at present do you designagainst uniqueness?

If uniqueness is a fact of nature,is trying to design against it

even a viable option?

Should you design for uniqueness?If so, how?

Page 57: Same and different - architectures for mass-uniqueness

“What’s the story?”Uniqueness– how and why

Page 58: Same and different - architectures for mass-uniqueness

Mass-uniquenessis uniqueness at scale

– where differenceor uniqueness

is a central factof the work itself

What is mass-uniqueness?

Page 59: Same and different - architectures for mass-uniqueness

Mass-uniquenessSome everyday examples:

•Healthcare – unique needs, Hickam’s Dictum

•Customer-service – unique needs, ‘long-tail’

•Clothing – fashion, body-types, shapes, sizes

•Education – every student is different, unique needs

•Information-search – unstructured, natural-language

•Farming – weather, micro-climate, soil-types

•City-planning – topography, geography, particularity

Page 60: Same and different - architectures for mass-uniqueness

standardised

A spectrum of uniqueness

customised unique

Page 61: Same and different - architectures for mass-uniqueness

standardised…

CC-BY-NC-ND actiononarmedviolence via Flickr

Page 62: Same and different - architectures for mass-uniqueness

customised…CC-BY-NC-SA Doctress Neutopia via Flickr

Page 63: Same and different - architectures for mass-uniqueness

customised…CC-BY-NC-SA Doctress Neutopia via Flickr

Page 64: Same and different - architectures for mass-uniqueness

unique…© Courtesy of 3D Systems

Page 65: Same and different - architectures for mass-uniqueness

unique…

© Courtesy of 3D Systems

Page 66: Same and different - architectures for mass-uniqueness

uniqueness…

© Courtesy of 3D Systems

Page 67: Same and different - architectures for mass-uniqueness

uniqueness makes it something to celebrate…

© Courtesy of 3D Systems

Page 68: Same and different - architectures for mass-uniqueness

Into practice…

How much mass-uniquenessexists in your business-context?

How much do you already designfor that uniqueness?

How do you supportthe required uniqueness at scale?

Page 69: Same and different - architectures for mass-uniqueness

“What’s the story?”A question of perspective

Page 70: Same and different - architectures for mass-uniqueness

Perspectives and journeys

Service-delivery is a journey of interactionswhere ‘inside-out’ (the organisation’s perspective)

touches ‘outside-in’ (the customer’s / supplier’s perspective)

Page 71: Same and different - architectures for mass-uniqueness

Outside-in…

CC-BY Fretro via Flickr

“Customers do not appear

in our processes,we appear in

their experiences.”Chris Potts, recrEAtion, Technics, 2010

Page 72: Same and different - architectures for mass-uniqueness

A stakeholder is anyonewho can wielda sharp-pointed stakein your direction…

CC-BY-NC-SA evilpeacock via Flickr

Stakeholders in the enterprise

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

Page 73: Same and different - architectures for mass-uniqueness

Narrative and storyhelp us to identify

the exceptionsand uniquenesses…

The role of narrative

Page 74: Same and different - architectures for mass-uniqueness

Technology

CC-BY-SA xdxd_vs_xdxd via Flickr

Process

People

The usual EA view

Page 75: Same and different - architectures for mass-uniqueness

Stage

CC-BY-SA xdxd_vs_xdxd via Flickr

Scene

Actor

ActorStage

Stage

Stage

A narrative-oriented viewStage

Scene

Scene

Stage

Page 76: Same and different - architectures for mass-uniqueness

Into practice…

What changesas you shift the perspective

from inside-out to outside-in?

What do the narratives tell youabout uniqueness in your business?

What do you need to changeto make best use of this?

Page 77: Same and different - architectures for mass-uniqueness

“What’s the story?”SCAN – making senseof uniqueness

Page 78: Same and different - architectures for mass-uniqueness

“Let’s do a quick SCAN of this…”

Order and unorder

Page 79: Same and different - architectures for mass-uniqueness

CC-BY bobaliciouslondon via Flickr

“We have a rule for everything!”

Page 80: Same and different - architectures for mass-uniqueness

CC-BY bobaliciouslondon via Flickr

Hmm… let’s do a quick SCAN of this…

Page 81: Same and different - architectures for mass-uniqueness

“Insanityis doingthe same thingand expectingdifferent results”

(Albert Einstein)

ORDER(IT-type rules do work here)

Take control! Impose order!

Page 82: Same and different - architectures for mass-uniqueness

“Insanityis doingthe same thingand expectingdifferent results”

(Albert Einstein)

“Insanityis doingthe same thingand expectingthe same results”

(not Albert Einstein)

ORDER(IT-type rules do work here)

UNORDER(IT-type rules don’t work here)

Order and unorder

Page 83: Same and different - architectures for mass-uniqueness

A quest for certainty: analysis, algorithms, identicality, efficiency, business-rule engines, executable models, Six Sigma...

SAMENESS(IT-systems do work

well here)

UNIQUENESS(IT-systems don’t work

well here)

Same and different

An acceptance of uncertainty: experiment, patterns, probabilities, ‘design-thinking’, unstructured process...

Page 84: Same and different - architectures for mass-uniqueness

THEORY

What we plan to do, in the expected conditions

What we actually do, in the actual conditions

PRACTICE

Theory and practice

Page 85: Same and different - architectures for mass-uniqueness

algorithm guideline

rule principle

Different types of decision-guides apply in each ‘domain’

Sensemaking guides decisions

Page 86: Same and different - architectures for mass-uniqueness

Guidelines for design

order unorder

fail-safe(high-certainty)

safe-fail(low-certainty)

plan

actual

Waterfall(‘controlled’ change)

Agile(iterative change)

analysis(knowable result)

experiment(unknowable result)

Page 87: Same and different - architectures for mass-uniqueness

Why we need people…

What is always going to beuncertain or unique?

(‘Messy’ – politics, management, wicked-problems, ‘should’ vs ‘is’, etc.)

What will always be ‘messy’?

Wherever these occur,we’re going to need human skill…

Page 88: Same and different - architectures for mass-uniqueness

Machines and people

order(rules do work here)

unorder(rules don’t work here)

fail-safe(high-certainty)

safe-fail(low-certainty)

analysis(knowable result)

experiment(unknowable result)

MACHINES PEOPLE

Waterfall(‘controlled’ change)

Agile(iterative change)

Page 89: Same and different - architectures for mass-uniqueness

misapplied difference - ‘special cases’ -

creates inefficiency

misapplied samenesscreates failure-demand– a key cause of waste…

Page 90: Same and different - architectures for mass-uniqueness

Into practice…

Trying to apply rules to everything,or to automate everything,

will cause your system to fail.

How do you identify the right balancebetween sameness and difference?

How will you avoid inefficiency,or failure-demand?

Page 91: Same and different - architectures for mass-uniqueness

“What’s the story?”Balancing samenessand uniqueness

Page 92: Same and different - architectures for mass-uniqueness

Taylorist-type modelstend to assume that everything

is a machine to ‘control’…

Find the right fit!

people will oftenrelate to machines

as if they’re other people…

Page 93: Same and different - architectures for mass-uniqueness

Wrong and right…

order(rules do work here)

unorder(rules don’t work here)

PEOPLEas MACHINES

PEOPLEas PEOPLE

CC-BY justin pickard via Flickr CC-BY andré luís via Flickr

Page 94: Same and different - architectures for mass-uniqueness

Right and wrong…

order(rules do work here)

unorder(rules don’t work here)

MACHINESas MACHINES

MACHINESas PEOPLE

CC-BY-SA izzard via FlickrCC-BY-SA MysteryBee via Flickr

Page 95: Same and different - architectures for mass-uniqueness

How we really think…

CC-BY Brett Jordan via Flickr

Page 96: Same and different - architectures for mass-uniqueness

Use context-maps such as SCANto identify

what may or must changewhat is or is not certain

how these vary over timeand what to do with each

Mapping the context-space

Page 97: Same and different - architectures for mass-uniqueness

A surgical example…

patient identity

surgery plan

emergency action

theatrebooking

consumables

pre-op complications

family behaviour

surgical-staff availability

change oftheatre-availability

action-records

equipmentplan

patientcondition

verify identity

NOW!

before

certain

uncertain

Page 98: Same and different - architectures for mass-uniqueness

A surgical example…

patient identity

theatrebooking

consumables

action-records

equipmentplan

verify identity

we need to be certain about all of these

NOW!

before

certain

uncertain

Page 99: Same and different - architectures for mass-uniqueness

A surgical example…

surgery plan

surgical-staff availability

change oftheatre-availability

patientcondition

we expect(and plan for)

uncertaintyabout these

NOW!

before

certain

uncertain

Page 100: Same and different - architectures for mass-uniqueness

A surgical example…

emergency action

pre-op complications

family behaviour

we don’t expectthese to happen,

but we need contingency-plans

and guiding-principlesfor all of them

NOW!

before

certain

uncertain

Page 101: Same and different - architectures for mass-uniqueness

Into practice…

How would you map the right fitfor each type of context?

How would you ensure you don’ttreat people as machinesor machines as people?

How will you managethe inherent uncertainties?

Page 102: Same and different - architectures for mass-uniqueness

“What’s the story?”Uniqueness, changeand governance

Page 103: Same and different - architectures for mass-uniqueness

standardised

Balancing the spectra…

customised unique

sameness uniqueness

high-probability low-probability

high-dependency low-dependency

reusability bespoke

low rate of change high rate of change

Page 104: Same and different - architectures for mass-uniqueness

We need architecturesthat express that balance

between sameness and uniqueness,and other trade-offs across the space…

Architectures and governance

…and governanceto guide relative-positioning

and changes over timebetween backbone and edge

Page 105: Same and different - architectures for mass-uniqueness

Architectures for change

BACKBONE EDGE

Page 106: Same and different - architectures for mass-uniqueness

Into practice…

What do you need, to balancesameness and differencecertainty and uncertainty

across your whole business-context?

What architecturesdo you need for this?

What governance do you needto manage their changes over time?

Page 107: Same and different - architectures for mass-uniqueness

Same and different

Some key take-aways, I hope?

•Many industries depend on mass-uniqueness

•Sameness and efficiency are important, but over-focus on sameness can fail, lethally

•Uniqueness is inherent and unavoidable

•Need ‘just enough sameness’ to support scale

•Work with uniqueness, not against it

Page 108: Same and different - architectures for mass-uniqueness

“What’s the story?”Thank you!

Page 109: Same and different - architectures for mass-uniqueness

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: • 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)

Image-credits: Slides 64-67 courtesy of 3D Systems: http://www.bespokeinnovations.com/ Other photo-images via Flickr or Wikimedia, as shown on each slide

Further information: