Architecting Value

91
Architecting Value
  • date post

    18-Sep-2014
  • Category

    Design

  • view

    28
  • download

    3

description

A presentation on the relationship of information architecture to systems, frameworks and strategy. Presented at the 2009 IA Summit.

Transcript of Architecting Value

Page 1: Architecting Value

Architecting Value

Page 2: Architecting Value

Matthew Milan

mmilan

[email protected]

design of design, situated/ubicomp, strategic theory, hardware hacking

Page 3: Architecting Value

Horror Stories Or, what happens when you poke a business without a framework.

Page 4: Architecting Value

Let’s hear your horror stories

Page 5: Architecting Value

This is what happens when you poke a monster without understanding its nature.

http://www.jasonchanart.com

Page 6: Architecting Value

STRATEGY "IS DEAD

Page 7: Architecting Value

Today systems oo frameworks oo strategies oo actions

Page 8: Architecting Value

Let’s level set

We’re not in Kansas anymore, Dorothy

Page 9: Architecting Value
Page 10: Architecting Value
Page 11: Architecting Value

Bruce Sterling, Economist

Page 12: Architecting Value
Page 13: Architecting Value

Jeanne Liedtka, Futurist

Page 14: Architecting Value

“He who can handle" the quickest rate of "

change survives”

Page 15: Architecting Value

John Boyd, Designer grandstrategic oo strategic oo grandtactical oo tactical

Page 16: Architecting Value
Page 17: Architecting Value

Bruce&"Jeanne&"John.

What happened to Jesse, Peter and Lou?

Page 18: Architecting Value

We need to expand our repertoire.

Page 19: Architecting Value
Page 20: Architecting Value

A mental tapestry of changing intentions for harmonizing and focusing our efforts as a basis for realizing some aim or purpose in an unfolding and often unforeseen world of many bewildering events and many contending interests.

Page 21: Architecting Value

To improve our ability to shape and adapt to unfolding circumstances, so that we (as individuals or as groups) can survive on our own terms.

Page 22: Architecting Value

Great strategy is not about competition."

Great strategy is about adaptation.

Page 23: Architecting Value
Page 24: Architecting Value

Observe"Orient"Decide"Act

Page 25: Architecting Value
Page 26: Architecting Value
Page 27: Architecting Value

A way of thinking about survival and

success.

Page 28: Architecting Value

Structural Strategy

Page 29: Architecting Value
Page 30: Architecting Value
Page 31: Architecting Value
Page 32: Architecting Value

Knowing what to do next

Page 33: Architecting Value

Getting value out of a system

Page 34: Architecting Value

Structure is power

Page 35: Architecting Value

Building structures creates power

Page 36: Architecting Value

Architects build structures

Page 37: Architecting Value

Architects work with systems Systems connect information

Page 38: Architecting Value

In systems, information=value Mapping that value is the domain of frameworks

Page 39: Architecting Value

How do you work "with systems?

Page 40: Architecting Value

Know what, where, why and how to poke

Page 41: Architecting Value

What&"Where&"Why&"How.

Page 42: Architecting Value

Observe&"Orient&"Decide&"Act.

Page 43: Architecting Value

System&"Framework&"Strategy&"Action.

Page 44: Architecting Value

The art of the poke

Page 45: Architecting Value

I promise you, there is information architecture

in these brambles, thickets and dark

forests

Page 46: Architecting Value

The great ice age

Page 47: Architecting Value

Futures under glass

Page 48: Architecting Value

The thawing

Page 49: Architecting Value

Shattered glass

Page 50: Architecting Value

The future of business is flexible frameworks

Just like the future of the web

Page 51: Architecting Value

Futures under plastic

Page 52: Architecting Value

Structural Strategy

Page 53: Architecting Value

The web is a social machine

Page 54: Architecting Value

Business is a social machine

Page 55: Architecting Value

When you wake up, your business model will

be a financial graph

Page 56: Architecting Value
Page 57: Architecting Value

How long did it take to get to the readoowrite web?

Page 58: Architecting Value

Where’s my readoowrite business?

Page 59: Architecting Value

10 years ago You had to know how to survive in a business

Page 60: Architecting Value

3 years ago You had to know how to speak the language of business

Page 61: Architecting Value

Today If you’re not changing the business, you should just go home

Page 62: Architecting Value

What we’re learning is that you don’t need to lead the

business to change the business.

Page 63: Architecting Value

It’s all about the poke.

POKE!

Page 64: Architecting Value

http://lyc71-dumaine.ac-dijon.fr/upi/img/guillaume/tableau_guillaume.jpg

Page 65: Architecting Value

Ceci n'est pas une système http://www.peterme.com/blog/wp-content/uploads/2007/02/ipod_system.png

Page 66: Architecting Value

Businesses are not models

Businesses are systems

Page 67: Architecting Value

Systems Thinking

There be frameworks here

Page 68: Architecting Value

You change systems with inputs

Page 69: Architecting Value

You know where to poke with frameworks

Page 70: Architecting Value
Page 71: Architecting Value
Page 72: Architecting Value

http://businessmodelsinc.files.wordpress.com/2009/01/nespresso_businnes_model1.png

Page 73: Architecting Value
Page 74: Architecting Value

Strategy is poking with intent to create value

That’s the “why” you poke part.

Page 75: Architecting Value

In the end, it’s about understanding the

outcomes of your poke in the greater

business ecosystem

Page 76: Architecting Value

Build a framework to understand how you can

change a system to execute a strategy

through tactical actions "

Page 77: Architecting Value

Make your framework flexible and your strategy will be adaptable."

Page 78: Architecting Value

Revise your framework, so that the model more closely represents the real world.

Page 79: Architecting Value

Being in a state of adaptability will ensure that you are always able to find and surface the value in systems"

Page 80: Architecting Value
Page 81: Architecting Value

There is no spoon

Page 82: Architecting Value

The art of the end-run

Page 83: Architecting Value

Good end-runs "are like zombies

Page 84: Architecting Value

ARCHITECTING VALUE

Page 85: Architecting Value

Most businesses have a limited view of how they monetize the value they generate.

Page 86: Architecting Value

Outcomes, not incomes

Page 87: Architecting Value

Design the ecosystem, not the design

Page 88: Architecting Value

Frameworks are the new sitemaps

Page 89: Architecting Value

Strategies are the new wireframes

Page 90: Architecting Value

Information Architecture is Strategy

Page 91: Architecting Value

Salmon swim upstream

A final thought