The Need to Know for Information Architects: Big Data to Big Information
Download as PPTX, PDF7 likes1,193 views
The document discusses the roles and skills of an information architect. It states that an information architect must be able to bridge various groups through skills like UI/UX, data warehousing, taxonomy, and knowledge management. The document also discusses how information architects can help organizations transform big data into big information through tools like master data management, data warehouses, and data hubs. It emphasizes that information architects should continue growing their careers through certification, training, mentorship programs, and contributing to their professional community.
The Need to Know for Information Architects: Big Data to Big Information
- 1. Information Architecture Information as Strategy
- 2. Themes Architecture is technology value not delivery Architecture is a profession not a job Good technology strategy is about how architects engage with you The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 3. Iasa A platform for architects Education Mentoring Career Path Certification Best Practice The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 4. Iasa Form Communities – 2002 to 2005 Career Path - 2007 Capability Model – 2008 Certification – 2009 Foundation, Associate, CITA-P, CITA-M Foundation Training – 2010 Associate Training – 2011 Mentoring - 2012 The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 5. Skills ≠
- 6. Skill Set Enterprise Architecture Software Infrastructure Information Business Architecture Architecture Architecture Architecture Foundation Body of Knowledge Design Human Dynamics Quality Attributes IT Environment Business Technology Strategy The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2009
- 7. Career Path Awareness - Foundation Knowledge - Associate Practice – Internship and Mentoring Experience – CITA-Professional Contribution – CITA-Master The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 8. Career Path
- 9. Architect Engagement Enterprise Architects Enterprise Business Information Architects Architects Business Capability Software Architect Infrastructure Architects Data Center Software Software Architect Architect
- 10. Information Architects Come from 3 places Combine skills to DBA succeed User Integration Interface The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 11. Information Architecture The storage, retrieval, integration and utilization of information across an organization for strategic gain. The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited. © IASA 2010
- 12. End Module
- 13. The Need to Know for Information Architects: From Big Data to Big Information Paul Preiss and Tom Thomas
- 14. Agenda • Review: Architecture Fundamentals • Introduction: Data, Information and Knowledge • The Value of the Information Architect • The Skills and Role • Big Data to Big Information • The future of the profession and how you can grow your career
- 15. Review: Architecture Fundamentals A Quick Overview
- 16. What is Architecture? Architecture is user experience Architecture is negotiating and bargaining Architecture is technology Architecture is form Architecture is communication Architecture is artful Architecture is agile Architecture is the creation of a better world Magnus Mårtensson – Microsoft March 2008
- 17. IASA’s Definition of an Architect is: Developer lead with Business person with business competence technical competence Technology Strategist for the business Network and system specialist that has IT person who bridges business sense and the gap between strong infrastructure business & technology competence
- 18. Key Concerns of an Architect Whole System Design and Integrity Alignment with the business Strategy Environment Customers System Evolution Architectures are long-lived A blueprint for implementing strategy Ability to evolve
- 19. Introduction Data, Information and Knowledge
- 20. Data Data is a raw material Data is the lowest level of abstraction to derive information and knowledge. Raw Data (i.e. unprocessed Data) is a collection of numbers, characters, images or other outputs from devices that collect information to convert physical quantities into symbols.
- 21. Information Information is data organized for a purpose Derived from the Latin verb informare as in "to give form to the mind", "to discipline", "instruct", "teach" Information is an ordered sequence of symbols that record or transmit a message Information is the summarization of Data
- 22. Knowledge Knowledge is a product of Information Knowledge is created from information that has been analyzed and assigned meaning Knowledge is a set of beliefs created from information Knowledge is the interpretation of information and the subsequent actions derived from that interpretation
- 23. The Value of the Information Architect Going Beyond Just Design
- 24. The Definition The dictionary definition of value: “the worth of something in terms of the amount of other things for which it can be exchanged or in terms of some medium of exchange” The dictionary definition of information: “knowledge communicated or received concerning a particular fact or circumstance” http://dictionary.reference.com/browse/value http://dictionary.reference.com/browse/information
- 25. Important to Understand Information is at the core of all decisions and businesses: Empowers facts not guesses or assumptions Market research, logistics and advertising Inventory quantity, location and turn time to restocking Processes, procedures and intellectual property Remove information from a company what is left?
- 26. The Benefits of Information Strategy Thinking outside of the box for efficiency, growth and creativity Enablement of embracing that change does and will happen Leveraging existing assets into new paradigms Maximize reuse of information and pre-existing investments Who are some of the most successful companies in your domain or in the world? Why?
- 27. Value of Information Multipliers: Time since first available Quality and accuracy Respect and/or proven expertise in the domain
- 28. The Skills and Role Getting the job done the right way
- 29. The Challenge and the opportunity! As an IA you are in the middle creating bridges out to: Management (C suite, directors, mid-level) Operations, Sales – B2B, B2C Web Designers and Developers Software Engineers Database Administrators ?????
- 30. Operations, Sales, B2B, B2C and more... “the other customers” Ensure the information you provide is tailored to the audience Ensure your deliverables are in a form they can use quickly Keep your eyes open for reuse by others Beware of and put an end to hoarders and ad hoc silos Be on the watch for misuse, mis-storage and lack of security Every customer is different – needs and expectations If you are looking you can find a use for everything and anything...
- 32. The Roles and Skills Required The many hats we wear... UI/UX Data Warehousing and Business Intelligence Data Security and Privacy Metadata, Taxonomy and Knowledge Management Yeah we probably wear that “other” hat too...
- 33. Big Data to Big Information Where we are, where we are going and how we might get there
- 34. Big Data Where it may come from Visitor/User/Customer Information Transactions Log files Raw data (of all types and forms) – structured and unstructured Where else does YOUR data come from?
- 35. Bridging the Gap How do we go from (big) data to (big) information Context + Content + User Understand the problem before we try to create the solution Get stakeholder and executive buy in Roll out in a way that makes sense for your organization Keeping in mind: size, architectural maturity, previous projects Are you maximizing the usefulness of your data?
- 36. Big Information The tools we may utilize to get the job done Master Data Management aka MDM RDBMS to NOSQL Date Warehouses with Data Marts App silos to data hubs with app spokes What do you think is coming next?
- 37. How to stay ahead of the curve and continue to grow your career! Certification and Training IFC IAC (Information Architecture and more) CITA-P IASA Mentorship Program Contribute to your local and global community... Only you can decide where you will go next!
Editor's Notes
- #3: Before we get started talking about the what, why, who and how of architecture we’d like to clarify some ongoing themes of our architecture practice. First architecture is about technology value at your organization. We are required to save and make money for you in much the same way as any other business unit including sales and marketing. We are not here to make the best developed technology, nor the most stable, nor necessarily deliver every business requirement. We are here to make sure everything (and yes we mean everything!) that gets built for you, by customers or by our providers meets or exceeds expected return on investment. Architecture is a profession not just a job. We are dedicated to adopting best practices from industry of course but our commitment is to making sure that you are working with trained, certified professionals and that those professionals are providing the best service to your company possible. Just like any great initiative we believe this is all about people not just process. Finally, despite our many successes over the past few years as a team, we are also aware of a great number of opportunities to improve architecture practice and support within the company. We are committed to ensuring that every area where architecture touches your role that you have the most support possible.
- #14: Key Message(s):Speakers Notes:TODO:
- #17: Key Message(s):Speakers Notes:TODO:
- #18: Key Message(s):Speakers Notes:TODO:
- #19: Key Message(s):Speakers Notes:TODO:
- #20: Key Message(s):Speakers Notes:TODO:
- #21: Key Message(s):Speakers Notes:TODO:
- #22: Key Message(s):Speakers Notes:TODO:
- #23: Key Message(s):Speakers Notes:TODO:
- #24: Key Message(s):Speakers Notes:TODO:
- #25: Key Message(s):Speakers Notes:TODO:
- #26: Key Message(s):Speakers Notes:TODO:
- #27: Key Message(s):Speakers Notes:TODO:
- #28: Key Message(s):Speakers Notes:TODO:
- #29: Key Message(s):Speakers Notes:TODO:
- #30: Key Message(s):Speakers Notes:TODO:
- #31: Key Message(s):Speakers Notes:TODO:
- #32: Key Message(s):Speakers Notes:TODO:
- #33: Key Message(s):Speakers Notes:TODO:
- #34: Key Message(s):Speakers Notes:TODO:
- #35: Key Message(s):Speakers Notes:TODO:
- #36: Key Message(s):Speakers Notes:TODO:
- #37: Key Message(s):Speakers Notes:TODO:
- #38: Key Message(s):Speakers Notes:TODO: