TRANSCRIPT 🔗
WEBVTT
1
00:00:01.520 --> 00:00:04.839
This is your Morning Boost, recorded in the forward Ed
2
00:00:04.960 --> 00:00:09.279
Network studios, a weekly spark for educators and school leaders
3
00:00:09.480 --> 00:00:14.119
ready to lead, teach, and live with greater intention. This
4
00:00:14.320 --> 00:00:15.599
is your Morning Boost.
5
00:00:18.399 --> 00:00:21.399
Good morning everybody, and a welcome back to your Morning Boost.
6
00:00:21.679 --> 00:00:25.559
It happens almost every time you are three days into
7
00:00:25.559 --> 00:00:30.079
a new initiative and somebody says this isn't working now.
8
00:00:30.120 --> 00:00:33.960
Sometimes they might be right, but sometimes it's just Tuesday.
9
00:00:34.159 --> 00:00:37.280
I mean, we've introduced a new process and people are
10
00:00:37.359 --> 00:00:41.600
learning it. Somebody clicked the wrong button, something took longer
11
00:00:41.640 --> 00:00:45.000
than it expected, or the technology didn't cooperate. I mean,
12
00:00:45.359 --> 00:00:47.679
could even just be a step that looked really simple
13
00:00:47.719 --> 00:00:51.439
when we designed it suddenly feels awkward when fifty people
14
00:00:51.439 --> 00:00:54.719
are trying to use it all at once, and already
15
00:00:54.880 --> 00:00:58.039
somebody is ready to pull the plug. I understand that
16
00:00:58.200 --> 00:01:02.159
reaction when we when we spend months planning something, we
17
00:01:02.240 --> 00:01:05.120
want it to work immediately. We want people to use
18
00:01:05.159 --> 00:01:08.920
it correctly, We want the technology to cooperate and everything
19
00:01:08.959 --> 00:01:12.200
to feel natural. But one of the hardest lessons I've
20
00:01:12.239 --> 00:01:17.519
learned about implementation is this early implementation problems aren't averted
21
00:01:18.000 --> 00:01:22.799
their evidence. A new system is supposed to expose things
22
00:01:22.840 --> 00:01:26.799
that you couldn't see during planning. Real people doing real
23
00:01:26.879 --> 00:01:30.200
work will find the awkward steps. They will uncover assumptions
24
00:01:30.200 --> 00:01:33.719
that we didn't realize we made. They'll find the technology bugs.
25
00:01:34.079 --> 00:01:37.000
They'll discover places where something that looked real simple on
26
00:01:37.079 --> 00:01:42.439
paper becomes more complicated in practice. The question isn't whether
27
00:01:42.519 --> 00:01:45.879
there will be problems. There will be. The question is
28
00:01:46.319 --> 00:01:49.400
what kind of problem are we looking at. Is it
29
00:01:49.439 --> 00:01:55.239
a design problem, is it a training problem, a technology problem,
30
00:01:55.519 --> 00:01:58.079
or is it simply what happens when people are learning
31
00:01:58.120 --> 00:02:01.040
something new? Can we tell the difference.
32
00:02:06.439 --> 00:02:11.240
This segment is sponsored by Grunmeyer Leader Services. Since twenty thirteen,
33
00:02:11.680 --> 00:02:14.719
GLS has been a trusted partner for school districts across
34
00:02:14.759 --> 00:02:19.439
the Midwest, specializing in executive recruitment and leadership supporting. They
35
00:02:19.479 --> 00:02:22.919
believe that great schools start with great leaders, and they
36
00:02:22.919 --> 00:02:25.159
are here to help you find a perfect fifth for
37
00:02:25.240 --> 00:02:28.879
your district transform your school's future with the right leader.
38
00:02:29.319 --> 00:02:33.319
Visit Grunmeyer leader search dot com to learn more. Grunmeyer
39
00:02:33.400 --> 00:02:37.560
Leader Services transforming education one leader at a time.
40
00:02:44.240 --> 00:02:46.400
A number of years ago, we were implementing a new
41
00:02:46.520 --> 00:02:49.280
MTSS system in my school, and the goal behind. It
42
00:02:49.360 --> 00:02:53.400
was really pretty straightforward. We wanted to become more responsive
43
00:02:53.439 --> 00:02:56.719
to student needs. We needed a better way to identify
44
00:02:56.800 --> 00:02:59.560
what students needed, to keep track of the supports that
45
00:02:59.560 --> 00:03:02.560
we were and honestly just to make sure that the
46
00:03:02.639 --> 00:03:05.199
right people had access to the information they needed to
47
00:03:05.240 --> 00:03:08.759
make the right decisions. We also had an opportunity to
48
00:03:08.840 --> 00:03:11.759
use a new feature inside of our student information system,
49
00:03:11.759 --> 00:03:14.280
and it was one that seemed like it could really
50
00:03:14.360 --> 00:03:17.560
help accomplish all of this. On paper, it all made
51
00:03:17.599 --> 00:03:21.680
perfect sense, and instead of creating another spreadsheet or another
52
00:03:21.800 --> 00:03:25.560
standalone program somewhere else, we could build the work into
53
00:03:25.639 --> 00:03:29.039
the student information system that people are already using every day.
54
00:03:29.680 --> 00:03:33.000
The information would stay connected to the student, the process
55
00:03:33.120 --> 00:03:37.479
could become more consistent, so ultimately we've believed it would
56
00:03:37.479 --> 00:03:41.039
help us build a stronger MTSS system. There was just
57
00:03:41.240 --> 00:03:44.960
one problem. Actually, there were a lot of little problems.
58
00:03:45.039 --> 00:03:48.280
The feature itself was new, the process was new. The
59
00:03:48.400 --> 00:03:51.639
people using both of these were new to the entire system,
60
00:03:51.719 --> 00:03:54.439
so there was a lot of new all at one time.
61
00:03:54.960 --> 00:03:56.520
So we should have been able to predict that it
62
00:03:56.560 --> 00:03:59.599
wasn't going to be perfect. People would run into something
63
00:03:59.639 --> 00:04:01.919
that didn't work. The way that we expected it to
64
00:04:03.000 --> 00:04:05.080
a step took a little longer than we thought it would,
65
00:04:05.159 --> 00:04:09.120
or something I remember something wouldn't display correctly. I mean,
66
00:04:09.159 --> 00:04:11.479
we
Load full transcript
use the process maybe in a way we hadn't
67
00:04:11.479 --> 00:04:14.120
anticipated too. So all of this just adds up, and
68
00:04:14.199 --> 00:04:18.360
every one of those moments caused this larger frustration. It's
69
00:04:18.439 --> 00:04:21.600
understandable if you're the person doing the work, you're not
70
00:04:21.680 --> 00:04:24.759
thinking about the long term potential of the system. You're
71
00:04:24.800 --> 00:04:28.000
just thinking, I need to get this done and right now.
72
00:04:28.040 --> 00:04:30.560
This is not making my job any easier. It's making
73
00:04:30.639 --> 00:04:35.439
it harder. That's real, and as leaders, we can't dismiss that.
74
00:04:36.360 --> 00:04:38.920
One of the worst responses that we can give people
75
00:04:39.040 --> 00:04:43.040
during implementation is some version of just trust the process,
76
00:04:43.839 --> 00:04:46.560
because if I'm asking somebody to use a system and
77
00:04:46.600 --> 00:04:50.040
they're telling me something isn't working, I need to understand
78
00:04:50.079 --> 00:04:54.319
what they're experiencing. But there's another danger on the opposite
79
00:04:54.360 --> 00:04:58.000
side of this. We also can't assume that every frustration
80
00:04:58.240 --> 00:05:01.360
means that the whole idea is wrong. That's where implementation
81
00:05:01.480 --> 00:05:05.319
becomes difficult, because the frustration is real, the feedback is
82
00:05:05.439 --> 00:05:09.600
very important, and the overall direction can still be exactly right.
83
00:05:10.079 --> 00:05:12.120
All three of those things can be true at the
84
00:05:12.120 --> 00:05:15.920
exact same time. I think sometimes we struggle with that.
85
00:05:16.319 --> 00:05:18.560
You know, in schools, we struggle with this because we're
86
00:05:18.639 --> 00:05:21.920
used to evaluating things very quickly. Did the lesson work,
87
00:05:21.959 --> 00:05:24.560
did the meeting work, did the schedule work? Did the
88
00:05:24.600 --> 00:05:29.560
new process work? Yes? Or no? Implementation? It just it
89
00:05:29.600 --> 00:05:33.399
isn't that clean. Something can be the right system and
90
00:05:33.560 --> 00:05:35.920
still have a bad step in it. Something can be
91
00:05:35.959 --> 00:05:39.639
the right process and still need adjustment. It can all
92
00:05:39.680 --> 00:05:43.360
be very valuable but still have bugs, And people can
93
00:05:43.399 --> 00:05:46.319
believe in the goal but still be frustrated by how
94
00:05:46.360 --> 00:05:50.800
they're trying to accomplish it. These aren't contradictions, they're just
95
00:05:50.959 --> 00:05:55.639
normal parts of building something new. So when something went wrong,
96
00:05:56.079 --> 00:05:59.800
we started asking a different question, what kind of problem
97
00:05:59.920 --> 00:06:03.600
is is this? Is this something the technology company needs
98
00:06:03.639 --> 00:06:07.040
to fix okay? Or did we design part of the
99
00:06:07.120 --> 00:06:14.120
process poorly? Or do people simply need more training? Or
100
00:06:14.160 --> 00:06:18.160
maybe even is this exactly what learning something new looks like.
101
00:06:19.319 --> 00:06:22.439
The answer to all of that mattered because each one
102
00:06:22.519 --> 00:06:26.240
of those requires a different leadership response, and the only
103
00:06:26.279 --> 00:06:29.600
way that we could answer those questions was by listening
104
00:06:29.680 --> 00:06:33.680
to the people actually using the system. The end users.
105
00:06:33.720 --> 00:06:37.519
Here they become incredibly important. They are finding things that
106
00:06:37.560 --> 00:06:41.279
we never would have discovered sitting around a planning table. Well,
107
00:06:41.279 --> 00:06:43.920
of course they are. That's what happens when a plan
108
00:06:44.120 --> 00:06:47.319
finally meets real life. I can sit in my office
109
00:06:47.319 --> 00:06:50.319
and map out a process from beginning to end and think, hmmm,
110
00:06:50.560 --> 00:06:53.920
that looks pretty good. Then a teacher tries to use
111
00:06:53.920 --> 00:06:56.720
it while juggling everything else that's happening during the school day,
112
00:06:56.720 --> 00:06:59.800
and immediately they will discover something that I never considered.
113
00:07:00.240 --> 00:07:02.600
That is not failure of the teacher, that's not failure
114
00:07:02.600 --> 00:07:06.360
of me. That's just viuable information about the design. And
115
00:07:06.399 --> 00:07:08.519
that's where I think leaders need to make an important
116
00:07:08.560 --> 00:07:14.399
shift during implementation. Before the launch, weird designers. After the launch,
117
00:07:14.639 --> 00:07:19.319
we become observers. We have to watch what actually happens,
118
00:07:19.600 --> 00:07:22.560
not what we hoped would happened, not what the flow
119
00:07:22.680 --> 00:07:27.560
chart said should happen, what actually happens when people begin
120
00:07:27.720 --> 00:07:31.439
using the system. That's where the real information begins. In
121
00:07:31.600 --> 00:07:34.800
our case, in that particular case, we started finding the bugs.
122
00:07:34.839 --> 00:07:37.800
Some were small, some were more significant, and there was
123
00:07:37.879 --> 00:07:40.279
a few that you could fix real quickly, but the
124
00:07:40.319 --> 00:07:43.480
others took some time, and some of the things we
125
00:07:43.519 --> 00:07:45.800
saw weren't even really bugs at all. They were just
126
00:07:45.839 --> 00:07:48.600
simply parts of a new process that people just needed
127
00:07:48.600 --> 00:07:51.600
time to learn. But sorting all of that out that
128
00:07:51.720 --> 00:07:54.120
became the work. The goal isn't to prove that we
129
00:07:54.160 --> 00:07:56.959
had selected the right system. The goal is to make
130
00:07:56.959 --> 00:08:00.000
sure that the system actually helps us become more responsible
131
00:08:00.160 --> 00:08:04.920
to students. That's a very
important distinction, because once leaders
132
00:08:04.959 --> 00:08:08.560
invest time and energy into creating something, it becomes very
133
00:08:08.600 --> 00:08:13.240
easy to become defensive. This was our idea, I designed it,
134
00:08:13.319 --> 00:08:17.399
I believe in this, and then when someone criticized part
135
00:08:17.480 --> 00:08:21.399
of it, it's tempting to hear criticism of the decision
136
00:08:21.639 --> 00:08:26.240
rather than information about the implementation. That's very dangerous. But
137
00:08:26.319 --> 00:08:29.920
the opposite is also just as dangerous. If every complaint
138
00:08:29.959 --> 00:08:33.679
immediately causes us to change the system, nobody ever has
139
00:08:33.799 --> 00:08:37.720
enough time to actually learn it. Sometimes leadership means adjusting.
140
00:08:38.360 --> 00:08:42.840
Sometimes leadership also means staying the course, and knowing which
141
00:08:42.840 --> 00:08:47.320
one is needed requires more than reacting to whoever spoke last.
142
00:08:53.000 --> 00:08:56.480
Are you ready to transform your school or classroom? Join
143
00:08:56.559 --> 00:08:59.799
hosts Adam and Jim on Control Shift, Lead, the monthly
144
00:09:00.000 --> 00:09:03.759
podcast on the Forward D Network. Every episode They bring
145
00:09:03.799 --> 00:09:06.919
in top educators from across the United States to deliver
146
00:09:07.039 --> 00:09:10.639
three game changing insights. Something you can control in your work,
147
00:09:11.159 --> 00:09:13.879
something that will shift your thinking, and something you can
148
00:09:13.960 --> 00:09:18.480
use to lead tomorrow. Don't just manage lead, subscribe to
149
00:09:18.519 --> 00:09:19.840
control shift lead today.
150
00:09:27.480 --> 00:09:31.639
There's actually some research behind this idea. Implementation science has
151
00:09:31.679 --> 00:09:35.440
spent decades studying the difference between choosing a good practice
152
00:09:35.480 --> 00:09:38.159
and actually getting that practice to work in the real world.
153
00:09:38.919 --> 00:09:41.919
One of the foundational researchers in that field is Dean Fixing.
154
00:09:42.279 --> 00:09:44.960
One of the ideas that I find most helpful from
155
00:09:45.000 --> 00:09:48.200
his work is that there's a difference between launching something
156
00:09:48.279 --> 00:09:51.639
and truly embedding it into an organization. Those aren't the
157
00:09:51.679 --> 00:09:55.440
same thing. Sometimes we evaluate a new system as though
158
00:09:55.440 --> 00:09:58.639
it has already reached its full potential, when it's really
159
00:09:58.720 --> 00:10:02.600
just taking its first step. We're judging a finished product
160
00:10:02.679 --> 00:10:05.840
while we're still building it, and I think that's incredibly
161
00:10:05.879 --> 00:10:10.639
important for school leaders to remember because early implementation it
162
00:10:10.679 --> 00:10:14.000
can feel very messy. I mean, people are still learning,
163
00:10:14.600 --> 00:10:19.879
we're still establishing routines, we're refining technology, and everyone is
164
00:10:19.919 --> 00:10:22.519
trying to figure out how the pieces all fit together.
165
00:10:22.960 --> 00:10:26.360
That's normal, and it brings me back to something I
166
00:10:26.399 --> 00:10:29.360
don't think it's talked about enough during implementation, and that
167
00:10:29.480 --> 00:10:33.559
is resolved. Now, there's a difference between that and stubbornness.
168
00:10:34.600 --> 00:10:38.200
In fact, resolve and stubbornness can look very similar from
169
00:10:38.240 --> 00:10:41.200
a distance, but they are not the same thing. Stubborness
170
00:10:41.240 --> 00:10:45.960
says we're not changing anything. Resolve says, we still believe
171
00:10:46.000 --> 00:10:48.080
in what we're trying to do and where we're trying
172
00:10:48.120 --> 00:10:51.240
to go, and we're going to keep improving until we
173
00:10:51.279 --> 00:10:55.200
get there. That's a very different kind of leadership. With
174
00:10:55.320 --> 00:10:58.480
our MTSS system, we believe the direction was right. We
175
00:10:58.600 --> 00:11:01.200
needed a better way to respond on to student needs.
176
00:11:01.480 --> 00:11:05.639
We needed better information, We needed the work connected inside
177
00:11:05.759 --> 00:11:10.279
one system instead of depending on separate spreadsheets and emails,
178
00:11:10.840 --> 00:11:13.919
people's memories, I mean, all of that part. It hadn't changed.
179
00:11:14.720 --> 00:11:18.320
So every time we encountered some frustration, we had something
180
00:11:18.360 --> 00:11:21.600
to measure it against. Does this problem tell us the
181
00:11:21.639 --> 00:11:22.399
goal is wrong?
182
00:11:23.360 --> 00:11:23.440
No?
183
00:11:24.679 --> 00:11:29.200
Does it tell us this step needs improvement? Maybe okay,
184
00:11:29.639 --> 00:11:34.000
then let's improve the step. That's where stakeholder feedback became
185
00:11:34.080 --> 00:11:37.799
so valuable. Once a system goes live, the people closest
186
00:11:37.840 --> 00:11:41.399
to the work start generating information almost immediately. I mean,
187
00:11:41.399 --> 00:11:45.480
the challenge isn't simply collecting complaints. The challenge is collecting
188
00:11:45.600 --> 00:11:50.679
useful information. There's a difference between this whole thing is
189
00:11:50.879 --> 00:11:54.240
terrible and when I get to this step, I have
190
00:11:54.320 --> 00:11:58.159
to enter the same information twice. I mean, that's something
191
00:11:58.159 --> 00:12:02.840
that we can solve or you'll hear this takes forever. Okay,
192
00:12:03.360 --> 00:12:06.679
which part? What were you trying to accomplish and how
193
00:12:06.720 --> 00:12:10.120
long did it take? What would have made it easier.
194
00:12:11.320 --> 00:12:15.480
The more specific the feedback becomes, the more useful it becomes,
195
00:12:15.600 --> 00:12:18.240
and leaders play an
important role in helping people move
196
00:12:18.320 --> 00:12:23.399
from frustration to information. When something doesn't work, our first
197
00:12:23.440 --> 00:12:27.720
reaction usually isn't very specific. Usually it's something like, this
198
00:12:27.759 --> 00:12:33.200
whole thing is ridiculous and maybe or maybe one button
199
00:12:33.279 --> 00:12:35.799
is in the wrong place. I mean, we just need
200
00:12:35.840 --> 00:12:38.519
to figure it out. And that became part of the
201
00:12:38.559 --> 00:12:41.279
work for us. We needed feedback from the people using
202
00:12:41.279 --> 00:12:45.080
the system to understand where the actual problems were. Then
203
00:12:45.120 --> 00:12:48.440
we faced another leadership challenge, what do we fix first?
204
00:12:49.279 --> 00:12:53.600
Because implementation creates another reality. You usually can't fix everything
205
00:12:53.639 --> 00:12:56.879
at once, and some problems will stop the work completely,
206
00:12:56.960 --> 00:12:58.639
so those have to move to the top. Of the
207
00:12:58.679 --> 00:13:03.399
list create frustration, but they might have some reasonable workarounds.
208
00:13:03.519 --> 00:13:06.600
Those also matter because they don't need to come first.
209
00:13:07.279 --> 00:13:08.679
And then you're also going to have some that are
210
00:13:08.679 --> 00:13:12.919
cosmetic that maybe only affect a handful of situations. Those
211
00:13:13.000 --> 00:13:16.080
might disappear naturally as people become more confident with the
212
00:13:16.159 --> 00:13:20.799
new process. If leaders treat every issue as equally urgent,
213
00:13:21.480 --> 00:13:26.759
implementation becomes chaotic. At best. People never know which version
214
00:13:26.799 --> 00:13:29.720
of the process they're supposed to be using because leadership
215
00:13:29.799 --> 00:13:34.600
changes it every three days. That's not responsive. This that's instability,
216
00:13:34.840 --> 00:13:40.000
and instability creates its own implementation problems. So in our case,
217
00:13:40.039 --> 00:13:46.240
we listened, We identified patterns, we prioritized, we made thoughtful adjustments.
218
00:13:47.039 --> 00:13:49.600
Then we gave people enough time to actually use the
219
00:13:49.639 --> 00:13:54.240
revised process. That's much slower than reacting, but it's also
220
00:13:54.320 --> 00:13:59.399
much more effective. I think that lesson applies well beyond technology.
221
00:13:59.679 --> 00:14:02.919
Maybe you have redesigned your morning arrival process this year.
222
00:14:03.279 --> 00:14:07.919
That first morning, it probably feels chaotic, and that doesn't
223
00:14:07.919 --> 00:14:12.039
automatically mean the plan is bad. Just watch where's the bottleneck?
224
00:14:12.600 --> 00:14:14.639
Is it happening because people are still trying to learn
225
00:14:14.679 --> 00:14:17.879
the routine, or is there a structural problem that will
226
00:14:17.879 --> 00:14:21.639
still exist once everybody knows what they're doing. Those require
227
00:14:21.679 --> 00:14:25.399
two very different responses. Maybe you've changed the intervention schedule
228
00:14:25.799 --> 00:14:30.840
teachers confused the first week. Okay, again, that's information, But
229
00:14:30.960 --> 00:14:34.240
what kind of information. Do we need a different schedule
230
00:14:34.399 --> 00:14:36.679
or do we simply need a clearer way for people
231
00:14:36.720 --> 00:14:40.240
to access that information. That's why I think one of
232
00:14:40.240 --> 00:14:43.360
the most important things leaders can do during any implementation
233
00:14:43.519 --> 00:14:47.320
is resist the urge to immediately label the result success
234
00:14:47.559 --> 00:14:52.000
or failure, or working or not working. Sometimes we just
235
00:14:52.039 --> 00:14:55.480
don't know yet. We need enough time to see a pattern.
236
00:14:56.559 --> 00:15:00.840
One complaint is information ten people encountering the the same obstacle.
237
00:15:01.440 --> 00:15:05.360
That's a pattern, and patterns deserve our attention. The same
238
00:15:05.440 --> 00:15:08.320
question keeps coming up, there may be a clarity problem.
239
00:15:08.559 --> 00:15:11.919
If the same step keeps slowing everybody down, there may
240
00:15:11.960 --> 00:15:16.519
be a process problem. If the technology repeatedly fails, there
241
00:15:16.559 --> 00:15:19.879
might be a product problem. But we don't discover any
242
00:15:19.879 --> 00:15:22.519
of that. If our only response is to either defend
243
00:15:22.559 --> 00:15:27.279
the plan or abandon it, we have to investigate. Every
244
00:15:27.440 --> 00:15:33.480
implementation problem isn't a verdict, it's evidence, and evidence needs interpretation.
245
00:15:34.039 --> 00:15:46.720
That's the leadership work. As we wrap up today. Chances
246
00:15:46.759 --> 00:15:49.960
are there something new being implemented in your school right now.
247
00:15:50.240 --> 00:15:53.279
Maybe it's a technology platform, maybe it's a new schedule
248
00:15:53.399 --> 00:15:56.360
or an intervention process, or maybe it's simply a different
249
00:15:56.399 --> 00:16:00.200
way students move through one part of your building, where
250
00:16:00.240 --> 00:16:02.840
along the way there's a pretty good chance somebody is
251
00:16:02.879 --> 00:16:07.840
going to say this isn't working. When that happens, I
252
00:16:07.879 --> 00:16:11.120
think our job as leaders to take the statement seriously
253
00:16:11.840 --> 00:16:17.000
without automatically accepting the conclusion. Because something did happen, there's
254
00:16:17.039 --> 00:16:20.360
information there. Our job is to figure out what kind
255
00:16:20.399 --> 00:16:23.840
of information it is. Maybe you've uncovered a flaw that
256
00:16:24.000 --> 00:16:27.600
genuinely needs to be fixed. Maybe you've discovered an assumption
257
00:16:27.720 --> 00:16:31.360
the planning team never realized they had made. Maybe you've
258
00:16:31.360 --> 00:16:34.720
identified exactly where the next adjustment needs to happen. Or
259
00:16:35.799 --> 00:16:40.320
maybe you're simply experiencing what every organization experiences when people
260
00:16:40.360 --> 00:16:46.080
begin learning something new. Those situations can feel remarkably similar
261
00:16:46.159 --> 00:16:48.639
when you're standing in the middle of them. That's why
262
00:16:48.720 --> 00:16:54.799
leadership during implementation requires both responsiveness and resolve. We have
263
00:16:54.879 --> 00:16:57.440
to be willing to change something we helped create, and
264
00:16:57.480 --> 00:17:00.240
we have to be willing to stay the course when
265
00:17:00.279 --> 00:17:03.320
the destination is still right, even if the road feels
266
00:17:03.320 --> 00:17:07.519
a little bumpy. Neither one is particularly easy, But the
267
00:17:07.519 --> 00:17:09.920
goal isn't to protect the plan. The goal is to
268
00:17:09.960 --> 00:17:15.799
accomplish the purpose. Our MTSS system wasn't successful because everything
269
00:17:15.839 --> 00:17:19.039
worked perfectly on day one, because it didn't. It became
270
00:17:19.160 --> 00:17:23.480
successful because we listened. We identified the problems that mattered
271
00:17:23.519 --> 00:17:27.079
the most, and we made thoughtful adjustments, and we gave
272
00:17:27.160 --> 00:17:30.839
people enough time to become successful with the new system.
273
00:17:31.359 --> 00:17:35.119
Maybe that's a better definition of a successful launch, not
274
00:17:35.279 --> 00:17:38.440
one where nothing goes wrong, but one where we learned
275
00:17:38.519 --> 00:17:41.880
quickly enough to make the system better without losing sight
276
00:17:41.920 --> 00:17:46.160
of why we built it in the first place. Thank
277
00:17:46.200 --> 00:17:48.119
you for spending a few minutes with me this morning.
278
00:17:48.160 --> 00:17:51.279
I appreciate everything that you do for your students, your staff,
279
00:17:51.720 --> 00:17:54.599
and your communities. Have great week Boosters. We'll see you
280
00:17:54.640 --> 00:17:56.119
next time on your morning boost.
281
00:17:58.000 --> 00:18:01.960
That's your morning boost from AWBs Education and Media. If
282
00:18:01.960 --> 00:18:04.759
this episode helped you reset your thinking or take your
283
00:18:04.799 --> 00:18:08.440
next step forward, share it with a colleague, and don't
284
00:18:08.440 --> 00:18:11.400
forget to subscribe so your next boost is ready when
285
00:18:11.440 --> 00:18:15.640
you need it. Keep showing up with intention, keep moving forward,
286
00:18:15.799 --> 00:18:17.000
and we'll see you next time.