História: Negociar responsabilidades e planos de vida

Nível: C2

A complex design

A senior engineer and a platform lead were coordinating a migration with several changing dependencies. The first plan assumed that one engineer would make every design decision and arrange every rollout step. He accepted responsibility for migration coordination but clarified that final design decisions had to be shared. The team set an expectation of one weekly check-in and named the timing of the dependency audit. The scope became smaller and more realistic.

A fair counterproposal

The design review was initially planned for Thursday, but one service owner needed more time to test a dependency. The owner proposed Friday and explained how the timing would protect the migration path. The counterproposal was accepted after everyone checked on-call availability. They assigned design ownership and agreed who would respond if an unexpected dependency failed. The plan became workable because it respected capacity as well as technical responsibility.

Notas de vocabulário

• a changing dependency — uma dependência em mudança
• a dependency audit — uma auditoria de dependências
• a rollout step — uma etapa de implementação

Prática com a história

1. Write a technical counterproposal with a reason.
2. Write an agreement that includes the unexpected.