Even in the capitalist hellscape of tech startups, we have like a frontend group that makes decisions about the front end code that’s separate from the entire engineering org. Likewise there’s one for the backend, for devops concerns, and so on.
Some orgs are disorganized and require a lot of vertical approval steps, but that’s not an inherent nature of committee
For hierarchical committees where order needs to come from the top down, sure, your sarcasm is warranted.
Still, there are other structures of committee organization that are horizontal in nature and allow for much more flexibility when it comes to needing to make decisions.
Usually some people will take initiative and some people will delegate their responsibilities. Form committees , that sort of thing.
Committees, the pinnacle of efficiency.
Efficiency doesn’t need to be the highest prioritized metric in a business. It’s pretty important, but there are more important things
Even in the capitalist hellscape of tech startups, we have like a frontend group that makes decisions about the front end code that’s separate from the entire engineering org. Likewise there’s one for the backend, for devops concerns, and so on.
Some orgs are disorganized and require a lot of vertical approval steps, but that’s not an inherent nature of committee
You have a head of UX that makes the decisions (at least in the dozens of startups I have worked in/with).
For hierarchical committees where order needs to come from the top down, sure, your sarcasm is warranted.
Still, there are other structures of committee organization that are horizontal in nature and allow for much more flexibility when it comes to needing to make decisions.
Yup. Pretty much standard stuff. Before you know it, here we are.