Switching Platforms Without Losing Ground
Presented by:
Transcript
Cassie and I are excited to talk with you today about one of everyone's least
favorite topics, which is change.
Yeah, so I think this one's particularly
tricky for IT leaders.
I think a lot of IT folks kind of find themselves in a position where they're
accountable for change going well, but they're not necessarily responsible for all
the elements within the change, and that can
lead to some difficulty. So,
Cassie and I are going to speak. I'm going to talk about some kind of theories of
change, some kind of business school stuff.
The goal in that part of the talk is to kind of highlight some of the psychology
behind change, some of what some of the kind of big-time thinkers in institutional
change have said on the topic over time, think about some of the best practices of
change management.
And then Cassie's going to double-click into making that a little bit more grounded
and a little bit more in the kind of technical vendor change space.
Cassie manages our client services and is a longtime implementation manager at both
August Schools and other IT platforms in ed tech.
So frankly, knows a lot more about the details than I do.
And I should say at the beginning here,
we're not really experts so much as we've made a lot of mistakes in helping
people through change in different ways, and we like to think we've learned from
our own mistakes and improved our process.
And if we can help anyone else kind of prevent a mistake in a change and
kind of see around the corner, we're here for that.
And yeah, and this is going to be a theme to the conversation, but
change for the better is still really hard, and I think everyone knows that in
theory. But you've probably been through this thing where you see
the hot new thing at the Atlas conference, and you're really excited about this new
vendor, and you know it's going to be a better solution than what you have, or
maybe you're kind of replacing nothing with something, and then all of a sudden
you're down the road and you're just like, "Oh, how did this become such a
headache?"
But, and even highly successful implementations,
it's just kind of an inherently tricky thing.
And we'll actually talk about some of the research that talks about the dip before
the increase in productivity or whatever your goals are in a change.
So, getting into probably the most famous framework
for institutional change, this professor,
John Kotter, released a book in the '90s called "Leading Change," and it's
become a touchstone for kind of all other people who have thought about
institutional change and change in business and organizational change since.
It's hard to find an MBA syllabus that doesn't talk or ground itself in John
Kotter's work.
So, I'll talk a little bit about his framework, and then other thinkers
have also kind of echoed some of this stuff, and there's just a lot of research
about some of the psychology at play here.
But first and foremost, establishing a sense of urgency.
Why change? And you're going to need to touch back to this again and again
throughout the process. Why did we get ourselves into this?
That's just such an important part of the change process.
It's really about the why, and part of that is the why now.
Forming a guiding coalition, and again, I'll be double-clicking into these topics.
Forming a guiding coalition, in my opinion, is
probably the most important thing.
And knowing your role so well, like I think as an IT leader, really thinking about
the group that's going to be deeply involved in helping lead through the change is
really, really important. And again, back to that,
because you might have identified the vendor or you might have originally kind of
been an important part of the process of choosing a vendor, people are going to
look at you for the success of the vendor.
So, making sure that you're not the only one on the hook and making sure you have a
great team around you is going to be very important for the success of the change
and kind of surviving it personally, honestly.
And creating a vision of success. What will the world look like when we
do change is a really important part of this, and I have heard the best practices
here are, it wants to be simple, it wants to be tangible, really something you can
kind of imagine and picture.
Also, a vision that's somewhat flexible.
It's really important for people not to picture a new world that's only in their
mind. It wants to be a shared vision across the coalition, across the greater
community that's affected by the change.
But it can't be rigid because it's going to be an emergent thing,
and kind of you're imagining a better future together, and you want to crystallize
that vision to whatever degree you can.
But at the end of the day, you don't want it to feel like there's disappointment if
it's not exactly kind of the picture you imagined.
So, building in flexibility while having clarity of vision is really
important.
Communication is going to be a big part of what we talk about here today.
You cannot communicate enough.
And number five, empowering others to act.
The way Kotter really talks about this primarily is about removing impediments, and
I think this is a great thing you can do as an IT leader, is really
getting rid of blockers, moving through things, and getting things out of the way
for the people dealing with change.
Creating short-term wins, having a lot of milestones, and really not thinking of
things as this binary thing as an IT leader. "Okay, I set it up.
People have their accounts, training's scheduled, job here is done, change
happened." Not exactly how it tends to go.
So, really kind of laying out a vision that is going to grow over time.
And then really thinking about this as something that needs to be consolidated and
isn't really complete until the new thing is just how it's done, and that's when
change is really complete. It's when
it's anchored in the culture and the kind of new way becomes just the way it is.
So, to speak to urgency a little bit and the big why thing here.
To speak to the why,
one famous thinker in change management,
Lewin, talks about this kind of idea of you need to give up the past, you need to
kind of unfreeze, then you're in this kind of murky, weird zone in the middle, and
then you need to reconsolidate around a new vision.
And that's similar to the way Kotter's framework starts, which is like, first
people need to say that the current, the status quo is problematic.
We need to give up something that isn't working, and that's the reason for
change. And that can be an unfun thing, and that involves a lot of looking in the
mirror and saying, "We have a problem in our current operations." And that's
something you're going to need to remind people of through the process and remind
people of the why. It's about like, what's currently painful in our process?
So, really, an important part of thinking about this too very tangibly is when
you're evaluating vendors.
I remember when we were early in this business, we got really excited when a strong
IT leader kind of bulldozed the sales process through, made it happen fast, and
like, "Oh, this is great." Then we were like, "Oh, we're actually selling people
all along the way." Making sure that you're bringing people along in the sales
process is very, very important for them to kind of reflect on the problems that
they currently have. ... and for them to buy into a change, because that's what's
going to make building this guiding coalition really work.
So, I do think that you really want your guiding coalition to start
being formed as you're evaluating vendors before you commit to change,
ideally.
People are excited about it, they're bought in at all levels in the organization.
And
Kotter's thinking talks a lot about what makes a good guiding coalition, because
again, I think this is just paramount to success.
One thing Kotter talks a lot about is you need folks in position of power, so
kind of an executive sponsor. That might be you in your IT leadership position.
That might be the head of school. It might be a divisional head.
It might be a functional leader, depending on what kind of vendor you're thinking
about swapping out. But someone in a position of authority really putting their...
kind of co-signing it and saying, "Hey, this is what we're doing." And
with buy-in in a kind of well-informed decision alongside the folks who
are actually going to be in the day-to-day and have the functional knowledge to
know whether this is a good decision and the nitty-gritty details of what it's
going to take to change. So really,
thinking about... Kotter talks about as diverse a coalition as
possible, and this is diversity of potentially levels in
hierarchy in an institution, but also, ideally, hopefully there are both men and
women involved. Hopefully there are people in different functions who are being
affected. The more diversity in a guiding coalition, this has been well studied,
the more likely it is to be successful.
So you just want a lot of voices represented in your guiding coalition.
And again, if they've bought in for the why and they were kind of bought in early
in the process, it's going to be easier to pull them in to be kind of co-leaders in
the process with you.
This is a fun one to me because this is also, again, a study.
It's a little bit social science-off, but the number's amazing because it's
basically like, you should communicate 10 times more than you think.
And they kind of studied all these different changes and what went wrong, and
people feeling like, "Hey, you've done this before, right?" Like, "I never got that
email. I didn't know this was supposed to happen.
No one told me." And then you're like, "Actually, I told you four different times."
Well, if you think you should send one email, you should send 10 emails.
If you think you're going to have to have one meeting, you probably need to have 10
meetings. 10 is literally the factor by which leaders tend to
underestimate the need for communication.
And again, it's coming back to that why again and again.
And ideally, this communication isn't coming from one person.
It's coming from different members of the guiding coalition, different folks with
different goals and responsibilities, different expertise.
It's really important to have a really
kind of a broad group conveying the different messages around the change, being
really consistent about it over time.
I think this one's a little bit obvious, but it's really important to just not
treat this as just one big splash change, right?
Especially, we have a cross-functional platform, we have a lot of different user
groups we work with, and one of the best practices in change is to
actually change one user group at a time and really show one group
being very successful and then having more groups learn from them as quickly as
possible. But doing everything at once just can create just like a lot of...
If everyone's in the dip at once, it can create a lot of kind of fear.
But if you have some folks who are kind of beyond the implementation dip, and the
dip is basically, "I started a new thing.
I'm obviously less competent than what I was when I was doing the thing I'm used
to." So even if I'm going to something better, I'm currently incompetent.
If everyone's feeling a little less confident at the same time, it's really hard.
So when you have people who have started to gain the benefits of change, the other
folks who are about to go through change are kind of inspired to work through that
trough in a different way, and that can be really helpful, and this is another
thing that's been really kind of studied in a lot of different ways.
This slide is a little bit outside of the Kotter framework for change, but
really interesting, and we see this in practice in a lot of different ways, and I'm
sure you have too, kind of like
surprising resistance. And there's a lot of
kind of people representing a willingness to change explicitly, but then kind
of not actually committing to a change.
And there's this amazing thinker, Robert Kegan, who wrote this book, "Immunity to
Change." I've actually been to an Immunity to Change workshop, and it's
really cool. They ask you to think about a change you might want to make in your
own life that's been hard to make, and
usually what they find is that your stated desire to change
is, you're like, "Of course, I want to quit smoking, whatever, but I can't,
I can't, I can't." Obviously, that's a complicated one, but
there's often a hidden desire that is being satisfied by not changing.
So, I think the common one we run into in change management is like, "Yeah, no, of
course I want to switch to the new platform. I know it's better.
I'm excited about it." But when you're actually going through it, there's this
feeling of incompetence, and you
don't want to feel incompetent. That's a really weird thing to say.
So this kind of unobserved desire or an unobserved need is
highly... It makes it really hard to change.
So, this is like a really common thing in trying to break habits.
It's like, "Why, when I know I think I want to change, can I not?" It's like,
"Well, are you sure you really want to?"
So,
the guard railing against kind of people,
to ground it again in our world,
we're in a highly regulated space in health records, and the risk of losing
documentation is like traumatic and it makes people very afraid.
So there's this kind of like really good desire to protect that might not
be kind of... You might not even be kind of in touch with it consciously.
So anything you can do as a leader kind of managing folks through change to help
people kind of protect against and guardrail against kind of
hidden desires. And I think that one of the takeaways here is just like, don't be
surprised when people are resistant, and it can be for a lot of complex
reasons. And just because someone says they want to do something, there can be
something under it that's really, really scary that can be hard to express,
especially in a work context where people need to present as very confident and
kind of gathered.
Another thing here that's, there's a kind of concerns come in a predictable order
is the work of Holland Horde, and the main takeaway of that is like everyone is
basically very selfish when it comes to change. They're like, "Yeah, cool.
This is going to be better for the kids," or, "It's going to be better for the
whole staff." And really, folks need to get through like, "How will this affect me
personally?" And only when they understand how it's going to manifest in their
day-to-day can they start to kind of grok how much impact it's going to have
more broadly. So like, folks are very selfish in kind of moments of change,
and that's okay, that's good. It's just good to be aware of.
So- I'm going to pass it off to Cassidy shortly, who's going to talk about some of
the, how we think about vendor change management at August Schools, some of the
watch outs for us. But one thing I meant to say in the beginning,
it's part of this kind of accountable, responsible thing that I think IT leaders
get themselves into for vendor change.
It's like,
and part of what we're trying to shine a light on here is the complexity of change,
how much psychology is involved in it, building that guiding coalition.
It's like someone's going to need to lead the change within the institution.
And
I think sometimes that's not explicitly part of the IT role.
Some of the schools we've worked through, they have operations managers, they have
folks who it's their job to do these types of things.
I would just encourage you to maybe like, if I don't know the name of the person
leading this change, it's probably de facto you.
And data and permissions and access is just not going to be the only part of it,
and really being thoughtful about building that coalition to be successful is
really important.
With that, I'll hand it to Cassidy, who's going to bring this down to earth
a little bit.
Thanks, Pete. Yeah, so now that we've talked a little bit about the change
management framework, I'm going to apply that to, like we mentioned, software
onboarding, and I'm going to use us as an example with an EHR onboarding.
So we've broken this down to kind of four pillars, right?
Data, workflow training, permissions and access, and families and the school
community.
You as IT leaders, you're very familiar with the data and permissions aspects, as
Pete mentioned. The pain actually is most likely going to be during workflow and
training, right? This can be difficult for teams when they have established
processes or those Google Sheets that they're very attached to, as Pete mentioned.
We need to work together to rebuild and rethink those workflows to make the
platform work for them. Last and certainly not least, families in the school
community, often forgotten because they aren't here with us in the room or in the
building. They're often though a main, like a key decision when making this switch.
A better user interface, better functionality, streamlined communication,
especially for us, platform security.
So we always encourage our schools to have a plan for communication and training
for families, and that it's not just end users and that they're kind of lumped into
that group as well.
So to briefly touch back on pillars one and three, because the areas you're
familiar with already, data, we sync with student information systems on a nightly
basis. We also augment all of that data with legacy records, right?
That could be coming from old systems, our previous platforms, Google Notes or
Google Docs, OneNote. It could be a variety of different sources for that data.
And where you will need to collaborate with the team especially is deciding kind of
what stays and what gets archived, right?
There's a lot of information that we bring in during a transition like this that is
something the team may need to reference if a certain situation arises, but most of
the time it really is just that, it's a reference.
We need to look at a physical from three years ago.
Not necessarily what we want to see when we open a student's record, but we want it
there for us if and when we need it. So, talking through that with you and on
IT, but also bringing that to the teams and talking through what do we want to keep
live and what do we want to kind of move to an archive or an inactive status that's
reference only.
Some really important decisions there.
For permissions and access, sounds just exactly as it is, making sure everybody can
get logged in, they have single sign-on, it's nice and secure, making sure they're
ready for training, and that those decision makers that you group together for this
coalition, making sure they have the appropriate permissions to make those
decisions and make those changes in the platform, and that it doesn't all have to
be routed through you if that's not kind of the agreement you've made with the
team.
Going back one slide here, just a second, Pete.
For transition planning, one thing that is often forgotten with permission, in the
unfortunate event that a team has turnover during or very shortly after an
onboarding, it's always important to remember to make sure that there's other users
beyond just IT who can manage users, just in the event that everybody gets locked
out unintentionally. All right, we can go ahead.
So, as we mentioned, workflow is usually where the pain happens during a transition
like this. It's not necessarily a learning issue or that just that it's a new
platform. This is where teams can have difficulties making decisions.
So again, during that coalition, teams often spend time with us
live on implementation calls trying to make decisions, but often realizing the
teams that actually are impacted by those decisions aren't even in the room, right?
So we want to make sure that we're making and thinking about those workflows before
we even get together on a call. So what can you do from an IT perspective to make
this more successful? Host an internal meeting before setup or implementation
begins. Before anybody gets to training, we want to make sure everybody's on the
same page and talking through policy, protocol, what needs to remain the same,
where are there opportunities for improvement, and are there things, again, that
the team's are holding onto because that's what they're comfortable with, but it's
actually inefficient and kind of hurting their day-to-day.
Coming into your first implementation call with some clarity around these, and you
don't have to have all your decisions made, but having clarity about who's going to
be impacted, what are your school's policies, what's your workflow, that will put
you kind of one step ahead when it comes to this onboarding experience.
We have tools to make it as smooth as possible, but ultimately it is for your
school to decide. So this is where you might need, for an IT perspective, you might
need to step in and help them make decisions that are going to result in adoption
and long-term success.
Some decisions to expect here, who can see information, what information can they
see, what kind of data are you capturing or collecting, and where are, again, there
improvements or opportunities for improvement on your workflows, but what workflows
don't need to change or shouldn't change?
So through all of these discussions, somebody needs to be in the room who has the
authority to make that decision on behalf of the team.
Now, for teams with a leader, so very clear kind of organization, they are like a
nurse leader, right? We like to partner with them first to make those decisions,
kind of get everything configured as a starting point before opening it up.
For example, like working with a nurse leader, we want to work with them to
establish the forms that go to families, but also their documentation that they
want their nurses using on a daily basis.
So we want to make those decisions, get that configured, and then open it up to all
of the end users to make sure they're kind of focused and they're only seeing what
they're actually going to be using on a daily basis.
Because some schools are organizationally flat, not every team has a leader,
that might result in you stepping in to help, again, make those decisions.
So if that sounds like your school, as Pete mentioned, there's a gap there, you
might need to fill it to help them kind of come to a decision and establish policy.
And just like that can be difficult with teams with a process, they have a current
platform or process today, it can be equally difficult for those without one,
right? Counseling teams, if they're coming from paper, they've only ever documented
in notebooks before, there can be a lot of anxiety around visibility and access to
documentation when we're thinking about switching to an electronic platform.
So acknowledging that concern and those anxieties, and getting ahead of that and
being the leader that can kind of shepherd them along can really make the whole
onboarding run smoother.
Now, once we start to make these kinds of decisions, that's where we start to get
into kind of the meat and potatoes, right? We're getting into the training.
We want to show them how they're going to use the platform to complete their
day-to-day tasks and apply all of these workflows in the platform.
To train, we do this by group. So each team and user gets their own dedicated
training materials, live session with us, answer questions, to make sure they're
feeling well-informed.
How this rollout occurs is really up to your school.
So, from an IT perspective, again, it's important to look at the teams and think
about what would be the best rollout strategy.
Pete had mentioned kind of starting with one team and then letting them spread
their success to others. So, like starting with a counseling team who doesn't have
a platform today and letting their success and excitement in the platform spread to
those that maybe are a little bit more hesitant or they already have a platform,
like nurses or learning specialists.
Getting them excited about opportunities to collaborate and streamline their
day-to-day conversations and emails into a single platform, using real-life
examples is going to be really successful here.
Some teams with more, schools with eager teams, they kind of choose to onboard
everybody simultaneously,
and that's perfectly fine. And for both of these rollout plans, we follow a common
approach where we train the trainer.
So, we onboard one person from the school or the team, and make sure they can take
that to the rest of the team to execute the training.
An example of this recently, I worked with a team in Ontario, all-girls school,
through the spring and summer. We trained one person at the school, and then when
everybody came back in for in-services day, that person led the training, and I was
here more of as a backup for additional questions or concerns maybe they couldn't
answer during their trainings.
So, whichever route you take, we use a method of I do, we do, you do.
We show the group how to do it, you do it together as a group, and then everybody
takes it independently on their own.
We also understand people have different learning styles. Some people are tactile.
They want to learn in the platform.
They want to click around and access through trial and error.
Other teams, maybe they're a little bit more hesitant.
They prefer kind of written materials or going through a full how-to video
before they get access and try it on their own.
So, in order to solicit this, we certainly provide training materials through
different mediums, right? Short help center articles and how-to videos, longer form
training content, so that each user can find the best fit that aligns with their
learning style.
Thinking back to Pete's discussion about communication and small wins, we use a
project management tool to help this transition, right?
We want to keep everybody aligned and on the same page.
We also want to track those milestones and checkpoints.
And like Pete mentioned, it's like each one project is a variety of individual
projects in itself, right? So, we want to keep teams and the momentum going by
allowing them to mark their tasks and responsibilities as complete to kind of keep
the excitement going and the satisfaction of marking your to-do list off.
This tool also helps teams keep and track project progress for
everybody involved. It's not just often one team doing this.
It's a variety of teams. So, it's helpful to see kind of where everybody is so they
can collaborate and talk with one another, and make sure everybody's kind of going
along and keeping up with the project plan.
This also helps break the project into smaller pieces, keeping it all very
manageable. We want to make sure that we're acknowledging that training and form
building, they're two distinct phases of the project.
So, it just makes it a little bit easier to plan. That's okay.
You can go to the next slide there. So, when we're talking about timing, right,
this goes hand-in-hand with the project management tool. It isn't always linear.
Sometimes we're looping back around and kind of going and running different phases
of the project at the same time, right?
So, a platform change like August Schools, it's a variety of individual projects.
So, we try to recognize everybody. Everybody in every team has their own go-live.
How you sequence them is up to you. A common workflow we see kind of aligns with
the school calendar in that documentation and changing that is much more
difficult mid-year or mid-semester.
So, that might be a more natural transition to run when the school year change has
happened, versus something like re-enrollment forms for families.
That usually happening in the spring, that's another opportunity for teams to kind
of time and align their rollout to the school calendar.
So,
and thinking about that too, for families with go-live, it's important too to
remember that some teams keep their team on their current platform.
Even though families have transitioned, they keep their team on their current
platform for day-to-day workflows, and then we'll transition them later.
And all of this, keeping in mind, there's usually long blocks of time between these
phases. We launch forms, but we're not actually charting until the fall.
So, just plan for kind of refreshers on training and daily tasks
in between these times and kind of approaching the time of the back-to-school time
of year.
Again, allowing all of this to take the transition in bite-sized pieces.
And when we're thinking about timing too, even after go-live, your account manager
will help track progress and make sure your team are getting value out of the
platform. So, we help track usage to make sure teams aren't just attending
training, but they're actually following through and using the platform in the way
that we designed it for them to be used.
If we see concerning trends, we always bring it back to the team and so that we can
kind of regroup, talk about where are their blockers, where are their adoption
concerns, so we can build an action plan together.
And although this transition happens, there are changes that happen after the
school year begins. Like November, this time of year, many teams, they've settled
in for the school year now. So, this is when we start to see things starting to
change slightly. So, decisions they maybe made at the beginning are starting to
shift, right? So, like templates are changing, dropdowns are expanding or reducing
them to get better data out of the platform, reports to see trends.
Those kinds of changes start to happen as well.
So, a team of counselors, maybe they originally decided, "We want to keep all of
our notes locked down. We don't want to see everything everybody's doing," because
of those privacy concerns we talked about earlier.
Maybe they had an unplanned absence and then couldn't access each other's notes.
So, because of that situation and that real-life experience, they decided,
"Actually, we want to see each other's notes, not because we want to look at them,
but because if something happens, we want to have easy access to those."
So, those are all great signs of an onboarding going well, right?
The team is making the platform their own.
They can make decisions early on, and then after seeing and kind of working with
it, it opens the door for more changes and decisions to come later.
All right. So, that brings us back to our fourth pillar here, and that is
communication with families and the school community.
So, we talk about families often a key reason why you're making a change like this,
but they're not in the building. So, communication, this is where
over-communication is very important, right?
Having a clear plan on when that communication is going to go live, who is it
coming from, to make sure the families feel well-informed too.
So, we've seen a handful of different approaches kind of go well here.
We had a school who, in their email signature, they put a little blurb about August
Schools and that they were transitioning next school year to August.
That helped get families, anytime they got an email from the nurse, they got a
little bit more accustomed to the August Schools name and the logo, so it wasn't a
big surprise when that change happened.
Others have decided kind of more scheduled announcements that they roll out with
their forms is the best way to communicate with their families.
So, we had a school in California who, they start their form collection very early
in the calendar year. So, right before the holiday break, they announced that they
were going to be switching platforms, and they actually did a phased rollout with
their families. So, just like different teams can join at different times, they had
new families start and did re-enrolling families later in the spring, just giving
more time for them to educate and inform their families through the spring.
Other teams just prefer just like one announcement going out shortly before their
forms, short and sweet, and then they kind of force the families into it.
Keeping in mind, we're also going back to training here.
Like, we want to make sure families are being trained on how to use the platform.
They are end users ultimately, and that they're completing kind of documentation
for the teams that use the platform on a daily basis.
So, it's really important that they have a good experience.
So, we're sure to give you kind of prompts and training materials that then you can
use to then turn around, make specific to your school and team, and make sure it's
a nice transition for your families. Change is hard. We're here to help.
And we want the team to see value quickly, right?
So, although it can be daunting, how well that up, change management plan's
important before we start onboarding.
Great. Chloe?
Yeah. Thanks, Pete and Cassidy. I'm Chloe from August Schools as well, and I just
wanted to open it up to if anyone has any questions, you can feel free to either
write those in the chat or unmute, and you can ask that way.
So, while that's going on, we also have a companion guide that will be coming soon
that we are co-publishing with Atlas as well, and that's going to go into some
of the theory that was brought today, some of the grounding as well, and then there's
going to be some checklists as well. So, it'll be like an interactive guide.
We will email that to you all. We're also interested if anyone has anything they'd
like to share with our team via email, maybe not here, any questions you have, you
can feel free to reach us at hello@augustschools.com.
We love to hear what your experience have been like with change, things that have
been challenging or easier or gone well. So, yeah.
Are there any questions?
Thanks, everyone, for joining. Really appreciate y'all spending time with us.
Have a great Thanksgiving next week, and hope to see you all down the road.
Indeed. Thanks, everybody. Thank you, Pete and Cassidy and Chloe.
Thanks for this great presentation. We really appreciate it.
Thank you to August Schools for all your support.
Again, we appreciate that as well.
To our attendees, if you joined a little late, so the recording will get sent out
tomorrow, and as soon as the shared resource is ready, watch your inbox because we
will be promoting that as well and getting that out to everybody.
We're excited about that. So, another thanks to August Schools for that.
And if anyone has any questions about any of it, you can reach out to August
Schools or reach out to us, and we will connect you with August Schools happily
about other services and products. We're grateful. Thank you all so much.
See you, everyone.
Take care.
Takeaways
-
Build Diverse Coalitions
Form a cross-functional guiding coalition early during vendor evaluation to ensure shared buy-in and prevent IT from bearing the sole responsibility for success.
-
Overcommunicate the Why
Communicate the reasons for change roughly ten times more than initially expected, consistently reinforcing current operational pain points and the vision for the future.
-
Structure Software Transitions
Break platform migrations down into manageable pillars covering data, workflows, permissions, and family communication while aligning rollouts with the school calendar.
-
Manage Workflow Friction
Host internal meetings before setup begins to establish policies, evaluate legacy processes, and help teams make decisions that ensure long-term platform adoption.