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, incidents, or the concrete cost of a recent change. Teams that feel heard are more open to new directions.
Propose a gradual path rather than a full migration. A bounded pilot in one feature area lets you prove the approach before asking the team to commit.
Ship small wins early. Success in a constrained area builds trust faster than any argument.
Principles
- Pilot in one area first — measure results before asking the wider team to commit.
- Enable, don’t bottleneck — facilitate and unblock rather than holding the pen yourself.
- Accept good-enough interim states — perfection kills buy-in.
Follow-up angles
- Acknowledge sunk cost and past constraints without blaming the authors.