Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Thinking outside the box enterprsie architecture ias10 online

81 views

Published on

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.

Published in: Internet
  • Be the first to comment

  • Be the first to like this

Thinking outside the box enterprsie architecture ias10 online

  1. 1. Enterprise Information Architecture IA Out of the Box Twitter: @info_do Web: www.info-do.org Ren Pope
  2. 2. Admin/Housekeeping • I lied… • I’m broke • Podiums suck • He who laughs (presents) last… • IA+EA I IA n
  3. 3. Agenda • The Enterprise • Information Architecture – Traditional IA – Traditional EIA • Start to think outside the Box • Where to start • How to Sustain
  4. 4. The Enterprise What is an Enterprise?The PeopleThe OrganizationsThe ProcessesThe Systems
  5. 5. The Enterprise Characteristics • Large, unwieldy • Centralized Control/Decentralized execution • Stovepiped Management
  6. 6. Enterprise Architecture • Capture • Analyze • Design • Report Uses multiple disciplines to: Align What is Enterprise Architecture?
  7. 7. Enterprise Architecture • Redundancy • Gaps • Compliance Identify Why Enterprise Architecture?
  8. 8. Information Architecture “Traditional” Information Architecture Display-like interfaces Presentation of Information Focused On User-Centered Design Organization of Information
  9. 9. Information Architecture “Traditional” Enterprise Information Architecture Focused On User-Centered Design across the Enterprise Intranet Internet CMS
  10. 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. 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. 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. 13. An Enterprise Exercise for the IA Decompose the Meeting (Content Analysis) Agenda Notes Reports Product Regulations & Policies Schedules Artifacts Dependencies
  14. 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. 15. An Enterprise Exercise for the IA Decompose the Meeting (Content Analysis) Schedule • Recurrence • “Business Rhythm”
  16. 16. An Enterprise Exercise for the IA Decompose the Meeting (Content Analysis) Agenda Notes Artifacts • Information rich • Reveals structures
  17. 17. An Enterprise Exercise for the IA Decompose the Meeting (Content Analysis) Dependencies • Inputs and outputs Reports Product
  18. 18. An Enterprise Exercise for the IA Align Across Enterprise
  19. 19. Meeting • Agenda • Personnel  • Updates  • Sales  • Business Development  • Product Review  • Schedule • Period  • Duration  • Dependencies • Product Website  •Quarterly Review  • Sales Forecast (Ops)  • Sales Forecast (Fin)  • High Level • Shows Structure • Each Node is an “Architectural Effort”  Required  Optional Meeting Components
  20. 20. Meeting Dependencies Current Gap Opportunity Meeting A Meeting B Meeting D Meeting C Personnel Product Forecast Personnel Projection Issue
  21. 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. 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. 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. 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
  25. 25. IA

×