4 ms·
I work for a "flat" company. I've certainly observed some of the troubling characteristics of this organizational approach described above and elsewhere in com
by MisterOctober 7y ago
I work for a "flat" company. I've certainly observed some of the troubling characteristics of this organizational approach described above and elsewhere in comments.
There are some positive characteristics [in our implementation at least] as well, a few of which are :
1) Decisions with broad effect [i.e., beyond the decider's personal work domain] are handled with the "advice process," wherein all affected parties are consulted and their advice weighed before the decision is taken. This can be cumbersome, but on the other hand, it is a check against "cowboy" and "act first, consider later" types.
2) Each person is assigned an "area of responsibility / AOR" -- a work or problem domain[s] in which they are acknowledged to hold more expertise than those not assigned that 'AOR.' This prevents [in practice] people [say] in the shipping department making decisions about software development.
3] The org is not _totally_ flat. The CEO and COO are acknowledged to have veto power and the 'AOR' of big decisions that have a potentially existential bearing on the company.
Having always worked at rigidly hierarchical companies before this, I'll say I've more or less gotten used to it and can see the benefits.
One thing I especially like about it is that there is no chance of an "Office Space" situation where a boss, or bosses, continually interrupt work to pester about things that are wastes of time -- each worker is more or less left to determine their own task prioritization and has the power to discontinue tasks that are pointless. We use the kanban system for task / bug / feature tracking.
- daniel_iversen 7y agoYes AORs are great and is quite a complete system (rough consensus is nice too but that’s only a part of the solution) - here’s more details on AORs: https://blog.asana.com/2017/12/distributed-responsibility-engineering-manager/ https://blog.asana.com/2017/12/distributed-responsibility-en...