In short
A resource conflict between engineering programs is settled early by knowing, for each program, which dates depend on the shared team and by how much each date moves if the team is split either way. With those numbers the decision is a short conversation between two owners and a vice president. Without them it is discovered when a date slips. Tymeline holds the commitments on both programs and puts the quantified choice in front of the approver weeks ahead.
How the conflict usually surfaces
Both programs plan the same physical-design or firmware team for the same window, each plan is internally fine, and nobody is holding both against the calendar. The conflict surfaces when one program's milestone arrives and the team is on the other program.
Settling it on the numbers
Tymeline holds every commitment on each program, so it sees the overlap when the plans are made rather than when they collide. It works out the date impact of each way of splitting the team and puts the options in front of the two program owners and their vice president. The decision is made in minutes, weeks early, and both programs re-plan the same day.