Saying no — Examples

Example 1 — Refusing the dashboard, answering the need

A stakeholder has asked for a second reporting dashboard, and three months of tickets say the data behind it is missing, not badly presented. A good no refuses the item and keeps the relationship, so the reply must acknowledge the need, refuse the solution, give the trade, and name a condition for reversal.

Message from the head of sales:
  Can we get a second dashboard for the pipeline? The current one is
  useless for my team. I have asked before and nothing happens, so
  tell me if I should raise it elsewhere.

Solution

That is a real problem — I see it in the tickets too, and the current
dashboard is missing last quarter's deals.

I will not build a second dashboard this quarter: the same data is
missing from the first one, so a second view would be wrong the
same way. If the fix is the data, it is a two-week job I would
move up.

What would change my mind: a different measure, not a different
view. Send one example where the numbers disagree. Support has a
saved view that pulls the missing deals.

This is a decision rather than a delay because it names the item refused, the reason it loses, and the condition that would reverse it, so the requester can influence the outcome rather than wait. The usual mistake is silence.

Example 2 — The refusal log that turns repeats into process

Four requests were refused over two months, two with the same wording from different people, and each conversation starts again. A refusal log turns a repeat into evidence — first about the request, third about the process. Record the refusals below and say what the repeat changes.

Feb  saved payment methods  refused: below refunds, review in June
Mar  second dashboard       refused: the data is missing
Mar  saved payment methods  refused again, same reason given
Apr  saved payment methods  asked once more, via a director

Solution

Request               Refused because           Route offered
saved payment methods below refunds in the order review 6 June
second dashboard      the data is missing        fix the feed
saved payment methods same as February           the June review
saved payment methods escalated, same answer     the June review

Read: the same request from four directions in ten weeks is evidence
about the request, not the people. Change: publish the review date
with the order.

The log shows the repeat and names the process change: the third occurrence is a signal that the order and its reasons need to be public. The common failure is treating each repeat as a fresh conversation.