People often think of enterprise information architecture as the practice of harmonizing the design and usability of an enterprise’s many disparate internet and intranet sites. However, information architects can add further value to the enterprise which they serve. Information architects can use their techniques and methods to provide more of an impact to their organization than designing and implementing computer based user interfaces. Information architecture can organize, align and exploit information across the enterprise.
The impact and scope of enterprise information architecture can range from the mild: mapping paper based forms and reports; to the sublime: aligning organizational critical mission, policy and administrative information.
3. Agenda
• The Enterprise
• Information Architecture
– Traditional IA
– Traditional EIA
• Start to think outside the Box
• Where to start
• How to Sustain
10. Start to Think Outside of the Box
MeetingsFilling Systems
Regulations and
Documentation
PresentationsThe Web
Let go of the Interface….
All have information the (E)IA
can work with!
11. An Enterprise Exercise for the IA
Meetings Why?
• Usability
• Find inefficiencies
• Promote information sharing and knowledge
• Make meetings more “usable”
• Economy
• Increase Productivity
• Free Resources
12. An Enterprise Exercise for the IA
Meetings
Traditional IA Actions
• Analyze
• Document
Content
Inventory
Content
Map
EA Actions
Align to Enterprise
Regulations and
Documentation
Presentations
13. An Enterprise Exercise for the IA
Decompose the Meeting (Content Analysis)
Agenda
Notes Reports
Product
Regulations
& Policies Schedules Artifacts Dependencies
14. An Enterprise Exercise for the IA
Decompose the Meeting (Content Analysis)
Regulations & Policies
• Mandate for the meeting
• Objectives
• Define Inputs and outputs
• Who should be there
• Insight to perceived, actual
and should be
15. An Enterprise Exercise for the IA
Decompose the Meeting (Content Analysis)
Schedule
• Recurrence
• “Business Rhythm”
16. An Enterprise Exercise for the IA
Decompose the Meeting (Content Analysis)
Agenda
Notes
Artifacts
• Information rich
• Reveals structures
17. An Enterprise Exercise for the IA
Decompose the Meeting (Content Analysis)
Dependencies
• Inputs and outputs
Reports
Product
21. An Enterprise Exercise for the IA
Findings, Recommendations & Results
Agenda
Notes Reports
Product
Regulations
& Policies Schedules Artifacts Dependencies
• Personnel
Reporting
Gap (A-B)
• Policy Infraction
(C-D)
• Practice
Recommendation
(D-A)
• 60% Of Agenda
Items Align—
Possible Content
Structure for
Intranet
• Meeting D
Produce Personnel
Projection
22. EIA Keys to Success
• Organizational Buy in
– Dedicate resources (Policy, People, Funding)
• Individual Buy in
– Stovepipe management barrier to success
• Execution Model
– Plan to Plan
– Baby Steps
• Actionable Architecture
– No Shelfware!
– No Wallpaper!
23. EIA Thoughts
• EIA works with but is not:
– Records Management (DB Centric)
– Enterprise Librarian (Content Management
Centric)
– Data Architect (Too small)
– Knowledge Management (Too Big)
24. EIA Reference
• Zachman Framework
(www.zachmaninternational.com)
• The Art of Enterprise Information
Architecture: A Systems-Based
Approach for Unlocking Business
Insight (Amazon.com)
• Youtube—Greg the Architect SOA
This SOA That