Talk:Holacracy/Archives/2019
 | This is an archive of past discussions about Holacracy. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Level design
Is Holacracy a level design? To all I read (and I read only a few things) I would say yes. For my understanding it is a top-down approach of designing, realizing and maintaining/adapting a company for a specific purpose. It can be seen as process setup to create some sort of organic growth including or even building upon creation of order out of the chaos. With all the feedback and controlling the interactive levels look to me like they will resemble rather close what is known as the v-model in the engineering world, including software engineering. Is my understanding of the topic at this extent correct? Does it make sense to add such or alternate statements to the article? --Alexander.stohr (talk) 08:17, 19 July 2016 (UTC)
I'm not sure what you are referring to as "level design", as well as I can't see the relationship between Holacracy and v-model. If you can link an independent source that already does that analysis might be useful. Folletto (talk) 00:53, 30 December 2016 (UTC)
I think Alexander means flat organization by level design, which is anti-hierarchical, but is hierarchical in the case of holacracy. Either it is or isn't, which it is or isn't, or is, heh. --John Bessa (talk) 15:21, 6 June 2019 (UTC)
