4 steps to scaling a #SOC:
1. Collect data, you won't know what it means
2. Collect data, *kind* of understand it
3. Collect data, understand it. Able to say: "This is what's happening, let's try changing *that*"
4. Operational control. "If we do *this*, *that* will happen"
1. Collect data, you won't know what it means
2. Collect data, *kind* of understand it
3. Collect data, understand it. Able to say: "This is what's happening, let's try changing *that*"
4. Operational control. "If we do *this*, *that* will happen"
What you measure is mostly irrelevant. It’s that you measure and understand what it means and what you can do to move your process dials up or down.
If you ask questions about your #SOC constantly (ex: how much analyst time do we spend on suspicious logins and how can we reduce that?) - progress is inevitable.
W/o constantly asking questions and answering them using data, scaling/progress is coincidental.
W/o constantly asking questions and answering them using data, scaling/progress is coincidental.
You can apply this methodology to other areas of a business.
Take sales. If we start w/ the premise that “booked meetings” eventually results in new business, how many /week? What causes that # to go up or down? If you know what levers you have to make your process move, $.
Take sales. If we start w/ the premise that “booked meetings” eventually results in new business, how many /week? What causes that # to go up or down? If you know what levers you have to make your process move, $.
Ask yourself these questions:
1. What can I know?
2. How can I know it?
3. What does it mean?
4. What makes the data change? (Events, process, automation, etc)
5. Where do I want to get to?
6. What does great look like?
7. What’s stopping me?
1. What can I know?
2. How can I know it?
3. What does it mean?
4. What makes the data change? (Events, process, automation, etc)
5. Where do I want to get to?
6. What does great look like?
7. What’s stopping me?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
