Taxonomy Development Infographic
Here is a poster design I’ve been working on for a while – it summarises the empirical, evidence based taxonomy development process we recommend.
This is the link to an A4 pdf version.
This is the link to an A3 pdf version.
We’re going to look at costs/prices for printing this on high quality poster paper and shipping it if there’s a demand. Let us know!
8 Comments so far
- Chris Collison
Really nice job Partick.
My only nit is the way I read the flow - I naturally wand 4 5 6 to be th eother way around so that my journey through the process is an unbroken “2” shape.
- Chris Collison
Sorry for the typos above! Written in haste! :O)
Patrick, this is coming along nicely. I agree with Jack’s comment on the handwriting font, it is hard to read on the screen. The flow doesn’t bother me so much becasue it is clearly numbered and seems to make sense on where the next step is. The one thing missing for me is the concept of “buy in”. Perhaps this is implied in the open card sorting step? In my case, involvement of key stakeholders was necessary in getting our taxonomy up and running. This may be especially true in organizations that do not currently have a taxonomy in place and where the concepts are very new.
- Patrick Lambe
Hey Jack - the screen version is just a thumbnail, it was designed for pdf. Agree on the number of words, but considering I got down to this from a 280 page book, I think I’m doing pretty well!
Chris - the flow was tricky, as I needed to make a connection between the warrant work and the scenarios for scenario testing.
Kim, yes good point about buy-in - it should really sit in the planning stage, where key stakeholders are first engaged and their needs considered. I’ll ask Jack if I can have a few more words!!
- Michael Sutton
In Patrick’s chart, I was very encouraged to see the use of the WARRANT. To me, this is an integral element that invigorates buy-in from the stakeholders. In my recent foundational MBA knowledge management class at Westminster College, I took two weeks of a 7-week course to DRAFT and FINALIZE the wiki charter for our Atlassian Confluence KM-Wiki Project. All the learners where amazed at their reflection upon recent corporate wiki initiatives in their own organizations, where the projects died and withered for lack of a charter/warrant and the ensuing collaborative stage of hammering our the details of the warrant.
Patrick’s charts also have that ‘Dan Roam flavour’ about them, (“The Back of the Napkin: Solving Problems and Selling Ideas with Pictures,” and Unfolding the Napkin”). I really appreciate this informal style of picture making and knowledge mapping.
In Edgar’s chart, the elements of the infographic I found very useful were the highly structured, top-down, definitional approach to what I often refer to with my learners as “functional disambiguation.” (OK, sometimes I slip into academic speak, even though I consider myself a scholarly practitioner.) I am reminded by your chart of many of the classical AIIM.org posters down about a decade ago to help illustrate ECM.
Thanks for sharing these artifacts. They will help me jumpstart many of the learners in this Summer semester’s foundational knowledge mobilization course.
- Annette Hexelschneider
Very interesting. Thank you.
May humble suggestions are:
I think it could be structured a bit more into the three steps. Visually. In an unobtrusive way. I mean perhaps with three lightly coloured horizontal bands. The name of the phases bold in the colour of the band.
How to Build a Taxonomy as headline could be on top of the poster.
Looking forward to more km infographic contests
Thank you for sharing this info via TaxoCop. I too have been pleased with your use of warrant as I have sometimes found that folks think a taxo can be developed in a vacuum. I’d add “System Warrant” as well to user and content warrants in that whatever gets developed if implemented in a system has to reflect system constraints (and we’ve all been in the “can’t handle more than flat lists” boat. The other thing that is somewhat implicit but may be worth pointing out is that this is all iterative, and that multiple paths may be followed (particularly during planning and testing) with pros and cons identified until the stakeholders agree that requirements are met in the most effective, efficient way. Really appreciate your sharing this.
Carol
Page 1 of 1 pages
Comment Guidelines: Basic XHTML is allowed (<strong>, <em>, <a>) Line breaks and paragraphs are automatically generated. URLs are automatically converted into links.
Nice picto graphic of the process. My only nit has to do with the handwriting - it’s a little hard to read when on screen. The PDF version looks like it will be okay.
A more substantive comment would be to think about reducing the amount of text to the key elements of the process as you see it.
Posted on May 02, 2012 at 08:56 PM | Comment permalink