Project management software: delivery deadline negotiation
Use this delivery deadline negotiation exercise to agree a feasible schedule using actual dependencies and acceptance steps. You are discussing a shared project planning workspace with an operations lead at a professional-services firm. The point of the practice is to make a useful decision together, including recognising when the offer is not a fit.
Agree milestones, required client inputs and a procedure for handling delays.
The situation
In this fictional brief, client deadlines live in different spreadsheets and dependency changes arrive late. The buyer wants a single view of owners, dependencies and delivery dates. Your offer is a shared project planning workspace, but you must first establish whether its scope addresses the actual need.
A relevant delivery constraint is that client teams must retain access to an export of their work. Treat that as a fact in the exercise; do not remove it to make the sale easier.
| Your counterpart | an operations lead at a professional-services firm |
|---|---|
| Offer under discussion | a shared project planning workspace |
| Evidence available | a sample project with one late dependency and the resulting schedule change |
| Terms to clarify | Agree who imports data, maintains the plan and owns exit exports. |
How to approach delivery deadline negotiation
A useful question for this stage: “If an input arrives late, which part of the schedule should change?” Ask it when the conversation creates a reason for it, rather than reciting every question in order.
- Work backwards from the required outcome. Identify approvals and inputs. Offer a phased delivery if it is genuinely feasible.
- Ground the discussion in the buyer’s work. Ask: “Which handover creates the most rework when a delivery date changes?” Listen for a concrete example before making a claim.
- Use evidence relevant to the decision: a sample project with one late dependency and the resulting schedule change. Explain what it demonstrates and what remains unverified.
- Agree milestones, required client inputs and a procedure for handling delays.
An industry-specific concern
Buyer: “Another tool will just add more administration.”
Possible response: “Let us time the current weekly update and compare the same update on one sample project before asking everyone to move.”
Why this response helps: it acknowledges the concern, brings the discussion back to a verifiable requirement and leaves room for a different decision. Adapt the wording to what the buyer actually said.
Run the practice
- Prepare for two minutes. One person takes the seller role and one plays an operations lead at a professional-services firm. Read the offer and constraint separately from your preferred answer.
- Have a five-minute conversation focused on agree a feasible schedule using actual dependencies and acceptance steps. The buyer should answer consistently with the brief and ask for evidence when a claim is vague.
- Add this challenge: The buyer wants the full scope sooner but cannot accelerate approvals. Explain the trade-off between scope and timing.
- Pause for feedback. Quote one useful question and one missed opportunity. Repeat the difficult exchange using a different response.
- Finish by writing the actual agreement. A sensible option, when it fits, is to run one internal project for two weekly planning cycles. A clear decision to pause is also a useful outcome.
What to avoid
| Common mistake | Accepting a date without checking access, approvals or delivery capacity. |
|---|---|
| A stronger direction | We can assess that date once the inputs and approval windows are confirmed. Here is the dependency that currently controls it. |
| Scope and claim boundary | Do not present feature count as proof of adoption. |
| What to measure in real work | time spent preparing the weekly delivery update. Establish a baseline and definition before interpreting a change. |
An example conversation
What makes that date important, and which deliverable is needed by then?
Our concern is that client deadlines live in different spreadsheets and dependency changes arrive late. Also, client teams must retain access to an export of their work.
Which handover creates the most rework when a delivery date changes?
Another tool will just add more administration.
Let us time the current weekly update and compare the same update on one sample project before asking everyone to move.
If an input arrives late, which part of the schedule should change?
Your working sheet.
Make the exercise your own. Notes are saved in this browser when storage is available. Download a copy to keep; avoid confidential information on a shared device.
Example: client deadlines live in different spreadsheets and dependency changes arrive late; client teams must retain access to an export of their work.
Example: If an input arrives late, which part of the schedule should change? Industry question: Which handover creates the most rework when a delivery date changes?
Example: a sample project with one late dependency and the resulting schedule change. Do not present feature count as proof of adoption.
Example: Propose a clear next step, such as: run one internal project for two weekly planning cycles. Confirm the owner and date.
Review your work
This is a reflection checklist, not an automated assessment.
Questions
Who is this project management software exercise for?+
Can I use the example as a script?+
How should I assess the result?+
Fictional training scenario. The dialogue illustrates response choices; it is not a customer testimonial or a record of a real sale.
Explore more sales resourcesTake the conversation further.
Read a practical guide to structuring your sales practice, or explore the current London sales masterclass.
Plan your sales practiceExplore Jordan Belfort in London