# Change Management ### About this export | Field | Value | | --- | --- | | **content_type** | course | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/change-management | | **language** | en | | **product_area** | change management | | **learning_path** | standalone | | **course_id** | change-management | | **slug** | change-management | | **version** | 2026-03-18 | | **last_updated** | 2026-04-28 | | **status** | published | | **keywords** | ["change management"] | | **summary_one_line** | Course Overview Digital transformation fails when we swap systems but forget to swap mindsets. Practical Change Management is a hands-on guide designed to move teams from "what was" to "what will be" in a way that sticks… | | **total_duration_minutes** | 44 | | **lessons_count** | 9 | | **video_lessons_count** | 9 | | **text_lessons_count** | 0 | | **linked_learning_path** | standalone | | **linked_assessment_ref** | LMS_UNCONFIGURED_COURSE_ASSESSMENT | | **markdown_file_url** | /academy/md/courses/change-management.md | | **generated_at** | 2026-04-28T06:55:38.384Z | | **intended_audience** | [] | | **prerequisites** | [] | | **related_courses** | [] | > **Academy MD v3** — companion `.md` for Ask AI. Quizzes and graded assessments are **LMS-only**; this file never contains answer keys. ## Course Overview | Metadata | Value | | --- | --- | | Catalog duration | 44m 15s | | Released (if known) | 2026-03-18 | | Product area | change management | ### Description ### Course Overview Digital transformation fails when we swap systems but forget to swap mindsets. **Practical Change Management** is a hands-on guide designed to move teams from "what was" to "what will be" in a way that sticks. Through real-world stories—from global retail brands to healthcare organizations—this course strips away the buzzwords and focuses on the "human layer" of transformation. You will learn how to craft a compelling narrative for change, build organizational readiness, manage resistance as feedback, and create a repeatable playbook for future transitions. **By the end of this course, you will be able to:** * Identify the "Change Triggers" and "Outcome Lines" that drive urgency. * Align the three anchors of change: Mindset, Empowerment, and Support. * Use a "Preflight Checklist" to ensure organizational readiness before launch. * Turn skeptical resistors into empowered owners of the solution. * Build a "Change Playbook" to make transformation a repeatable organizational capability. ### Learning objectives 1. Follow each lesson in order. 2. Practice in a training stack using placeholders **YOUR_STACK_API_KEY** and **YOUR_DELIVERY_TOKEN** in local `.env` files only. 3. Validate API responses against the official documentation. ### Topics covered change management ## Course structure ```text change-management/ ├── 01-what-is-change-management- · video · 293s ├── 02-why-we-change · video · 292s ├── 03-the-human-layer-of-change · video · 387s ├── 04-the-preflight · video · 353s ├── 05-launching-change-and-building-momentum · video · 326s ├── 06-turning-momentum-into-culture · video · 264s ├── 07-turning-friction-into-fuel · video · 269s ├── 08-learning-adapting-and-scaling-success · video · 237s ├── 09-make-change-repeatable · video · 234s ``` ## Lessons ### Lesson 01 — What is Change Management? #### Video details #### At a glance - **Title:** What Is Change Management - **Duration:** 4m 53s - **Media link:** https://cdn.jwplayer.com/previews/ORYEkxiv - **Publish date (unix):** 1769111666 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113550 kbps - video/mp4 · 180p · 180p · 193318 kbps - video/mp4 · 270p · 270p · 239251 kbps - video/mp4 · 360p · 360p · 275747 kbps - video/mp4 · 406p · 406p · 306519 kbps - video/mp4 · 540p · 540p · 400397 kbps - video/mp4 · 720p · 720p · 554613 kbps - video/mp4 · 1080p · 1080p · 1135941 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/ORYEkxiv-120.vtt` #### Transcript Change. It's one of those words that either make people lean in or tense up. And if you've ever been through a digital transformation before, you know exactly what I mean. I want to start with a story. A few years ago, I worked with a global retail brand that was launching a new content platform. The project was technically flawless, the infrastructure was modern, the integrations were seamless, and the vendor had all the right slides about efficiency and scale. But six months after the launch, the team was still publishing content the old way. The fancy new platform had basically become a slightly shinier version of the one they left behind. So what went wrong? It wasn't the tool, it was the transition. No one had managed the human side of the change, how people's roles would evolve, how their habits and definitions of what success was going to be would change. They swapped a system but not a mindset. That's the gap change management fills. Change management is the discipline of helping people move from what was to what will be in a way that sticks. It's the bridge between strategy and execution. Between a PowerPoint vision and a real working future. And here's the simple truth. I've seen over and over again. Organizations don't change because a tool is shiny. They change because the status quo is no longer getting them the outcomes they need. Sometimes the industry forces the issue. Our customers expect omnichannel personalization. And sometimes it's internal. We can't keep burning out the same people to meet every deadline. Whatever the trigger, the motive is always the same. The way we work today can't get us to where we're going tomorrow. So what outcomes drive this kind of change? Think about goals like cutting time to publish from weeks to days. Giving marketers freedom without creating risk. Scaling personalization without doubling headcount. Building systems resilient enough to evolve and not to have to rebuild every few years. Those aren't feature goals. They're human goals. The reality is change management isn't about technology. It's about people. It's about helping teams unlearn comfortable routines and replace them with better ones. And that's messy. It's emotional. And it's deeply human work. When you think about it, every successful transformation shares three ingredients. First, a clear outcome. We're not just adopting tools. We're solving a problem. Next, a shared story. Everyone knows why we're doing this and what success looks like. And third, a guided path. A plan that supports people through the confusion and the uncertainty that change naturally brings. That's what we're going to explore in this course. We'll talk about the psychology of change, why people resist it, and how to bring them along for the ride. We'll look at practical steps to prepare your organization before the rollout begins. We'll walk through ways to build champions, manage resistance, and keep the momentum long after launch day. In other words, we're going to connect the vision of the transformation to the practice of making it real. Because change isn't a one-time event. It's a skill set. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:11.960 Change. It's one of those words that either make people lean in or tense up. And if you've 2 00:00:11.960 --> 00:00:18.120 ever been through a digital transformation before, you know exactly what I mean. 3 00:00:18.120 --> 00:00:25.600 I want to start with a story. A few years ago, I worked with a global retail brand that 4 00:00:25.600 --> 00:00:33.040 was launching a new content platform. The project was technically flawless, the infrastructure 5 00:00:33.040 --> 00:00:42.440 was modern, the integrations were seamless, and the vendor had all the right slides about 6 00:00:42.440 --> 00:00:49.840 efficiency and scale. But six months after the launch, the team was still publishing 7 00:00:49.840 --> 00:00:59.600 content the old way. The fancy new platform had basically become a slightly shinier version 8 00:00:59.600 --> 00:01:08.520 of the one they left behind. So what went wrong? It wasn't the tool, it was the transition. 9 00:01:08.520 --> 00:01:16.360 No one had managed the human side of the change, how people's roles would evolve, how their 10 00:01:16.360 --> 00:01:25.480 habits and definitions of what success was going to be would change. They swapped a system 11 00:01:25.480 --> 00:01:31.840 but not a mindset. That's the gap change management fills. 12 00:01:31.840 --> 00:01:39.440 Change management is the discipline of helping people move from what was to what will be 13 00:01:39.440 --> 00:01:47.480 in a way that sticks. It's the bridge between strategy and execution. Between a PowerPoint 14 00:01:47.480 --> 00:01:54.320 vision and a real working future. And here's the simple truth. I've seen over 15 00:01:54.320 --> 00:02:02.040 and over again. Organizations don't change because a tool is shiny. They change because 16 00:02:02.040 --> 00:02:10.240 the status quo is no longer getting them the outcomes they need. Sometimes the industry 17 00:02:10.240 --> 00:02:20.560 forces the issue. Our customers expect omnichannel personalization. And sometimes it's internal. 18 00:02:20.560 --> 00:02:27.640 We can't keep burning out the same people to meet every deadline. Whatever the trigger, 19 00:02:27.640 --> 00:02:37.200 the motive is always the same. The way we work today can't get us to where we're going tomorrow. 20 00:02:37.200 --> 00:02:45.960 So what outcomes drive this kind of change? Think about goals like cutting time to publish 21 00:02:45.960 --> 00:02:54.280 from weeks to days. Giving marketers freedom without creating risk. Scaling personalization 22 00:02:54.320 --> 00:03:02.360 without doubling headcount. Building systems resilient enough to evolve and not to have 23 00:03:02.360 --> 00:03:10.800 to rebuild every few years. Those aren't feature goals. They're human goals. 24 00:03:10.800 --> 00:03:18.160 The reality is change management isn't about technology. It's about people. It's about 25 00:03:18.160 --> 00:03:25.840 helping teams unlearn comfortable routines and replace them with better ones. And that's 26 00:03:25.840 --> 00:03:31.100 messy. It's emotional. And it's deeply human work. 27 00:03:31.100 --> 00:03:37.120 When you think about it, every successful transformation shares three ingredients. 28 00:03:37.120 --> 00:03:44.720 First, a clear outcome. We're not just adopting tools. We're solving a problem. 29 00:03:44.720 --> 00:03:53.280 Next, a shared story. Everyone knows why we're doing this and what success looks like. 30 00:03:53.280 --> 00:04:01.440 And third, a guided path. A plan that supports people through the confusion and the uncertainty 31 00:04:01.440 --> 00:04:08.320 that change naturally brings. That's what we're going to explore in this course. 32 00:04:08.800 --> 00:04:15.680 We'll talk about the psychology of change, why people resist it, and how to bring them 33 00:04:15.680 --> 00:04:23.080 along for the ride. We'll look at practical steps to prepare your organization before 34 00:04:23.080 --> 00:04:31.440 the rollout begins. We'll walk through ways to build champions, manage resistance, and 35 00:04:31.440 --> 00:04:35.640 keep the momentum long after launch day. 36 00:04:35.640 --> 00:04:42.680 In other words, we're going to connect the vision of the transformation to the practice 37 00:04:42.680 --> 00:04:49.320 of making it real. Because change isn't a one-time event. It's a skill set. ``` ```transcript [00:00] Change. It's one of those words that either make people lean in or tense up. And if you've [00:11] ever been through a digital transformation before, you know exactly what I mean. [00:18] I want to start with a story. A few years ago, I worked with a global retail brand that [00:25] was launching a new content platform. The project was technically flawless, the infrastructure [00:33] was modern, the integrations were seamless, and the vendor had all the right slides about [00:42] efficiency and scale. But six months after the launch, the team was still publishing [00:49] content the old way. The fancy new platform had basically become a slightly shinier version [00:59] of the one they left behind. So what went wrong? It wasn't the tool, it was the transition. [01:08] No one had managed the human side of the change, how people's roles would evolve, how their [01:16] habits and definitions of what success was going to be would change. They swapped a system [01:25] but not a mindset. That's the gap change management fills. [01:31] Change management is the discipline of helping people move from what was to what will be [01:39] in a way that sticks. It's the bridge between strategy and execution. Between a PowerPoint [01:47] vision and a real working future. And here's the simple truth. I've seen over [01:54] and over again. Organizations don't change because a tool is shiny. They change because [02:02] the status quo is no longer getting them the outcomes they need. Sometimes the industry [02:10] forces the issue. Our customers expect omnichannel personalization. And sometimes it's internal. [02:20] We can't keep burning out the same people to meet every deadline. Whatever the trigger, [02:27] the motive is always the same. The way we work today can't get us to where we're going tomorrow. [02:37] So what outcomes drive this kind of change? Think about goals like cutting time to publish [02:45] from weeks to days. Giving marketers freedom without creating risk. Scaling personalization [02:54] without doubling headcount. Building systems resilient enough to evolve and not to have [03:02] to rebuild every few years. Those aren't feature goals. They're human goals. [03:10] The reality is change management isn't about technology. It's about people. It's about [03:18] helping teams unlearn comfortable routines and replace them with better ones. And that's [03:25] messy. It's emotional. And it's deeply human work. [03:31] When you think about it, every successful transformation shares three ingredients. [03:37] First, a clear outcome. We're not just adopting tools. We're solving a problem. [03:44] Next, a shared story. Everyone knows why we're doing this and what success looks like. [03:53] And third, a guided path. A plan that supports people through the confusion and the uncertainty [04:01] that change naturally brings. That's what we're going to explore in this course. [04:08] We'll talk about the psychology of change, why people resist it, and how to bring them [04:15] along for the ride. We'll look at practical steps to prepare your organization before [04:23] the rollout begins. We'll walk through ways to build champions, manage resistance, and [04:31] keep the momentum long after launch day. [04:35] In other words, we're going to connect the vision of the transformation to the practice [04:42] of making it real. Because change isn't a one-time event. It's a skill set. ``` #### Key takeaways - Connect **What is Change Management?** 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. ### Lesson 02 — Why We Change #### Video details #### At a glance - **Title:** Why We Change - **Duration:** 4m 52s - **Media link:** https://cdn.jwplayer.com/previews/GJUxXiDo - **Publish date (unix):** 1769113167 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113614 kbps - video/mp4 · 180p · 180p · 190434 kbps - video/mp4 · 270p · 270p · 239248 kbps - video/mp4 · 360p · 360p · 274333 kbps - video/mp4 · 406p · 406p · 304489 kbps - video/mp4 · 540p · 540p · 402388 kbps - video/mp4 · 720p · 720p · 563115 kbps - video/mp4 · 1080p · 1080p · 1154379 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/GJUxXiDo-120.vtt` #### Transcript Every change starts with tension. Something isn't working anymore, even if it used to. Let's go back to that retail example from the previous clip. Six months after their new content platform went live, leadership was frustrated. We invested in modern technology, they said, so why isn't anyone faster? When we dug deeper, the answer was simple. The system wasn't the bottleneck, the process was. Content still had to flow through five approval layers, each owned by a different team. So the fancy new stack didn't fix the old inefficiencies, it just inherited them. That's the moment when real change begins. When you stop blaming tools and start re-examining the system. Change happens when the current reality becomes unacceptable. Sometimes that realization comes from the top, a CEO sets a bold new direction. Sometimes it comes from the ground, a designer, a developer, or a marketer who's tired of fighting the same friction week after week. But in every case, the spark of change is the same. A gap between the outcomes we want and the results we're getting. I call this gap the change trigger. Here are a few you see all the time. A company that's growing faster than its processes can handle. Or a legacy system that becomes a liability. And a brand trying to move from local to global operations. Or a team that's losing top talent because the way they work feels like quicksand. Each of those scenarios starts the same internal conversation. If we keep doing what we're doing, what happens next? And that's where your story begins. Because change doesn't sell itself, people need a narrative to follow. I like to craft that narrative using a simple framework. I call it the outcome line. It goes like this. We're changing because the current reality is blocking a desired outcome and doing nothing will cost us whatever the cost of the delay is. It's short, it's clear, and it gives people something to rally behind. Let me give you an example. Imagine a financial services company. We're launching a new product takes 8 weeks. By the time the campaign goes live, competitors have already moved on. Their outcome line might sound like this. We're changing because our 8-week launch cycle is blocking our ability to respond to market trends. If we don't fix it, we'll continue to lose market share to our competitors. Or a healthcare organization where compliance reviews are manual and error-prone. Their version might be, we're changing because our manual review process creates risk. We need a system that keeps us compliant without slowing us down. See how both examples name the pain and then connect it directly to the outcome. That's the story people buy into. Not the platform, not the buzzwords, the outcome. Because here's the thing. People don't get excited about change for its own sake. They get excited about progress. They want to know how this will make their work better, their team stronger, or their customers happier. That's the emotional core of change management. Aligning people around a share reason to move. If we skip that story and go straight to, here's the new tool, we lose half the room before we even start. So, before you launch your next initiative, pause and ask, what's the current reality that's no longer acceptable? What's the outcome we're chasing? What's the cost if we stay the same? Once you can tell that story clearly, the rest of the plan starts to make sense. And that's where we're headed next. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:07.540 Every change starts with tension. 2 00:00:07.540 --> 00:00:11.920 Something isn't working anymore, even if it used to. 3 00:00:11.920 --> 00:00:16.840 Let's go back to that retail example from the previous clip. 4 00:00:16.840 --> 00:00:22.600 Six months after their new content platform went live, leadership was frustrated. 5 00:00:22.600 --> 00:00:29.900 We invested in modern technology, they said, so why isn't anyone faster? 6 00:00:29.900 --> 00:00:33.640 When we dug deeper, the answer was simple. 7 00:00:33.640 --> 00:00:39.100 The system wasn't the bottleneck, the process was. 8 00:00:39.100 --> 00:00:45.900 Content still had to flow through five approval layers, each owned by a different team. 9 00:00:45.900 --> 00:00:52.540 So the fancy new stack didn't fix the old inefficiencies, it just inherited them. 10 00:00:52.540 --> 00:00:57.180 That's the moment when real change begins. 11 00:00:57.180 --> 00:01:03.220 When you stop blaming tools and start re-examining the system. 12 00:01:03.220 --> 00:01:08.300 Change happens when the current reality becomes unacceptable. 13 00:01:08.300 --> 00:01:15.460 Sometimes that realization comes from the top, a CEO sets a bold new direction. 14 00:01:15.460 --> 00:01:22.380 Sometimes it comes from the ground, a designer, a developer, or a marketer who's tired of 15 00:01:22.380 --> 00:01:27.860 fighting the same friction week after week. 16 00:01:27.860 --> 00:01:32.460 But in every case, the spark of change is the same. 17 00:01:32.460 --> 00:01:39.020 A gap between the outcomes we want and the results we're getting. 18 00:01:39.020 --> 00:01:42.700 I call this gap the change trigger. 19 00:01:42.700 --> 00:01:46.520 Here are a few you see all the time. 20 00:01:46.520 --> 00:01:50.900 A company that's growing faster than its processes can handle. 21 00:01:50.900 --> 00:01:55.700 Or a legacy system that becomes a liability. 22 00:01:55.700 --> 00:02:01.040 And a brand trying to move from local to global operations. 23 00:02:01.040 --> 00:02:07.920 Or a team that's losing top talent because the way they work feels like quicksand. 24 00:02:07.920 --> 00:02:13.000 Each of those scenarios starts the same internal conversation. 25 00:02:13.000 --> 00:02:17.960 If we keep doing what we're doing, what happens next? 26 00:02:17.960 --> 00:02:21.680 And that's where your story begins. 27 00:02:21.680 --> 00:02:27.280 Because change doesn't sell itself, people need a narrative to follow. 28 00:02:27.280 --> 00:02:30.480 I like to craft that narrative using a simple framework. 29 00:02:30.480 --> 00:02:33.320 I call it the outcome line. 30 00:02:33.320 --> 00:02:34.800 It goes like this. 31 00:02:34.800 --> 00:02:42.440 We're changing because the current reality is blocking a desired outcome and doing nothing 32 00:02:42.520 --> 00:02:46.600 will cost us whatever the cost of the delay is. 33 00:02:46.600 --> 00:02:51.960 It's short, it's clear, and it gives people something to rally behind. 34 00:02:51.960 --> 00:02:53.600 Let me give you an example. 35 00:02:53.600 --> 00:02:56.400 Imagine a financial services company. 36 00:02:56.400 --> 00:02:59.560 We're launching a new product takes 8 weeks. 37 00:02:59.560 --> 00:03:04.800 By the time the campaign goes live, competitors have already moved on. 38 00:03:04.800 --> 00:03:08.040 Their outcome line might sound like this. 39 00:03:08.040 --> 00:03:13.640 We're changing because our 8-week launch cycle is blocking our ability to respond to 40 00:03:13.640 --> 00:03:15.320 market trends. 41 00:03:15.320 --> 00:03:20.960 If we don't fix it, we'll continue to lose market share to our competitors. 42 00:03:20.960 --> 00:03:28.000 Or a healthcare organization where compliance reviews are manual and error-prone. 43 00:03:28.000 --> 00:03:34.440 Their version might be, we're changing because our manual review process creates risk. 44 00:03:34.440 --> 00:03:40.000 We need a system that keeps us compliant without slowing us down. 45 00:03:40.000 --> 00:03:48.040 See how both examples name the pain and then connect it directly to the outcome. 46 00:03:48.040 --> 00:03:50.840 That's the story people buy into. 47 00:03:50.840 --> 00:03:55.720 Not the platform, not the buzzwords, the outcome. 48 00:03:55.720 --> 00:03:57.320 Because here's the thing. 49 00:03:57.320 --> 00:04:01.240 People don't get excited about change for its own sake. 50 00:04:01.240 --> 00:04:03.880 They get excited about progress. 51 00:04:03.880 --> 00:04:09.040 They want to know how this will make their work better, their team stronger, or their 52 00:04:09.040 --> 00:04:10.840 customers happier. 53 00:04:10.840 --> 00:04:15.240 That's the emotional core of change management. 54 00:04:15.240 --> 00:04:19.360 Aligning people around a share reason to move. 55 00:04:19.360 --> 00:04:25.080 If we skip that story and go straight to, here's the new tool, we lose half the room 56 00:04:25.080 --> 00:04:27.120 before we even start. 57 00:04:27.120 --> 00:04:33.760 So, before you launch your next initiative, pause and ask, what's the current reality 58 00:04:33.760 --> 00:04:36.840 that's no longer acceptable? 59 00:04:36.840 --> 00:04:39.600 What's the outcome we're chasing? 60 00:04:39.600 --> 00:04:43.200 What's the cost if we stay the same? 61 00:04:43.200 --> 00:04:48.680 Once you can tell that story clearly, the rest of the plan starts to make sense. 62 00:04:48.680 --> 00:04:51.000 And that's where we're headed next. ``` ```transcript [00:00] Every change starts with tension. [00:07] Something isn't working anymore, even if it used to. [00:11] Let's go back to that retail example from the previous clip. [00:16] Six months after their new content platform went live, leadership was frustrated. [00:22] We invested in modern technology, they said, so why isn't anyone faster? [00:29] When we dug deeper, the answer was simple. [00:33] The system wasn't the bottleneck, the process was. [00:39] Content still had to flow through five approval layers, each owned by a different team. [00:45] So the fancy new stack didn't fix the old inefficiencies, it just inherited them. [00:52] That's the moment when real change begins. [00:57] When you stop blaming tools and start re-examining the system. [01:03] Change happens when the current reality becomes unacceptable. [01:08] Sometimes that realization comes from the top, a CEO sets a bold new direction. [01:15] Sometimes it comes from the ground, a designer, a developer, or a marketer who's tired of [01:22] fighting the same friction week after week. [01:27] But in every case, the spark of change is the same. [01:32] A gap between the outcomes we want and the results we're getting. [01:39] I call this gap the change trigger. [01:42] Here are a few you see all the time. [01:46] A company that's growing faster than its processes can handle. [01:50] Or a legacy system that becomes a liability. [01:55] And a brand trying to move from local to global operations. [02:01] Or a team that's losing top talent because the way they work feels like quicksand. [02:07] Each of those scenarios starts the same internal conversation. [02:13] If we keep doing what we're doing, what happens next? [02:17] And that's where your story begins. [02:21] Because change doesn't sell itself, people need a narrative to follow. [02:27] I like to craft that narrative using a simple framework. [02:30] I call it the outcome line. [02:33] It goes like this. [02:34] We're changing because the current reality is blocking a desired outcome and doing nothing [02:42] will cost us whatever the cost of the delay is. [02:46] It's short, it's clear, and it gives people something to rally behind. [02:51] Let me give you an example. [02:53] Imagine a financial services company. [02:56] We're launching a new product takes 8 weeks. [02:59] By the time the campaign goes live, competitors have already moved on. [03:04] Their outcome line might sound like this. [03:08] We're changing because our 8-week launch cycle is blocking our ability to respond to [03:13] market trends. [03:15] If we don't fix it, we'll continue to lose market share to our competitors. [03:20] Or a healthcare organization where compliance reviews are manual and error-prone. [03:28] Their version might be, we're changing because our manual review process creates risk. [03:34] We need a system that keeps us compliant without slowing us down. [03:40] See how both examples name the pain and then connect it directly to the outcome. [03:48] That's the story people buy into. [03:50] Not the platform, not the buzzwords, the outcome. [03:55] Because here's the thing. [03:57] People don't get excited about change for its own sake. [04:01] They get excited about progress. [04:03] They want to know how this will make their work better, their team stronger, or their [04:09] customers happier. [04:10] That's the emotional core of change management. [04:15] Aligning people around a share reason to move. [04:19] If we skip that story and go straight to, here's the new tool, we lose half the room [04:25] before we even start. [04:27] So, before you launch your next initiative, pause and ask, what's the current reality [04:33] that's no longer acceptable? [04:36] What's the outcome we're chasing? [04:39] What's the cost if we stay the same? ``` #### Key takeaways - Connect **Why We Change** 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. ### Lesson 03 — The Human Layer of Change #### Video details #### At a glance - **Title:** The Human Layer Of Change - **Duration:** 6m 27s - **Media link:** https://cdn.jwplayer.com/previews/ELZtElv9 - **Publish date (unix):** 1769201653 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113575 kbps - video/mp4 · 180p · 180p · 184638 kbps - video/mp4 · 270p · 270p · 232324 kbps - video/mp4 · 360p · 360p · 264924 kbps - video/mp4 · 406p · 406p · 293327 kbps - video/mp4 · 540p · 540p · 388326 kbps - video/mp4 · 720p · 720p · 546232 kbps - video/mp4 · 1080p · 1080p · 1138310 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/ELZtElv9-120.vtt` #### Transcript We've talked about why organizations change, but let's be honest. The hard part isn't deciding to change, it's getting people to come with you. Every organization says, our people are our greatest asset. But when change hits, that same strength can feel like resistance. I saw this firsthand a few years ago with a global publishing company. They were moving from traditional print workflows to a fully digital content platform. The technology worked great, the issue was emotional. Editors who had spent 20 years perfecting a craft suddenly felt like their expertise didn't translate. They weren't rejecting the platform, they were protecting their identity. That's the human layer of change, the part no software can automate. Whenever I work with teens, I look for three ingredients that make or break the human transition. Think of them as the anchors of change, which are mindset, empowerment, and support. Culture isn't a slogan, it's the invisible operating system of a company. The shared assumptions about how work gets done. Changing culture means inviting people to challenge those assumptions. It's the shift from that's how we've always done it to let's figure out a better way. And it starts at the top because leaders model the behaviors the rest of the organization will follow. And here's the part we don't talk about enough. If people don't feel safe raising their hand, asking questions, or challenging outdated processes, if the culture values output over outcomes, then transformation doesn't just struggle, it fails. Not might, not could, will. Because meaningful change requires curiosity, transparency, and the psychological safety to speak up before small cracks become big problems. Without that, every initiative collapses under the weight of unspoken concerns. At that publishing company, the breakthrough came when a senior editor volunteered to pilot the new process, publicly. She made her learning visible, the stumbles, the wins, the time saved. Suddenly, the rest of the team didn't see the change as a threat, they saw it as proof that their skills could evolve. Culture doesn't change by decree, it changes when people see someone they respect taking the first step. That moment wasn't just about adoption, it was leadership in action. Because good leaders do two things during change, they provide clarity and they reinforce culture. Clarity means helping people see what's changing and why, and making sure they have what they need to move forward. Culture means modeling calm in the face of chaos, showing that uncertainty isn't a danger, it's discovery. Change without ownership is chaos. Someone has to own the outcome, not in theory, but by name. And when I say empowered, I don't mean assigned. Empowerment means giving someone the authority, the time, and the trust to drive progress, and holding them accountable for specific, measurable outcomes that everyone agreed to up front. Not vague promises, not we'll know when we see it, but clear, observable results that define what success actually looks like. So accountability isn't emotional or subjective, it's rooted in shared expectations. In one organization I worked with, the content team had been stuck for months waiting on decisions from a committee that met once a quarter. We fixed it by naming a single change owner. She could make decisions on 80% of the things autonomously, and escalate only the 20% that truly needed leadership review. Within weeks, velocity doubled, not because people worked harder, but because decision friction disappeared. That's empowerment in action, clarity, and trust. Here's where most transformations fail. We train people on what to do, but not how to be successful doing it. Real enablement means giving teams the tools, time, and confidence to operate in the new world. Think job aids, office hours, templates, short videos like these, anything that lowers the learning curve. At another company, we created a day one success plan. Every new workflow had a 15-minute walkthrough and a simple checklist that led to a visible win on the first try. That early success became contagious. Support builds confidence and confidence builds adoption. When these three anchors, mindset, empowerment, and support are aligned, change feels less like a corporate initiative and more like a shared adventure. People move from compliance to commitment. But when even one is missing, change becomes something that's happening to people, not with them. That's when progress slows, trust erodes, and the old ways quietly sneak back in. So before we start mapping the tactical plan, the meetings, the milestones, the tools, we have to make sure these human anchors are in place. Because the truth is, if we can't win hearts, we'll never sustain habits. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:09.740 We've talked about why organizations change, but let's be honest. 2 00:00:09.740 --> 00:00:16.160 The hard part isn't deciding to change, it's getting people to come with you. 3 00:00:16.160 --> 00:00:21.500 Every organization says, our people are our greatest asset. 4 00:00:21.500 --> 00:00:26.700 But when change hits, that same strength can feel like resistance. 5 00:00:26.700 --> 00:00:31.720 I saw this firsthand a few years ago with a global publishing company. 6 00:00:31.720 --> 00:00:37.640 They were moving from traditional print workflows to a fully digital content platform. 7 00:00:37.640 --> 00:00:43.040 The technology worked great, the issue was emotional. 8 00:00:43.040 --> 00:00:49.080 Editors who had spent 20 years perfecting a craft suddenly felt like their expertise 9 00:00:49.080 --> 00:00:51.020 didn't translate. 10 00:00:51.020 --> 00:00:56.340 They weren't rejecting the platform, they were protecting their identity. 11 00:00:56.340 --> 00:01:03.740 That's the human layer of change, the part no software can automate. 12 00:01:03.740 --> 00:01:10.980 Whenever I work with teens, I look for three ingredients that make or break the human transition. 13 00:01:10.980 --> 00:01:19.060 Think of them as the anchors of change, which are mindset, empowerment, and support. 14 00:01:19.060 --> 00:01:24.340 Culture isn't a slogan, it's the invisible operating system of a company. 15 00:01:24.340 --> 00:01:29.000 The shared assumptions about how work gets done. 16 00:01:29.000 --> 00:01:34.340 Changing culture means inviting people to challenge those assumptions. 17 00:01:34.340 --> 00:01:39.780 It's the shift from that's how we've always done it to let's figure out a better 18 00:01:39.780 --> 00:01:40.780 way. 19 00:01:40.780 --> 00:01:47.060 And it starts at the top because leaders model the behaviors the rest of the organization 20 00:01:47.060 --> 00:01:48.520 will follow. 21 00:01:48.520 --> 00:01:51.960 And here's the part we don't talk about enough. 22 00:01:51.960 --> 00:01:58.400 If people don't feel safe raising their hand, asking questions, or challenging outdated 23 00:01:58.400 --> 00:02:05.600 processes, if the culture values output over outcomes, then transformation doesn't just 24 00:02:05.600 --> 00:02:08.120 struggle, it fails. 25 00:02:08.120 --> 00:02:12.120 Not might, not could, will. 26 00:02:12.120 --> 00:02:19.180 Because meaningful change requires curiosity, transparency, and the psychological safety 27 00:02:19.180 --> 00:02:24.280 to speak up before small cracks become big problems. 28 00:02:24.280 --> 00:02:30.500 Without that, every initiative collapses under the weight of unspoken concerns. 29 00:02:30.500 --> 00:02:35.700 At that publishing company, the breakthrough came when a senior editor volunteered to pilot 30 00:02:35.700 --> 00:02:38.500 the new process, publicly. 31 00:02:38.500 --> 00:02:43.700 She made her learning visible, the stumbles, the wins, the time saved. 32 00:02:43.700 --> 00:02:49.660 Suddenly, the rest of the team didn't see the change as a threat, they saw it as proof 33 00:02:49.660 --> 00:02:52.500 that their skills could evolve. 34 00:02:52.500 --> 00:02:58.320 Culture doesn't change by decree, it changes when people see someone they respect taking 35 00:02:58.320 --> 00:03:00.220 the first step. 36 00:03:00.220 --> 00:03:05.480 That moment wasn't just about adoption, it was leadership in action. 37 00:03:05.480 --> 00:03:12.120 Because good leaders do two things during change, they provide clarity and they reinforce 38 00:03:12.120 --> 00:03:14.320 culture. 39 00:03:14.320 --> 00:03:20.380 Clarity means helping people see what's changing and why, and making sure they have 40 00:03:20.380 --> 00:03:23.620 what they need to move forward. 41 00:03:23.620 --> 00:03:29.400 Culture means modeling calm in the face of chaos, showing that uncertainty isn't a 42 00:03:29.400 --> 00:03:32.240 danger, it's discovery. 43 00:03:32.240 --> 00:03:35.080 Change without ownership is chaos. 44 00:03:35.080 --> 00:03:40.080 Someone has to own the outcome, not in theory, but by name. 45 00:03:40.080 --> 00:03:44.920 And when I say empowered, I don't mean assigned. 46 00:03:44.920 --> 00:03:50.960 Empowerment means giving someone the authority, the time, and the trust to drive progress, 47 00:03:50.960 --> 00:03:56.840 and holding them accountable for specific, measurable outcomes that everyone agreed to 48 00:03:57.240 --> 00:03:58.240 up front. 49 00:03:58.240 --> 00:04:04.600 Not vague promises, not we'll know when we see it, but clear, observable results that 50 00:04:04.600 --> 00:04:08.140 define what success actually looks like. 51 00:04:08.140 --> 00:04:15.720 So accountability isn't emotional or subjective, it's rooted in shared expectations. 52 00:04:15.720 --> 00:04:21.080 In one organization I worked with, the content team had been stuck for months waiting on 53 00:04:21.080 --> 00:04:25.200 decisions from a committee that met once a quarter. 54 00:04:25.200 --> 00:04:28.880 We fixed it by naming a single change owner. 55 00:04:28.880 --> 00:04:35.920 She could make decisions on 80% of the things autonomously, and escalate only the 20% that 56 00:04:35.920 --> 00:04:38.760 truly needed leadership review. 57 00:04:38.760 --> 00:04:43.680 Within weeks, velocity doubled, not because people worked harder, but because decision 58 00:04:43.680 --> 00:04:45.600 friction disappeared. 59 00:04:45.600 --> 00:04:50.880 That's empowerment in action, clarity, and trust. 60 00:04:50.880 --> 00:04:54.200 Here's where most transformations fail. 61 00:04:54.200 --> 00:05:00.800 We train people on what to do, but not how to be successful doing it. 62 00:05:00.800 --> 00:05:07.680 Real enablement means giving teams the tools, time, and confidence to operate in the new 63 00:05:07.680 --> 00:05:08.680 world. 64 00:05:08.680 --> 00:05:15.760 Think job aids, office hours, templates, short videos like these, anything that lowers the 65 00:05:15.760 --> 00:05:18.080 learning curve. 66 00:05:18.080 --> 00:05:22.240 At another company, we created a day one success plan. 67 00:05:22.280 --> 00:05:28.480 Every new workflow had a 15-minute walkthrough and a simple checklist that led to a visible 68 00:05:28.480 --> 00:05:31.080 win on the first try. 69 00:05:31.080 --> 00:05:34.440 That early success became contagious. 70 00:05:34.440 --> 00:05:39.000 Support builds confidence and confidence builds adoption. 71 00:05:39.000 --> 00:05:44.960 When these three anchors, mindset, empowerment, and support are aligned, change feels less 72 00:05:44.960 --> 00:05:49.920 like a corporate initiative and more like a shared adventure. 73 00:05:49.920 --> 00:05:53.260 People move from compliance to commitment. 74 00:05:53.260 --> 00:06:00.000 But when even one is missing, change becomes something that's happening to people, not 75 00:06:00.000 --> 00:06:01.000 with them. 76 00:06:01.000 --> 00:06:08.400 That's when progress slows, trust erodes, and the old ways quietly sneak back in. 77 00:06:08.400 --> 00:06:14.880 So before we start mapping the tactical plan, the meetings, the milestones, the tools, we 78 00:06:14.880 --> 00:06:19.680 have to make sure these human anchors are in place. 79 00:06:19.680 --> 00:06:25.840 Because the truth is, if we can't win hearts, we'll never sustain habits. ``` ```transcript [00:00] We've talked about why organizations change, but let's be honest. [00:09] The hard part isn't deciding to change, it's getting people to come with you. [00:16] Every organization says, our people are our greatest asset. [00:21] But when change hits, that same strength can feel like resistance. [00:26] I saw this firsthand a few years ago with a global publishing company. [00:31] They were moving from traditional print workflows to a fully digital content platform. [00:37] The technology worked great, the issue was emotional. [00:43] Editors who had spent 20 years perfecting a craft suddenly felt like their expertise [00:49] didn't translate. [00:51] They weren't rejecting the platform, they were protecting their identity. [00:56] That's the human layer of change, the part no software can automate. [01:03] Whenever I work with teens, I look for three ingredients that make or break the human transition. [01:10] Think of them as the anchors of change, which are mindset, empowerment, and support. [01:19] Culture isn't a slogan, it's the invisible operating system of a company. [01:24] The shared assumptions about how work gets done. [01:29] Changing culture means inviting people to challenge those assumptions. [01:34] It's the shift from that's how we've always done it to let's figure out a better [01:39] way. [01:40] And it starts at the top because leaders model the behaviors the rest of the organization [01:47] will follow. [01:48] And here's the part we don't talk about enough. [01:51] If people don't feel safe raising their hand, asking questions, or challenging outdated [01:58] processes, if the culture values output over outcomes, then transformation doesn't just [02:05] struggle, it fails. [02:08] Not might, not could, will. [02:12] Because meaningful change requires curiosity, transparency, and the psychological safety [02:19] to speak up before small cracks become big problems. [02:24] Without that, every initiative collapses under the weight of unspoken concerns. [02:30] At that publishing company, the breakthrough came when a senior editor volunteered to pilot [02:35] the new process, publicly. [02:38] She made her learning visible, the stumbles, the wins, the time saved. [02:43] Suddenly, the rest of the team didn't see the change as a threat, they saw it as proof [02:49] that their skills could evolve. [02:52] Culture doesn't change by decree, it changes when people see someone they respect taking [02:58] the first step. [03:00] That moment wasn't just about adoption, it was leadership in action. [03:05] Because good leaders do two things during change, they provide clarity and they reinforce [03:12] culture. [03:14] Clarity means helping people see what's changing and why, and making sure they have [03:20] what they need to move forward. [03:23] Culture means modeling calm in the face of chaos, showing that uncertainty isn't a [03:29] danger, it's discovery. [03:32] Change without ownership is chaos. [03:35] Someone has to own the outcome, not in theory, but by name. [03:40] And when I say empowered, I don't mean assigned. [03:44] Empowerment means giving someone the authority, the time, and the trust to drive progress, [03:50] and holding them accountable for specific, measurable outcomes that everyone agreed to [03:57] up front. [03:58] Not vague promises, not we'll know when we see it, but clear, observable results that [04:04] define what success actually looks like. [04:08] So accountability isn't emotional or subjective, it's rooted in shared expectations. [04:15] In one organization I worked with, the content team had been stuck for months waiting on [04:21] decisions from a committee that met once a quarter. [04:25] We fixed it by naming a single change owner. [04:28] She could make decisions on 80% of the things autonomously, and escalate only the 20% that [04:35] truly needed leadership review. [04:38] Within weeks, velocity doubled, not because people worked harder, but because decision [04:43] friction disappeared. [04:45] That's empowerment in action, clarity, and trust. [04:50] Here's where most transformations fail. ``` #### Key takeaways - Connect **The Human Layer of Change** 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. ### Lesson 04 — The Preflight #### 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. ### Lesson 05 — Launching Change and Building Momentum #### Video details #### At a glance - **Title:** Launching Change And Building Momentum - **Duration:** 5m 26s - **Media link:** https://cdn.jwplayer.com/previews/ODcKIqmO - **Publish date (unix):** 1769546862 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113499 kbps - video/mp4 · 180p · 180p · 193739 kbps - video/mp4 · 270p · 270p · 244733 kbps - video/mp4 · 360p · 360p · 281158 kbps - video/mp4 · 406p · 406p · 312209 kbps - video/mp4 · 540p · 540p · 413672 kbps - video/mp4 · 720p · 720p · 582335 kbps - video/mp4 · 1080p · 1080p · 1191514 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/ODcKIqmO-120.vtt` #### Transcript Once you're ready to go, the hardest part isn't getting people to understand the change, it's getting them to believe in it. Every major transformation needs a spark, something that turns planning into movement. And here's what I've learned. Logic starts the conversation, but emotion sustains it. When change begins, people aren't asking, is this efficient? They're asking, is this worth it? Because change always comes with effort, discomfort, and a little bit of fear. So the question becomes, how do we light that match without burning people out? Again, let's start with a story. A few years ago, a marketing team was re-platforming their entire digital ecosystem. They were smart, experienced, and exhausted. The previous three initiatives had started strong, fizzled, and quietly disappeared. Each one leaving a little less enthusiasm for the next. So before they touched a single workflow, they decided to build what I call change readiness energy. They did something symbolic, small, but visible. Every person wrote down what frustrated them about the old system on a sticky note. They filled the wall with thousands of little complaints. They then took them outside, read a few out loud, and burned them, literally. It wasn't about the fire. It was about the release. It said, we're done with what's not working, and we're moving forward together. That moment changed everything. It wasn't a meeting. It was a signal. And it created the two things every change leader needs, belief and momentum. Now, lighting the match doesn't have to be theatrical, but it does have to be intentional. Here are three principles you can use to launch any major change. 1. Burn the ships, but with empathy. There's a famous story about Hernan Cortez arriving in Mexico and burning his fleet so his men had no way back. That kind of commitment works, but let's modernize it. In organizations, burning the ships means removing the easy path to the old way of doing things, not by force, but by clarity. If you keep both systems running indefinitely, you'll split focus and stall adoption. So make a decision. When does the new way become the way? Mark that date. Communicate it early. But also make sure people have the training, support, and confidence to get there. Commitment without preparation is cruel. 2. Find and fuel your champions. Every transformation has early adopters, the ones already saying, this makes sense, let's go. They're your most valuable asset. At Airbnb, one of their internal mottos for change was, don't scale process, scale belief. They identified champions in each region, gave them early access, let them shape the rollout, and then turned them into internal storytellers. Champions make change contagious. They don't just follow the plan, they embody it. So instead of trying to convince the skeptics first, empower the believers and let their success do the convincing. 3. Reframe the narrative. When people resist, it's rarely about the change itself. It's about loss, loss of control, loss of identity, loss of competence. So shift the story from we're changing the system to we're evolving how we work. Change is language that centers progress. We're building faster, smarter versions of ourselves. This isn't about replacing what works, it's about expanding what's possible. The goal is to make people feel invited into the future, not dragged into it. When you combine these three, commitment, champions, and reframing, change starts to feel less like a mandate and more like a movement. And movements create momentum. Momentum is what gets you through the first wave of resistance. It turns why are we doing this into how can I help make it better. That's the shift every successful transformation reaches, when people start to see themselves in the story. So before you launch, ask yourself, what's our spark, who's our champion, and how will we make this story feel personal? Get those right, and the match you strike won't just ignite the project, it'll light the path forward. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:09.800 Once you're ready to go, the hardest part isn't getting people to understand the change, 2 00:00:09.800 --> 00:00:13.000 it's getting them to believe in it. 3 00:00:13.000 --> 00:00:19.680 Every major transformation needs a spark, something that turns planning into movement. 4 00:00:19.680 --> 00:00:22.120 And here's what I've learned. 5 00:00:22.120 --> 00:00:27.000 Logic starts the conversation, but emotion sustains it. 6 00:00:27.000 --> 00:00:31.560 When change begins, people aren't asking, is this efficient? 7 00:00:31.560 --> 00:00:34.600 They're asking, is this worth it? 8 00:00:34.600 --> 00:00:40.200 Because change always comes with effort, discomfort, and a little bit of fear. 9 00:00:40.200 --> 00:00:47.680 So the question becomes, how do we light that match without burning people out? 10 00:00:47.680 --> 00:00:50.400 Again, let's start with a story. 11 00:00:50.400 --> 00:00:58.200 A few years ago, a marketing team was re-platforming their entire digital ecosystem. 12 00:00:58.200 --> 00:01:02.860 They were smart, experienced, and exhausted. 13 00:01:02.860 --> 00:01:08.720 The previous three initiatives had started strong, fizzled, and quietly disappeared. 14 00:01:08.720 --> 00:01:12.880 Each one leaving a little less enthusiasm for the next. 15 00:01:12.880 --> 00:01:20.080 So before they touched a single workflow, they decided to build what I call change readiness 16 00:01:20.080 --> 00:01:21.520 energy. 17 00:01:21.520 --> 00:01:25.920 They did something symbolic, small, but visible. 18 00:01:25.920 --> 00:01:31.560 Every person wrote down what frustrated them about the old system on a sticky note. 19 00:01:31.560 --> 00:01:35.200 They filled the wall with thousands of little complaints. 20 00:01:35.200 --> 00:01:41.440 They then took them outside, read a few out loud, and burned them, literally. 21 00:01:41.440 --> 00:01:43.520 It wasn't about the fire. 22 00:01:43.520 --> 00:01:45.440 It was about the release. 23 00:01:45.440 --> 00:01:52.360 It said, we're done with what's not working, and we're moving forward together. 24 00:01:52.360 --> 00:01:54.760 That moment changed everything. 25 00:01:54.760 --> 00:01:56.320 It wasn't a meeting. 26 00:01:56.320 --> 00:01:57.800 It was a signal. 27 00:01:57.800 --> 00:02:04.760 And it created the two things every change leader needs, belief and momentum. 28 00:02:04.880 --> 00:02:12.120 Now, lighting the match doesn't have to be theatrical, but it does have to be intentional. 29 00:02:12.120 --> 00:02:17.480 Here are three principles you can use to launch any major change. 30 00:02:17.480 --> 00:02:18.640 1. 31 00:02:18.640 --> 00:02:21.360 Burn the ships, but with empathy. 32 00:02:21.360 --> 00:02:28.440 There's a famous story about Hernan Cortez arriving in Mexico and burning his fleet so 33 00:02:28.440 --> 00:02:31.160 his men had no way back. 34 00:02:31.160 --> 00:02:35.560 That kind of commitment works, but let's modernize it. 35 00:02:35.560 --> 00:02:42.040 In organizations, burning the ships means removing the easy path to the old way of doing 36 00:02:42.040 --> 00:02:45.900 things, not by force, but by clarity. 37 00:02:45.900 --> 00:02:52.080 If you keep both systems running indefinitely, you'll split focus and stall adoption. 38 00:02:52.080 --> 00:02:54.040 So make a decision. 39 00:02:54.040 --> 00:02:57.920 When does the new way become the way? 40 00:02:57.920 --> 00:02:59.960 Mark that date. 41 00:02:59.960 --> 00:03:01.200 Communicate it early. 42 00:03:01.200 --> 00:03:07.440 But also make sure people have the training, support, and confidence to get there. 43 00:03:07.440 --> 00:03:10.960 Commitment without preparation is cruel. 44 00:03:10.960 --> 00:03:12.160 2. 45 00:03:12.160 --> 00:03:15.060 Find and fuel your champions. 46 00:03:15.060 --> 00:03:21.280 Every transformation has early adopters, the ones already saying, this makes sense, let's 47 00:03:21.280 --> 00:03:22.280 go. 48 00:03:22.280 --> 00:03:24.500 They're your most valuable asset. 49 00:03:24.500 --> 00:03:32.340 At Airbnb, one of their internal mottos for change was, don't scale process, scale belief. 50 00:03:32.340 --> 00:03:38.500 They identified champions in each region, gave them early access, let them shape the 51 00:03:38.500 --> 00:03:44.260 rollout, and then turned them into internal storytellers. 52 00:03:44.260 --> 00:03:46.380 Champions make change contagious. 53 00:03:46.380 --> 00:03:49.860 They don't just follow the plan, they embody it. 54 00:03:49.860 --> 00:03:55.640 So instead of trying to convince the skeptics first, empower the believers and let their 55 00:03:55.640 --> 00:03:58.620 success do the convincing. 56 00:03:58.620 --> 00:04:00.180 3. 57 00:04:00.180 --> 00:04:02.080 Reframe the narrative. 58 00:04:02.080 --> 00:04:05.640 When people resist, it's rarely about the change itself. 59 00:04:05.640 --> 00:04:11.620 It's about loss, loss of control, loss of identity, loss of competence. 60 00:04:11.620 --> 00:04:18.340 So shift the story from we're changing the system to we're evolving how we work. 61 00:04:18.340 --> 00:04:21.220 Change is language that centers progress. 62 00:04:21.220 --> 00:04:25.040 We're building faster, smarter versions of ourselves. 63 00:04:25.040 --> 00:04:30.720 This isn't about replacing what works, it's about expanding what's possible. 64 00:04:30.720 --> 00:04:36.680 The goal is to make people feel invited into the future, not dragged into it. 65 00:04:36.680 --> 00:04:42.500 When you combine these three, commitment, champions, and reframing, change starts to 66 00:04:42.500 --> 00:04:46.620 feel less like a mandate and more like a movement. 67 00:04:46.620 --> 00:04:50.220 And movements create momentum. 68 00:04:50.220 --> 00:04:54.300 Momentum is what gets you through the first wave of resistance. 69 00:04:54.300 --> 00:04:59.860 It turns why are we doing this into how can I help make it better. 70 00:04:59.860 --> 00:05:05.760 That's the shift every successful transformation reaches, when people start to see themselves 71 00:05:05.760 --> 00:05:07.340 in the story. 72 00:05:07.340 --> 00:05:14.580 So before you launch, ask yourself, what's our spark, who's our champion, and how will 73 00:05:14.580 --> 00:05:18.260 we make this story feel personal? 74 00:05:18.260 --> 00:05:23.420 Get those right, and the match you strike won't just ignite the project, it'll light 75 00:05:23.420 --> 00:05:24.500 the path forward. ``` ```transcript [00:00] Once you're ready to go, the hardest part isn't getting people to understand the change, [00:09] it's getting them to believe in it. [00:13] Every major transformation needs a spark, something that turns planning into movement. [00:19] And here's what I've learned. [00:22] Logic starts the conversation, but emotion sustains it. [00:27] When change begins, people aren't asking, is this efficient? [00:31] They're asking, is this worth it? [00:34] Because change always comes with effort, discomfort, and a little bit of fear. [00:40] So the question becomes, how do we light that match without burning people out? [00:47] Again, let's start with a story. [00:50] A few years ago, a marketing team was re-platforming their entire digital ecosystem. [00:58] They were smart, experienced, and exhausted. [01:02] The previous three initiatives had started strong, fizzled, and quietly disappeared. [01:08] Each one leaving a little less enthusiasm for the next. [01:12] So before they touched a single workflow, they decided to build what I call change readiness [01:20] energy. [01:21] They did something symbolic, small, but visible. [01:25] Every person wrote down what frustrated them about the old system on a sticky note. [01:31] They filled the wall with thousands of little complaints. [01:35] They then took them outside, read a few out loud, and burned them, literally. [01:41] It wasn't about the fire. [01:43] It was about the release. [01:45] It said, we're done with what's not working, and we're moving forward together. [01:52] That moment changed everything. [01:54] It wasn't a meeting. [01:56] It was a signal. [01:57] And it created the two things every change leader needs, belief and momentum. [02:04] Now, lighting the match doesn't have to be theatrical, but it does have to be intentional. [02:12] Here are three principles you can use to launch any major change. [02:17] 1. [02:18] Burn the ships, but with empathy. [02:21] There's a famous story about Hernan Cortez arriving in Mexico and burning his fleet so [02:28] his men had no way back. [02:31] That kind of commitment works, but let's modernize it. [02:35] In organizations, burning the ships means removing the easy path to the old way of doing [02:42] things, not by force, but by clarity. [02:45] If you keep both systems running indefinitely, you'll split focus and stall adoption. [02:52] So make a decision. [02:54] When does the new way become the way? [02:57] Mark that date. [02:59] Communicate it early. [03:01] But also make sure people have the training, support, and confidence to get there. [03:07] Commitment without preparation is cruel. [03:10] 2. [03:12] Find and fuel your champions. [03:15] Every transformation has early adopters, the ones already saying, this makes sense, let's [03:21] go. [03:22] They're your most valuable asset. [03:24] At Airbnb, one of their internal mottos for change was, don't scale process, scale belief. [03:32] They identified champions in each region, gave them early access, let them shape the [03:38] rollout, and then turned them into internal storytellers. [03:44] Champions make change contagious. [03:46] They don't just follow the plan, they embody it. [03:49] So instead of trying to convince the skeptics first, empower the believers and let their [03:55] success do the convincing. [03:58] 3. [04:00] Reframe the narrative. [04:02] When people resist, it's rarely about the change itself. [04:05] It's about loss, loss of control, loss of identity, loss of competence. [04:11] So shift the story from we're changing the system to we're evolving how we work. ``` #### Key takeaways - Connect **Launching Change and Building Momentum** 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. ### Lesson 06 — Turning Momentum into Culture #### Video details #### At a glance - **Title:** Turning Momentum Into Culture - **Duration:** 4m 24s - **Media link:** https://cdn.jwplayer.com/previews/VCHUK8uy - **Publish date (unix):** 1769546923 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113548 kbps - video/mp4 · 180p · 180p · 189547 kbps - video/mp4 · 270p · 270p · 233773 kbps - video/mp4 · 360p · 360p · 270959 kbps - video/mp4 · 406p · 406p · 299811 kbps - video/mp4 · 540p · 540p · 393218 kbps - video/mp4 · 720p · 720p · 548838 kbps - video/mp4 · 1080p · 1080p · 1140821 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/VCHUK8uy-120.vtt` #### Transcript The launch is exciting, there's energy, applause, maybe even cake. But what happens the next morning? Every change effort faces a silent moment of truth. When the spotlight moves on, in real life comes back. The dashboards look good, the project team disbands, and suddenly people start to drift toward the comfortable, old way of doing things. Not because they want to fail, but because that's where the muscle memory lives. That's why sustaining change isn't about holding the line, it's about building new muscle memory, faster than the old one fades. I'll give you an example. A few years ago, there was a consumer brand that had just rolled out a new composable content system. Launch day was flawless, clean migration, excited teams, lots of internal buzz. But by month three, usage data told a different story. Only half the team was using the new workflow, the rest had quietly reverted to their old process in spreadsheets and shared drives. The company didn't have a technology problem, it had a sustainability problem. So they rebooted, not with another big initiative, but with small, intentional rhythms. They added weekly wins calls, where teams shared one success using the new system. Two-minute how-we-did-it videos featuring real employees. And a visible leaderboard celebrating people who found creative ways to improve the workflow. In 60 days, adoption shot up 40%, not because of pressure, but because success had become visible and contagious. That's the power of rhythm. Culture changes one small win at a time. When you think about sustaining change, there are three parts I always look for. First, rituals over reminders. While reminders don't change behavior, rituals do. Make the new way part of how people start their week, review their work, or celebrate results. If retrospectives or stand-ups highlight how teams use new tools to solve problems, the behavior reinforces itself naturally. Change isn't maintained through compliance, it's maintained through community. Second, celebrate learning, not just outcomes. In the early stages, mistakes are data. Reward the teams who experiment, who share what didn't work, who explore new features others were afraid to touch. At a tech company I partnered with, they gave a Fail Forward award every quarter. It recognized people who tried something new, learned from it, and shared the lesson. That one ritual made experimentation safe and it kept momentum alive long after the project ended. Third, close the loop and show the impact. Once people start seeing results, tell those stories. If campaign velocity doubled, show the before and after. If marketing can publish globally in a single click, celebrate that. People need evidence that their effort is paying off. It transforms compliance into pride. And pride is the point where culture shifts from, we have to, to, we get to. Here's the truth. Change doesn't become culture because you told people to keep doing it. It becomes culture when the new way feels normal. And that takes reinforcement, not in the form of more meetings, but in the stories we tell the habits we reward, and the systems we design. So if the earlier clips in the course were about planning, launching, and igniting, this one's about building staying power. Because momentum doesn't just carry you forward, it defines who you become next. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:09.840 The launch is exciting, there's energy, applause, maybe even cake. 2 00:00:09.840 --> 00:00:12.640 But what happens the next morning? 3 00:00:12.640 --> 00:00:16.360 Every change effort faces a silent moment of truth. 4 00:00:16.360 --> 00:00:20.560 When the spotlight moves on, in real life comes back. 5 00:00:20.560 --> 00:00:26.360 The dashboards look good, the project team disbands, and suddenly people start to drift 6 00:00:26.360 --> 00:00:30.160 toward the comfortable, old way of doing things. 7 00:00:30.160 --> 00:00:35.160 Not because they want to fail, but because that's where the muscle memory lives. 8 00:00:35.160 --> 00:00:40.020 That's why sustaining change isn't about holding the line, it's about building new 9 00:00:40.020 --> 00:00:44.040 muscle memory, faster than the old one fades. 10 00:00:44.040 --> 00:00:45.880 I'll give you an example. 11 00:00:45.880 --> 00:00:50.540 A few years ago, there was a consumer brand that had just rolled out a new composable 12 00:00:50.540 --> 00:00:52.400 content system. 13 00:00:52.400 --> 00:00:59.360 Launch day was flawless, clean migration, excited teams, lots of internal buzz. 14 00:00:59.360 --> 00:01:04.740 But by month three, usage data told a different story. 15 00:01:04.740 --> 00:01:10.580 Only half the team was using the new workflow, the rest had quietly reverted to their old 16 00:01:10.580 --> 00:01:14.700 process in spreadsheets and shared drives. 17 00:01:14.700 --> 00:01:20.900 The company didn't have a technology problem, it had a sustainability problem. 18 00:01:20.900 --> 00:01:27.520 So they rebooted, not with another big initiative, but with small, intentional rhythms. 19 00:01:27.520 --> 00:01:34.780 They added weekly wins calls, where teams shared one success using the new system. 20 00:01:34.780 --> 00:01:39.240 Two-minute how-we-did-it videos featuring real employees. 21 00:01:39.240 --> 00:01:46.800 And a visible leaderboard celebrating people who found creative ways to improve the workflow. 22 00:01:46.820 --> 00:01:53.540 In 60 days, adoption shot up 40%, not because of pressure, but because success had become 23 00:01:53.540 --> 00:01:56.580 visible and contagious. 24 00:01:56.580 --> 00:01:58.960 That's the power of rhythm. 25 00:01:58.960 --> 00:02:03.180 Culture changes one small win at a time. 26 00:02:03.180 --> 00:02:09.180 When you think about sustaining change, there are three parts I always look for. 27 00:02:09.180 --> 00:02:12.860 First, rituals over reminders. 28 00:02:12.920 --> 00:02:17.240 While reminders don't change behavior, rituals do. 29 00:02:17.240 --> 00:02:24.220 Make the new way part of how people start their week, review their work, or celebrate results. 30 00:02:24.220 --> 00:02:30.560 If retrospectives or stand-ups highlight how teams use new tools to solve problems, the 31 00:02:30.560 --> 00:02:34.240 behavior reinforces itself naturally. 32 00:02:34.240 --> 00:02:40.040 Change isn't maintained through compliance, it's maintained through community. 33 00:02:40.040 --> 00:02:43.480 Second, celebrate learning, not just outcomes. 34 00:02:43.480 --> 00:02:46.920 In the early stages, mistakes are data. 35 00:02:46.920 --> 00:02:52.140 Reward the teams who experiment, who share what didn't work, who explore new features 36 00:02:52.140 --> 00:02:54.540 others were afraid to touch. 37 00:02:54.540 --> 00:03:00.520 At a tech company I partnered with, they gave a Fail Forward award every quarter. 38 00:03:00.520 --> 00:03:05.920 It recognized people who tried something new, learned from it, and shared the lesson. 39 00:03:05.920 --> 00:03:12.960 That one ritual made experimentation safe and it kept momentum alive long after the 40 00:03:12.960 --> 00:03:14.560 project ended. 41 00:03:14.560 --> 00:03:19.000 Third, close the loop and show the impact. 42 00:03:19.000 --> 00:03:22.840 Once people start seeing results, tell those stories. 43 00:03:22.840 --> 00:03:27.220 If campaign velocity doubled, show the before and after. 44 00:03:27.220 --> 00:03:32.920 If marketing can publish globally in a single click, celebrate that. 45 00:03:32.920 --> 00:03:36.400 People need evidence that their effort is paying off. 46 00:03:36.400 --> 00:03:40.040 It transforms compliance into pride. 47 00:03:40.040 --> 00:03:46.640 And pride is the point where culture shifts from, we have to, to, we get to. 48 00:03:46.640 --> 00:03:48.180 Here's the truth. 49 00:03:48.180 --> 00:03:52.720 Change doesn't become culture because you told people to keep doing it. 50 00:03:52.720 --> 00:03:56.560 It becomes culture when the new way feels normal. 51 00:03:56.560 --> 00:04:02.880 And that takes reinforcement, not in the form of more meetings, but in the stories we tell 52 00:04:02.960 --> 00:04:07.280 the habits we reward, and the systems we design. 53 00:04:07.280 --> 00:04:13.200 So if the earlier clips in the course were about planning, launching, and igniting, this 54 00:04:13.200 --> 00:04:16.080 one's about building staying power. 55 00:04:16.080 --> 00:04:22.280 Because momentum doesn't just carry you forward, it defines who you become next. ``` ```transcript [00:00] The launch is exciting, there's energy, applause, maybe even cake. [00:09] But what happens the next morning? [00:12] Every change effort faces a silent moment of truth. [00:16] When the spotlight moves on, in real life comes back. [00:20] The dashboards look good, the project team disbands, and suddenly people start to drift [00:26] toward the comfortable, old way of doing things. [00:30] Not because they want to fail, but because that's where the muscle memory lives. [00:35] That's why sustaining change isn't about holding the line, it's about building new [00:40] muscle memory, faster than the old one fades. [00:44] I'll give you an example. [00:45] A few years ago, there was a consumer brand that had just rolled out a new composable [00:50] content system. [00:52] Launch day was flawless, clean migration, excited teams, lots of internal buzz. [00:59] But by month three, usage data told a different story. [01:04] Only half the team was using the new workflow, the rest had quietly reverted to their old [01:10] process in spreadsheets and shared drives. [01:14] The company didn't have a technology problem, it had a sustainability problem. [01:20] So they rebooted, not with another big initiative, but with small, intentional rhythms. [01:27] They added weekly wins calls, where teams shared one success using the new system. [01:34] Two-minute how-we-did-it videos featuring real employees. [01:39] And a visible leaderboard celebrating people who found creative ways to improve the workflow. [01:46] In 60 days, adoption shot up 40%, not because of pressure, but because success had become [01:53] visible and contagious. [01:56] That's the power of rhythm. [01:58] Culture changes one small win at a time. [02:03] When you think about sustaining change, there are three parts I always look for. [02:09] First, rituals over reminders. [02:12] While reminders don't change behavior, rituals do. [02:17] Make the new way part of how people start their week, review their work, or celebrate results. [02:24] If retrospectives or stand-ups highlight how teams use new tools to solve problems, the [02:30] behavior reinforces itself naturally. [02:34] Change isn't maintained through compliance, it's maintained through community. [02:40] Second, celebrate learning, not just outcomes. [02:43] In the early stages, mistakes are data. [02:46] Reward the teams who experiment, who share what didn't work, who explore new features [02:52] others were afraid to touch. [02:54] At a tech company I partnered with, they gave a Fail Forward award every quarter. [03:00] It recognized people who tried something new, learned from it, and shared the lesson. [03:05] That one ritual made experimentation safe and it kept momentum alive long after the [03:12] project ended. [03:14] Third, close the loop and show the impact. [03:19] Once people start seeing results, tell those stories. [03:22] If campaign velocity doubled, show the before and after. [03:27] If marketing can publish globally in a single click, celebrate that. [03:32] People need evidence that their effort is paying off. [03:36] It transforms compliance into pride. [03:40] And pride is the point where culture shifts from, we have to, to, we get to. [03:46] Here's the truth. [03:48] Change doesn't become culture because you told people to keep doing it. [03:52] It becomes culture when the new way feels normal. [03:56] And that takes reinforcement, not in the form of more meetings, but in the stories we tell [04:02] the habits we reward, and the systems we design. [04:07] So if the earlier clips in the course were about planning, launching, and igniting, this [04:13] one's about building staying power. [04:16] Because momentum doesn't just carry you forward, it defines who you become next. ``` #### Key takeaways - Connect **Turning Momentum into Culture** 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. ### Lesson 07 — Turning Friction into Fuel #### Video details #### At a glance - **Title:** Turning Friction Into Fuel - **Duration:** 4m 29s - **Media link:** https://cdn.jwplayer.com/previews/nKNZ4c9A - **Publish date (unix):** 1769287833 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113806 kbps - video/mp4 · 180p · 180p · 192313 kbps - video/mp4 · 270p · 270p · 239570 kbps - video/mp4 · 360p · 360p · 279361 kbps - video/mp4 · 406p · 406p · 309886 kbps - video/mp4 · 540p · 540p · 410034 kbps - video/mp4 · 720p · 720p · 576499 kbps - video/mp4 · 1080p · 1080p · 1206152 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/nKNZ4c9A-120.vtt` #### Transcript Every change effort eventually hits resistance, and here's the truth, that's not a sign that something's wrong, it's a sign that something's real. If you've ever led a transformation, you know that moment when the enthusiasm dips. Someone says, this used to be easier. Another person jokes, we'll be back to the old ways soon, and you can feel the momentum start to wobble. It's tempting to see resistance as the enemy, but it's actually feedback. Every pushback, every complaint, every skeptical question is the organization trying to make sense of change. Think about a financial services team going through a massive replatforming. The developers are all in, but the content and compliance folks, not so much. They saw the new workflow as a threat, extra steps, new approvals, and what they believed was more overhead. So instead of pushing harder, they slowed down. They ran a listening session, no slides, no justifications. They simply asked, what's worrying you? What came out wasn't rebellion, it was fear, fear of losing control, fear of being replaced by automation, fear of making the same mistakes again, fear that the system would go live before they were ready. That session changed everything because once people feel heard, they stop defending and they start engaging. Resistance is rarely about the change itself, it's about what the change means to them. Most change initiatives don't fail because of technology, they fail because of leadership. When leaders lack clarity or react emotionally to resistance, they amplify fear and create chaos instead of easing it. The best leaders slow the temperature of the room, they listen, clarify, and keep the team moving forward even when things get messy. So when resistance shows up, try reframing it. Instead of asking, how do I get people to stop pushing back, ask, what is this push back telling me? Maybe it's telling you that communication isn't clear. Maybe the training came too late. Maybe a team is worried they're losing their voice in decision making. In one organization, the breakthrough came when leadership invited the loudest critics to co-create part of the rollout plan. They didn't become cheerleaders overnight, but they became owners of the solution. And ownership is the fastest path from skepticism to support. That's the paradox of resistance. The people who challenge the change the hardest often care the most about getting it right. Think about friction in physics. Without it, motion has no traction. Resistance gives you the feedback you need to adjust, to grip the ground, and to steer forward. That's why the best change leaders don't fight resistance, they use it. They turn friction into fuel. They ask questions like, what truth is hiding inside the tension? What value or tradition are people afraid of losing? How can we honor that while still moving ahead? The goal isn't to silence resistance, it's to understand it so deeply that it transforms into insight. One of my favorite ways to approach this is by storytelling. When someone says, this new system slows me down, don't correct them. Show them or tell them a story. Tell them about a peer who used the new approach and got time back, or a customer who benefited because of it. Facts inform, but stories persuade. And persuasion is how resistance becomes momentum. When you lead with empathy, you earn permission to lead with conviction. And when people feel both understood and supported, change stops feeling like something that's happening to them and starts feeling like something they own. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:10.340 Every change effort eventually hits resistance, and here's the truth, that's not a sign 2 00:00:10.340 --> 00:00:15.260 that something's wrong, it's a sign that something's real. 3 00:00:15.260 --> 00:00:22.600 If you've ever led a transformation, you know that moment when the enthusiasm dips. 4 00:00:22.600 --> 00:00:25.780 Someone says, this used to be easier. 5 00:00:25.780 --> 00:00:32.020 Another person jokes, we'll be back to the old ways soon, and you can feel the momentum 6 00:00:32.020 --> 00:00:34.120 start to wobble. 7 00:00:34.120 --> 00:00:39.620 It's tempting to see resistance as the enemy, but it's actually feedback. 8 00:00:39.620 --> 00:00:45.520 Every pushback, every complaint, every skeptical question is the organization trying to make 9 00:00:45.520 --> 00:00:47.940 sense of change. 10 00:00:47.940 --> 00:00:52.280 Think about a financial services team going through a massive replatforming. 11 00:00:52.280 --> 00:00:59.200 The developers are all in, but the content and compliance folks, not so much. 12 00:00:59.200 --> 00:01:05.200 They saw the new workflow as a threat, extra steps, new approvals, and what they believed 13 00:01:05.200 --> 00:01:07.460 was more overhead. 14 00:01:07.460 --> 00:01:10.480 So instead of pushing harder, they slowed down. 15 00:01:10.480 --> 00:01:15.260 They ran a listening session, no slides, no justifications. 16 00:01:15.260 --> 00:01:18.680 They simply asked, what's worrying you? 17 00:01:18.680 --> 00:01:25.360 What came out wasn't rebellion, it was fear, fear of losing control, fear of being replaced 18 00:01:25.360 --> 00:01:32.480 by automation, fear of making the same mistakes again, fear that the system would go live 19 00:01:32.480 --> 00:01:34.580 before they were ready. 20 00:01:34.580 --> 00:01:40.800 That session changed everything because once people feel heard, they stop defending and 21 00:01:40.800 --> 00:01:43.220 they start engaging. 22 00:01:43.220 --> 00:01:50.580 Resistance is rarely about the change itself, it's about what the change means to them. 23 00:01:50.580 --> 00:01:56.520 Most change initiatives don't fail because of technology, they fail because of leadership. 24 00:01:56.520 --> 00:02:02.940 When leaders lack clarity or react emotionally to resistance, they amplify fear and create 25 00:02:02.940 --> 00:02:05.380 chaos instead of easing it. 26 00:02:05.380 --> 00:02:11.020 The best leaders slow the temperature of the room, they listen, clarify, and keep the team 27 00:02:11.020 --> 00:02:14.820 moving forward even when things get messy. 28 00:02:14.820 --> 00:02:18.700 So when resistance shows up, try reframing it. 29 00:02:18.700 --> 00:02:24.300 Instead of asking, how do I get people to stop pushing back, ask, what is this push 30 00:02:24.300 --> 00:02:26.740 back telling me? 31 00:02:26.740 --> 00:02:30.620 Maybe it's telling you that communication isn't clear. 32 00:02:30.620 --> 00:02:33.140 Maybe the training came too late. 33 00:02:33.140 --> 00:02:38.020 Maybe a team is worried they're losing their voice in decision making. 34 00:02:38.020 --> 00:02:42.960 In one organization, the breakthrough came when leadership invited the loudest critics 35 00:02:42.960 --> 00:02:46.340 to co-create part of the rollout plan. 36 00:02:46.340 --> 00:02:52.220 They didn't become cheerleaders overnight, but they became owners of the solution. 37 00:02:52.220 --> 00:02:57.740 And ownership is the fastest path from skepticism to support. 38 00:02:57.740 --> 00:03:00.440 That's the paradox of resistance. 39 00:03:00.440 --> 00:03:06.580 The people who challenge the change the hardest often care the most about getting it right. 40 00:03:06.580 --> 00:03:08.700 Think about friction in physics. 41 00:03:08.700 --> 00:03:12.300 Without it, motion has no traction. 42 00:03:12.300 --> 00:03:16.460 Resistance gives you the feedback you need to adjust, to grip the ground, and to steer 43 00:03:16.460 --> 00:03:17.460 forward. 44 00:03:17.460 --> 00:03:22.700 That's why the best change leaders don't fight resistance, they use it. 45 00:03:22.700 --> 00:03:25.540 They turn friction into fuel. 46 00:03:25.540 --> 00:03:30.780 They ask questions like, what truth is hiding inside the tension? 47 00:03:30.780 --> 00:03:34.940 What value or tradition are people afraid of losing? 48 00:03:34.940 --> 00:03:38.380 How can we honor that while still moving ahead? 49 00:03:38.380 --> 00:03:43.940 The goal isn't to silence resistance, it's to understand it so deeply that it transforms 50 00:03:43.940 --> 00:03:45.900 into insight. 51 00:03:45.900 --> 00:03:50.140 One of my favorite ways to approach this is by storytelling. 52 00:03:50.140 --> 00:03:54.940 When someone says, this new system slows me down, don't correct them. 53 00:03:54.940 --> 00:03:57.220 Show them or tell them a story. 54 00:03:57.220 --> 00:04:03.340 Tell them about a peer who used the new approach and got time back, or a customer who benefited 55 00:04:03.740 --> 00:04:05.020 because of it. 56 00:04:05.020 --> 00:04:08.280 Facts inform, but stories persuade. 57 00:04:08.280 --> 00:04:12.580 And persuasion is how resistance becomes momentum. 58 00:04:12.580 --> 00:04:17.540 When you lead with empathy, you earn permission to lead with conviction. 59 00:04:17.540 --> 00:04:23.140 And when people feel both understood and supported, change stops feeling like something that's 60 00:04:23.140 --> 00:04:28.340 happening to them and starts feeling like something they own. ``` ```transcript [00:00] Every change effort eventually hits resistance, and here's the truth, that's not a sign [00:10] that something's wrong, it's a sign that something's real. [00:15] If you've ever led a transformation, you know that moment when the enthusiasm dips. [00:22] Someone says, this used to be easier. [00:25] Another person jokes, we'll be back to the old ways soon, and you can feel the momentum [00:32] start to wobble. [00:34] It's tempting to see resistance as the enemy, but it's actually feedback. [00:39] Every pushback, every complaint, every skeptical question is the organization trying to make [00:45] sense of change. [00:47] Think about a financial services team going through a massive replatforming. [00:52] The developers are all in, but the content and compliance folks, not so much. [00:59] They saw the new workflow as a threat, extra steps, new approvals, and what they believed [01:05] was more overhead. [01:07] So instead of pushing harder, they slowed down. [01:10] They ran a listening session, no slides, no justifications. [01:15] They simply asked, what's worrying you? [01:18] What came out wasn't rebellion, it was fear, fear of losing control, fear of being replaced [01:25] by automation, fear of making the same mistakes again, fear that the system would go live [01:32] before they were ready. [01:34] That session changed everything because once people feel heard, they stop defending and [01:40] they start engaging. [01:43] Resistance is rarely about the change itself, it's about what the change means to them. [01:50] Most change initiatives don't fail because of technology, they fail because of leadership. [01:56] When leaders lack clarity or react emotionally to resistance, they amplify fear and create [02:02] chaos instead of easing it. [02:05] The best leaders slow the temperature of the room, they listen, clarify, and keep the team [02:11] moving forward even when things get messy. [02:14] So when resistance shows up, try reframing it. [02:18] Instead of asking, how do I get people to stop pushing back, ask, what is this push [02:24] back telling me? [02:26] Maybe it's telling you that communication isn't clear. [02:30] Maybe the training came too late. [02:33] Maybe a team is worried they're losing their voice in decision making. [02:38] In one organization, the breakthrough came when leadership invited the loudest critics [02:42] to co-create part of the rollout plan. [02:46] They didn't become cheerleaders overnight, but they became owners of the solution. [02:52] And ownership is the fastest path from skepticism to support. [02:57] That's the paradox of resistance. [03:00] The people who challenge the change the hardest often care the most about getting it right. [03:06] Think about friction in physics. [03:08] Without it, motion has no traction. [03:12] Resistance gives you the feedback you need to adjust, to grip the ground, and to steer [03:16] forward. [03:17] That's why the best change leaders don't fight resistance, they use it. [03:22] They turn friction into fuel. [03:25] They ask questions like, what truth is hiding inside the tension? [03:30] What value or tradition are people afraid of losing? [03:34] How can we honor that while still moving ahead? [03:38] The goal isn't to silence resistance, it's to understand it so deeply that it transforms [03:43] into insight. [03:45] One of my favorite ways to approach this is by storytelling. [03:50] When someone says, this new system slows me down, don't correct them. [03:54] Show them or tell them a story. [03:57] Tell them about a peer who used the new approach and got time back, or a customer who benefited [04:03] because of it. [04:05] Facts inform, but stories persuade. [04:08] And persuasion is how resistance becomes momentum. [04:12] When you lead with empathy, you earn permission to lead with conviction. [04:17] And when people feel both understood and supported, change stops feeling like something that's [04:23] happening to them and starts feeling like something they own. ``` #### Key takeaways - Connect **Turning Friction into Fuel** 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. ### Lesson 08 — Learning, Adapting, and Scaling Success #### Video details #### At a glance - **Title:** Learning, Adapting, And Scaling Success - **Duration:** 3m 57s - **Media link:** https://cdn.jwplayer.com/previews/zCVNI2b6 - **Publish date (unix):** 1769546895 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113787 kbps - video/mp4 · 180p · 180p · 186685 kbps - video/mp4 · 270p · 270p · 230803 kbps - video/mp4 · 360p · 360p · 263917 kbps - video/mp4 · 406p · 406p · 292078 kbps - video/mp4 · 540p · 540p · 380185 kbps - video/mp4 · 720p · 720p · 524369 kbps - video/mp4 · 1080p · 1080p · 1049150 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/zCVNI2b6-120.vtt` #### Transcript Every transformation ends with the same question. Did it work? That question can sound simple, but what we measure after change determines whether it becomes part of the culture or just another project in the archives. And here's what most organizations get wrong. They measure completion, not capability. They celebrate launch day, then move on. But change management doesn't end when the new system goes live. It ends when people can thrive inside of it. Let me tell you another quick story. A global retailer had just completed a major CMS migration. The rollout was clean. On paper, the project was a success. But when we looked closer, something didn't add up. The site was faster, but publishing wasn't. The new workflow existed, but adoption lagged. So instead of marking the project done, we reframed the metric. Success wasn't go-live achieved. It was go-live adopted. They started tracking time-to-value, how long before teams were actually producing at the same or better pace. Engagement, who was locking in, contributing, and creating. Satisfaction, how confident people felt in the new way of working. Within a few weeks, the data told a clear story. The system wasn't failing. The enablement was. Once they addressed that, the metrics flipped, and the transformation became sustainable. That's the difference between managing a project and managing change. So how do you measure the right things? Start by asking, what did this change set out to improve? If your why was faster delivery, measure lead time. If it was better collaboration, measure cross-team engagement. If it was consistency, measure quality and error rates. The goal isn't to report numbers, it's to tell a story. One that connects outcomes back to the reasons we began this journey in the first place. But measuring success is only half the story. The other half is learning from what didn't go as planned. Every transformation leaves behind clues, moments of friction, workarounds, and we should have done this sooner insights. If you document those patterns and share them, you're not just finishing a project, you're upgrading your organization's change muscle. You should build what I call a change playbook. It's a living document that captures what worked, what didn't, what we'd do differently next time. It becomes your internal field guide for every future transformation. And over time, that's how organizations move from managing change to mastering change. So here's the takeaway. Success isn't a milestone, it's a capability. It's the ability to adapt, to learn faster than the market changes, and to bring your people with you every time you do. That's what real change management builds. Not just a new workflow, but a culture that can evolve continuously. So if you remember one thing from this course, make it this. Change doesn't stop at implementation. It compounds through reflection, learning, and iteration. Just like great design, great products, and great teams. And when that happens, change stops being a disruption and becomes your organization's competitive advantage. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:07.480 Every transformation ends with the same question. 2 00:00:07.480 --> 00:00:09.080 Did it work? 3 00:00:09.080 --> 00:00:14.600 That question can sound simple, but what we measure after change determines whether it 4 00:00:14.600 --> 00:00:20.000 becomes part of the culture or just another project in the archives. 5 00:00:20.000 --> 00:00:23.440 And here's what most organizations get wrong. 6 00:00:23.440 --> 00:00:27.320 They measure completion, not capability. 7 00:00:27.320 --> 00:00:30.240 They celebrate launch day, then move on. 8 00:00:30.240 --> 00:00:34.600 But change management doesn't end when the new system goes live. 9 00:00:34.600 --> 00:00:38.600 It ends when people can thrive inside of it. 10 00:00:38.600 --> 00:00:41.280 Let me tell you another quick story. 11 00:00:41.280 --> 00:00:45.920 A global retailer had just completed a major CMS migration. 12 00:00:45.920 --> 00:00:47.400 The rollout was clean. 13 00:00:47.400 --> 00:00:50.600 On paper, the project was a success. 14 00:00:50.600 --> 00:00:53.820 But when we looked closer, something didn't add up. 15 00:00:53.820 --> 00:00:56.760 The site was faster, but publishing wasn't. 16 00:00:56.760 --> 00:01:00.740 The new workflow existed, but adoption lagged. 17 00:01:00.740 --> 00:01:07.060 So instead of marking the project done, we reframed the metric. 18 00:01:07.060 --> 00:01:09.060 Success wasn't go-live achieved. 19 00:01:09.060 --> 00:01:12.420 It was go-live adopted. 20 00:01:12.420 --> 00:01:18.460 They started tracking time-to-value, how long before teams were actually producing at the 21 00:01:18.460 --> 00:01:20.780 same or better pace. 22 00:01:20.780 --> 00:01:25.540 Engagement, who was locking in, contributing, and creating. 23 00:01:25.540 --> 00:01:30.600 Satisfaction, how confident people felt in the new way of working. 24 00:01:30.600 --> 00:01:33.240 Within a few weeks, the data told a clear story. 25 00:01:33.240 --> 00:01:35.120 The system wasn't failing. 26 00:01:35.120 --> 00:01:37.000 The enablement was. 27 00:01:37.000 --> 00:01:42.200 Once they addressed that, the metrics flipped, and the transformation became sustainable. 28 00:01:42.200 --> 00:01:47.760 That's the difference between managing a project and managing change. 29 00:01:47.760 --> 00:01:51.300 So how do you measure the right things? 30 00:01:51.300 --> 00:01:55.920 Start by asking, what did this change set out to improve? 31 00:01:55.920 --> 00:01:59.240 If your why was faster delivery, measure lead time. 32 00:01:59.240 --> 00:02:04.360 If it was better collaboration, measure cross-team engagement. 33 00:02:04.360 --> 00:02:08.800 If it was consistency, measure quality and error rates. 34 00:02:08.800 --> 00:02:12.940 The goal isn't to report numbers, it's to tell a story. 35 00:02:12.940 --> 00:02:18.400 One that connects outcomes back to the reasons we began this journey in the first place. 36 00:02:18.500 --> 00:02:21.420 But measuring success is only half the story. 37 00:02:21.420 --> 00:02:25.660 The other half is learning from what didn't go as planned. 38 00:02:25.660 --> 00:02:31.420 Every transformation leaves behind clues, moments of friction, workarounds, and we should 39 00:02:31.420 --> 00:02:34.060 have done this sooner insights. 40 00:02:34.060 --> 00:02:40.180 If you document those patterns and share them, you're not just finishing a project, you're 41 00:02:40.180 --> 00:02:44.040 upgrading your organization's change muscle. 42 00:02:44.040 --> 00:02:47.460 You should build what I call a change playbook. 43 00:02:47.520 --> 00:02:54.880 It's a living document that captures what worked, what didn't, what we'd do differently 44 00:02:54.880 --> 00:02:56.440 next time. 45 00:02:56.440 --> 00:03:01.120 It becomes your internal field guide for every future transformation. 46 00:03:01.120 --> 00:03:08.440 And over time, that's how organizations move from managing change to mastering change. 47 00:03:08.440 --> 00:03:10.580 So here's the takeaway. 48 00:03:10.580 --> 00:03:14.320 Success isn't a milestone, it's a capability. 49 00:03:14.320 --> 00:03:19.820 It's the ability to adapt, to learn faster than the market changes, and to bring your 50 00:03:19.820 --> 00:03:23.540 people with you every time you do. 51 00:03:23.540 --> 00:03:26.460 That's what real change management builds. 52 00:03:26.460 --> 00:03:31.140 Not just a new workflow, but a culture that can evolve continuously. 53 00:03:31.140 --> 00:03:36.180 So if you remember one thing from this course, make it this. 54 00:03:36.180 --> 00:03:38.880 Change doesn't stop at implementation. 55 00:03:38.880 --> 00:03:43.720 It compounds through reflection, learning, and iteration. 56 00:03:43.720 --> 00:03:48.460 Just like great design, great products, and great teams. 57 00:03:48.460 --> 00:03:54.060 And when that happens, change stops being a disruption and becomes your organization's 58 00:03:54.060 --> 00:03:55.860 competitive advantage. ``` ```transcript [00:00] Every transformation ends with the same question. [00:07] Did it work? [00:09] That question can sound simple, but what we measure after change determines whether it [00:14] becomes part of the culture or just another project in the archives. [00:20] And here's what most organizations get wrong. [00:23] They measure completion, not capability. [00:27] They celebrate launch day, then move on. [00:30] But change management doesn't end when the new system goes live. [00:34] It ends when people can thrive inside of it. [00:38] Let me tell you another quick story. [00:41] A global retailer had just completed a major CMS migration. [00:45] The rollout was clean. [00:47] On paper, the project was a success. [00:50] But when we looked closer, something didn't add up. [00:53] The site was faster, but publishing wasn't. [00:56] The new workflow existed, but adoption lagged. [01:00] So instead of marking the project done, we reframed the metric. [01:07] Success wasn't go-live achieved. [01:09] It was go-live adopted. [01:12] They started tracking time-to-value, how long before teams were actually producing at the [01:18] same or better pace. [01:20] Engagement, who was locking in, contributing, and creating. [01:25] Satisfaction, how confident people felt in the new way of working. [01:30] Within a few weeks, the data told a clear story. [01:33] The system wasn't failing. [01:35] The enablement was. [01:37] Once they addressed that, the metrics flipped, and the transformation became sustainable. [01:42] That's the difference between managing a project and managing change. [01:47] So how do you measure the right things? [01:51] Start by asking, what did this change set out to improve? [01:55] If your why was faster delivery, measure lead time. [01:59] If it was better collaboration, measure cross-team engagement. [02:04] If it was consistency, measure quality and error rates. [02:08] The goal isn't to report numbers, it's to tell a story. [02:12] One that connects outcomes back to the reasons we began this journey in the first place. [02:18] But measuring success is only half the story. [02:21] The other half is learning from what didn't go as planned. [02:25] Every transformation leaves behind clues, moments of friction, workarounds, and we should [02:31] have done this sooner insights. [02:34] If you document those patterns and share them, you're not just finishing a project, you're [02:40] upgrading your organization's change muscle. [02:44] You should build what I call a change playbook. [02:47] It's a living document that captures what worked, what didn't, what we'd do differently [02:54] next time. [02:56] It becomes your internal field guide for every future transformation. [03:01] And over time, that's how organizations move from managing change to mastering change. [03:08] So here's the takeaway. [03:10] Success isn't a milestone, it's a capability. [03:14] It's the ability to adapt, to learn faster than the market changes, and to bring your [03:19] people with you every time you do. [03:23] That's what real change management builds. [03:26] Not just a new workflow, but a culture that can evolve continuously. [03:31] So if you remember one thing from this course, make it this. [03:36] Change doesn't stop at implementation. [03:38] It compounds through reflection, learning, and iteration. [03:43] Just like great design, great products, and great teams. [03:48] And when that happens, change stops being a disruption and becomes your organization's [03:54] competitive advantage. ``` #### Key takeaways - Connect **Learning, Adapting, and Scaling Success** 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. ### Lesson 09 — Make Change Repeatable #### Video details #### At a glance - **Title:** Make Change Repeatable- - **Duration:** 3m 54s - **Media link:** https://cdn.jwplayer.com/previews/8FaMwhMY - **Publish date (unix):** 1769287814 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113547 kbps - video/mp4 · 180p · 180p · 179720 kbps - video/mp4 · 270p · 270p · 220836 kbps - video/mp4 · 360p · 360p · 252333 kbps - video/mp4 · 406p · 406p · 278038 kbps - video/mp4 · 540p · 540p · 360792 kbps - video/mp4 · 720p · 720p · 496693 kbps - video/mp4 · 1080p · 1080p · 1004084 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/8FaMwhMY-120.vtt` #### Transcript Every organization can change once. The real question is, can you do it again? When I think about great organizations, the ones that stay relevant year after year, they all share one thing in common. They've learned how to make change repeatable. It's not about luck or even vision. It's about process, a rhythm, a playbook. Because change isn't a single event. It's a skill your organization can build, refine, and get better at over time. Throughout this course, we've explored that journey step by step. We started with the why, the moment when the status quo stopped working. We talked about the who, the people at the center of every transformation. We covered how to prepare, how to launch, and how to sustain momentum when the initial excitement fades. And finally, we looked at how to measure and learn so that every round of change strengthens the next. This last step, creating your change playbook, is what turns everything you've done into something scalable. A good change playbook doesn't have to be fancy. It can live in a shared document, a slide deck, even a Miro board. What matters is what it captures. Document what worked, document what didn't, and most importantly, document why. Because your future teams will face new tools, new markets, and new constraints. The principles of good change—clarity, empathy, accountability, rhythm—those don't change. They compound. Think of your playbook like design patterns in software, reusable solutions to recurring problems. When the next transformation begins, you're not starting from scratch. You're building on what you've already learned. One organization I worked with built a change hub, a simple internal site where anyone could share lessons from recent projects. They tagged them by theme—communication, leadership, training, rollout. So before anyone kicked off a new initiative, they could search and see what worked last time, what pitfalls to avoid, and what rituals drove adoption. That small investment turned into something much bigger—a culture of learning. Change became less about risk and more about readiness. That's what you're building, too. Because at the end of the day, the goal of change management isn't to survive disruption. It's to become fluent in it. To build teams that see change not as an interruption, but as a familiar, navigable process. To lead people through uncertainty with confidence, empathy, and clarity. And to do it over and over again, with less friction each time. So as you build your playbook, ask yourself, what did we learn about how people responded to change? What made this easier or harder than it needed to be? And how can we make the next one even better? If you keep answering those questions, your organization won't just adapt to change—it'll lead it. And that's the point. Change isn't something you endure. It's something you own. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:07.480 Every organization can change once. 2 00:00:07.480 --> 00:00:11.080 The real question is, can you do it again? 3 00:00:11.080 --> 00:00:17.320 When I think about great organizations, the ones that stay relevant year after year, they 4 00:00:17.320 --> 00:00:20.120 all share one thing in common. 5 00:00:20.120 --> 00:00:23.480 They've learned how to make change repeatable. 6 00:00:23.480 --> 00:00:26.520 It's not about luck or even vision. 7 00:00:26.520 --> 00:00:30.040 It's about process, a rhythm, a playbook. 8 00:00:30.040 --> 00:00:32.560 Because change isn't a single event. 9 00:00:32.560 --> 00:00:38.800 It's a skill your organization can build, refine, and get better at over time. 10 00:00:38.800 --> 00:00:42.840 Throughout this course, we've explored that journey step by step. 11 00:00:42.840 --> 00:00:48.140 We started with the why, the moment when the status quo stopped working. 12 00:00:48.140 --> 00:00:53.500 We talked about the who, the people at the center of every transformation. 13 00:00:53.500 --> 00:00:59.480 We covered how to prepare, how to launch, and how to sustain momentum when the initial 14 00:00:59.480 --> 00:01:01.420 excitement fades. 15 00:01:01.420 --> 00:01:07.860 And finally, we looked at how to measure and learn so that every round of change strengthens 16 00:01:07.860 --> 00:01:09.260 the next. 17 00:01:09.260 --> 00:01:14.780 This last step, creating your change playbook, is what turns everything you've done into 18 00:01:14.780 --> 00:01:17.180 something scalable. 19 00:01:17.220 --> 00:01:20.260 A good change playbook doesn't have to be fancy. 20 00:01:20.260 --> 00:01:25.320 It can live in a shared document, a slide deck, even a Miro board. 21 00:01:25.320 --> 00:01:28.740 What matters is what it captures. 22 00:01:28.740 --> 00:01:35.860 Document what worked, document what didn't, and most importantly, document why. 23 00:01:35.860 --> 00:01:41.040 Because your future teams will face new tools, new markets, and new constraints. 24 00:01:41.720 --> 00:01:49.880 The principles of good change—clarity, empathy, accountability, rhythm—those don't change. 25 00:01:49.880 --> 00:01:51.480 They compound. 26 00:01:51.480 --> 00:01:57.560 Think of your playbook like design patterns in software, reusable solutions to recurring 27 00:01:57.560 --> 00:01:58.720 problems. 28 00:01:58.720 --> 00:02:02.520 When the next transformation begins, you're not starting from scratch. 29 00:02:02.520 --> 00:02:06.560 You're building on what you've already learned. 30 00:02:06.560 --> 00:02:12.960 One organization I worked with built a change hub, a simple internal site where anyone could 31 00:02:12.960 --> 00:02:15.720 share lessons from recent projects. 32 00:02:15.720 --> 00:02:21.560 They tagged them by theme—communication, leadership, training, rollout. 33 00:02:21.560 --> 00:02:27.040 So before anyone kicked off a new initiative, they could search and see what worked last 34 00:02:27.040 --> 00:02:33.640 time, what pitfalls to avoid, and what rituals drove adoption. 35 00:02:33.640 --> 00:02:39.560 That small investment turned into something much bigger—a culture of learning. 36 00:02:39.560 --> 00:02:43.560 Change became less about risk and more about readiness. 37 00:02:43.560 --> 00:02:46.760 That's what you're building, too. 38 00:02:46.760 --> 00:02:52.360 Because at the end of the day, the goal of change management isn't to survive disruption. 39 00:02:52.360 --> 00:02:55.340 It's to become fluent in it. 40 00:02:55.340 --> 00:03:02.780 To build teams that see change not as an interruption, but as a familiar, navigable process. 41 00:03:02.780 --> 00:03:08.020 To lead people through uncertainty with confidence, empathy, and clarity. 42 00:03:08.020 --> 00:03:14.580 And to do it over and over again, with less friction each time. 43 00:03:14.580 --> 00:03:21.500 So as you build your playbook, ask yourself, what did we learn about how people responded 44 00:03:21.500 --> 00:03:23.120 to change? 45 00:03:23.120 --> 00:03:27.580 What made this easier or harder than it needed to be? 46 00:03:27.580 --> 00:03:31.380 And how can we make the next one even better? 47 00:03:31.380 --> 00:03:37.540 If you keep answering those questions, your organization won't just adapt to change—it'll 48 00:03:37.540 --> 00:03:38.740 lead it. 49 00:03:38.740 --> 00:03:40.500 And that's the point. 50 00:03:40.500 --> 00:03:43.020 Change isn't something you endure. 51 00:03:43.020 --> 00:03:45.100 It's something you own. ``` ```transcript [00:00] Every organization can change once. [00:07] The real question is, can you do it again? [00:11] When I think about great organizations, the ones that stay relevant year after year, they [00:17] all share one thing in common. [00:20] They've learned how to make change repeatable. [00:23] It's not about luck or even vision. [00:26] It's about process, a rhythm, a playbook. [00:30] Because change isn't a single event. [00:32] It's a skill your organization can build, refine, and get better at over time. [00:38] Throughout this course, we've explored that journey step by step. [00:42] We started with the why, the moment when the status quo stopped working. [00:48] We talked about the who, the people at the center of every transformation. [00:53] We covered how to prepare, how to launch, and how to sustain momentum when the initial [00:59] excitement fades. [01:01] And finally, we looked at how to measure and learn so that every round of change strengthens [01:07] the next. [01:09] This last step, creating your change playbook, is what turns everything you've done into [01:14] something scalable. [01:17] A good change playbook doesn't have to be fancy. [01:20] It can live in a shared document, a slide deck, even a Miro board. [01:25] What matters is what it captures. [01:28] Document what worked, document what didn't, and most importantly, document why. [01:35] Because your future teams will face new tools, new markets, and new constraints. [01:41] The principles of good change—clarity, empathy, accountability, rhythm—those don't change. [01:49] They compound. [01:51] Think of your playbook like design patterns in software, reusable solutions to recurring [01:57] problems. [01:58] When the next transformation begins, you're not starting from scratch. [02:02] You're building on what you've already learned. [02:06] One organization I worked with built a change hub, a simple internal site where anyone could [02:12] share lessons from recent projects. [02:15] They tagged them by theme—communication, leadership, training, rollout. [02:21] So before anyone kicked off a new initiative, they could search and see what worked last [02:27] time, what pitfalls to avoid, and what rituals drove adoption. [02:33] That small investment turned into something much bigger—a culture of learning. [02:39] Change became less about risk and more about readiness. [02:43] That's what you're building, too. [02:46] Because at the end of the day, the goal of change management isn't to survive disruption. [02:52] It's to become fluent in it. [02:55] To build teams that see change not as an interruption, but as a familiar, navigable process. [03:02] To lead people through uncertainty with confidence, empathy, and clarity. [03:08] And to do it over and over again, with less friction each time. [03:14] So as you build your playbook, ask yourself, what did we learn about how people responded [03:21] to change? [03:23] What made this easier or harder than it needed to be? [03:27] And how can we make the next one even better? [03:31] If you keep answering those questions, your organization won't just adapt to change—it'll [03:37] lead it. [03:38] And that's the point. [03:40] Change isn't something you endure. [03:43] It's something you own. ``` #### Key takeaways - Connect **Make Change Repeatable** 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. ## Resources & references | Page | Companion Markdown | | --- | --- | | /courses/change-management/what-is-change-management- | /academy/md/courses/change-management/what-is-change-management-.md | | /courses/change-management/why-we-change | /academy/md/courses/change-management/why-we-change.md | | /courses/change-management/the-human-layer-of-change | /academy/md/courses/change-management/the-human-layer-of-change.md | | /courses/change-management/the-preflight | /academy/md/courses/change-management/the-preflight.md | | /courses/change-management/launching-change-and-building-momentum | /academy/md/courses/change-management/launching-change-and-building-momentum.md | | /courses/change-management/turning-momentum-into-culture | /academy/md/courses/change-management/turning-momentum-into-culture.md | | /courses/change-management/turning-friction-into-fuel | /academy/md/courses/change-management/turning-friction-into-fuel.md | | /courses/change-management/learning-adapting-and-scaling-success | /academy/md/courses/change-management/learning-adapting-and-scaling-success.md | | /courses/change-management/make-change-repeatable | /academy/md/courses/change-management/make-change-repeatable.md | ## Supplement for indexing ### Content summary Course Overview Digital transformation fails when we swap systems but forget to swap mindsets. Practical Change Management is a hands-on guide designed to move teams from "what was" to "what will be" in a way that sticks… Course Overview Digital transformation fails when we swap systems but forget to swap mindsets. Practical Change Management is a hands-on guide designed to move teams from "what was" to "what will be" in a way that sticks. Through real-world stories—from global retail brands to healthcare organizations—this course strips away the buzzwords and focuses on the "human layer" of transformation. You will learn how to craft a compelling narrative for change, build organizational readiness, manage resistance as feedback, and create a repeatable playbook for future transitions. By the end of this cours ### Retrieval tags - change management - change-management - What - Change - Management - Why - The - Human - Layer - Preflight - Launching - and - Building - Momentum ### Indexing notes Chunk at each "### Lesson NN — Title" heading; copy lesson_id and topics from the preceding HTML comment into chunk metadata for RAG filters. Course slug: change-management. Union of lesson topic tokens: What, Change, Management, Why, The, Human, Layer, Preflight, Launching, and, Building, Momentum, Turning, into, Culture, Friction, Fuel, Learning, Adapting, Scaling, Success, Make, Repeatable. Do not embed or retrieve LMS-only quiz items or mastery exam answer keys from this export. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: What is Change Management? | `https://cdn.jwplayer.com/v2/media/ORYEkxiv/poster.jpg?width=720` | | Video thumbnail: Why We Change | `https://cdn.jwplayer.com/v2/media/GJUxXiDo/poster.jpg?width=720` | | Video thumbnail: The Human Layer of Change | `https://cdn.jwplayer.com/v2/media/ELZtElv9/poster.jpg?width=720` | | Video thumbnail: The Preflight | `https://cdn.jwplayer.com/v2/media/IfFJY4qo/poster.jpg?width=720` | | Video thumbnail: Launching Change and Building Momentum | `https://cdn.jwplayer.com/v2/media/ODcKIqmO/poster.jpg?width=720` | | Video thumbnail: Turning Momentum into Culture | `https://cdn.jwplayer.com/v2/media/VCHUK8uy/poster.jpg?width=720` | | Video thumbnail: Turning Friction into Fuel | `https://cdn.jwplayer.com/v2/media/nKNZ4c9A/poster.jpg?width=720` | | Video thumbnail: Learning, Adapting, and Scaling Success | `https://cdn.jwplayer.com/v2/media/zCVNI2b6/poster.jpg?width=720` | | Video thumbnail: Make Change Repeatable | `https://cdn.jwplayer.com/v2/media/8FaMwhMY/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/` |