# Turning Momentum into Culture

### About this export

| Field | Value |
| --- | --- |
| **content_type** | lesson |
| **platform** | contentstack-academy |
| **source_url** | https://www.contentstack.com/academy/courses/change-management/turning-momentum-into-culture |
| **course_slug** | change-management |
| **lesson_slug** | turning-momentum-into-culture |
| **markdown_file_url** | /academy/md/courses/change-management/turning-momentum-into-culture.md |
| **generated_at** | 2026-04-28T06:55:38.404Z |

> 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.

<!-- ai_metadata: {"lesson_id":"06","type":"video","duration_seconds":264,"video_url":"https://cdn.jwplayer.com/previews/VCHUK8uy","thumbnail_url":"https://cdn.jwplayer.com/v2/media/VCHUK8uy/poster.jpg?width=720","topics":["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
<!-- PLACEHOLDER: replace with real transcript before publish if cues were auto-derived from WebVTT -->
[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.

## Supplement for indexing

### Content summary

Turning Momentum into Culture. Turning Momentum into Culture in Change Management (change-management).

### Retrieval tags

- Turning
- Momentum
- into
- Culture
- change-management
- lesson 06
- Turning Momentum into Culture
- change-management lesson

### Indexing notes

Index this lesson as a primary chunk tagged with lesson_id "06" and topics: [Turning, Momentum, into, Culture].
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: Turning Momentum into Culture | `https://cdn.jwplayer.com/v2/media/VCHUK8uy/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/` |
