Skip to content
Kaarne Superstore⌕
Customers & Sales

Tell a Client That a Late Idea Belongs in the Next Release

A useful suggestion can wait without disappearing. Capture its customer problem, explain the launch choice and name the next assessment.

Two people compare a current website platform with a later platform holding a clipped idea card.

Two days before the planned launch, the client suggests a comparison tool. The idea may be valuable, but putting it into this release would introduce new content decisions, implementation and review. The conversation needs to preserve the idea while making the release choice understandable.

Establish what kind of late request it is

In this fictional example, an agency is launching a website for a specialist workshop. The agreed release explains service options and provides an enquiry route. The client now wants visitors to answer three questions and receive a suggested service. Before deferring it, ask what problem prompted the suggestion.

A missing correction to an inaccurate service promise is different from an enhancement to an otherwise usable route. A late observation may expose a launch-blocking issue that deserves immediate attention. Do not use “next release” as a way to avoid examining that possibility. Establish whether the current agreed journey remains appropriate without the proposed addition.

Explain the release impact in the actual journey

For the comparison tool, list the decisions it introduces: who defines the service rules, what happens when the answers do not fit, how the result is worded, where the visitor goes next and who reviews the resulting paths. Then ask the implementer to assess the actual work. Do not label it a quick widget because the interface sounds small.

Keep this discussion about the pending launch window. The general question of what the client bought belongs in the project’s agreed scope process. Here the immediate choice is whether to change the release contents and timing, launch the agreed journey, or choose a clearly defined narrower release. A future feature should not become an implied commitment merely because someone captured the idea.

Offer options with consequences

Present a small set of real alternatives. Option one: release the agreed service descriptions and enquiry route after the current checks, then assess the comparison tool for a later release. Option two: pause the launch while the team defines the new feature and revises the plan. Option three might be a simpler, reviewed explanation that answers the underlying question without introducing the tool, if the team can genuinely prepare it.

Do not promise all three as equally feasible. State which assessment or decision is missing for each. Explain what existing checks would need repeating if the change enters now. Use the actual site and team constraints rather than a generic claim that late ideas always cause delay.

Use a reply that respects the idea

A possible client message reads: “The service chooser could help visitors distinguish the options. For this launch, we have prepared the service pages and enquiry route we agreed. The chooser adds service rules and result paths that are not yet defined or checked. My recommendation is to finish the current release checks and assess the chooser separately. If it is essential for launch, we should pause and agree the revised scope and timing before continuing. Which direction would you like us to assess?”

The wording explains a recommendation without pretending the client has already accepted it. If the current route has an unresolved weakness, name it honestly alongside the proposed options. Do not imply the launch is ready merely to make deferral easier to sell.

Preserve a useful later-release record

Capture the originating page and version, the customer problem, the proposed behaviour, the intended benefit as a hypothesis, and the questions still unanswered. Add the decision to defer, its owner, the reason and a next assessment point. Keep a short example of the proposed customer path so the later conversation can start from recognisable material.

For the fictional tool, the first later action might be “offer owner drafts service-choice rules for review”, not “developer builds chooser”. Agree when that action will be considered and who will invite the decision. A backlog title with no owner or return point preserves very little of the original conversation.

Confirm the current release boundary

Read the choice back: what will launch, what remains outside it, what must still be checked and when the deferred idea returns. Ask the authorised client contact to confirm the choice at that scope. Then update the release record so colleagues do not rediscover the suggestion and quietly start building it. Deferral works when the idea stays understandable and the present commitment stays explicit.

Preserve the idea and its page context even when it moves to a later release. A well-kept feedback record lets you defer work without making the client repeat the request.

Continue with Who Can Settle Conflicting Website Feedback? and What Should Stay in the Website Backlog?.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.