the futures of businessLessons learnt in EA articulation   strategies, services, senses and story       Tom Graves, Tetrad...
Inviting insight:Eight real-world challenges     from EA practice
#1“It’s all about service”
Challenge:Change business focus    from product      to service
ProductProduct is static…                        CC-BY Kiran Kodoru via Flickr
ServiceServiceimpliesaction…   …action           implies           service               CC-BY Igor Schwarzmann via Flickr
It’s always about people…               …‘service’ means that          someone’s needs are served                         ...
Practice: ServiceProducts always imply a service… • Whom do you serve, and how? • How will you know you’ve served? • How w...
#2“Which point of view?”
Challenge:Use the architecture to help strategists  to break out ofthe self-centric box
alwaysInside-in…       at risk of             drowning in              the detail…                    CC-BY Myrmi via Flickr
Inside-out…  We create an architecture      for an organisation,but about a broader enterprise.                           ...
Outside-in…               “Customers             do not appear          in our processes,               we appear in      ...
Outside-out…There’s always a larger scope…                                 CC-BY Matt Brown via Flickr
Practice: PerspectiveWhat changes as you change perspective?   • Inside-in   • Inside-out   • Outside-in   • Outside-outWh...
#3“It depends…”
Challenge:  Create consistency   and awareness of   interdependenceacross the architecture
Interdependence       In an ecosystem of services,  everything depends on everything else          For ecosystem viability...
(which is where this guy comes into the picture…)
Everything’s a service(focus on some service in a chosen value-flow)
Everything’s a service(interactions occur before and after the main transactions)
Everything’s a service(identify subsidiary services to manage interactions)
Everything’s a service(identify inbound and outbound partners for the interactions)
Everything’s a service(include links with services to direct, coordinate and validate)
Everything’s a service(include relationships with investors and beneficiaries)
Everything’s a service(this ‘robot’ is the Enterprise Canvas service-template)
Keep it simple…    …build the (human) story
Practice: InterdependenceHow do the services serve each other? •   Service-consumption (before, during, after) •   Service...
#4“Everything changes”
Challenge:  Expect changein the architecture
There is no ‘state’…- no certain ‘as-is’ or ‘to-be’…                                     …there                           ...
…and when we get there…                              CC-BY Miguel Vieira via Flickr  …it’s not the ‘there’ we expected.
What stays the same on the journey?                            CC-BY Gordon Hunter via Flickr …how will we know we’ve arri...
Practice: Change If everything’s changing,     how can you know    that you’ve arrived? What map can you use   if ‘there’ ...
#5“Where are we headed?”
Challenge:Create a stable anchor-direction      for the architecture
A myriad of ‘guiding stars’ out there…      …choose one that looks right to you.             Example (TED conferences): “I...
“Ideas worth                             spreading”Concern: the focus ofinterest to everyone inthe shared-enterprise      ...
Action: what is beingdone toor with or aboutthe concern                        “Ideas worth spreading”                    ...
Qualifier:          “Ideas worththe emotive            spreading”driver for actionon the concern                     CC-BY...
Practice: DirectionWhat guiding-star for the enterprise?   • Focus   • Action   • QualifierHow to link organisation with e...
#6“Share the story”
Challenge:    Create awareness      of architectureas a shared responsibility   for and of everyone
Nice view of structure, but…
…where are the people?
…where’s the story?
So start with a structure…
…include the human story
Practice: EngagementHow can you include people in the story? •   Engage everyone in building the story •   Make it persona...
#7“Embrace the senses”
Challenge:Create stronger engagement    in the architecture
Texture…           CC-BY Mike Baird via Flickr
Shape…         CC-BY Franco Follini via Flickr
Sound…         CC-BY Angelo Cesare via Flickr
Aroma…         CC-BY Andy Tyler via Flickr
Taste…         CC-BY Ian Armstrong via Flickr
Tangibility…
Practice: SensesWhat can you do to engage the senses?   • Texture   • Shape   • Sound   • Scent   • TasteHow to make the a...
#8“Architecture as story”
Challenge: Describe relationships between        structure and story,    organisation and enterprise,the human aspects of ...
Here’s part of a text-based version,  nicely generic, nicely abstract –   the usual way we’d do this…
Whose architecture?           “An architecture          describes structure      to support a shared-story.”              ...
Whose architecture?    “An organisation is bounded by    rules, roles and responsibilities;       an enterprise is bounded...
(yawn…)
Here’s another way to do it,for that specific audience…
Current EA emphasises structure...So, here’s a structure...
It’s called the Sambadromo...Which doesn’t really tell us anything.To make sense of a structure,we need the story here... ...
…the story of Carnaval.                          CC-BY Boban021 via Flickr
Here, in Rio, a huge shared-story...                                 CC-BY sfmission via Flickr
Full of colour, sound, spectacle...                                      CC-BY sfmission via Flickr
...and occasional extremes...                                CC-BY sfmission via Flickr
But it’s more aboutexuberance,and pride...                      CC-BY sfmission via Flickr
The young(er)...                   CC-BY sfmission via Flickr
The old(er)...                 CC-BY sfmission via Flickr
The whole community…                       CC-BY sfmission via Flickr
And if a line-up like this...                                CC-BY sfmission via Flickr
might remind you of this...                              CC-BY bobaliciouslondon via Flickr
do rememberto keep track of the story!                 CC-BY sfmission via Flickr
Yet when the party’s over,and it’s time to head home...                                CC-BY sfmission via Flickr
Someone must be there to clean up...- because that’s part of the story too.                                   CC-BY otubo ...
Process, assets, data, locations....- all the usual structure-stuff......all those necessary details   of organisation.   ...
Organisation focusses on structure…                               CC-BY Avodrocc via Flickr
yet the enterprise is the story.                                   CC-BY Boban021 via Flickr
The structure happens    because of the story.
A key task of enterprise-architectureis to rememberand design for that fact,maintaining the balancebetween structure and s...
Practice: StoryUse a story to explain an abstract idea •   Make it visual, vibrant, engaging •   Make it personal, human, ...
“What’s the story?”   “What next?”
Practice: Your insightsWhat did you discover in doing this? • Service               • Perspective • Interdependence       ...
the futures of businessThank you!
Further information: Contact:        Tom Graves Company:        Tetradian Consulting Email:          tom@tetradian.com Twi...
Upcoming SlideShare
Loading in...5
×

Lessons-learnt in EA articulation

1,363
-1

Published on

A 'mini-workshop' on insights from current developments and practice in enterprise-architecture (BCS-EA conference, London, October 2012)

The main part of the presentation is split into eight 'chunks', each tackling a single 'lesson-learnt' from trying to explain EA themes to others in real-world EA practice. Each 'chunk' is timed as around two minutes of background and overview (the bulk of the slides, between the respective 'Challenge' and 'Practice'), and then four minutes pair-discussion around the questions summarised on the respective 'Practice' slide. With two minutes at the start for overall lead-in, and ten minutes at the end for general discussion about what came up for participants during the Practice sections, this fits exactly into a one-hour time-slot.

(See http://www.slideshare.net/tetradian/lessonslearnt-in-ea-articulation-worksheet for the associated worksheet.)

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,363
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
105
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Lessons-learnt in EA articulation

  1. 1. the futures of businessLessons learnt in EA articulation strategies, services, senses and story Tom Graves, Tetradian Consulting BCS EA Conference, London, October 2012
  2. 2. Inviting insight:Eight real-world challenges from EA practice
  3. 3. #1“It’s all about service”
  4. 4. Challenge:Change business focus from product to service
  5. 5. ProductProduct is static… CC-BY Kiran Kodoru via Flickr
  6. 6. ServiceServiceimpliesaction… …action implies service CC-BY Igor Schwarzmann via Flickr
  7. 7. It’s always about people… …‘service’ means that someone’s needs are served CC-BY AllBrazilian via Wikimedia
  8. 8. Practice: ServiceProducts always imply a service… • Whom do you serve, and how? • How will you know you’ve served? • How will you know you’ve served well? • Who decides?How do you move from product to service?
  9. 9. #2“Which point of view?”
  10. 10. Challenge:Use the architecture to help strategists to break out ofthe self-centric box
  11. 11. alwaysInside-in… at risk of drowning in the detail… CC-BY Myrmi via Flickr
  12. 12. Inside-out… We create an architecture for an organisation,but about a broader enterprise. CC-BY – Paul – via Flickr
  13. 13. Outside-in… “Customers do not appear in our processes, we appear in their experiences.” Chris Potts, recrEAtion, Technics, 2010 CC-BY Fretro via Flickr
  14. 14. Outside-out…There’s always a larger scope… CC-BY Matt Brown via Flickr
  15. 15. Practice: PerspectiveWhat changes as you change perspective? • Inside-in • Inside-out • Outside-in • Outside-outWhat do these differences imply? To whom?
  16. 16. #3“It depends…”
  17. 17. Challenge: Create consistency and awareness of interdependenceacross the architecture
  18. 18. Interdependence In an ecosystem of services, everything depends on everything else For ecosystem viability,everything needs to support everything else CC-BY codiferous via Flickr
  19. 19. (which is where this guy comes into the picture…)
  20. 20. Everything’s a service(focus on some service in a chosen value-flow)
  21. 21. Everything’s a service(interactions occur before and after the main transactions)
  22. 22. Everything’s a service(identify subsidiary services to manage interactions)
  23. 23. Everything’s a service(identify inbound and outbound partners for the interactions)
  24. 24. Everything’s a service(include links with services to direct, coordinate and validate)
  25. 25. Everything’s a service(include relationships with investors and beneficiaries)
  26. 26. Everything’s a service(this ‘robot’ is the Enterprise Canvas service-template)
  27. 27. Keep it simple… …build the (human) story
  28. 28. Practice: InterdependenceHow do the services serve each other? • Service-consumption (before, during, after) • Service-provision (before, during, after) • Direction, coordination, validation • Investor, beneficiary, governanceHow do the services talk with each other?What stories do they exchange? And why?
  29. 29. #4“Everything changes”
  30. 30. Challenge: Expect changein the architecture
  31. 31. There is no ‘state’…- no certain ‘as-is’ or ‘to-be’… …there is only everything’s moving… the ‘now’ CC-BY Webb Zahn via Flickr
  32. 32. …and when we get there… CC-BY Miguel Vieira via Flickr …it’s not the ‘there’ we expected.
  33. 33. What stays the same on the journey? CC-BY Gordon Hunter via Flickr …how will we know we’ve arrived?
  34. 34. Practice: Change If everything’s changing, how can you know that you’ve arrived? What map can you use if ‘there’ isn’t there when you get there?
  35. 35. #5“Where are we headed?”
  36. 36. Challenge:Create a stable anchor-direction for the architecture
  37. 37. A myriad of ‘guiding stars’ out there… …choose one that looks right to you. Example (TED conferences): “Ideas worth spreading” Use it as your guiding-star. Everywhere.
  38. 38. “Ideas worth spreading”Concern: the focus ofinterest to everyone inthe shared-enterprise CC-BY UK DFID via Flickr
  39. 39. Action: what is beingdone toor with or aboutthe concern “Ideas worth spreading” CC-BY US Army Africa via Flickr
  40. 40. Qualifier: “Ideas worththe emotive spreading”driver for actionon the concern CC-BY HDTPCAR via Flickr
  41. 41. Practice: DirectionWhat guiding-star for the enterprise? • Focus • Action • QualifierHow to link organisation with enterprise?How to use it as your guiding-star?
  42. 42. #6“Share the story”
  43. 43. Challenge: Create awareness of architectureas a shared responsibility for and of everyone
  44. 44. Nice view of structure, but…
  45. 45. …where are the people?
  46. 46. …where’s the story?
  47. 47. So start with a structure…
  48. 48. …include the human story
  49. 49. Practice: EngagementHow can you include people in the story? • Engage everyone in building the story • Make it personal: anecdotes, images, photos • Support conversation and communication • Make it their storyWhat else can you do to share the story?
  50. 50. #7“Embrace the senses”
  51. 51. Challenge:Create stronger engagement in the architecture
  52. 52. Texture… CC-BY Mike Baird via Flickr
  53. 53. Shape… CC-BY Franco Follini via Flickr
  54. 54. Sound… CC-BY Angelo Cesare via Flickr
  55. 55. Aroma… CC-BY Andy Tyler via Flickr
  56. 56. Taste… CC-BY Ian Armstrong via Flickr
  57. 57. Tangibility…
  58. 58. Practice: SensesWhat can you do to engage the senses? • Texture • Shape • Sound • Scent • TasteHow to make the architecture tangible?
  59. 59. #8“Architecture as story”
  60. 60. Challenge: Describe relationships between structure and story, organisation and enterprise,the human aspects of architecture,to enterprise-architects and others from the defence-industry
  61. 61. Here’s part of a text-based version, nicely generic, nicely abstract – the usual way we’d do this…
  62. 62. Whose architecture? “An architecture describes structure to support a shared-story.” Tom Graves, The Enterprise As Story, Tetradian, 2012Organisation aligns with structure, enterprise with story.We need a balance of both for the architecture to work.
  63. 63. Whose architecture? “An organisation is bounded by rules, roles and responsibilities; an enterprise is bounded by vision, values and commitments.” Tom Graves, Mapping the Enterprise, Tetradian, 2010Organisation aligns with structure, enterprise with story.We need a balance of both for the architecture to work.
  64. 64. (yawn…)
  65. 65. Here’s another way to do it,for that specific audience…
  66. 66. Current EA emphasises structure...So, here’s a structure...
  67. 67. It’s called the Sambadromo...Which doesn’t really tell us anything.To make sense of a structure,we need the story here... CC-BY Avodrocc via Flickr
  68. 68. …the story of Carnaval. CC-BY Boban021 via Flickr
  69. 69. Here, in Rio, a huge shared-story... CC-BY sfmission via Flickr
  70. 70. Full of colour, sound, spectacle... CC-BY sfmission via Flickr
  71. 71. ...and occasional extremes... CC-BY sfmission via Flickr
  72. 72. But it’s more aboutexuberance,and pride... CC-BY sfmission via Flickr
  73. 73. The young(er)... CC-BY sfmission via Flickr
  74. 74. The old(er)... CC-BY sfmission via Flickr
  75. 75. The whole community… CC-BY sfmission via Flickr
  76. 76. And if a line-up like this... CC-BY sfmission via Flickr
  77. 77. might remind you of this... CC-BY bobaliciouslondon via Flickr
  78. 78. do rememberto keep track of the story! CC-BY sfmission via Flickr
  79. 79. Yet when the party’s over,and it’s time to head home... CC-BY sfmission via Flickr
  80. 80. Someone must be there to clean up...- because that’s part of the story too. CC-BY otubo via Flickr
  81. 81. Process, assets, data, locations....- all the usual structure-stuff......all those necessary details of organisation. CC-BY jorgeBRAZIL via Flickr
  82. 82. Organisation focusses on structure… CC-BY Avodrocc via Flickr
  83. 83. yet the enterprise is the story. CC-BY Boban021 via Flickr
  84. 84. The structure happens because of the story.
  85. 85. A key task of enterprise-architectureis to rememberand design for that fact,maintaining the balancebetween structure and story.Architecture is about structure.Architecture is also about story.We need both, to make it all happen. CC-BY SheilaTostes via Flickr
  86. 86. Practice: StoryUse a story to explain an abstract idea • Make it visual, vibrant, engaging • Make it personal, human, ‘real-world’ • Include all of the senses • Make it their story – their terms, their jokesWhat else to engage your audience in the story?
  87. 87. “What’s the story?” “What next?”
  88. 88. Practice: Your insightsWhat did you discover in doing this? • Service • Perspective • Interdependence • Change • Direction • Engagement • Senses • StoryWhat will you do different on Monday morning?
  89. 89. the futures of businessThank you!
  90. 90. Further information: Contact: Tom Graves Company: Tetradian Consulting Email: tom@tetradian.com Twitter: @tetradian ( http://twitter.com/tetradian ) Weblog: http://weblog.tetradian.com Slidedecks: http://www.slideshare.net/tetradian Publications: http://tetradianbooks.com and http://leanpub.com/u/tetradian Books: • The enterprise as story: the role of narrative in enterprise-architecture (2012) • Mapping the enterprise: modelling the enterprise as services with the Enterprise Canvas (2010) • Everyday enterprise-architecture: sensemaking, strategy, structures and solutions (2010) • Doing enterprise-architecture: process and practice in the real enterprise (2009)
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×