The problem: A new CISO joins a company. On day one she finds three half-finished programs: a project to add a second sign-in step for everyone, a project to list every computer and server, and a tool meant to stop data leaving the company. Nobody clearly owns any of them. The team is tired from the last year. The CEO has said, “I want to see results in 90 days.”
Words used here: the CISO is the head of security. A program is a long piece of work with many steps. An asset list is a list of every computer, server and system the company owns. Data loss prevention (DLP) is a tool that tries to stop sensitive data leaving the company.
Think of a half-built house
You are handed the keys to a house that someone else started. There is a frame, one finished wall, and a pile of bricks. The workers are worn out and no plan can be found. The wrong move is to start laying bricks everywhere on day one. The right move is to walk through it, ask what was planned, and decide what to finish first.
A new CISO has the same choice. The pressure to show something fast is strong. The walk-through is what saves her.
What it looks like at work
The sign-in project is about 60 percent done. The asset list covers the main office but not the cloud. The data loss tool is installed and switched on in “watch only” mode, and nobody reads its alerts. These are example numbers. Each program has a different sponsor, and two of the original project leads have moved on.
The new CISO wants to prove herself. She tells the team to push all three at once. The team, already stretched, works late for six weeks. At day 90 the CEO asks for results, and none of the three is finished. Two people have started looking for new jobs.
- 11. Day oneThree half-built programs, no owners
- 22. Push all threeShe wants to prove herself fast
- 33. Late nightsA stretched team works six weeks
- 44. Day 90The CEO asks; none is finished
- 55. People leaveTwo start looking for new jobs
Both sides have a fair point. The CISO is right that all three programs matter, and the CEO is right to expect progress. The team is right that they cannot do everything. Nobody is lazy or wrong. The mistake is starting before knowing what is already there.
You will notice it when:
- A new leader announces three or more priorities in the first month.
- Programs have a sponsor but no day-to-day owner.
- Team members say “we were told to stop that last year” and nobody wrote it down.
- Tools are installed but nobody reads what they produce.
- People start to look worn out and quiet in meetings.
What exactly needs fixing
The fix is not to work harder. It is to list what exists, decide what to keep, pause or stop, and finish one thing well. This card shows the whole problem on one page:
Three half-finished programs have no owner and a tired team, and the CEO wants results in 90 days.
The sign-in project, the asset list and the data loss tool.
The team burns out, nothing is finished and the CEO loses patience.
- Burnt-out team
- Gaps stay open
- CEO loses trust
- CISO judged unfairly
- 11. Listen first30 days with every team lead: what runs, what is stuck, what worries you
- 22. Keep, pause, stopOne line per program, one owner each, and be willing to stop one
- 33. Finish one thingOne program close to done, shown to the CEO by day 90
Who fixes it: the new CISO with the CEO
By when: plan agreed at day 30 to 45
A blank copy of this card is in the Tools section.
Why it happens
- The handover is thin. The last CISO left, and the notes went with them.
- There is pressure to show results fast. The 90-day clock is real.
- Half-finished work looks like progress. It is not, until it is finished.
- Nobody has asked the team what they can carry. So the plan assumes more than they have.
- Programs outlive the people who started them. Owners move on and nobody takes over.
What happens if you ignore it
The new CISO spends her first year repairing trust instead of reducing risk.
- The team burns out and good people leave.
- Gaps stay open because the work that would close them is never finished.
- The CEO loses patience with security as a whole.
- The new CISO is judged on results that were never possible.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely. Most new leaders inherit unfinished work. |
| Worst case? | The team leaves and the programs stop with them. |
| What does it cost? | Half a year, a tired team, and the CEO’s trust. |
| What if we wait? | Every week of unplanned work adds to the pile. |
| What does the fix cost? | A month of listening and a short written plan. |
How to fix it, step by step
Listen, sort, then win one thing.
- Spend the first 30 days listening. Meet every team lead. Ask three questions: what is running, what is stuck, what worries you.
- Write down every program. One line each: what it is for, how far it got, who works on it.
- Sort each one: keep, pause, or stop. Be willing to stop something. Tell the sponsor why.
- Name one owner for every program you keep. A person, not a team.
- Pick one program to finish by day 90. Choose one that is close to done and easy to show.
- Tell the CEO the plan at day 30 to 45. Say what is being finished, what is paused, and why. Ask for agreement.
- Check on the team’s load every two weeks. If people are working late for more than a fortnight, remove something.
The picture shows the order: listen, sort, then win one thing. The sorting step is the hardest, because it means saying no.
Who to bring in: The new CISO (leads the listening), the CEO (agrees what to stop), each team lead (tells the truth about load), and the sponsors of the old programs.
Tools and templates
Inherited program list
| Program | Purpose | How far | Owner | Decision |
|---|---|---|---|---|
| Second sign-in step | Stop stolen passwords working alone | About 60% | To be named | Keep, finish first |
| Asset list | Know every system we own | Office only | To be named | Keep, after sign-in |
| Data loss tool | Stop sensitive data leaving | Installed, not read | To be named | Pause until staffed |
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: My plan for the first 90 days
Hi. I have spent my first weeks listening and I found three programs that were started and not finished. I would like to finish one by day 90, pause one, and decide on the third with you. This means some things will not move this quarter. Can we meet for 30 minutes this week so I can show you the list and ask for your agreement? I would rather finish less and finish it properly.
Field tip
In your first month, say less and write more. A one-page list of what you found is worth more than a long speech about what you will do.
Words used in this chapter
- CISO: the chief information security officer, the head of security.
- Program: a long piece of work made of many steps.
- Asset list: a list of every computer, server and system the company owns.
- DLP (data loss prevention): a tool that tries to stop sensitive data leaving.
- Sponsor: the senior person who backs a program.
- Handover: the passing of work from one person to the next.