Choose the right word

• We need to [to formalize / layer of management / flat hierarchy] our promotion criteria before the annual review.
• Adding another [layer of management / team size cap / scaling bottleneck] slowed down decision-making in the London office.
• Maintaining a [flat hierarchy / second-system effect / to institutionalize] became impossible once our Seattle staff exceeded fifty people.
• When communication breaks down, it is best [to split a team / to formalize / every bit as] into two autonomous squads.
• Enforcing a strict [team size cap / scaling bottleneck / layer of management] of eight people keeps our agile ceremonies efficient.
• Database I/O became our primary [scaling bottleneck / second-system effect / flat hierarchy] during the peak holiday shopping season in Boston.
• The executives wanted [to institutionalize / to split a team / nowhere near] best practices across the entire Cambridge organization.
• Our polished Austin headquarters is [a far cry from / every bit as / nowhere near] the cramped basement we started in.
• The legacy codebase was [nowhere near / a far cry from / more of a] as modular as our new microservices.
• The new design is [every bit as / a far cry from / nowhere near] complex as the one we abandoned in Chicago.
• Building an overly complicated replacement architecture often triggers the [second-system effect / team size cap / flat hierarchy] in growing tech companies.

Sources: photo by Veronika Andrews on Pexels