Skip to tutorial content
Rate module Not yet rated

Running the Kickoff Call

4 min read
On this page

In this lesson, you will learn:

  • How to structure a 90-minute kickoff
  • How to answer hard questions calmly
  • How to close with clear next steps

🔁 Quick look back: Last time: Preparing the Kickoff Pack. You learned what goes into the kickoff pack, and why you send it early.

1 The Problem: Kickoff Can Waste 90 Minutes

Kickoffs often go wrong in the same ways:

  • One topic takes the whole hour.
  • A hard question gets a vague answer.
  • People leave without knowing what to do next.

🎯 The problem: A kickoff can waste 90 minutes and leave people unsure.

👉 The fix: Run a timed agenda, answer hard questions plainly, and end with named actions.

Six agenda items with minutes.
Figure 1. The Clear View kickoff agenda (90 minutes).

2 Running the call

  1. Start on time. Ask Anita to open with why SNWR wants Clear View.
  2. Explain Discovery with the one-page explainer. Avoid jargon.
  3. Show the plan and the six gates. Say what you need from whom, and when.
  4. Take questions. Park long topics for a follow-up.
  5. Close by reading out each action, its owner and its date.

💡 Good to know: Keep a ‘parking lot’ list on screen. Long topics go there, so the meeting stays on time.

3 Answering hard questions

Farah asked: ‘Will your scans break anything?’ A good answer is honest and specific:

  • Scans only read data. They don’t change devices.
  • We start with one server, then a small pilot, before anything bigger.
  • Fragile ranges, like building systems, are excluded.
  • Scans run at night, inside approved windows, under change control.

⭐ Remember: If you don’t know an answer, say so, and promise a date to follow up.

4 Project Clear View: How We Implemented It

📍 Situation: Kickoff is Monday of week 1. Twelve people join, with Oliver in London.

🧭 Decision: Run a strict 90-minute agenda and leave with owned actions.

🛠️ Steps we took:

  1. Anita opened with the three pains: empty CI fields, the spreadsheet, the VPN outage.
  2. You explained one scan of snwr-mail-01 using the explainer.
  3. You answered Farah’s question with the four points above.
  4. You closed with seven actions. For example: Ravi sends the subnet list by Wednesday.

✅ What we verified:

  • Every action has an owner and a date.
  • The meeting ended on time.

📁 Evidence: Kickoff notes and the action list, sent the same afternoon.

5 Quick recap

  • Use a timed agenda: goals, how it works, plan, roles, questions, next steps.
  • Explain Discovery in plain words.
  • Answer hard questions honestly and specifically.
  • Close with actions that each have an owner and a date.

6 Check yourself

Think of your answer first. Then tap to check.

1 What’s a ‘parking lot’ in a meeting? Show answer

A list of long topics saved for later, so the meeting stays on time.

2 How did you answer ‘Will your scans break anything?’ Show answer

Scans only read data; start small; fragile ranges excluded; scans at night under change control.

3 What must every kickoff action have? Show answer

An owner and a date.

Nice work! You can run a Discovery kickoff. 🎉
Next up: Roles and Responsibilities (RACI)

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.