The problem: The company needs to replace its endpoint protection (the software that guards laptops and servers). The head of IT backs Tool A, which is cheaper and easier to run. The CISO backs Tool B, which caught more attacks in a test. Each brings a slide deck with a different test and different criteria. Four months pass, and the old licence will end in six weeks.
Words used here: endpoint protection is software that guards laptops and servers from attacks. A licence is the permission to use a product for a period. Criteria are the things you judge a choice on. Weights show how much each one matters.
Think of two friends choosing where to eat
Two friends are hungry. One says, “Pizza, it is cheap.” The other says, “Sushi, it is better.” Each is right by their own measure. They stand on the pavement and argue about the restaurants, and the clock goes on. If they had agreed first what mattered (cheap, close, or best) the choice would have taken a minute.
The head of IT and the CISO are arguing about the restaurants. They never agreed what matters.
What it looks like at work
The head of IT tests Tool A on 50 laptops for ease of rollout and running cost. The CISO tests Tool B on a set of sample attacks for detection. These are example numbers. Both tests are fair, and neither answers the other’s question. Each leader presents to the steering group and each is persuasive.
The project lead cannot compare the two and the group cannot decide. Procurement waits for a decision. With six weeks left on the old licence, the company is forced into a rushed purchase on poor terms, and the CEO asks why it took four months.
- 11. Two viewsIT backs Tool A, security backs Tool B
- 22. Two testsDifferent samples, different criteria
- 33. Two decksBoth persuasive, neither comparable
- 44. No decisionMonths pass and the meetings repeat
- 55. Deadline winsA rushed buy on poor terms
Both leaders have a fair point. IT is right that a tool that is hard to run will be run badly. Security is right that a tool that misses attacks is not worth running. Both want the company protected. The problem is not their view of the tools. They have no shared way to weigh them.
You will notice it when:
- Two decks show two different tests of two different tools.
- Nobody can say what the criteria are or how much each one counts.
- The meetings return to the same argument each time.
- A date on a contract is getting close and no choice has been made.
- People start asking for a “third opinion” to break the tie.
What exactly needs fixing
The fix is not to decide who is right. It is to agree how the choice will be made before looking at any tool, then to test together. This card shows the whole problem on one page:
IT and security back different endpoint tools, with different tests, and the old licence ends in six weeks.
The endpoint protection replacement project and its steering group.
The old tool stops getting updates before a new one is in place.
- Months of time
- Rushed contract
- Split between teams
- Gap in protection
- 11. Agree the scoringCriteria and weights out of 100, agreed before any tool is looked at
- 22. Test togetherOne shared test, with the run team scoring ease of use
- 33. Name a tie-breakIf scores are close, the CEO or CIO decides the same day
Who fixes it: CISO and head of IT together
By when: scoring agreed this week, decision in 3 weeks
A blank copy of this card is in the Tools section.
Why it happens
- Each leader measures what they care about. Cost and ease for IT, detection for security.
- Nobody wrote the criteria first. So each side wrote them to suit its choice.
- The tests are not the same. Different samples give different results.
- There is no tie-break. Two equal leaders cannot settle it between them.
- Waiting feels safer than choosing. Until the deadline arrives.
What happens if you ignore it
The deadline decides, not the company.
- A rushed purchase at poor terms, because time has run out.
- A gap in protection if the old licence ends.
- IT and security stop trusting each other’s judgement.
- The loser of the argument runs the tool without believing in it.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, in any company with two strong views and a shared budget. |
| Worst case? | The old tool stops getting updates before a new one is in place. |
| What does it cost? | Months of time, a rushed contract, and a split between teams. |
| What if we wait? | The licence date decides for you. |
| What does the fix cost? | Two meetings to agree scoring, and a joint test. |
How to fix it, step by step
Agree the scoring, test together, then name a tie-break.
- Put the two leaders in one room before looking at any tool. The aim is to agree how the choice will be made.
- Write the criteria. Cost, ease of running, detection, support, fit with our systems.
- Give each a weight. Out of 100 points in total, so that trade-offs are visible.
- Agree one test. The same sample attacks, the same laptops, the same time period.
- Test together. Both teams watch, and the run team scores ease of use.
- Score against the sheet. Not against the slide deck.
- Name a tie-break. If scores are within a few points, the CEO or CIO decides the same day.
The picture shows the order: agree the scoring, test together, then name a tie-break. The first step is the one both leaders will resist, and it is the one that works.
Who to bring in: The CISO and the head of IT (co-own the choice), the run team (scores ease of use), procurement (sets the timetable), and the CEO or CIO (breaks a tie).
Tools and templates
Scoring sheet
| Criterion | Weight (of 100) | Tool A score | Tool B score |
|---|---|---|---|
| Detects attacks in the shared test | 35 | ||
| Ease of running day to day | 25 | ||
| Cost over three years | 20 | ||
| Fit with our systems | 10 | ||
| Vendor support | 10 |
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 failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to start the talk
Subject: Agreeing how we will choose the endpoint tool
Hi both. We have two good options and a licence that ends in six weeks. Before we debate the tools again, can we agree how we will choose? I would like us to write five criteria with weights, run one shared test, and agree that the CEO breaks a tie if it is close. Can we meet for 45 minutes this week? I am not asking either of you to give way. I am asking us to agree the ruler first.
Field tip
If a decision has dragged on for more than a month, ask: “Do we all agree how we will decide?” The answer is usually no.
Words used in this chapter
- Endpoint protection: software that guards laptops and servers from attacks.
- Licence: permission to use a product for a set period.
- Criteria: the things you judge a choice on.
- Weight: how much one criterion counts.
- Tie-break: a person or rule that decides when the scores are close.
- Steering group: the senior people who oversee a project.