The problem: The delivery manager is judged on dates and profit. A security fix costs both, so it feels like a threat to their own results, and they say, “Let us do it later.”
Words used here: a delivery manager is the person responsible for finishing a client project on time and within budget. Margin is the profit left after the project’s costs.
Think of a builder who gets a bonus for finishing on time
A builder is paid a bonus if the house is handed over on the promised day. One week before handover, the inspector finds a crack in a load-bearing wall. Fixing it means a delay, extra cost, and no bonus. The builder says, “We will fix it after the family moves in.” Nobody doubts that the crack matters. But the builder is paid for the date, not for the wall.
The same pressure sits behind many security findings.
What it looks like at work
A project is two weeks from go-live. Security checks the application and finds a serious weakness: a form on the site does not check what people type into it, so an attacker could send harmful input. Fixing it needs about a week of developer time.
Security writes: “This must be fixed before launch.” The delivery manager answers: “The client has fixed the date. A delay costs us the profit, and my bonus depends on both. Log it as a later fix.” Security cannot stop the release, and the manager has no reason to.
- 11. The scorecardJudged on date and profit only.
- 22. Two weeks leftGo-live is in two weeks.
- 33. Security findsOrder form lets in harmful input.
- 44. Security asksFix it before launch. It needs one week.
- 55. The answerLog it as a later fix.
The delivery manager is not careless. They are doing exactly what their scorecard rewards.
You will notice it when:
- Security findings arrive in the last two weeks of a project.
- The answer is always “the date is fixed” or “we will fix it in the next release.”
- Findings are written in technical words, so the manager cannot tell how bad they are.
- Nobody agreed in advance what must be fixed before go-live.
- “Later” fixes sit on the waiting list for months.
What exactly needs fixing
Two things are missing: a rule agreed before the project starts, and a way to show the manager what the finding costs in their own terms. This card shows the whole problem on one page:
Security found a serious flaw in the order form, and the delivery manager wants to fix it later.
The order form on the client site, two weeks before go-live.
An attacker sends harmful input and reads client data.
- Emergency release
- Penalties
- Client data leak
- Lost trust
- 11. Set must-fix rules
- 22. Offer three options
- 33. Head decides
Who fixes it: head of delivery
By when: decision in 3 days
A blank copy of this card is in the Tools section.
Why it happens
- The scorecard rewards dates and profit only. Quality and security are not on it.
- Security is called in late. A finding in the last two weeks feels like an ambush.
- Nobody agreed on “must-fix” rules. Every finding becomes a new argument.
- Security speaks in technical words. The manager hears “warning,” not “cost.”
- Raising a problem is risky for the manager. The client may blame them for the delay.
- Client pressure is real. The date may be written in the contract.
What happens if you ignore it
The weakness reaches the client, and the cost comes later and bigger.
- A weakness in a live system is harder and slower to fix.
- The client may find it first, through their own audit or a real attack.
- The manager is blamed later, and the lesson people take is “security slows us down.”
- Security loses influence, and the next project is even harder.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Quite likely on any project with a fixed date. |
| Worst case? | A client data leak soon after launch. |
| What does it cost? | An emergency release, a talk with the client, possible penalties, and lost trust. |
| What if we wait? | The fix costs more, and the client may hear about it from someone else. |
| What does the fix cost? | Often days, not weeks, if it is found early and the right option is chosen. |
How to fix it, step by step
Turn a security argument into a business decision that the right person makes.
- Agree on must-fix rules at the start of the project. A short list of issues that must be fixed before go-live, signed by the head of delivery.
- Join the project early. Look at the design, not only the finished product, so findings arrive while they are cheap to fix.
- Say it in the manager’s words. Days of work, cost, and risk to the client. Not technical names.
- Offer options, not just a demand. A full fix, the smallest safe fix, or a stop-gap with a dated follow-up.
- Show the cost of waiting. Fixing after launch means a new release, telling the client, and possible penalties.
- Ask the head of delivery to decide, not the manager alone. Give them the card and the options.
- Ask for one line on the scorecard. For example: no serious security issue still open at go-live.
- Look back afterwards. Note what was found late and why, so the next project finds it earlier.
This is the picture to show the delivery manager. It talks about days, cost, and risk to the client.
Who to bring in: The head of delivery (the decision), the delivery manager, the lead developer (the real effort), security (the risk and the options), and the client contact if the date or the requirement is in the contract.
Tools and templates
Must-fix rules, agreed at the start
| How serious | Rule | Who can say “ship anyway” |
|---|---|---|
| Critical | Must be fixed before go-live | Head of delivery, in writing, with the client told |
| High | Fixed before go-live, or a stop-gap with a date | Head of delivery, in writing |
| Medium | Fixed within an agreed time after go-live | Delivery manager |
| Low | Added to the waiting list | Delivery manager |
Options for the finding
| Option | Effort | Risk left | Who signs |
|---|---|---|---|
| Full fix | Longest | None | Delivery manager |
| Smallest safe fix | Short | Low | Delivery manager |
| Stop-gap, fix by a date | Short now, more later | Medium until fixed | Head of delivery |
| Ship as it is | None | High | Head of delivery, in writing |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the head of delivery
Subject: One decision needed before go-live: a serious weakness in the order form
Hi [name]. Our review found a serious weakness in the order form. It lets an attacker send harmful input. Below are four options with their effort and risk. We recommend the smallest safe fix. We need your decision by [date] so the release date does not move. I am happy to walk through it in 15 minutes.
Field tip
Do not tell a delivery manager that security matters. Show them what the delay costs, and what the shortcut costs.
Words used in this chapter
- Delivery manager: the person responsible for finishing a client project on time and within budget.
- Margin: the profit left after the project’s costs.
- Go-live: the day the project is released for real use.
- Must-fix rule: a rule that says a release cannot go out until a given issue is fixed.
- Stop-gap: a temporary protection until the real fix is done.