pdelgallego

1/ As you mentioned, this is not a good approach for start-ups. The single-threaded model keeps teams autonomous and focused by eliminating alignment in big companies. It tries to replicate the nimbleness of start-ups within business units and teams. A startup should already be focused on finding a market fit as fast as possible.

2/ Not everything should be run as single-threaded. For example, AWS sales and support teams run as functional teams because otherwise, it will impact the customer's experience.

A better approach for start-ups and small businesses is using something similar to the Directly Responsible Individuals approach. Its focus is on decision-making ownership and speed. [1]

Thanks for the feedback. I will try to incorporate it into the post.

One of the metrics that I use address your point:

Number of Ex-Engineers (NOEE): This is the total number of unique engineers who have touched a code and have left the company as of the release date of the software system

Implications: This measure deals with knowledge transfer. If the employee(s) who worked on a piece of code leaves the company then there is a likelihood that the new person taking over might not be familiar with the design rationale, the reasoning behind certain bug fixes, and information about other stake holders in the code.

A large loss of team members affects the knowledge retention and thus quality.