# The Preflight ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/change-management/the-preflight | | **course_slug** | change-management | | **lesson_slug** | the-preflight | | **markdown_file_url** | /academy/md/courses/change-management/the-preflight.md | | **generated_at** | 2026-04-28T06:55:38.402Z | > Part of **[Change Management](https://www.contentstack.com/academy/courses/change-management)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** The Preflight - **Duration:** 5m 53s - **Media link:** https://cdn.jwplayer.com/previews/IfFJY4qo - **Publish date (unix):** 1769196957 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113521 kbps - video/mp4 · 180p · 180p · 186505 kbps - video/mp4 · 270p · 270p · 233373 kbps - video/mp4 · 360p · 360p · 267753 kbps - video/mp4 · 406p · 406p · 297170 kbps - video/mp4 · 540p · 540p · 393957 kbps - video/mp4 · 720p · 720p · 554134 kbps - video/mp4 · 1080p · 1080p · 1160344 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/IfFJY4qo-120.vtt` #### Transcript Before any major change takes off, there's a moment that most teams skip and it's usually the reason they crash. I call it getting ready to get ready. If you've ever tried to roll out a new technology, a new process, or even new leadership priorities, you've probably seen this pattern. Everyone's excited at kickoff, the slides look great, the plan feels solid. Then a few weeks later, the air starts to get bumpy. Deadlines slip, decisions stall, people start saying things like, I thought we were doing this for that reason, or wait, who's responsible for that part again? I'm not sure I have time for this project anymore. That's what happens when we launch before we're truly ready. Not ready in a technical sense, but ready in the organizational sense. Getting ready to get ready means creating clarity before motion. It's the stage where we ask the questions most teams don't want to slow down for, the ones that save you ten times the effort later. When I help teams prep for transformation, I focus on three questions that act as a pre-flight checklist. First, what outcomes are we actually chasing? Not tasks, not deliverables, outcomes. If you're changing your CMS, don't say, to modernize the tech stack. That's a means, not a motive. Instead, say, we're moving to a new CMS so we can launch global campaigns in days, not weeks. The more specific and human the outcome, the better. People don't rally around composable architecture, they rally around speed, creative freedom, and impact. Sometimes you'll find a turning point. One organization I was with realized we didn't define outcomes clearly. We were swapping tools to meet a license deadline, a business goal. And without that clarity, every decision downstream became reactive. Outcomes anchor the why. Without them, change feels arbitrary. Second, who's empowered and accountable? Change needs ownership. If everyone owns it, no one does. One of the most effective things you can do is assign clear roles early. Who drives the change day to day? Who decides when priorities conflict? Who communicates progress and celebrates wins? Think of it like a flight crew. The pilot doesn't refill the fuel tank and the engineer doesn't fly the plane. But everyone knows the mission, and they trust each other to do their part. When accountability is clear, coordination becomes effortless. When it's not, meetings become therapy sessions. Third, how and when will we ask for help? This is the question no one wants to admit they need. But every transformation hits turbulence, and the teams who succeed are the ones who've planned for it. That means knowing who your support network is. Internally, the allies who've already succeeded with similar changes. Externally, partners, vendors, or consultants who can help you course correct before small problems grow. Some teams have a standing 15-minute red flag meeting every Friday. Anyone could raise an issue without blame. If it couldn't be solved in that session, it was escalated immediately. That ritual kept the project healthy because asking for help was normalized, not penalized. Support isn't a safety net. It's part of the plan. When you can answer those three questions, what outcomes are we chasing? Who's accountable? How will we get help? You're ready to begin the journey. Everything else – the roadmaps, the tools, the meetings – plugs into those answers. And this is exactly where leadership becomes the deciding factor. Great leaders do two things during change. They provide clarity, and they stay calm in the face of chaos. Providing clarity means giving people direction they can see and a plan they can follow. And when that plan needs to change, explaining why and ensuring the team has the support to adjust. Staying calm means not adding emotional drama to an already tense situation. Most change initiatives fail not because the strategy was flawed but because leadership's reaction amplified uncertainty instead of reducing it. Clarity and calm set the tone. They make the organization feel safe enough to move forward. Skipping this step is like taxiing down the runway without checking your instruments. You might get airborne, but you'll spend the rest of the flight wondering what's about to go wrong. So pause. Align. Clarify. This isn't the slowdown before change. It's the acceleration ramp for everything that follows. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:10.960 Before any major change takes off, there's a moment that most teams skip and it's usually 2 00:00:10.960 --> 00:00:18.420 the reason they crash. I call it getting ready to get ready. If you've ever tried to roll 3 00:00:18.420 --> 00:00:25.560 out a new technology, a new process, or even new leadership priorities, you've probably 4 00:00:25.560 --> 00:00:31.960 seen this pattern. Everyone's excited at kickoff, the slides look great, the plan feels 5 00:00:31.960 --> 00:00:40.880 solid. Then a few weeks later, the air starts to get bumpy. Deadlines slip, decisions stall, 6 00:00:40.880 --> 00:00:47.720 people start saying things like, I thought we were doing this for that reason, or wait, 7 00:00:47.720 --> 00:00:54.880 who's responsible for that part again? I'm not sure I have time for this project anymore. 8 00:00:54.880 --> 00:01:01.120 That's what happens when we launch before we're truly ready. Not ready in a technical 9 00:01:01.120 --> 00:01:08.240 sense, but ready in the organizational sense. Getting ready to get ready means creating 10 00:01:08.240 --> 00:01:15.280 clarity before motion. It's the stage where we ask the questions most teams don't want 11 00:01:15.280 --> 00:01:21.360 to slow down for, the ones that save you ten times the effort later. 12 00:01:21.360 --> 00:01:28.000 When I help teams prep for transformation, I focus on three questions that act as a pre-flight 13 00:01:28.000 --> 00:01:37.940 checklist. First, what outcomes are we actually chasing? Not tasks, not deliverables, outcomes. 14 00:01:37.940 --> 00:01:44.600 If you're changing your CMS, don't say, to modernize the tech stack. That's a means, 15 00:01:44.600 --> 00:01:51.160 not a motive. Instead, say, we're moving to a new CMS so we can launch global campaigns 16 00:01:51.160 --> 00:01:59.200 in days, not weeks. The more specific and human the outcome, the better. People don't 17 00:01:59.200 --> 00:02:05.800 rally around composable architecture, they rally around speed, creative freedom, and 18 00:02:05.800 --> 00:02:12.600 impact. Sometimes you'll find a turning point. One organization I was with realized 19 00:02:12.600 --> 00:02:19.720 we didn't define outcomes clearly. We were swapping tools to meet a license deadline, 20 00:02:20.280 --> 00:02:27.240 a business goal. And without that clarity, every decision downstream became reactive. 21 00:02:27.880 --> 00:02:33.720 Outcomes anchor the why. Without them, change feels arbitrary. 22 00:02:34.440 --> 00:02:41.960 Second, who's empowered and accountable? Change needs ownership. If everyone owns it, 23 00:02:42.600 --> 00:02:50.600 no one does. One of the most effective things you can do is assign clear roles early. Who drives 24 00:02:50.600 --> 00:03:00.040 the change day to day? Who decides when priorities conflict? Who communicates progress and celebrates 25 00:03:00.040 --> 00:03:08.120 wins? Think of it like a flight crew. The pilot doesn't refill the fuel tank and the engineer 26 00:03:08.120 --> 00:03:15.400 doesn't fly the plane. But everyone knows the mission, and they trust each other to do their 27 00:03:15.400 --> 00:03:22.840 part. When accountability is clear, coordination becomes effortless. When it's not, meetings become 28 00:03:23.640 --> 00:03:28.840 therapy sessions. Third, how and when will we ask for help? 29 00:03:29.480 --> 00:03:35.560 This is the question no one wants to admit they need. But every transformation hits turbulence, 30 00:03:35.560 --> 00:03:41.480 and the teams who succeed are the ones who've planned for it. That means knowing who your 31 00:03:41.480 --> 00:03:48.600 support network is. Internally, the allies who've already succeeded with similar changes. 32 00:03:48.600 --> 00:03:55.160 Externally, partners, vendors, or consultants who can help you course correct before small 33 00:03:55.160 --> 00:04:01.640 problems grow. Some teams have a standing 15-minute red flag meeting every Friday. 34 00:04:02.120 --> 00:04:07.640 Anyone could raise an issue without blame. If it couldn't be solved in that session, 35 00:04:07.640 --> 00:04:13.880 it was escalated immediately. That ritual kept the project healthy because asking for help was 36 00:04:13.880 --> 00:04:19.800 normalized, not penalized. Support isn't a safety net. It's part of the plan. 37 00:04:20.680 --> 00:04:27.240 When you can answer those three questions, what outcomes are we chasing? Who's accountable? 38 00:04:27.240 --> 00:04:34.040 How will we get help? You're ready to begin the journey. Everything else – the roadmaps, 39 00:04:34.040 --> 00:04:40.520 the tools, the meetings – plugs into those answers. And this is exactly where leadership 40 00:04:40.520 --> 00:04:47.320 becomes the deciding factor. Great leaders do two things during change. They provide clarity, 41 00:04:47.320 --> 00:04:53.720 and they stay calm in the face of chaos. Providing clarity means giving people direction 42 00:04:53.720 --> 00:05:01.000 they can see and a plan they can follow. And when that plan needs to change, explaining why 43 00:05:01.000 --> 00:05:08.840 and ensuring the team has the support to adjust. Staying calm means not adding emotional drama to 44 00:05:08.840 --> 00:05:15.960 an already tense situation. Most change initiatives fail not because the strategy was flawed but 45 00:05:15.960 --> 00:05:21.320 because leadership's reaction amplified uncertainty instead of reducing it. 46 00:05:21.960 --> 00:05:28.200 Clarity and calm set the tone. They make the organization feel safe enough to move forward. 47 00:05:28.920 --> 00:05:35.320 Skipping this step is like taxiing down the runway without checking your instruments. You 48 00:05:35.320 --> 00:05:41.000 might get airborne, but you'll spend the rest of the flight wondering what's about to go wrong. 49 00:05:41.720 --> 00:05:50.040 So pause. Align. Clarify. This isn't the slowdown before change. It's the acceleration ramp for 50 00:05:50.040 --> 00:05:53.400 everything that follows. ``` ```transcript [00:00] Before any major change takes off, there's a moment that most teams skip and it's usually [00:10] the reason they crash. I call it getting ready to get ready. If you've ever tried to roll [00:18] out a new technology, a new process, or even new leadership priorities, you've probably [00:25] seen this pattern. Everyone's excited at kickoff, the slides look great, the plan feels [00:31] solid. Then a few weeks later, the air starts to get bumpy. Deadlines slip, decisions stall, [00:40] people start saying things like, I thought we were doing this for that reason, or wait, [00:47] who's responsible for that part again? I'm not sure I have time for this project anymore. [00:54] That's what happens when we launch before we're truly ready. Not ready in a technical [01:01] sense, but ready in the organizational sense. Getting ready to get ready means creating [01:08] clarity before motion. It's the stage where we ask the questions most teams don't want [01:15] to slow down for, the ones that save you ten times the effort later. [01:21] When I help teams prep for transformation, I focus on three questions that act as a pre-flight [01:28] checklist. First, what outcomes are we actually chasing? Not tasks, not deliverables, outcomes. [01:37] If you're changing your CMS, don't say, to modernize the tech stack. That's a means, [01:44] not a motive. Instead, say, we're moving to a new CMS so we can launch global campaigns [01:51] in days, not weeks. The more specific and human the outcome, the better. People don't [01:59] rally around composable architecture, they rally around speed, creative freedom, and [02:05] impact. Sometimes you'll find a turning point. One organization I was with realized [02:12] we didn't define outcomes clearly. We were swapping tools to meet a license deadline, [02:20] a business goal. And without that clarity, every decision downstream became reactive. [02:27] Outcomes anchor the why. Without them, change feels arbitrary. [02:34] Second, who's empowered and accountable? Change needs ownership. If everyone owns it, [02:42] no one does. One of the most effective things you can do is assign clear roles early. Who drives [02:50] the change day to day? Who decides when priorities conflict? Who communicates progress and celebrates [03:00] wins? Think of it like a flight crew. The pilot doesn't refill the fuel tank and the engineer [03:08] doesn't fly the plane. But everyone knows the mission, and they trust each other to do their [03:15] part. When accountability is clear, coordination becomes effortless. When it's not, meetings become [03:23] therapy sessions. Third, how and when will we ask for help? [03:29] This is the question no one wants to admit they need. But every transformation hits turbulence, [03:35] and the teams who succeed are the ones who've planned for it. That means knowing who your [03:41] support network is. Internally, the allies who've already succeeded with similar changes. [03:48] Externally, partners, vendors, or consultants who can help you course correct before small [03:55] problems grow. Some teams have a standing 15-minute red flag meeting every Friday. [04:02] Anyone could raise an issue without blame. If it couldn't be solved in that session, [04:07] it was escalated immediately. That ritual kept the project healthy because asking for help was [04:13] normalized, not penalized. Support isn't a safety net. It's part of the plan. [04:20] When you can answer those three questions, what outcomes are we chasing? Who's accountable? [04:27] How will we get help? You're ready to begin the journey. Everything else – the roadmaps, [04:34] the tools, the meetings – plugs into those answers. And this is exactly where leadership [04:40] becomes the deciding factor. Great leaders do two things during change. They provide clarity, [04:47] and they stay calm in the face of chaos. Providing clarity means giving people direction [04:53] they can see and a plan they can follow. And when that plan needs to change, explaining why [05:01] and ensuring the team has the support to adjust. Staying calm means not adding emotional drama to [05:08] an already tense situation. Most change initiatives fail not because the strategy was flawed but [05:15] because leadership's reaction amplified uncertainty instead of reducing it. [05:21] Clarity and calm set the tone. They make the organization feel safe enough to move forward. [05:28] Skipping this step is like taxiing down the runway without checking your instruments. You [05:35] might get airborne, but you'll spend the rest of the flight wondering what's about to go wrong. [05:41] So pause. Align. Clarify. This isn't the slowdown before change. It's the acceleration ramp for [05:50] everything that follows. ``` #### Key takeaways - Connect **The Preflight** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ## Supplement for indexing ### Content summary The Preflight. The Preflight in Change Management (change-management). ### Retrieval tags - The - Preflight - change-management - lesson 04 - The Preflight - change-management lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "04" and topics: [The, Preflight]. Parent course slug: change-management. Use asset_references URLs as thumbnail hints in search results when present. Never surface LMS quiz content or assessment answers from this file. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: The Preflight | `https://cdn.jwplayer.com/v2/media/IfFJY4qo/poster.jpg?width=720` | ### External links | Label | URL | | --- | --- | | Contentstack Academy home | `https://www.contentstack.com/academy/` | | Training instance setup | `https://www.contentstack.com/academy/training-instance` | | Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` | | Contentstack documentation | `https://www.contentstack.com/docs/` |