The hierarchy is a construct that help people deal with the otherwise overwhelming complexity of the network of interactions. A formalized static hierarchy has been a help in the past, or at least a comfort, but more and more a hindrance to agile enterprises today.

I agree that "Hierarchies should be seen as temporary, negotiated agreements to get work done, not immutable power structures."

It is worth reflecting on the idea that a single hierarchy implies an omniscient viewpoint. Why only one? Isn't there really a multiplicity of hierarchies all intermingled at the same time? Isn't also possible the relevant hierarchy depends upon your viewpoint and purpose? Taken further, it might be that every individual sees a different hierarchy to the network around them. Allowing nodes to chose their relationships gets close to this. Getting to a true understanding of a network organization will require exploring these kinds of ideas.

In any case, a hierarchy is merely a construct to tell a story. As our stories go quicker, so should hierarchies.