business architecture: upwards, downwards, sideways, back

95
Business Architecture: Upwards, Downwards, Sideways, Back Tom Graves, Tetradian Consulting

Upload: tetradian-consulting

Post on 14-Apr-2017

4.578 views

Category:

Business


0 download

TRANSCRIPT

Page 1: Business Architecture: Upwards, Downwards, Sideways, Back

Business Architecture:Upwards, Downwards, Sideways, BackTom Graves, Tetradian Consulting

Page 2: Business Architecture: Upwards, Downwards, Sideways, Back

Business architecture:What’s this about?

What is business-architecture?

Where do we start?

Click icon to add picture

Click icon to add picture

Page 3: Business Architecture: Upwards, Downwards, Sideways, Back

What isBusiness Architecture?

Business-architecture isthe architecture

– the structure and the story –of the business of the

business.

Page 4: Business Architecture: Upwards, Downwards, Sideways, Back

What is Business Architecture?

Domains typically include business-models, operating-models and

capability-models.Domains in the business-architecture may also

include process-architectures, organisation-architectures, financial-

architectures and more.

Each organisation’s Business Architecture is its own choice of

architecture-domains.

Page 5: Business Architecture: Upwards, Downwards, Sideways, Back

Warning…

It’s a distinct architecture in its own right– we need to understand it as such,and then how it intersects with IT.

Business-architecture is more than“anything not-IT that might affect

IT”!

Page 6: Business Architecture: Upwards, Downwards, Sideways, Back

Where to start: Business-model…

Business Model Canvas and Value Proposition

20/01/2016CC-BY-NC Strategyzr

Page 7: Business Architecture: Upwards, Downwards, Sideways, Back

Where to start: Business-model…

Business Model Canvas populated, crosslinked

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 8: Business Architecture: Upwards, Downwards, Sideways, Back

Where to start: Business-model…

Business-model as descriptive story20/01/2016CC-BY-NC Strategyzr

Page 9: Business Architecture: Upwards, Downwards, Sideways, Back

Where to start: Capability-maps…

Capability-map: Functional Business Model

Accept Orders

Contact Customer

Manage the Business

Deliver Orders

Support the Business

Process Orders

Consolidate Orders

Manage Production

Management

Manage Licensee Outbound Operations

Manage Materials

Receipt and Verification

Manage Facility

Pre-Production Processing

Manage Container & Label StrategiesManage VehiclesManage Equipment and

Equipment-StrategiesManage Facility

Property

Manage Relationship

with Licensees

Manage Asset

Service Providers

Manage Transport Sub-Contracts for

Delivery

Manage NCR-Code Configurations

Define Processing Strategies

Define Performance Management

Manage Production Systems Strategies

Design and Develop Facility I nfrastructure

Manage Production-Planning Strategies

Manage Facility

I nformationManage Core

Business

Manage Post-Production Operations

Setup for Contractor Delivery

Manage Equipment

Maintenance

Manage Production Operations

Accept from

Agency

Accept from

Contractor

Accept at Facility

Accept at Customer Location

Manage FinanceManage Human Resources Manage Facility Administration

Manage Materials Strategies

Prepare Customer Transfer

Support Customer

Bulk Orders

Handle Customer

Complaints & Inquiries

Process Service

Requests

Fulfil Order

Prepare Fulfillment Transfer

Support Bulk Fulfillment

Orders

Handle Fulfillment Complaints & Inquiries

Process Fulfillment Requests

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 10: Business Architecture: Upwards, Downwards, Sideways, Back

Where to start: Capability-maps…

Three-tier Functional Business Model

Customer

OutboundInbound

Support

Transport

Process

Check and prepare vehicle

Road Transport Operations

Drop Off Orders & empty containers

Handle vehicle incidents (breakdowns,

re-fuel, etc.)

Capture transport run events

Drive transport vehicle between locations

Pick Up Orders & empty containers

Complete preparation of orders into consignments

Commence carrier service

Carrier staff verify consignment details & hand

over consignment to contractor

Lodge consignments with carrier

Verify / accept consignment Visit "trans-ship" port

Complete carrier service

Receive & verify consignments

Handle consignment exceptions

Separate and store containers etc. in preparation

for transport to facility

Domestic Carrier Transport Operations

Planning & Monitoring of Carrier Services

Determine required lodgement &

handover times

Receive new/ updated schedules

from carriers

Develop & maintain carrier lodgement

schedules

Monitor carrier services & provide corrective action

Assess disputed/late consignments

Transport Facility Management

Time and Attendance

Monitoring & Control

Review Facility Performance & implement

improvements

Planning & Scheduling

Staffing & Rostering

Manage

Stream orders into production

batches

Manage batch containers prior

to pick up

Consolidate Orders

Create & Maintain Facility NCR-Code

Plans

Estimate Production Volumes

Plan & Schedule Production Operations

Staffing & Rostering

Time and Attendance

Monitor Order Processing

Review Facility Performance & imp.

improvements

Corrective Action for Processing

Quality Control

Dock Management

Production Management

Corrective Action for Transport &

Delivery

Materials Receipt and Verification

Inspection of inbound materials

Process “Under Bond” Materials

Process Hazardous Materials

Handover Materials to Warehouse

Licensee Outbound Operations

Inspection of outbound product

Prepare licensee consignment for

despatch

Capture outbound volumes and

events

Despatch outbound product via licensee

carrier

Receive Transfers at Facility

Transfers Damage Check

Slotting / Sequencing

Interleaving

Pre-Mould Verify

Slippage Adjustment

Batch Alignment for Moulding

Pre-Production Processing at

Facility

Capture Processing Events

Prepare Customer Transfer

Plan Transfer Production

Prepare Transfer Data

Prepare Transfer Production

Prepare Transfer Documentation

Support Customer Bulk Orders

Advise customer of bulk-order

issues

Manage Customer Order

Quality

Support customer bulk orders

Handle Customer Complaints &

InquiriesReceive & record

notification of problems

Investigate & resolve problems

Report Status of Order

Handle general inquiries

Process Service Requests

Process Requests

Process Other Requests

Process Payment for Service

Consumable Tools

ManagementSpecify Tools requirements

Acquire & Locate Consumable Tools

Maintain inventory of Consumable Tools

Manage & perform maintenance of

Consumable Tools

Container & Label Management

Specify container requirements

Acquire & Supply Containers

Manage & perform maintenance of

containers

Maintain inventory of containers

Label Policy & Design

Manage Label Stock

Specify vehicle requirements

Vehicle Management

Purchase or Lease vehicles (&

accessories)

Dispose of vehicles

Maintain inventory of vehicles

Manage contracts with fuel suppliers

Monitor payments to fuel suppliers

Manage allocation of vehicles to facilities

Manage vehicle registration &

insurance

Prepare claims for diesel & alternative

fuel grant

Manage maintenance of

vehicles

Design, Specify & Evaluate New

Equipment

Purchase/Dispose Equipment &

Spares

Install & Relocate Equipment

Develop Maintenance

Strategies

Monitor & Optimise Performance &

Reliability

Equipment Management

Ensure Logistics & OH&S Compliance

Manage Equipment Configuration

Manage Technical Documents &

Support Systems

Manage Inventory, Repairs & Stores

Infrastructure

Property Management

Specify Property Requirements

Acquire Property

Dispose of Property

Manage Building Administration

Establish & Maintain Relationships with

Licensees

Manage Relationship with

Licensees

Calculate Revenue due from Licensees

Specify materials requirements

Materials Management

Acquire & Locate Materials

Maintain inventory of Materials

Select & Manage Asset Maintenance Service Providers

Evaluate & select Asset Maintenance Service Providers

Establish & maintain Asset Maintenance

Contracts

Monitor Service Provider performance

Terminate Contract

Manage Transport Sub-Contractors

Maintain Contractor Service Information

Evaluate & Select Transport

Contractors

Establish & Maintain Transport Contracts

Monitor Contractor Performance

Manage Payments to Contractors

Terminate Contract

Select & Manage Agencies

Evaluate & Select Agencies

Establish & Maintain Contracts with

Agencies

Monitor Agencies Performance

Manage Payments To/From Agencies

Terminate Contract with Agency

NCR-Code Management

NCR-Data Strategy, Policy &

Procedures

Maintain NCR Information

Maintain Machine Configuration Data

NCR Configuration Improvement

Manage Machine-Specific NCR Configuration

NCR Code-Sharing Management &

Support

Processing Policy, Procedures & Governance

Processing Strategies

Sorting Strategy & Design

Develop Processing Plans

Measurement of Service Quality

Measure Financial Performance

Measurement of Resource Utilisation

Performance Analysis

Performance Management

Production Systems

Initiate Project

Evaluate Solutions

Finalise Project

Systems support & maintenance

Develop / Enhance System

Implement System

Determine business systems

strategies

Systems control & Administration

Specify Facility Requirements

Model Proposed Solutions

Select & Design Preferred Solution

Plan & Schedule Facility

Development

Implement Facility Changes

Construct Facilities & Equipment

Facility / Infrastructure Design & Development

Production Planning

Determine prod’n strategy & direction

Capacity Planning

Investment Planning

Determine prod’n principles &

policies

Legislative Compliance

Develop & maintain Dangerous Goods

policies & procedures

Production Capability Analysis

Manage Facility Information

Define Costing Reference Data

Maintain Prod’n Structure

Information

Define terminology, & codes

Manage barcoding standards, formats & characteristics

Manage central storage of event

information

Manage inventory of

scanners

Manage central storage of production

volumes

I nternational CarrierTransport Operations

Receive inbound containers at origin

port

Handover outbound containers at

destination port

Transport bond containers from origin port to destination port

Manage Core Business

Develop Business Strategies

Manage business performance &

operations

Co-ordinate Projects

Develop Business Plans Manage Projects

Develop business perf. measures

& targets

Receive Container from Contractor

Drop-Off

Setup forContractorDelivery

Receive Misdirected Container from

Contractor

Deliver Container via Contractor

Record errors & notify customer

Store articles

Verify Customer Pick-up

Handle Undeliverables

(including missorts)

Calculate Priority Delivery Charge

Capture Contractor Delivery Events

Despatch Container for Contractor

Pick-Up

Handle delivery vehicle incidents

Check & Prepare Delivery Vehicles

Document Handover to Transport

Driver

CaptureNon-Contractor Delivery Events

Setup forNon-Contractor

Delivery

Handle Customer Returns

Deliver Container to Customer

Operate Vehicle for Transport Runs

Drop Off / Pick Up at Facility Depot

Establish Production Volumes

Time and Attendance

Monitor Post-Production Operations

Corrective Action

Review Facility Performance &

Implement Improvements

Manage Post-Production Operations

Staffing & Rostering

Plan & Schedule Operations

NCR-Code Updates

Capture Machine Configuration

Changes

Capture Tool Changes

Capture Machine Changes

Capture and Notify NCR-Code Changes

Equipment Maintenance

Plan & Schedule Equipment

Maintenance

Perform & Reord Equipment

Maintenance

Correct & Record Equipment Faults &

Parts Usage

Monitor & Report Maintenance Compliance

Modify Equipment

Optimise Equipment

Performance & Reliability

Handle Non-Valid Orders

Machine Preparation

Moulding

Capture volumes & machine statistics

Prepare agency consignments

Prepare product for road transport

Production Operations

Capture production events

Inward Dock Operations

Initial Preparation

Move Product between

processing steps

Order Configuration

Machine Production

Manual Preparation

Capture Order

Assemble Order

Prepare order documentation

Accept from Contractor

Accept Agency Order

Capture inbound order events

Receive inbound order from agency

Print & apply agency identifier

labels

Reconciliation of agency bills &

orders

Record agency order violations

Handover order documentation to transport driver

Receive Order Lodgement

Accept at Facility

Receive electronic order via internet

Process electronic order via email

Verify Order

Preparation & Streaming

Handle Rejected Orders

Capture Order information

Process Payment for Order

Handover Order to Transport

Driver

Capture actual acceptance

events

Verify Order

Accept at Customer Location

Finance

Provide Financial Analysis & Direction

Support Business Cases

Produce budgets & forecasts

Manage Financial Policy & Procedures

Record & monitor expenditure

Human Resources

Succession Planning Recruitment Maintain employee

recordsOccupational Health

& Safety Operational Training Leave AdministrationStaff Development Industrial Relations

Facility Administration

General Administration

Perform & Manage Stores Function

Manage Technical Documents

Maintain Technical Help Desk

Capture Consolidation

Events

Accept Inbound Requests

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 11: Business Architecture: Upwards, Downwards, Sideways, Back

A cautionary tale…

Foiled by financial-architecture?CC-BY-SA foam via Flickr

Page 12: Business Architecture: Upwards, Downwards, Sideways, Back

• Look upward to connect with big-picture

• Look downward to connect with real world

• Look sideways to connect all together• Beware of the pressures to go

backward

Four themes…

Page 13: Business Architecture: Upwards, Downwards, Sideways, Back

Business architecture:Looking upward

What is the broader context for this business-model?

How will the business-model make sense to all of its stakeholders?

Click icon to add picture

Click icon to add picture

Page 14: Business Architecture: Upwards, Downwards, Sideways, Back

Why anything happens…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

The vision describes the desired-ends for action;values guide action, describing how success would feel.

A tension exists between what is, and what we want

Page 15: Business Architecture: Upwards, Downwards, Sideways, Back

The nature of service…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

A service represents a means toward an end – ultimately, the desired-ends of the enterprise-vision.

Page 16: Business Architecture: Upwards, Downwards, Sideways, Back

Relations between services…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Services exchange value with each other, to help each service reach toward the respective vision and outcome.

Page 17: Business Architecture: Upwards, Downwards, Sideways, Back

Values and value…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Each service sits at an intersection of values (vertical) and exchanges of value (horizontal)

Page 18: Business Architecture: Upwards, Downwards, Sideways, Back

Organisation and enterprise…

Organisation“a structure and means to achieve

ends”(bounded by rules, roles and responsibilities)

Organisation and enterprise are not the same!

Enterprise “a shared purpose, a bold endeavour”

(bounded by vision, values and commitments)

Page 19: Business Architecture: Upwards, Downwards, Sideways, Back

Organisation as ‘the enterprise’

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

This is almost entirely internal – no-one else involved.

Page 20: Business Architecture: Upwards, Downwards, Sideways, Back

Supply-chain as ‘the enterprise’

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

This is about transactions with others, but usually from the organisation’s view first, or only.

Page 21: Business Architecture: Upwards, Downwards, Sideways, Back

Market as ‘the enterprise’

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

We start to address the complexity of the market-place – which often includes a more customer-centric view.

Page 22: Business Architecture: Upwards, Downwards, Sideways, Back

Shared-story as ‘the enterprise’

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

We engage with all of the complexities of the entire shared-enterprise – the enterprise-as-itself.

Page 23: Business Architecture: Upwards, Downwards, Sideways, Back

A stakeholder in the storyis anyonewho can wielda sharp-pointed stakein our direction…

CC-BY-NC-SA evilpeacock via Flickr

Stakeholders in the enterprise

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

Page 24: Business Architecture: Upwards, Downwards, Sideways, Back

Beware of anticlients…

Anticlients arise through deeply-held beliefs, or from perceived betrayal by the

organisation.Do not ignore anticlient-risks!

– anticlients do not transact, but interact in the story in ways that can destroy the

organisation.

Anticlients share the same enterprise, but deeply disagree with how the organisation

operates within that story.

Page 25: Business Architecture: Upwards, Downwards, Sideways, Back

Vision, purpose, promise

This is also about howwe keep to our purpose,and keep our promise……in a viable business, we don’t make promises that we can’t or won’t keep! Proximus, Belgium

Page 26: Business Architecture: Upwards, Downwards, Sideways, Back

A three-part ‘story’ that makes sense to all enterprise-stakeholders

Elements of a vision-statement

Action (‘How’): what is being done toor with or about the concern

Example: “Ideas worth spreading”

Qualifier (‘Why’): the emotive driverfor action on the concern

Example: “Ideas worth spreading”

Concern (‘What’): the focus of interestto everyone in the shared-enterprise

Example: “Ideas worth spreading”

Page 27: Business Architecture: Upwards, Downwards, Sideways, Back

Vision outlines the shared-story…

Principles devolve from values…

Value-propositions must align to vision, values, principles…Vision, role, mission, goal…

Values devolve from the vision…

Page 28: Business Architecture: Upwards, Downwards, Sideways, Back

Connect to the story

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 29: Business Architecture: Upwards, Downwards, Sideways, Back

A cautionary tale…

Organisation as enterprise?

Page 30: Business Architecture: Upwards, Downwards, Sideways, Back

Business architecture:Looking downward

How will the business-model be implemented?

What are some of the hidden ‘gotchas’ that could break the business-model?

Click icon to add picture

Click icon to add picture

Page 31: Business Architecture: Upwards, Downwards, Sideways, Back

Realising the business-model

Use SCORE to identify:- capabilities needed for the business-

model- which can be bought-in or outsourced

- which capabilities must remain in-house- the reasoning behind those decisions

Assemble from capabilities(‘capability’ as ‘the ability to do work’)

Page 32: Business Architecture: Upwards, Downwards, Sideways, Back

Introducing SCORE

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 33: Business Architecture: Upwards, Downwards, Sideways, Back

Start with an assertion:Everything in the enterpriseis or represents a service.

(If so, we can describe everythingin the same consistent, fractal way.)

Page 34: Business Architecture: Upwards, Downwards, Sideways, Back

(Business Model Canvas isn’t fractal– it’s linked only to a single high-level

view– so we need to adapt that business-

modelto a more fractal frame.)

Fractality is our friend…allows us to use the same

patternseverywhere, at every level

Page 35: Business Architecture: Upwards, Downwards, Sideways, Back

Business-model to Enterprise Canvas

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 36: Business Architecture: Upwards, Downwards, Sideways, Back

From an IT-centric view…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 37: Business Architecture: Upwards, Downwards, Sideways, Back

…but it’s much more than just IT

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 38: Business Architecture: Upwards, Downwards, Sideways, Back

Service-content…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

We can view in various ways what services consist of – but eventually we’ll need the full detail.

Page 39: Business Architecture: Upwards, Downwards, Sideways, Back

Service-content…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

At higher levels of abstraction (lists and relations only), we can get away with simple Zachman-interrogatives…

Page 40: Business Architecture: Upwards, Downwards, Sideways, Back

Service-content…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

…as we move towards detail, we must become more specific – yet still fully fractal.

Page 41: Business Architecture: Upwards, Downwards, Sideways, Back

Asset (‘What’)- a resource for which

the enterprise acknowledges responsibility

Composition:any combination of asset-dimensions.

Page 42: Business Architecture: Upwards, Downwards, Sideways, Back

Function (external of ‘How’)- external-facing interface,

responsible for service-contracts, protocols, SLAs, etc;

accepts and returns assetsComposition:

any combination of asset-dimensions.

Page 43: Business Architecture: Upwards, Downwards, Sideways, Back

Location (‘Where’)- a position within the terms of

a specific schemaComposition:

any combination of asset-dimensions,plus time-as-location.

Page 44: Business Architecture: Upwards, Downwards, Sideways, Back

Capability (‘Who’ / ‘How’ / ‘What’)- the ability to do something:

- agent enacts the capability- action asset-type acted upon

- skill-level competence of the agentComposition:

agent / action: asset-dimensions;skill-level: skills/decision dimensions;

also recursively consists of other services

Page 45: Business Architecture: Upwards, Downwards, Sideways, Back

Event (‘When’)- trigger for a function and

underlying capabilityComposition:

any combination of asset-dimensions.

Page 46: Business Architecture: Upwards, Downwards, Sideways, Back

Decision / Reason (‘Why’)- sensemaking / decision-

makingfor the service, and/or its type

of guidance or governanceComposition:

any combination of decision/skills dimensions.

Page 47: Business Architecture: Upwards, Downwards, Sideways, Back

Asset-dimensions…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Most entities will consist of any appropriate combination– e.g. book is physical ‘thing’, has information, is valued.

Page 48: Business Architecture: Upwards, Downwards, Sideways, Back

Decision/skills dimensions…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Most contexts will need to include combinations of these.

Page 49: Business Architecture: Upwards, Downwards, Sideways, Back

Working with complexity

Some complexities must be removed, others acknowledged and embraced

Use SCAN to identify:- where complexity exists, in what form- which complexities can be eliminated

- which complexities are inherent (‘wild’)- what techniques to use for each

Page 50: Business Architecture: Upwards, Downwards, Sideways, Back

SCAN for complexity-mapping

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 51: Business Architecture: Upwards, Downwards, Sideways, Back

Order and unorder

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

“Insanityis doing

the same thingand expecting

the same results”(not Albert Einstein)

ORDER(IT-type rules do work here)

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

“Insanityis doing

the same thingand expecting

different results”(Albert Einstein)

certain

uncertain

edge of uncertainty

Page 52: Business Architecture: Upwards, Downwards, Sideways, Back

Same and different

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

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)

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

certain

uncertain

Page 53: Business Architecture: Upwards, Downwards, Sideways, Back

A surgical example…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

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!

certain

uncertain

before

Page 54: Business Architecture: Upwards, Downwards, Sideways, Back

SCAN framework summary

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

order unorder

SIMPLE(enact)

regulationrotation(rules)

NOT-KNOWN(explore)reframe

rich-randomness(principles)

COMPLICATED(evaluate)

reciprocationresonance(algorithms)

AMBIGUOUS(experiment)

recursionreflexion

(patterns, guidelines)

NOW!

certain

uncertain

plan

actual

before

Page 55: Business Architecture: Upwards, Downwards, Sideways, Back

A spectrum of servicesalso implies

a spectrum of governance:governance of governance

itself.

Page 56: Business Architecture: Upwards, Downwards, Sideways, Back

Backbone and edge

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

order(rules do work here)

unorder(rules don’t work here)

fail-safe(high-dependability)

safe-fail(low-dependability)

analysis(knowable result)

experiment(unknowable result)

BACKBONE EDGE

Waterfall(‘controlled’ change)

Agile(iterative change)

Page 57: Business Architecture: Upwards, Downwards, Sideways, Back

Backbone and edge

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 58: Business Architecture: Upwards, Downwards, Sideways, Back

Backbone, domain and edge

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

order unorder

fail-safe(high-dependency)

BACKBONEsafe-fail

(low-dependency)

EDGE

plan

actual

Waterfall(‘controlled’ change)

Agile(iterative change)

Mixed(guided change)

analysis(knowable result)

DOMAIN experiment(unknowable result)

Page 59: Business Architecture: Upwards, Downwards, Sideways, Back

Pace-layering (and more)Different elements change at different rates – from days to

decades.Different elements have different lifetimes – from nanoseconds to

centuries.Different elements reference other

elements that have different rates of change, and different lifetimes.

It gets kinda complicated…

Page 60: Business Architecture: Upwards, Downwards, Sideways, Back

A cautionary tale…

Do the small details matter?

Page 61: Business Architecture: Upwards, Downwards, Sideways, Back

Business architecture:Looking sidewaysHow do we ensure compliance in the business-model?

How do we guide connection and change?

How do connect to and support the values of the broader enterprise?

Click icon to add picture

Click icon to add picture

Page 62: Business Architecture: Upwards, Downwards, Sideways, Back

Link services to broader enterprise

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Horizontal value-flow is easier to model, but we need also to support vertical links to enterprise-values

Page 63: Business Architecture: Upwards, Downwards, Sideways, Back

Interrelations between services

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 64: Business Architecture: Upwards, Downwards, Sideways, Back

Direction – strategy and tactics

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 65: Business Architecture: Upwards, Downwards, Sideways, Back

Direction – management-functions

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Staff-management includes policy, strategy, tactics

Page 66: Business Architecture: Upwards, Downwards, Sideways, Back

Staff-management, line-management

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Staff-managemen

t(looks to future)

Line-managemen

t(looks to past)

Page 67: Business Architecture: Upwards, Downwards, Sideways, Back

Coordination – action and change

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 68: Business Architecture: Upwards, Downwards, Sideways, Back

Coordination end-to-end

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 69: Business Architecture: Upwards, Downwards, Sideways, Back

Coordination over time

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 70: Business Architecture: Upwards, Downwards, Sideways, Back

Coordination – projects and change

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Modes for coordination link to modes for direction

Page 71: Business Architecture: Upwards, Downwards, Sideways, Back

Validation – connecting to values

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 72: Business Architecture: Upwards, Downwards, Sideways, Back

Enterprise-values areeveryone’s responsibility.

(Enterprise-values typically include:health-and-safety, security, reliability,

efficiency, effectiveness, financial-probity,environment, ethics and many more.)

Page 73: Business Architecture: Upwards, Downwards, Sideways, Back

Supporting the values

- build awareness of the business-importance of that value

- build capability to enact supportfor that value in real-world action

- assess compliance on and support continual-improvement on that value

For each enterprise-value,we need support-services that:

Page 74: Business Architecture: Upwards, Downwards, Sideways, Back

Investors and beneficiaries

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 75: Business Architecture: Upwards, Downwards, Sideways, Back

We need to considerinvestments and returnsof every applicable type,

to and fromevery type of stakeholder.

(‘Applicable type’ is determinedby the shared-enterprise values.)

Page 76: Business Architecture: Upwards, Downwards, Sideways, Back

Always start from the values.

(Not the money.)

Page 77: Business Architecture: Upwards, Downwards, Sideways, Back

Hidden risks of outsourcing

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Boundary-of-control is a legal constraint;boundary-of-identity is where enterprise thinks it is…

Page 78: Business Architecture: Upwards, Downwards, Sideways, Back

Connect values across boundaries

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 79: Business Architecture: Upwards, Downwards, Sideways, Back

A cautionary tale…

Playing ‘Pass The Grenade’?

Page 80: Business Architecture: Upwards, Downwards, Sideways, Back

Business architecture:Not going backwards

What anti-patterns do we need to avoid in the business-model and business-architecture?

Click icon to add picture

Click icon to add picture

Page 81: Business Architecture: Upwards, Downwards, Sideways, Back

Upwards, downwards, sideways…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

the organisation within the shared-enterprise…

Page 82: Business Architecture: Upwards, Downwards, Sideways, Back

…built from services like this…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 83: Business Architecture: Upwards, Downwards, Sideways, Back

…but there are all manner of conceptual-errors that can cause an organisation and its business-model to become

disastrously inefficient and ineffective.

These include…

Page 84: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #1:“It’s all about us”

Leads to inability to engagewith customers and others,and creates anticlient risks.

Page 85: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #2:“It’s all about

efficiency”Often leads to local-efficiencies

at the expense ofoverall effectiveness.

Page 86: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #3:“It’s all about control”

Often leads to attempts to control that which cannot be

controlled– inherently causing frustration

and failure.

Page 87: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #4:“It’s all about the silos”

Beware of Conway’s Law – it leads to end-to-end fragmentation and

incomprehensible systems.

Page 88: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #5:“It’s all about the

owners”Over-focus on a single group of stakeholders will increase risks

from anticlients and (many) others.

Page 89: Business Architecture: Upwards, Downwards, Sideways, Back

Business-Design Error #6:“It’s all about the

money”Over-focus on money will distort

all forms of decision-making, and will cause longer-term

failure.

Page 90: Business Architecture: Upwards, Downwards, Sideways, Back

If we focus too much on money, we lose track of the ‘why’ of values.

If we lose track of the ‘why’ of values,

we disconnect from the enterprise.If we disconnect from the enterprise,

there’s no business…Always start from the values.

(Not the money.)

Page 91: Business Architecture: Upwards, Downwards, Sideways, Back

Values-first architecture…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

Page 92: Business Architecture: Upwards, Downwards, Sideways, Back

Money-first architecture…

20/01/2016CC-BY-NC-SA Tom Graves / Tetradian 2016

The supposed ‘normal’ architecture for businessembeds all of those design-errors, and more…

Page 93: Business Architecture: Upwards, Downwards, Sideways, Back

A cautionary tale…

“Our strategy is last year +10%”

Page 94: Business Architecture: Upwards, Downwards, Sideways, Back

SummaryIn business-architecture:• Look upward

to connect with big-picture• Look downward

to connect with the real world• Look sideways

to connect everything together• Beware of the pressures

to go backward to what doesn’t work

Click icon to add picture

Click icon to add picture

Page 95: Business Architecture: Upwards, Downwards, Sideways, Back

Contact: Tom Graves

Company: Tetradian Consulting

Twitter: @tetradian ( http://twitter.com/tetradian )

Website: http://tetradian.com

Weblog: http://weblog.tetradian.com

Slidedecks: http://www.slideshare.net/tetradian

Print-books: http://tetradianbooks.com

E-Books: http://leanpub.com/u/tetradian

Example titles:

• Mapping the enterprise: modelling the enterprise as services with the Enterprise Canvas (2010)

• The service-oriented enterprise: enterprise architecture and viable services (2009)

• Doing enterprise-architecture: process and practice in the real enterprise (2009)

Further information: