DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Change Request Nobody Wants to Raise

By Deepak Kumar, CISSP

The problem: A security fix needs a change request to the client. The delivery manager will not raise it, for fear of upsetting the client or looking like the team is late. Security says, “We need it.” The delivery manager says, “Let us wait for a better moment.” The better moment never comes.

Words used here: a change request is a formal ask to the client to change the scope, the price, or the date. A delivery manager is the person responsible for finishing a client project on time and within budget.

Think of a message sitting in drafts

You have to tell a customer that the job will cost a little more. You write the message, and you read it three times. Then you save it as a draft. Tomorrow is a better day, you think. A week later, the customer calls you, and the news is worse.

The message that stays in drafts
Change request, stuck in drafts
I do not want to upset them.
Delivery manager
Is there any news?
Client
The message is not hard to write. It is hard to send.

The message is not hard to write. It is hard to send.

What it looks like at work

Security finds that the client’s old login system cannot support a safe way of signing in. Fixing it needs a small change on the client’s side, and a change request. The security lead writes it. The delivery manager reads it and says, “The client has been upset about the date. Let us not raise it now.” Weeks go by. The client’s own auditor finds the gap, and asks why the project team never mentioned it.

How a needed request is never sent
  1. 11. Need foundSecurity finds a client-side fix
  2. 22. DraftedThe manager reads the request
  3. 33. Fear“The client may see it as a delay.”
  4. 44. WaitingIt stays in drafts for weeks
  5. 55. ResultThe client finds the gap first
Bad news gets worse the longer it waits.

Both sides are half right. The delivery manager is right that the client relationship matters, and that a badly worded request can sound like an excuse. Security is right that the client has a real need to know. What is missing is a short, calm way to deliver the message, which both teams stand behind.

You will notice it when:

  • A request has been “ready” for weeks and nobody sends it.
  • The delivery manager says “not now” more than once.
  • Security does not know how the client is likely to react.
  • The request is written in technical words.
  • Nobody has asked the client how they want to hear about problems.

What exactly needs fixing

The first fix is not the request. It is who carries the message, and how. This card shows the whole problem on one page:

The change request nobody wants to raise
WHAT IS BROKEN

A needed change request is never sent, because the manager fears the client.

WHERE IT IS

The project's change process and the talk with the client.

WHAT COULD GO WRONG

The client or an auditor finds the gap first, and trust drops.

WHAT IT COSTS US
  • Late discovery
  • Trust lost
  • Rushed fix
  • Client dispute
THE FIX, IN THREE MOVES
  1. 1
    1. Write one page
  2. 2
    2. Say it together
  3. 3
    3. Frame it as care
WHO FIXES IT

Who fixes it: manager and security

BY WHEN

By when: request sent in 1 week

A blank copy of this card is in the Tools section.

Why it happens

  • Raising a problem feels like admitting a mistake. Even when it is not the team’s mistake.
  • The delivery manager owns the client relationship. So they feel the risk personally.
  • Security writes in technical words. The request sounds like a complaint.
  • There is no calm, standard way. Every request feels like a first.
  • Past experience. A client once reacted badly to a request, and the team still remembers it.
  • Nobody shares the weight. The delivery manager feels alone with the message.

What happens if you ignore it

Bad news does not go away by waiting. It grows.

  • The client finds the gap first, and asks why nobody told them.
  • The fix is rushed, so it costs more and is more likely to fail.
  • Trust drops, which makes every later request harder to raise.
  • Security and delivery start to see each other as the problem.

At a glance

QuestionAnswer
How likely is it to hurt us?Quite likely. It is common wherever a client is touchy.
Worst case?The client or an auditor finds a gap that we knew about.
What does it cost?A rushed fix, a damaged relationship, and a worse conversation later.
What if we wait?The same message has to be sent, with a harder tone.
What does the fix cost?One page, one call, and a bit of courage shared by two people.

How to fix it, step by step

Make the message short, calm, and shared.

  1. Security writes one page. The risk in plain words, two or three options, the cost, and the date. No jargon.
  2. Read it with the delivery manager first. Ask: “What would upset the client here? What would help?” Change the wording together.
  3. Choose how the client likes to hear. A call, then a written note. Never surprise them by email alone.
  4. The delivery manager leads the call. They own the relationship. Security joins to answer the technical questions.
  5. Frame it as care. “We are protecting your data and your date.” Not “We found a problem with your system.”
  6. Offer options and a recommendation. Let the client choose, with a clear next step.
  7. Confirm in writing afterwards. A short email with what was agreed.
  8. If it is still stuck after a week, go up together. Both leads take it to the head of the project, with the one page.
Send the request together, as a plan
1. Security writesOne page: the risk, the options, the cost.
2. Say it togetherThe manager leads the call. Security backs it with facts.
3. Frame it as careWe are protecting your data and your date.
The client hears a plan, not a problem.

The picture shows the three moves. The important part is that two people carry the message, not one.

Who to bring in: The delivery manager (leads the call), security (the facts), the account lead (if the client is senior), and the head of the project (if it is stuck).

Tools and templates

One page for the client

FieldWrite here
What we foundOne sentence, in the client’s words
Why it matters to youYour data, your customers, your audit
OptionsFix now, fix by a date with a stop-gap, or accept the risk
Our recommendationOne option
What we need from youA decision by a date

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a leak, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the delivery manager

Subject: Sending the change request together

Hi [name]. I know the client has been unhappy about the date, and I do not want to make it worse. I wrote a one-page note about the login change. Could we read it together for 15 minutes and change anything that sounds wrong? I would like you to lead the call, and I will join to answer the technical questions. I think the client will take it better from you.

A short opening for the call

We are calling because we want to protect your data and your date. We found one thing that needs a small change on your side. We have three options, and a recommendation. We would like to go through them with you, and agree the next step today.

Field tip

Do not send the request for the delivery manager. Write it with them, and let them hold the call. They know the client best.

Words used in this chapter

  • Change request: a formal ask to change the scope, price, or date.
  • Delivery manager: the person responsible for finishing a client project on time and within budget.
  • Stop-gap: a temporary protection until the real fix is done.
  • Client relationship: the trust and habits between your team and the client.