Saying No Professionally

"Can you just install it? It's only a small thing." It is a small thing, the person asking is pleasant, and the technician is standing at their desk anyway. The policy that says no is somewhere on a wiki that nobody has opened since it was written. So the technician says yes, and the small thing takes forty minutes. The next person has heard that IT will do it if you ask nicely. Six months later the desk is maintaining a piece of software that nobody approved for a department that has built a process around it. Nobody said no because saying no felt rude, and the cost of yes was invisible until it was large.

This series is about saying no in a way that keeps the relationship and the policy. It covers why no is hard at a help desk and the three different kinds of no. It covers the anatomy of a good one, in five parts and about four sentences. It covers declining out-of-scope requests by pointing at something written rather than at yourself. Then comes offering an alternative instead of a wall. It covers saying no upward, to the manager who wants the exception, by escalating the decision rather than refusing alone. And it covers a no the whole team can stand behind, so that the answer does not depend on who picked up the phone. A good no takes longer to write than a yes. It is cheaper by Friday.

Articles in This Series

• Why No Is Hard at a Help Desk, and the Three Kinds of No
  The helper instinct, the fear of the complaint, and the hidden cost of yes. Covers the three kinds of no (not us, not now, not ever) and why each needs different words, and the three-kinds card.
• The Anatomy of a Good No: Five Parts in Four Sentences
  Acknowledge the ask, state the no plainly, give the real reason in one sentence, offer the alternative, leave the door open. Includes six nos rewritten from bad to good, and the no skeleton.
• Declining Out-of-Scope Requests: Point at the Page, Not Yourself
  Pointing at the published scope, routing to the right place, logging the request so the pattern is counted, the gray-area call, and the out-of-scope reply.
• Offering an Alternative Instead of a Wall: Four Kinds of Yes
  The workaround, the partial yes, the later yes, the who-else; when there is no alternative and how to say so; and the alternatives table.
• Saying No Upward: Managers, Directors and the Exception
  The manager asking for the exception, the director's request, escalating the decision rather than refusing alone, the written record, the yes-with-conditions, and the upward-no message.
• A No the Whole Team Can Stand Behind: The Common-Nos List
  Consistency across technicians, the written list of common nos with their wording, backing the technician who said it, reviewing the list, and the common-nos list.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.