Chapter 9
Negotiating dependencies and delivery tradeoffs
Work with distributed ownership, competing roadmaps, and organizational constraints to agree on a feasible product release.
The improved interface needs more useful eligibility information. The platform team understands the request, but its next release is committed to a reliability project. Your product lead still has a customer milestone approaching.
A persuasive prototype can make the benefit clearer. It cannot create engineering capacity. The decision is which response the organization can support and who accepts the consequences.
Separate facts from assumptions about process
“Security will block this” is often an unverified prediction. Ask which review applies, what information is needed, who can answer, and when. “The platform release has no unallocated capacity this month” may be a confirmed constraint from the owner. Record the difference.
For Casework, first establish what the existing service already supports: authoritative assignment checks, current case status, recorded assignment, and the documented version behavior. The local simulator demonstrates these concepts, but the real integration still needs verification.
Then identify the additional request. Perhaps the interface wants detailed reason codes that the service cannot currently guarantee. That is a narrower dependency than “we need the platform team before we can do anything.”
Map dependencies to decisions
| Dependency | Needed for | Person or team to consult | Consequence if unavailable |
|---|---|---|---|
| Access to administrators | Task evaluation | Research operations and operations lead | Domain assumptions remain unverified |
| Reliable current-state read | Uncertain-outcome recovery | Assignment service owner | The proposed recovery cannot be promised |
| Additional eligibility reasons | More specific explanations | Platform team | Use supported information and narrower messages |
| Shared component extension | Consistent feedback behavior | Component maintainers | Choose an existing pattern or a bounded local implementation |
| Support coverage | Pilot release | Support and engineering leads | Delay or reduce the pilot |
Include decision dates and confidence in your own working map. Revisit it when scope changes. A dependency list without a consequence gives stakeholders little basis for prioritization.
Present options with their continuing costs
The team can wait for detailed reason codes, ship a narrower explanation using supported facts, or build a product-specific workaround. Explain all three honestly.
Waiting may preserve a coherent implementation but delay useful recovery improvements. A narrower release may help now while leaving some questions unanswered. A local workaround may require duplicating domain rules and maintaining them whenever the service changes. If those rules affect authorization, the service must still enforce its own checks.
Estimate with the people who will do the work. Include review, migration, support, and follow-up. Do not describe the workaround as temporary without an owner and a credible condition for removing it.
Negotiate the commitment
In the fictional case, the product lead accepts a release using supported status information and clear uncertainty messages. The platform owner agrees to review a bounded reason-code proposal at a later planning point. That is a future review commitment, not a promised delivery date.
Write the agreement as a short decision note: the constraint, considered options, chosen scope, excluded behavior, accepting owners, and the event that reopens the decision. Link the relevant team plans so the same agreement does not need to be reconstructed in every meeting.
If the existing service cannot support reliable recovery at all, the narrower release may still be unacceptable. Escalate the decision with evidence and alternatives. A deadline does not supply a missing guarantee.
Use influence at the right scope
A junior practitioner can surface a dependency with a concrete failing example and seek help from their lead. A senior practitioner can coordinate the contract and propose options. A staff practitioner can examine whether repeated conflicts reveal a funding or ownership problem affecting several teams.
Escalation should resolve a decision or priority conflict. It should not ask leadership to pressure a team into an undocumented commitment. Include the affected team and make the tradeoff visible.
Practice: respond to a constrained roadmap
Assume the platform team cannot add detailed eligibility reasons before the customer milestone. Verify what remains feasible, compare at least three options, and recommend a release scope. Name the tradeoff owner and any condition that makes the release unacceptable.
For an advanced extension, examine how the same dependency affects another product. Propose a shared investment only after accounting for the work displaced from both roadmaps. Distinguish a role-played agreement from an accepted real commitment.
Review your work
The plan should reflect the commitments of the teams involved, including those outside your reporting line. A reviewer should see which constraints were verified, what happens if they persist, and who can revisit the choice.
The next chapter asks whether the solution is worth sharing with another product team.
Found an error? Report it.