I'm a bit bias here because I ran an independent private dance studio for six years. Making decisions can be hard and having guidelines and even a Charter to make decisions really helps move things. Ultimately, it does come down to one or two persons. Here are a few articles that help guide me through the process.
https://hbr.org/2006/11/how-well-run-boards-make-decisions
Committee vs. Final Decision Maker
Design by committee can work. However, you often need a group of like-minded individuals that do not differ in opinion too drastically for this succeed. In the extreme circumstances, if there are wildly divergent opinions, the group must be willing to forego their egos and accept the decisions that are made even when the decision is the polar opposite of what they believe to be the best decision. When all else fails, there is a final decision-maker at the top.
Thus enters the architect. They are after all, responsible for the product that is ultimately designed and built. They will help the team make decisions that are aligned with the macro-scale goals for the organization. While the development team themselves focus on the design decisions that are most beneficial at the micro-scale of the feature or system for which they are responsible.
No comments:
Post a Comment