July 13, 2005

are we hardwired to hierarchy?

zzzzzzz08.jpg
One of the main argu­ments we use to ratio­na­lize moro­nic and soul-destroying hie­rarchies in our work­place is that we’re bio­lo­gi­cally pro­gram­med that way i.e. it is in our gene­tic makeup to create moro­nic, soul-destroying “tree struc­ture” hie­rarchies, and to orga­nize things accor­dingly.
“It is scien­ti­ficly deter­mi­ned that I be moro­nic and sou­less” etc.
As a card-carrying mem­ber of the Madi­son Ave­nue “Fuck You” school of mar­ke­ting, I can cer­tainly relate. And I ima­gine, so can lots of peo­ple rea­ding this.
Sig begs to differ:

tree-structures, are we hard­wi­red?
If I say “Book” and “42”, what comes to your mind? Some “Hitchhi­king” perhaps?
What with “Umbre­lla” and “Film”? Any film tit­les coming to mind?
Add “Nanny”, “Flying”… would that be “Mary Pop­pins”?
See? Your brain is quick and natu­rally wired to inter­cept iffy tags!
Neverthe­less, I often hear that tree-structures are neces­sary and that we are hard-wired for tree-structure orga­ni­sing: Hie­rarchies, fol­ders…
That I would argue, humbly of course, is bogus.
Would “Film > Bri­tish loca­tion > Female lead > Dis­ney > Family > etc.” trig­ger “Mary Pop­pins!” as promptly?
Nah, didn’t think so…
We’re natu­rally inc­li­ned to tag impre­ci­sely and freely — and locate any object or sub­ject inter­cep­ting those tags. Fast, effi­cient and without trai­ning. And without any quest for stan­dards.
In other words, we need no clas­sic tree struc­tu­red data sor­ting. We would be bet­ter off without.

[DISCLOSURE:] Sig and I are wor­king together on a mostly sec­ret pro­ject. Even if what we’re doing is pro­ved wrong, well, at least we had fun trying. And if we prove to be even par­tially right, then… Holy Fuck. Holy Fuc­king Fuck. Holy Fuc­king Fuc­ked Fuck.
Indeed.

"Hugh's Daily Cartoon" Newsletter. A new cartoon sent out every weekday morning to your inbox [RSS version here.]. A wee chuckle to start your day off right etc.

19 Responses to “are we hardwired to hierarchy?”

  1. Rob Kischuk says:

    I’m not saying that you’re wrong, because I honestly don’t know. I’ll be eager to track the pro­gress of you and Sig’s expe­ri­ment.
    What I do take issue with, and perhaps it’s the real pro­blem with hie­rarchies in the first place, is that your exam­ple hie­rarchy was too gra­nu­lar. The hie­rarchy of many orga­ni­za­tions is also too gra­nu­lar. You could have said Film > Dis­ney > Live Action > Nanny, and you arrive at the same spot using the same num­ber of facts.
    Also, your fuzzy clues work fine for the remar­ka­ble (“film” and “neo”), but not as well for the anony­mous — find a 4 piece (or even 10 part) clue that would quickly lead most peo­ple to think of the movie “Soro­rity Boys”.

  2. Trying to read bet­ween the lines of Thin­gamy, and won­de­ring…
    …to what extent the mana­ge­ment of flow through the river­bed will focus on the narrow por­tions — the cons­trai­ning bott­le­necks — which limit what can pass throught the whole sys­tem, and at the same time are the source of tur­bu­lence (rapids?) that can upset the flow.
    …how much of your thin­king about the rela­tionship of tra­di­tio­nal hie­rarchi­cal struc­tu­res result in silos, which result in con­flic­ting objec­ti­ves and metrics that end up sub-optimizing the per­for­mance of the lar­ger system/organization.
    …how your left/right brain pers­pec­tive allows for the neces­sity of both (duh!). The left brain logic is neces­sary to analyze and define pro­ces­ses while the right brain makes you care about them. Nothing can get done without the left brain imple­men­ta­tion while without the right brain buy-in, nothing will get done.

  3. rich says:

    Just a quick thought …
    Tree struc­tu­res are impor­tant, there is a linea­rity about it which is con­vie­nient, but a late­ral take could be taken into account. It is also pos­si­ble that thought (or struc­tu­res) can be rhi­zo­mic — that is, like a rhi­zome, the roots that spread con­nect into each other, as oppo­sed to to sprea­ding and branching out inde­pen­dantly. A wiki­pe­dia entry for you:
    http://en.wikipedia.org/wiki/Rhizome

  4. Ric says:

    Rob: There’s been quite a bit of dis­cus­sion on this tags v hie­rarchies topic; some here on gaping­void, and some on the ori­gi­na­ting site (start here
    http://thingamy.typepad.com/sigs_blog/2005/06/tree_structures.html
    and work your way up the posts and com­ments until you get to the one Hugh links to here). The point you make that “You could have said Film > Dis­ney > Live Action > Nanny, and you arrive at the same spot using the same num­ber of facts” is in fact one of the bene­fits of the tag­ging — mul­ti­ple rou­tes to the same infor­ma­tion make it easier to find by dif­fe­rent people.

  5. Valdis says:

    It is not an OR pro­blem… hie­rarchy OR something else — like net­work
    It is an AND situa­tion… hie­rarchy AND net­work — presc­ri­bed AND emer­gent…
    We traverse/surf wha­te­ver paths get us to the solu­tion, some­ti­mes hie­rarchy, some­ti­mes horizontal/diagonal associations[network], and some­ti­mes both, jum­ping back and forth from one to the other until we get there.

  6. hugh macleod says:

    “jum­ping back and forth from one to the other until we get there…“
    That’s not how it wor­ked at ANY of the com­pa­nies I wor­ked for, back in my Madi­son Ave days ;-)

  7. Keith Handy says:

    Hie­rarchies can be directly trans­la­ted into linear lists — start with the first large branch, then the first sma­ller branch, and keep going like this until you’ve exhaus­ted all the sub-branches of any one lar­ger branch. This will always be use­ful for anal-retentives like myself who want to make sure we haven’t mis­sed anything.
    A free-floating web of asso­cia­tion, on the other hand — like the human brain — might have “dark areas” that we never get around to. Is it safe to assume that if we don’t hap­pen to find these, they weren’t impor­tant enough in the first place?

  8. Alex says:

    I couldn’t agree more with Val­dis… free form tags are use­ful, but so are hie­rarchies.
    Both Sig or you talk about tag­ging in such an OR orien­ted way. Which is very pro­vo­ca­tive, which is why you’re doing it I sup­pose.
    This not a binary pro­blem with a binary solu­tion, it is not black and white, it is not cut and dried. Each has their place.
    Why can’t Hie­rarchy AND Tag­ging they live side by side? What makes you think one is so use­ful it can ‘com­ple­tely’ replace the other?
    You use tooth­floss, but surely that doesn’t mean you should stop brushing your teeth?

  9. frosty says:

    I’ve also been wor­king on ways to find, fil­ter and orga­nize infor­ma­tion over the last year, inc­lu­ding pla­ying around with the tags idea a bit.
    There are many areas in which tags and tag-like orga­ni­za­tion offer huge poten­tial, in my opi­nion lar­gely because it gets a little clo­ser to the way our brains seem to work. And there are other twists on the con­cept that haven’t been explo­red much publicly, but when I get to public beta… ;-)
    I don’t know if, in the realm of digi­tal infor­ma­tion, there would ever be a com­plete move away from hie­rarchi­cal orga­ni­za­tion. I rather ima­gine nonhie­rarchi­cal (tags etc) forms taking over an ever lar­ger part of our digi­tal lives where strict orga­ni­za­tion isn’t a true requi­re­ment.
    For exam­ple, on sites like Slash­dot there are perio­dic lively deba­tes about Google’s approach, par­ti­cu­larly with Gmail: “don’t file, search.” That can be ama­zingly power­ful, but only where 100% accu­racy isn’t an abso­lute impe­ra­tive. You might want your e-mail wor­king that way, but I don’t think you want your ban­king sys­tem wor­king that way.
    Of course there’s also the data-mining angle, where any new way to find con­nec­tions is very wel­come, and is going to gene­rally be over­laid on a defi­ned struc­ture (set of struc­tu­res) any­way.
    I think we’ve rea­li­zed by now (or should have) that with the flood of digi­tal docu­ments, infor­ma­tion, etc., the/old/file/structure/concept isn’t going to cut it. At least not from the user’s point of view.
    And yes, soul-crushing hie­rarchies in busi­ness are stu­pid, but that has more to do with the egos and inse­cu­ri­ties of peo­ple “in charge of” other peo­ple than with any serious attempt at effi­cient orga­ni­za­tion.
    I highly recom­mend Oli­ver Sacks to anyone inte­res­ted in this topic.
    http://www.oliversacks.com/
    Unfor­tu­na­tely, this article has gone to “pay mode” but it’s great:
    http://www.nybooks.com/articles/16882

  10. pheloxi says:

    http://www.thingamy.com/
    the best kept public sec­ret. some one is crea­ting oxy thingany…uhm…I mean doxy moron (as di for digi­tal).
    thin­gamy could be the next gin­ger!
    see: the “i was there” fac­tor
    http://www.gapingvoid.com/Moveable_Type/archives/001716.html

  11. Jon Husband says:

    You pro­bably know what I think … phi­lo­sophi­cally.
    I like Frank Patrick’s points, and I agree strongly with Val­dis’ points .. theo­re­ti­cally.
    Prac­ti­cally, it IS “both/and” in my opi­nion, but only when there are those higher up in the hie­rarchy who think like that, are pre­dis­po­sed in terms of per­so­na­lity, or are in front of pro­blems where hie­rarchy is crea­ting more pro­blems than it is sol­ving (although there are many exam­ples where that is the situa­tion but the hie­rarchs wouldn’t ever think of tryiong other ways.
    IMO, the issue is that there are not any other *models* that have wides­pread awa­re­ness or con­di­tio­ned trust … orga­ni­za­tions have almost all of their mana­ge­ment pro­ces­ses deri­ved from hei­rarchi­cal struc­tu­ral assump­tions, and there are many cyc­les of rein­for­ce­ment going on … job eva­lua­tion, com­pen­sa­tion sche­mes, stra­tegy deve­lop­ment, objective-setting, accoun­ta­bi­lity and per­for­mance mana­ge­ment pro­ces­ses come to mind ;-)
    It WILL become “both/and” over time (See Stan davis work in Chap­ter 2 and 3 of Future Per­fect, from 1987, for a semi­nal dis­cus­sion on this spe­ci­fic point), because the com­pe­xity and pace of change is too rapid now .. net­works are neces­sary for effec­tive res­ponse, and some forms of effec­ti­vely func­tio­ning hie­rarchy are neces­sary for decision-making.
    It makes neces­sary peo­ple and skills such as “social” and “orga­ni­za­tio­nal” archi­tects, rather than big orga­ni­za­tio­nal / HR con­sul­ting hou­ses selling hie­rarchi­cal con­trol methods for the knowledge-and-network based work of peo­ple in today’s orga­ni­za­tions.
    i guess I should pro­bably get more active blog­ging on these issues, and par­ti­ci­pate more in the con­ver­sa­tion, given that I’ve been thin­king about and wor­king with them for a while now.
    Btw, the “hie­rarchy to wireacrhy” t-shirt design got rave reviews at Gnomedex.

  12. Valdis says:

    “That’s not how it wor­ked at ANY of the com­pa­nies I wor­ked for, back in my Madi­son Ave days ;-)
    And that was why you got the fuck out of there!
    BTW, hie­rarchies are a spe­cial type of net­work know as a “tree” — so it is ALL net­works, pat­terns of connections.

  13. Your Brain At Work

    Quick: umbre­lla, flying, nanny As Jeff Haw­kins points out in On Inte­lli­gence, your brain just sits in the wet, warm, dark­ness of your skull and tries to make sense out of pat­terns of nerve impul­ses. Via gaping void (Not

  14. Bet­ter than me: the hie­rarchies that bind

    My mother once said to me, “If you are on a date with a guy who is nice to you, but rude to the wai­ter, he is not a nice guy.” My mom is smart. I’ve taken that les­son with me throughout whiche­ver sta­tus I’ve been.

  15. Julian Bond says:

    If a tree struc­ture appea­red in the mesh and there was no taxo­no­mist to see it, would it still exist?
    Part of the pro­blem with hie­rarchies is the world seems to be mesh struc­tu­red rather than tree struc­tu­red. There’s always just enough cross links to screw up the nice neat tree we’re trying for.
    Which is pro­bably why every so often big com­pa­nies expe­ri­ment with matrix mana­ge­ment. Just before clo­sing down the whole divi­sion.
    Time for another article; “Out­li­ners con­si­de­red harm­ful”; or to pon­der the dif­fe­rence bet­ween tra­di­tio­nal XML and RDF.

  16. Jay Fienberg says:

    Not sure if you’d find this rele­vant, but I’ve writ­ten about and made some dia­grams sho­wing how tags rein­force hie­rarchies.
    Tags stuck on trees (with pic­tu­res!)
    http://icite.net/blog/200506/tags_trees.html
    Tags remove a middle level of hie­rarchy, but they don’t replace hie­rarchy – tags depend on trees.
    With tags, we get less access to hie­rarchy. This is a tra­deoff – we get hie­rarchy out of our face and don’t have to deal with its awk­ward­ness, but we also forgo the abi­lity to shape hie­rarchies on which we are being dependent.

  17. Valdis says:

    Julian, meshes can con­tain trees but not vice versa.
    The ans­wer to your ques­tion is “it depends”. We can find trees in the mesh, but as soon as we find cycles/loops in the trees, they stop being trees. Kind of like life in an ato­mic collider…

  18. Peter Marshall says:

    I agree with the “let’s not get all pissy” obser­va­tion made in a cou­ple of posts that BOTH hie­rarchy and tagging/association are use­ful, in their place… but I ALSO think that tag­ging is ALMOST always bet­ter.
    Gran­ting that this is partly a per­so­na­lity test thing, and many peo­ple will like hie­rarchy more than I do. Some may pos­sibly like it less (hard to ima­gine).
    But I think a fair test of this is to com­pare the uti­lity of X1 (www.x1.com) vs. MS Explo­rer. I star­ted using X1 as a desk­top search tool about a year ago, and I now use Explo­rer about 10% of the time to go to stuff.
    For non-X1ers, it essen­tially pro­vi­des an inter­face where you type in key­words, and as you type, it ins­tantly retrie­ves matches based just on inde­xing of ALL con­tents of ALL files, along with a “pre­view pane” sho­wing the con­tents of any file you select. The list of matching files upda­tes ins­tantly with each keys­troke, so no need to sub­mit, look at results, go back and try again, etc. It’s ins­tant feed­back — just keep adjus­ting the search terms till you get what you need.
    This has the use­ful side-effect of hel­ping you find rela­ted use­ful things you hadn’t thought of or remem­be­red… but even without that, it’s just a bet­ter, fas­ter way to find almost anything EXCEPT ima­ges or music or other non-text con­tent. Occa­sio­nally it’s fas­ter just to go to a fol­der that has everything for a spe­ci­fic pro­ject.. but 90% of the time, in my expe­rience, X1 is bet­ter.
    A second con­fir­ma­tion of the same thing is how well Gmail finds stuff I need, again with no fol­ders, just with key­word search. I never miss fol­ders for my mail — it’s all in one big buc­ket, and I always find what I need right away.
    Of course, I’ve never unders­tood peo­ple that have millions of Out­look fol­ders with hie­rarchy — I pre­fer even Outlook’s ane­mic search to the overhead of cate­go­ri­zing and then tra­ver­sing the cate­go­ries, not to men­tion the pro­blem of nee­ding mul­ti­ple path­ways and chan­ging path­ways to the same con­tent.
    In my view, hie­rarchy is RARELY right, but our sys­tems and pro­ces­ses use it MOST of the time. This should be flip­ped on it’s head, and it’s impor­tant to recog­nize this, not just to say “well, both are valua­ble”. We’ll never catch terro­rists by trac­king info on them in sin­gle, sta­tic hierarchies.

  19. Valdis says:

    Peter wri­tes ” We’ll never catch terro­rists by trac­king info on them in sin­gle, sta­tic hie­rarchies.” Yup.
    Yet, that is what we keep doing — repea­ting old beha­vior and expec­ting dif­fe­rent results. I rif­fed on this in a brief white paper — hie­rarchy vs net­work in the war on terror.
    http://www.orgnet.com/orgchart.html