Three teams building one product are on different cadences and each waits on the others. Would you align their sprints?

Short answer

Aligning cadences makes the waiting comparable and gives you one integration point, which is worth having.It does not shorten the queue - it only tidies the moment work joins one.

Scaling shows up here as cross-team dependencies, not as a framework diagram. Good scaling makes cross-team dependencies visible early, decides which dependency must be removed, and gives teams a cadence for integration that matches the risk. Weak scaling adds coordination meetings while cross-team dependencies keep arriving late. Strong scaling asks whether the dependency should exist at all, then uses planning, contracts, integration tests, or ownership changes to reduce it.