Question 3
Driving architecture decisions
You believe the current architecture won't scale, but the team is hesitant to change it. How do you influence the direction without blocking progress?
Answer outline
Lead with evidence: metrics, incident history, or the concrete cost of a recent change. Listen to the objections too. A team that feels heard is far more open to a new direction.
Propose a gradual path instead of a full migration. A bounded pilot in one feature area lets you prove the approach before you ask the whole team to commit.
Ship small wins early. Success in a constrained area builds trust faster than any argument, and it gives hesitant engineers something real to react to.
Principles
- Run a bounded pilot and measure it, so the wider team decides on results rather than opinions.
- Spend your time unblocking the team, and let others hold the pen on most decisions.
- Accept good-enough interim states, because insisting on perfection kills buy-in.
Follow-up angles
- Acknowledge the effort already invested and the constraints the original authors worked under, without blaming them.
