What you are asking for
A commitment is announced, then the team who has to deliver it is invited to estimate the work. Whether the scope or the date can still be adjusted is not stated.
What the system hears
If the promise already looks final, the estimate can be received as an expected confirmation rather than as information for deciding.
What that produces
Building can reveal a dependency, a smaller solution, or a capability already available. Bringing that information in before the commitment widens the options and helps avoid promises that are hard to keep. It does not require a detailed estimate for every idea. The depth should follow the risk, the uncertainty, and the cost of going back. A first comparison can be enough to choose what to explore. A significant commitment may call for a trial or further analysis.
The contribution expected has to be clear: options, order of magnitude, assumptions, unknowns, and effects on running the service. The people who know the technology, the operations, the customer relationship or the costs can each bring something decisive. No craft should be reduced to confirming a decision that is already closed.
Not all commitments are made in meetings. A call or a message thread can commit as much as a formal document. Whoever answers has to know what they can confirm and what is still subject to checking.
If the promise already exists, an estimate is still useful. It lets you organise the delivery or renegotiate. Presenting its late arrival as the team’s fault does not help handle the gap; the gap has to be made visible and the next step decided.
The decision
→ For an upcoming commitment, have the options and unknowns examined by the people concerned before you confirm a date, a cost or a scope.
→ If you have to answer earlier, separate what is confirmed from what still depends on a check, and say when you will come back.
→ At the next review, compare the assumptions to what was learned, and adjust the commitment if needed.
Start with a recent case, to see at what moment the information would have helped. Plan the time that check needs in the next comparable case.
From where you sit
- Engineering: lay out the assumptions and the options before pinning down a deadline.
- Sales: separate an intention from a confirmed promise.
- Operations: add the running load to the build effort.
- Management: take on the renegotiation when information changes the plan.
To discuss
In our last commitment, which information was known before the promise, and which called for an adjustment?