tag:blogger.com,1999:blog-3969035329941726644.post8044235647307728201..comments2024-03-11T00:24:38.244-07:00Comments on INFORMATION ACTION: actionable ideas for evidence-based decision-making: The Information Management Tube MapAlan D. Duncanhttp://www.blogger.com/profile/12790847883038860673noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3969035329941726644.post-26952668976746053912016-11-26T03:13:20.351-08:002016-11-26T03:13:20.351-08:00All too often we have only a vague sense of our de...All too often we have only a vague sense of our development areas and no clue as to how to address <a href="http://www.workbrighter.co.uk/how-to-identify-and-address-your-development-areas/" rel="nofollow">development Areas In work</a>, areas of development.TRebshttps://www.blogger.com/profile/12678518175373343373noreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-13327196162151971642014-04-27T05:49:06.360-07:002014-04-27T05:49:06.360-07:00Thanks for your comments Eric. This isn't a ro...Thanks for your comments Eric. This isn't a roadmap, a process or a project plan - it's an attempt to illustrate the relationships between the different skills-sets and competencies that an holistic (Enterprise) approach to Information Management requires. The phases and priorities of any specific project where these competencies are applied will depend on the nature of the requirements.<br /><br />Note too, that it specifically relates to Information Management practice, nor is it an architecture diagram. In that respect, it has a relationship with, but is different from Enterprise Architecture frameworks such as Zachman and TOGAF.Alan D. Duncanhttps://www.blogger.com/profile/12790847883038860673noreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-49235652500541027552014-04-19T09:33:03.834-07:002014-04-19T09:33:03.834-07:00Looks like a one dimensional layout of the Zachman...Looks like a one dimensional layout of the Zachman Framework. It is a really good circuit board design. I never studied circuitry because I found it too confusing. I love the color scheme. The content is exact, but the model lacks structure. It may be inappropriate model these artifacts into a process model, but I would like see project phase flow priorities and technology relationship layers displayed in a more meaningful manner. It may be valuable to add a “best practice” numbering sequence to offer greater clarity and simplification in understanding both “inter-relationships” and “intra-relationships” in the model. Good job… don’t forget to copyright your creation.<br /><br />Eric Paul McNeil, Sr.<br />ArrickAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-33663331700270884652014-03-12T07:10:14.137-07:002014-03-12T07:10:14.137-07:00Hi Alan;
As soon as I saw this and read the word ...Hi Alan;<br /><br />As soon as I saw this and read the word 'tube' I thought of this again:<br /><br />http://mathforum.org/mathimages/index.php/Tesseract<br /><br />John O'Gorman<br />Quantum Semantics IncAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-76388681819814124222014-03-08T01:20:59.143-08:002014-03-08T01:20:59.143-08:00Thanks Bridget - I'm glad you like the concept...Thanks Bridget - I'm glad you like the concept. I think my Information Management Competency Framework is different from, and complementary to, TOGAF (and other similar Enterprise Architecture models like the Zachman framework).<br /><br />EA frameworks describe the required architectural components in each of the architecture layers (answering the "What?" question). Whereas my framework is more target at articulating the capabilities, skills and activities that are needed in to deliver the components within the Data/Information Architectural Layer (the "How?" question.)Alan D. Duncanhttps://www.blogger.com/profile/12790847883038860673noreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-65787538267310984042014-03-07T01:23:34.397-08:002014-03-07T01:23:34.397-08:00I've been struggling with a visual for some ti...I've been struggling with a visual for some time. This is a great start. How would this fit alongside an enterprise architecture framework like TOGAF? Anonymoushttps://www.blogger.com/profile/15241954907071905319noreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-80090322552729474332014-03-04T15:16:33.714-08:002014-03-04T15:16:33.714-08:00A correspondent on LinkedIn has asked for an insig...A correspondent on LinkedIn has asked for an insight into the thought process of how I approached the tube map.<br /><br />I've had a pretty well-worn methodology of Information Management competencies, processes and deliverables defined for about 10 years now. It's always been developing, growing and evolving as I learn new techniques, refine ideas and gain new experiences (I'm a bit of an intellectual magpie in that regard!)<br /><br />But up until now it's always just been a library of artefacts, templates and presentation materials - organised and structured based on "best fit" for each competency area. The linkage between competencies and capabilities has been in my head - effectively, I'VE been the index and access interface for navigating the interconnections and relationships between different threads.<br /><br />When I read Gary Allemann & Nicola Askham's blog post, I had an "epiphany" of how to illustrate the whole IM/DG landscape visually. So I went through my library of competencies (each competency became a "tube line") and then picked out the artefacts & tasks (each becoming a "station"). <br /><br />It was then just a cae of identifying where in my mind each of the competencies intersect (plus a lot of shuffling to ensure that the resulting map was reasonably clearly laid out and readable!)<br /><br />Simples!Alan D. Duncanhttps://www.blogger.com/profile/12790847883038860673noreply@blogger.comtag:blogger.com,1999:blog-3969035329941726644.post-646959917166218042014-03-04T14:48:04.147-08:002014-03-04T14:48:04.147-08:00Wow, I always try to descibe to others all of the ...Wow, I always try to descibe to others all of the different aspects of Information Management but never put it into a pic like this. This is great, thanks.Anonymousnoreply@blogger.com