# Why We Change ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/change-management/why-we-change | | **course_slug** | change-management | | **lesson_slug** | why-we-change | | **markdown_file_url** | /academy/md/courses/change-management/why-we-change.md | | **generated_at** | 2026-04-28T06:55:38.400Z | > Part of **[Change Management](https://www.contentstack.com/academy/courses/change-management)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** 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. ## Supplement for indexing ### Content summary Why We Change. Why We Change in Change Management (change-management). ### Retrieval tags - Why - Change - change-management - lesson 02 - Why We Change - change-management lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "02" and topics: [Why, Change]. Parent course slug: change-management. Use asset_references URLs as thumbnail hints in search results when present. Never surface LMS quiz content or assessment answers from this file. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: Why We Change | `https://cdn.jwplayer.com/v2/media/GJUxXiDo/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/` |