The document discusses challenges related to enterprise architecture practice. It addresses the need to create consistency and awareness of interdependence across services, embrace change, provide direction and focus, share ownership of the architecture, engage stakeholders through multiple senses, and explain architecture concepts through storytelling. Storytelling is highlighted as a way to make abstract ideas more visual, personal and engaging for various audiences.

1. 3: “It depends…” 4: “Everything changes”
Create consistency and awareness of Expect change in the architecture
interdependence across the architecture Practice: Change
Practice: Interdependence If everything’s changing, how can you
How do the services serve each other? know that you’ve arrived?
• Service-consumption (before, during, What map can you use if ‘there’ isn’t
after) there when you get there?
• Service-provision (before, during,
after)
• Direction, coordination, validation
• Investor, beneficiary, governance
How do the services talk with each other?
What stories do they exchange? And why?
5: “Where are we headed?”
Create a stable anchor-direction for the
architecture
Practice: Direction
What guiding-star for the enterprise?
• Focus (the focus of interest to
everyone in the shared-enterprise)
• Action (what is being done to or
with or about the concern)
• Qualifier (the emotive driver for
action on the concern)
How to link organization with enterprise?
6: “Share the story”
Create awareness of architecture as a
shared responsibility for and of everyone
Practice: Engagement
How 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 story
What else can you do to share the story?

2. 7: “Embrace the senses”
Create stronger engagement in the
architecture
Practice: Senses
What can you do to engage the senses?
• Texture
• Shape
• Sound
• Scent
• Taste
How to make the architecture tangible?
Worksheet
Eight real-world challenges from EA practice
8: “Architecture as story” 1: “It’s all about service”
Describe relationships between structure Change business focus from product to
and story, organisation and enterprise, and service
the human aspects of architecture, to Practice: Service
architects from the defence-industry Products always imply a service…
Practice: Story • Whom do you serve, and how?
Use a story to explain an abstract idea • How will you know you’ve served?
• Make it visual, vibrant, engaging • How will you know you’ve served
• Make it personal, human, ‘real-world’ well?
• Include all of the senses • Who decides?
• Make it their story – their terms, How do you move from product to service?
their jokes
What else to engage your audience in the
story?
Further information: 2: “Which point of view?”
Contact: Tom Graves [Tetradian Consulting] Use the architecture to help strategists
to break out of the self-centric box
Phone 0781 560 6624 (intl: +44 781 560 6624); Skype: tom_graves
Practice: Perspective
Email: tom@tetradian.com What changes as you change
Twitter: @tetradian ( http://twitter.com/tetradian ) perspective?
Weblog: http://weblog.tetradian.com • Inside-in
• Inside-out
Slidedecks: http://www.slideshare.net/tetradian
• Outside-in
Publishing: http://tetradianbooks.com and http://leanpub.com/u/tetradian • Outside-out
Books: The enterprise as story: the role of narrative in enterprise-architecture (2012) What do these differences imply? To whom?
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)