From Tech Director to Interim Scheduler
Navigating the Surprise
Presented by:
When the registrar and database manager at Marlborough School left in June, Director of Technology Matt Norko became interim scheduler. In this ScheduleX-sponsored session, he and Sahil Bhargava, ScheduleX co-founder and CEO, explain why scheduling that depends on one person is a continuity risk and outline four steps: a retrospective, documented scheduling rules, registration review, and a decision matrix.
Transcript
So welcome, everyone. Today we have a really great session for you, very,
very popular. We have lots of people attending and signed up for this one, and we
are going to be talking about From Tech Director to Interim Scheduler: Navigating
the Surprise. So, today's session is brought to you by ScheduleX, and we have
Sahil, the co-founder and CEO at ScheduleX, and we also have a very familiar face
around the Atlas area. It's Matt Norco, who is the director of technology at
Marlborough School. So, very glad to have both of these gentlemen joining us
today. Welcome, and thank you for being here.
We're excited to hear from you guys today.
Thank you. Thank you for the introduction, Ashley. Hi, everybody.
Just to introduce myself again, my name is Sahil. I'm co-founder at ScheduleX.
Prior to this, I worked at a learning management system company, but I always
wanted to build something of my own.
I didn't know what to build, and that's when I met my co-founder, Kristen, who's on
the call, and we started ScheduleX.
So now we work with private schools on scheduling, and we worked with Matt, and we
have something interesting to share with you.
So we're going to sort of start talking about that.
But Matt, do you want to just quickly, for those of you who don't know you,
although everybody does know you, just quickly introduce yourself, and then we'll
start?
Absolutely. So, thanks for having me. I'm Matt Norco.
I'm the director of technology at Marlborough School here in Los Angeles,
and it's great to be here.
As everybody knows, and sort of the topic of the webinar is quite self-evident,
from tech director to interim scheduler, and that situation and privilege and honor
was given to Matt this past summer. So I want to just kick it off.
There's no background on this except the question on the screen, which is, Matt,
how exactly, and at what point in the year did you become the interim scheduler?
Somebody asked me before this webinar, "How does that happen?
Is that even a real thing? How does that happen?
What are the circumstances leading up to it?"
Yeah. So, at our school, we had the registrar and database manager as one
person, one position, that is in the technology department.
And so, we were super lucky. She was an awesome person, and
she just announced that she was leaving.
And it was one of those situations where we took for granted that she did it, and
it worked, and at the end of the summer, there was a schedule.
And it just kind of happened behind the scenes, and nobody really necessarily knew
all of the pieces that went into it.
And she announced that she was leaving late in the year and left the Friday of our
closing meetings. And so,
there's never a good time to lose your database manager and registrar, especially
when that is usually when that scheduling work is going to begin.
And so, that's kind of how it ended up with me.
And don't get me wrong, plenty of support from lots of other people, but we didn't
have enough time to get a replacement registrar hired before that process could
really begin, and so we had to start working on it.
And, as we'll talk about, there are a lot of things that we learned along the way
very quickly and some very late.
Yeah. And for everyone's benefit, what time of the year was this?
I mean, this was-
June 4th was the-
June 4th
... sort of last day.
Right.
So, yeah, right at sort of the beginning of when you would be working on schedule
for the following year.
Yeah. And you know what? So thanks for sharing that.
And the reason
this webinar is something that we sort of wanted to do is that a lot of schools are
actually running the same risk, and they don't realize.
That's why we wanted to share this with them.
So I'm going to drop something in the chat.
Just going to drop a link, and again, you don't have to look at it right now.
You can download, look at it later. But two things I want to share with you.
So the context is that we recently published a state of scheduling and benchmarking
report. Turns out there's not a lot of literature on scheduling.
What are the benchmarks? What are the performance outcomes you can get?
Both in terms of outcomes as well as process. We don't have a lot of that.
So we did some of that work. But two things I want to call out that were very
relevant. The first was this.
Two-thirds of the schools, and the sample was 48, so again, I understand that this
was not the whole independent school market, right? But it was definitely a start.
Two-thirds of schools have only one person that does scheduling.
Two-thirds, approximately 62.5%, right, they said that nobody could build the
schedule if the scheduler left. They could definitely say that, and there were a
bunch of maybes there as well. So it's safe to say that this is probably around
70%, right, where schools had a single-person dependency.
And we saw that across the board. But here's the other stat that makes life
complicated, and this is really, the combination of these two is quite lethal,
which is that most of these schools used to schedule by hand.
So they were used to hand scheduling.
83% of the schools were touching a manual process.
In fact, in the spirit of full disclosure, these yellow boxes that you see, other
tools, it's actually a hand scheduling tool, we just, for intellectual honesty
reasons, didn't call it that in the report.
But the reality is that 83%, even more schools than that, are really, really doing
this by hand, which means that there's one person who's a heroic scheduler doing it
the way they are doing it. But the other side of that coin is that nobody knows how
it's happening. Nobody really knows what's going on.
And when that person leaves, you have a bit of a situation, especially if it's in
June, because then somebody else has to pick up the process, and they don't know
where to start. So this was the background with which I think Matt became the
scheduler. And the first question I want to ask before we dive into the specifics
and before we go into the details of what you did, why is this a technology
problem? And the background on this is that,
at ScheduleX, I talk to a lot of schools about this.
If I've had 100 calls, almost all of them have an academic person, but only 40% of
them have a tech person. So I see a pattern where I don't always see the tech team
being involved. So Matt, what are your thoughts on that?
You've worked at four schools. In which schools is it a tech problem?
In which world is it an academic team problem? How do they come together?
Yeah. So,
just by virtue of how our department is organized, right?
Again, that database manager is the registrar, and that person is in the tech
office. And so, I think, when you talk about who owns that process, that's kind of
one of the reasons why it rests a lot in technology here at Marlborough School.
And I think this is also one of those situations, just like we think of all
these other systems in a school, where tech is responsible for the system itself,
not necessarily the data or how the system's used.
And so, it was really clear that we didn't really have a process, and we didn't
really have all of the systems set up so that academics could do the pieces that
they needed to do. And so, I think about this now just in this...
one product or the advanced database that they're using a different product.
We have some oversight to make sure that the systems themselves are working and the
data can flow to where it needs to flow.
And then whether or not you're registered as part of the tech team or part of
academics, that person then can actually get in there and do the work that they
need to in order to create their schedule and do the fulfillments that they need to
do. And like you said, at different schools, this has worked different ways.
And I've been at four schools, and two of them are set up this way, where the
registrar and database manager is part of the tech office, and two of them have
been the other way, where the registrar and database person is in academics.
And no matter what, there's really a lot of inspiration that goes on, partnership
that goes on, to make that work happen because it's so tightly part of the rest of
the systems of the school. So even if the position really lies with academics, tech
does still have a role to play from a systems perspective in making sure that all
the pieces are in place in order for that academic work to happen successfully.
Yeah, that makes sense. And the other aspect of this is that,
to the extent people know the details of scheduling,
I would ask a follow-up question. Are there parts of the process that certain teams
should own or parts of
the, I don't want to say function, but parts of the sequence that certain teams
should own? Is there a framework or something that people should keep in mind?
For example, these kind of things, academics can do.
These kind of things, tech should do.
What's the ideal way to do this, in your view?
Yeah. I think just understanding, obviously, the process of scheduling, and I know
we'll get into some of these specifics, but whether or not you're talking about
course registrations and where and how those are happening, and then where is that
data, right?
How are you able to use that or move it between systems?
And just who needs to be part of the decision-making tree, I think, is another
piece to think about, because there are going to be rules about the schedule that
are completely academic, and then there may be some other rules that are more space
constraints or things like that. And so, some of these, I think
the whole point of this, right, is that a lot of this work happens in one person's
mind or on one person's calendar, and systematizing it as much as you can
is ideal for making sure that the school is set up for success.
Because obviously, every school is able to churn out their schedule, but
to the point you made earlier, if that person leaves or there's an issue with that
person, how is the school going to be able to respond?
And having more people involved in that process, and at least somebody
managing the system as opposed to carrying out the individual tasks, I think, is
the piece that would be helpful for us to focus on here anyway.
And I think one of the things that, and I would love your thoughts on this, one of
the things that you all at Marlborough struck a really good balance with or
developed along the way as you were approaching this was that, hey, if you think of
scheduling as a process,
there's two parts to it. I mean, of course, I'm simplifying it.
There's many parts to it, but there's two big parts to it.
One is the master schedule, which is teachers, classes, and rooms, right?
That's how you're managing resources.
The other side of that is once the master schedule's built, and again, most schools
do a two-step process, so they do one and then the other.
Therefore, the other side of that is getting students in those classes.
Is that a useful or helpful way to sort of think about the distinction?
Like, for example, which team should own fulfillment, which team should own what
side of things? What do you think about that? Is that a helpful framework?
Yeah. And a really important distinction, and one that, quite frankly, I didn't
really think about or know before this process really happened.
And so I was trying to do both at the same time, not really thinking through,
obviously, there's some pretty serious implications when you're trying to do
fulfillment and the grid at the same time.
And as a school, I think one of the benefits to talking about this is that
you get to understand a little bit more about what the priorities are.
And if you're a school whose priority is to get 100% fulfillment, that's going to
affect what the master schedule looks like, that actual grid.
Versus if you're trying to make the grid work so that all of your
teachers have their spots and then you'll fulfill kind of as needed, that's
a different equation, right? But having that conversation ahead of time obviously is
super important. And we were one of those schools that did the grid
by hand, and so we have all the old versions of our grid.
But what's not there is the logic or reasoning why it is the way it is,
right? You can see the grid, but you can't see that this particular class or block
is in this spot because of some rule that exists at our school, right?
And so we don't have... There was not really a way to tie those rules to why the
schedule looked the way it did, which complicated when I was trying to do the grid
and the fulfillment at the same time.
And ultimately, that's where I needed lots of other help at the school, and we have
some great resources here to get it done.
But
that was a conversation that, unfortunately for us, wasn't documented and didn't
come out until really late in the process, and that sort of affected everything
that we did.
That makes sense. And the grid, again, just for everybody's benefit, because we can
nerd out about scheduling terminology all day long.
It's not that interesting for many people.
But the grid is, again, your teachers, your classes, and your rooms.
So think of that as a resource allocation part of the pie.
And again, the second part is students in those classes, which is fulfillment,
request fulfillment, course fulfillment, et cetera.
The difference between these two, and again, to build on top of what Matt has said,
the conversation you probably want to have or the distinction you want to draw, not
the conversation, the distinction you want to draw is where does your school find
the balance between being a student-driven schedule or a teacher-driven schedule?
Now, it's a tricky balance, and every school finds it differently.
But the answer to that question or the balance to that equation is what will
determine what parts are owned by tech and which ones are owned by academics.
Typically, that's what we've seen play out.
Continuing on, so Matt, now this is your problem, right?
Like June 10th, this is your problem. You have to deal with it.
Where do you start? I mean, I have a bunch of questions on the next slide.
I don't want to overwhelm you. I've got so many questions, but where do you start?
What's step one and two? And then I'll sort of take it from there.
Well,
I can tell you what I thought steps one and two were, and then at the end, I think
it really wasn't, right? And what I thought steps one and two were, were get the
course requests and try to build the schedule based off of them.
And it turns out that that really wasn't it, right?
And I think all those questions that you have on the next slide really get at why
that's not step one and step two.
As it
turned out, I didn't even know all of the information I didn't have until really
later in the process, which unfortunately sort of doomed me from the beginning, if
you will, because I didn't even realize that I was working with incomplete
information. And again, that's the whole, you got to nail down the process part,
right? But obviously,
realistically,
me.
But I think, let's go into your questions, because I feel like this is going to be-
Yeah.
It'll help out.
Perfect. So let me... I don't want to overwhelm you.
Let me start with a specific one, and then of course, we can sort of free flow
this. Because again, I'm trying to somewhat think from a tech director's
perspective, and I think the first and the most relevant question, which
I think you put in a lot of effort at, is expectation management.
So the question is, whose expectations do you need to manage?
And this is cool, as stakeholders, how do you manage those expectations, and what
does expectation setting and management look like?
Yeah. So super, that was definitely something that we had to work on
here, because
again, the schedule just happened in the past, and our registrar was great at
making it happen. And I don't necessarily think anybody knew
what lengths she had to go to in order to make the schedule happen.
And
when she left, one of the things that we needed to do is talk to our division heads
and say, "Okay, what are the priorities? We're going to do this.
We don't have her, so if the schedule's going to look different, then are we
okay with it looking different because our fulfillment's not going to match?
Or are we okay saying, if something's a rule, that that might not be able to be
honored?"
As it turns out, there's also lots of other people that needed to be involved, and
expectations really could have been managed.
And again, having not gone through the process before, it was one of those
situations where I don't think I knew what I didn't know.
And
one of the most... Actually been to sit down and talk about this together, where we
kind of discussed what were the priorities, so that way we could then set those
expectations. Because at the end of the day, your schedule's not 100% for
everybody, so somebody's going to not be thrilled with the end result.
And
I think the people, the leadership of the school needs to understand that if we're
trying to do this, here's the implication over here, and are we okay with that or
not? And if we're not, then we have to obviously adjust.
While you were managing those expectations, and again, let's say,
somebody on this call has that situation, you got to manage expectations.
For their benefit, could you give examples of some expectations that are either
hard to fulfill or cannot be fulfilled, or you were surprised by?
Yeah, so I think for us, a lot kind of went around the rules, right?
And so, we have certain scheduling rules that are requested, right?
And so we have a languages class that is an introductory language class, and
it's four different languages, and there's five teachers.
And so,
having a common planning period for those five teachers is really important.
In reality, that may or may not be possible, right?
And if that's sort of a hard rule,
then that means that those teachers' schedules and the rooms that they're in, it's
going to have a domino effect, right?
And depending on what else they're teaching, it may or may not be possible.
And so,
for us, a rule like that, and there's plenty of them, if you have
more than one teacher in one room or sharing a room at their location, does the
room need to be free for one block of your day, or can both teachers be out if we
need the room for a third teacher, or whatever those rules are.
And
it's not always possible, right? If you need to put a class somewhere, sometimes, I
guess, that just has to happen, obviously.
But when we built our schedule,
the way that we ended up making things work is unfortunately by not honoring some
of those rules. And so for us, I think that that's
one example of how those expectations, I think it would have been
great at the beginning of the summer to say, "Yeah, we're going to try to do that,
but we might not be able to because of XYZ." And again, I didn't know what I didn't
know, and so I didn't do that at the beginning, and that also is not helpful at the
end of the summer when all the teachers are returning.
So that was not great for me.
And I think the part of the trick here is, again, you said you don't know what you
don't know, so you're expected to do something that either is impossible or, and
people will find this, I mean, if they do this at their school, they'll realize
some of those were not done anyway. They were good to have.
So again, we can get to the solutions side of things later, so that also happens.
But my follow-up on this, or rather the flip side of the same question is, did you
notice implicit expectations or things that were not explicitly communicated or
defined but were expected and wanted? And what could examples of that look like?
Yeah. That was another one that came up.
Again, this goes back to the documentation.
It always happened before, whether or not it was written down sort of on our
registrar's internal notes or whether or not she just did it as part of the
process.
I created a schedule, and our folks looked at it, and after they looked at it,
they're like, "Oh, these two, this history class and English class need to be
cohorted." Well, that obviously has some pretty serious implications for the rest
of the schedule.
And so a history class, yeah, so we had that situation where
the whole...
and another grade where all of the history classes and English classes had to line
up by section too. And so, again, that has
some pretty serious domino effects.
And those were rules that existed that nobody even mentioned until after the
schedule was built, and then we had to kind of start over again.
And the time delay, especially at the end of the summer when things were being
released, is not what you want. And so, there's a lot of these
unwritten rules that existed but not
documented.
And so, all of them, unfortunately, are not minor things.
They're massive things. And even some of the just how information was communicated,
and again, this goes back to where these things are being collected, and so the
data portion is, we know that certain robotics
teams, for example, need to be in a particular group together, or we know that
research students need to be paired with a particular
mentor. And so, that information wasn't being collected and communicated on the
front end, but again, that has implications for where those blocks are going to be
and what those students' schedules look like.
And so,
yeah, I mean, there's definitely a lot of uncommunicated, really
impactful rules that
popped up afterwards where they weren't there,
which is not the best way to discover them.
Yeah. And in the beginning, I mentioned that on approximately 40% of the calls I
speak to the tech team, one of the questions that I always get from tech folks,
always, without fail, because again, they're thinking in terms of infra, they're
thinking in terms of systems, they're thinking in terms of redundancies, is the
question of, maybe this is not the right word, but I'm going to say the question of
equity or equity/balance, where my question to you out of this is,
did you notice while you were doing the process,
do there tend to be certain departments or certain cohorts of individuals that were
consistently absorbing the trade-offs or some sort of trade-offs where, because to
make something work, it's not going to work out for them, and it seemed to happen?
Did you notice something like that?
Yeah, that definitely did happen.
And again, I think that was one of the things where it'd be good to talk about
these as a group to really go back to that expectation setting.
The way that it works for us is that our department chairs will give the room
assignments, or they'll give
any specific requests or things like that.
And
they're not all the same, right? So one department might be requesting specific
things about rooms. Another department might be specifically requesting something
about the schedule, whatever it might be.
And there are certain constraints that obviously make sense, like a part-timer
can't be on this day or that day, but then there's other constraints that are a
little difficult to honor. So, we have language classrooms where
the teachers were moved, and the two teachers that are together teach higher-level
Spanish. And
it's a situation where we have too many sections to fit in the room, which means
that one of the teachers who's stationed in the room can't teach in the room, but
then the other one can. And so, it's just that kind of leads to some inequity in
that type situation. But then at a higher level,
which of those decisions should be up to the department chair, which of those
decisions should be up to the division leader?
We had a lot of classes. I think our languages department is the one that got hit
the heaviest, and probably because they have so many students that take any
particular language versus another one.
And even in some of those classes where we might only be running, so like our
Chinese program, we have not enough students really for two sections, and so we
run one bigger section, which means that they can't really fit in the
classroom that they would normally be in, right? And so, that's a struggle too.
And so even something like that, like class size, if we're not going to be firm
about when that's getting cut off, and what does that mean for the students as
well?
It has all these, again, downstream effects where it's the classroom-specific or
whatever it might be.
Yeah. And finally,
which of these problems, because I think one, again, I'm going to summarize all of
this in the solution side of things, so don't worry, everybody. We'll get there.
I know I just have one slide and not really any points because we didn't sort of
plan the talking points. But Matt, one of the things I also wanted to know, because
this, I believe, can really help schools out, is which of these problems start
before scheduling starts? Which of these are pre-scheduling problems or rather data
problems? We can talk about it in different ways, but which of these look like
scheduling problems, but really they started way before?
And it would be helpful for a director of tech or anybody, really, to know that
could happen. Where was this for you?
Yeah. So, I think
pretty much all of it can happen beforehand, and it didn't.
We were really good about meeting as department groups
with the academic leadership side and kind of looking at our requests and then
building schedules.
And I think that was one thing that's a little misleading because, again, the
requests aren't all in the same spot.
And so, when we had
middle school electives, for example, those were collected in Google Form versus
the academic stuff, which was collected in our Blackbaud course request process.
But then we had upper school English electives, which are done in a different
Google Form, but only the English electives.
The other electives are done in Blackbaud.
And then, again, there's all that information about
that's being communicated just via an email.
"These kids should be in this robotics class," or, "These kids should be paired
with this mentor for research." And so there's all these different
spaces where this data exists, and it's hard to have those meetings when
not all that data is there.
And then, I want to also emphasize, I think that add/drop data should be
included when we're thinking about this.
We ended up with a situation where we had
three sections of one class, and so many kids wanted to
add the class that this was, I think, one of our history classes.
So many kids wanted to add it that we really should have had two sections, but it
was too late. And this seems to be one of those things where if we have the data
points to suggest that there's going to be a higher add request for these
particular things, that that data be thrown in with the registration data to
understand realistically
what those sections could look like or should look like, especially if you're
trying to own them. So, I think from that data perspective, that's definitely a
beforehand thing.
Rules, and I think kind of understanding those at the beginning, especially if
those are changing, is super important and definitely better to nail down
before you honestly try to build that master schedule grid, and then you can think
about fulfillment. But
all of those things can be done ahead of time, and one of the things I think that
forces it to happen more naturally is that more
people know about them, right? Again, it's not that these things weren't happening
at our school, they were, but one person kind of knew the situation as opposed to
more people knowing the situation.
And then just that allows to have the documentation there for the school to rely on
if they need it, and not have this process just be with one person.
I think data flows is different, and all of this is data, but data flows,
especially on graduation requirements, on what students need to graduate.
I mean, they have to have that. There's no two ways about it.
That's one of the most compelling reasons why you do definitely need tech teams
involved, because they are managing systems and data from a variety of
perspectives. So, I mean, that's very helpful.
And I think we spoke about so many specific things.
I just want to, for two minutes, just hope to give people an idea of how complex
this problem is, because a lot of times, the metaphor that I get is that this is
like a puzzle. It's like a puzzle. It's a really hard puzzle, 500-piece puzzle.
Yeah, but it's not a puzzle.
I have a different metaphor which looks something like this, and I believe a lot of
us know what this is. We've probably seen this before.
It's a Rubik's Cube, where every move affects all the sides.
You cannot do this sequentially. For example, if you've ever played with one of
these, you know that you cannot start with red and then do yellow and then do blue.
It doesn't compute. It doesn't work that way, right? You can't do it sequentially.
It's got a million small decisions because everything's impacted, and to really
solve it effectively, you need a method.
You need some method, and anybody that does a good job of solving a Rubik's Cube
has some method behind it, right? And I use this analogy because scheduling at your
school, just for your mental model if nothing else, is like a Rubik's Cube, where
imagine if, say, the color green was what students wanted.
Top choice, request fulfillment, graduation requirements, and such, right?
Request fulfillment's one color.
Teacher constraints is another category of colors, like back-to-back classes,
common preps for departments where they want their homerooms.
Your courses become a separate category, a separate color, like sections, single
terms, APs, co-run courses, et cetera.
Rooms is a big one, right, where certain spaces have certain kinds of constraints.
That becomes a color of its own. Capacity constraints, shared spaces, the
scheduling rules, which we will touch upon, but the infamous rules, balancing
classes and sections, right? So, a lot of the time, your team, your school will
expect that if you've got two sections of algebra, both of them should have 10
kids. You cannot have one class with five kids and the other with 15 kids.
That's another constraint category.
And all of this impacts the mission of the school, right?
Equal access to students and tuition.
It's really like a Rubik's Cube where every piece affects everything else, and you
can't do it sequentially. You need some sort of method.
And with that background, if I told you, "Hey, you know what?
Do it using Post-it notes or spreadsheets." I don't know anybody who's done a
Rubik's Cube using spreadsheets or Post-it notes. It's really hard, right?
It's naturally very hard. Like I said, the prospect sounds unachievable, so you
know you can't do that.
And the result of both of those things is that, in a very realistic sense,
your school is probably ending up solving some sides of the cube, and you need to
know which ones they are. For example, and most commonly that we have seen,
teacher constraints will get solved, because if staff is unhappy, they'll tell you
about it. You will hear about it. So, teacher constraints in terms of
preferences, requests, et cetera, will get solved. Room is a hard constraint.
It's a law of physics. You can't fit in more students beyond the space you've got,
right? Or you can't have a biology lab class in the library. Can't do that.
So, there are a few things that are visible on the surface that will get solved.
Naturally, it's a partial solution to the big picture, but you must know what
you're solving and what you're not solving.
And I think that awareness and mental model is very beneficial because it really is
like a Rubik's Cube and not like a puzzle. A puzzle can be done piece by piece.
This is not one of the things that can be done piece by piece.
And with that in mind, I think let's just move on to, hey, what can schools do?
So, the practical side of things, the takeaway side of things. What can schools do?
Or if you're on the webinar, where do you start, and what can you take away from
this? So, we've broken it down to four steps, based on, of course, Max's process,
what we've seen at other schools. And the four steps are retro, documentation,
registration review, and decision matrix.
So, we'll sort of go over them one by one, and let's start with the retro.
So, while you have the current person... So, Matt, you want to just...
Maybe I can talk about this, and I would love to get examples of this to make it
sort of real for people. But while you still have the process running the way it
is, there's something you can do now. You don't have to wait till June for this.
Understand the key decisions that were made last year and why.
What were the decisions that were made? How were they made? Why were they made?
What are the constraints sort of driving those things?
Which of those preferences are needs and wants?
Needs and wants is going to be a big theme, because you might get complaints for
wants and not needs. But given that it's a Rubik's Cube, you can only account for
the needs if you're doing it by hand. So, big, big distinction.
Identify the legacy assumptions.
You will also notice as you do this, a lot of legacy assumptions sort of build in.
And relatedly, individual likes and preferences are different from school
priorities. So, Matt, to sort of make this real, any examples or any use
cases sort of come to mind that can speak to some of these?
Again, just to make it real for folks.
Yeah, no, I mean, I think kind of a few of them all together really are just that
our master schedule grid is usually based off last year's grid.
And so, whether or not...
So, I think some of those steps we just don't really ever talk about.
Even if talking about them just results in continuing, that's fine.
I think we, as a process, have not done this as a school.
And so, why decisions were made this year is something that you should think about
before going through the process for next year, because not every year is the same,
right? Whether or not all those Rubik's Cube individual pieces, they may not be the
same, teacher blocks might not be the same, our teacher constraints might not be
the same, the rules might be different, et cetera.
So, really understanding why those decisions were made, super helpful.
And I think what typically happens is that those legacy assumptions then are just
built into the schedule. So, for us, we have an electives block for our middle
school that is just on in these two particular blocks.
And- I think we just take for granted that those two blocks, one's on one day,
one's on the other day, those are the elective blocks.
And that kind of makes the whole schedule work a particular way for our middle
school. But to be honest with you, I don't know the assumption or whether or not
that's an actual need. And I don't think we've necessarily talked about that
either. And so, that is one of those things that's like, yeah, that would be
helpful to explore to understand really, is that a need or is that just something
that has happened because it always happened that way?
And if it is, could changing that help the schedule in other ways that we would
want to see happen? And so I think that's one of the things that's helpful.
And some of those legacy assumptions are going to be for that bottom point, which
is the individual likes, dislikes, right? And not the school priorities.
And
that is one of those situations, again, where if I talk about it in the next one
when we get to documentation, that's how you suss that piece out.
We need to identify the school priorities and school leadership and department
leadership need to all be on the same page.
And I think that is something that ends up leading to a lot of this retro work that
happens.
I want to build on top of that, to your on the points two, three, and four, with
another example. We were working with a school on the East Coast,
and somebody from the different setup, so tech was involved, but academics was also
involved. But anyway, they were reviewing the constraints that go in, right?
Because they were using our software to do it, so they were in a position to review
it. And one of the questions that I remember the assistant head of school asking me
is, "Hey, why is this statistics class not happening at this time?" And my response
was, "Hey, I mean, I don't know. That's what your scheduler put in as a
constraint." And she said, "Aha, because the scheduler is the stats teacher and
personally does not prefer to teach at that time. Please take that off.
That's not a constraint for our school." So, things like that happen, and I think
it's good to sort of be aware. I mean, you can definitely accommodate or not
accommodate, but it's good to be aware of that, of understanding what the current
process is.
Yeah.
The second one, and again, we've both, Matt and I, have entered this multiple
times, but to get specific, your school has a scheduling policy whether you know it
or not. And the goal of documentation is to figure out what that policy is,
hopefully get to an ideal policy, but definitely figure out what the policy is, and
that has four parts to it. The first one is document your school's scheduling
rules, and more than that, rank order the priorities that you want.
This is probably a big one because if you start asking everybody on what they would
like to have, you're going to get a list of 101 items.
The trick over here is to be able to rank order them in terms of what do we as an
institution want first, second, and then third, right?
That sort of a system works, is absolutely required.
Otherwise, you will run into a situation where somebody else would have taken a
different decision, and that may or may not be acceptable.
Matt, anything that comes to mind on the documentation?
Because I mean, I can definitely sort of describe, show something that's kind of
more detailed, but I want to get your perspective on this.
Yeah, no, the rules are super important.
There's two things I think that are really important.
So, for the rules, for example, one of the things that we ran into, not ran into,
but one of the rules for us was that we
were trying to balance teacher loads.
So we have a block schedule that is four blocks on one day, four blocks on the
other day, and our teachers are
teaching four blocks. So you would typically try to split that and go two and two.
That is a rule, that we're trying to balance that teaching load for our teachers.
But
if you do that, that's going to have certain schedule implications.
And so ranking whether or not that preference for teacher schedules outranks
what it should look like on the student schedule side is really important for the
school to prioritize, right? Only one can be true.
If the schedule needs to work in the way that teacher
is on one day and one on the other, or all four on one and none on the other, is
that acceptable or not? And that's going to have an implication on what the student
fulfillment piece looks like. And so that's an area where a hard
rule might actually be a soft rule because you might want to make sure that the
student fulfillments are happening more than making sure that a teacher's schedule
is balanced, even though you don't want to unbalanced teacher schedule.
But from the school's perspective, one has to be more important than the other in
order to build the schedule correctly.
Yeah. And if people need-
Yeah.
Yeah, please go on. Sorry, go
on. No, no, no. Yeah, this is a good example.
Just an example, because again, this may be strange vocabulary if you haven't heard
this before, but these are the questions you have to ask, where there's going to be
a category of things, as an example, courses that just run together.
Spanish and honors Spanish. It's really the same room, same teacher, same time.
Different course code for transcript purposes, but they really run together.
You want to ask every department which courses are running together, and which of
them absolutely need to, and which of them are optional.
Relatedly, you also, this is very common in middle school, for example, you want to
ask your team, or departments, "Hey, do we have courses that, for example, students
can only take one of them, or students need to take both of them?" For example,
labs and science courses with labs typically require students to take both.
So your data will reflect them as individual requests, but you do need to take
both. Very commonly in middle schools, there's something called cohorting.
So for example, in middle schools, everybody that took art in term one must
together, the same group, take music in term two, for example, right?
You will have courses that work that way, and you're going to want to ask those
questions before you start. And Matt, you were talking about the teacher side of
things, right? One luxury definitely you're going to get from your teams is, "Hey,
our department needs a common planning period.
Who is in that department that requires that group?" Right?
You're going to want to ask those kind of questions upfront.
Do leadership teams require a common planning period?
What is our school's policy on maximum back-to-back classes for teachers?
Do we strictly honor that policy? Do we honor...
Is it a soft constraint, a hard constraint?
Does it take priority over other things? Those are the kind of questions.
Just want to give everyone an example of the kind of rules we're talking about, but
these are the kinds of things that are required that will have to be documented one
way or another. Otherwise, people will not like the result of the schedule that
comes out.
Relatedly, a big area where everybody is definitely going to get tripped up, or
rather, let me take that back. 50/50 chance you get tripped up, some schools do,
some schools don't, is naturally everybody understands that every student's not
going to get something, but when they got to get something else, do you have a
rule-based assignment system of alternates, or is it just
whatever they could get into, right?
And you want to make sure from a systems perspective, from an equity perspective,
from a continuity perspective, from every perspective you can think of, to have a
rule-based assignment of courses.
For example, somebody is not getting into this class of Spanish, therefore they
should get into this other section of a language course.
It cannot be, or it shouldn't be, that somebody's taking those judgment calls, or
rather too many people are taking those judgment calls, because then all sorts of
other challenges come up. Your judgment could be different, you don't know how that
person exercised judgment, there could be potential for bias.
How do we know it was the right choice?
You want this to become policy that everybody has signed off on.
So as you start documenting the rules, ranking the rules, having rule-based
alternates, and relatedly, anything that was a one-off judgment call in the
retro, like whatever you think was a judgment call, worth building that into a
system. Anything that comes up as, "Okay, I could have taken that decision
differently," needs to become a policy, and that needs to get signed off by
everybody on the team. And there's no... You must get that signed off.
So Matt, you want to talk about that side of things?
Yeah. So this is another one that,
this is more on the fulfillment side, and so sort of a little outside of tech, but
I think one of the things that this piece,
one thing that became apparent in this piece, and especially later in the summer
when it was released, when the schedule was released to students, is not only the
alternate, or the assignment of alternate courses, but-
Who needs to be involved in that conversation is really...
That was a piece that was, I think, hard for us to really nail down.
And what I mean by that is, if a student is requested in physics, for
example, but then they change their mind and they wanted to be in AP physics,
right? Is that a student registrar question?
No, it's not, because somebody needs to approve them taking an AP course.
And who do you need involved in that decision? Is it a department chair?
So for us, it would be a department chair first, and/or the division head, and then
whatever it is. But also, we're a high school, so some of those decisions need to
be in conjunction with the college counselors as well, because if they needed
certain courses for their college path, then those alternate courses might not
be the same for everybody. And so, even just understanding who's available to have
the appropriate conversations throughout the summer is really important, and I
think knowing that ahead of time is something that you need to do, right?
And so, during summer, your department heads are not working probably, and so if
these questions come up, how do you deal with that, right?
Is somebody designated to answer or not? And how does...
You talked about earlier, like the graduation requests, and I think this will kind
of come in in the next one, but what does that process look like for alternates
that allow you to actually put those kids in
those classes?
What's going to happen is, the process of documenting the rules, rank ordering them
with your teams together, these rule-based assignment conversations, all of this
will become the scheduling policy.
I mean, the fact is it already was scheduling policy.
Somebody was doing it, just that one may or may not have known that was happening.
So this becomes policy, and it's best to get it signed off, because then this is
something that everybody can discuss, and they can collectively verify, audit, and
improve, and determine if that's advancing the school's mission or not.
Moving forward, registration review.
This is one of the more practical sides of things, but yes, Matt, you were saying
graduation requirements, right?
How funny would it be if you're building a schedule and turns out a student did not
request a course they needed to graduate? Does that ever happen?
Yeah, so funny. It happens a lot , as it turns out.
But I will say, beyond even the graduation requirements, because that I think is,
that's a pretty easy piece to figure out.
Put that in your process somewhere, like when those are being audited.
But for us, so going through this process,
one of the things that we realized is that there was no registration review
built into our process. And so, we had
350 add/drop requests that are happening the first two weeks of school, which is
insane. And obviously, every single one of those requests has a domino effect
with the schedule, and really does...
It may not be possible or it may force your sections to be too big or unbound,
however the implications are. And so for us, one of the things that became very
apparent at the end of this process this year was that sometime next year,
we need to build in a registration review where students are actually
acknowledging, and in some cases parents maybe are acknowledging, that these are
the courses you requested. Because when we're having those staffing
discussions in the spring, we're basing them off the assumption that the
registration requests are correct.
But then if in August the students are saying, "Oh, I didn't mean to request that,"
well, that would have had an implication back in May when we were talking about who
was teaching what. And so, it's a really important piece of the puzzle that I
think, to one of your points earlier, really should discuss sooner, because if
you're waiting until add/drop to have these discussions, nobody's happy then,
because it's throwing off the sections, the kids may not be in what they want, et
cetera, et cetera. It's just a headache that you can head off earlier before it
even happens.
Absolutely.
And be able to address those graduation requirements, because that's a piece that I
think also happens is that, we might think that based on what they requested,
they'll meet graduation requirements, but if they then change that, they may not
then meet graduation requirements.
And so at least it gives you an area to catch that.
Yeah. And I would say the last one is the decision matrix.
Again, we've sort of spoken about expectation management plenty, but I mean, just
some questions to think about on this is, what kind of decision inputs will you
require from different administrators?
Which of those administrators need to be involved?
Who will own the scheduling process, the tech versus the academic discussion, the
balance that's right for your school?
I would say an important one is who will defend or justify the outcome if someone
is unhappy? Like, who's accountable for it? It's tricky, right?
Because relatedly, what are reasonable versus unreasonable expectations?
This is part of the scheduling policy.
Again, they're all sort of related, all of these points, but yes, this is an
important piece that will also have to happen.
Stakeholder management, for the lack of a better word.
Yeah.
So, yeah. Go on. Yeah.
No, I was going to say, these are questions that we didn't really have answers to
at our school. And so,
I was the one that had to get up and say, "I'm sorry, because I didn't have all the
right information and it resulted in not the best outcome." And, you know what
I mean? That is answering these questions and making sure
you have the things that we've talked about today identified and
figure them out for your school, helps this work at the end of the day, this
matrix.
Yeah. And so, to give you a starting point, I know we've said a lot.
I'm going to drop something in the chat, and I'm going to share my screen to show
you exactly what I've dropped in the chat.
We've built something that's called
the Scheduling Continuity Audit.
So I've dropped a link to the document in the chat.
You can get it, download it if you want. We basically asked 12 questions, right?
So we've broken this down into different categories of questions, like critical
operations, single points of failure, documentation, redundancy, ownership.
We sort of asked 12 questions. And this is an audit that you can do with your team.
So do it together, do it as a team. And
very candidly, reflect on, "Hey, are we doing this fully, partly, or not doing it
at all?" Score the points, and it's out of 24 points, and then see if you are
exposed to some sort of risk or not, right?
Again, feel free to download this. This is a free resource.
And it's just going to give you a starting point for all of the discussions and all
of the stuff that Matt and I have been talking about.
So I've added the link to the chat. Actually, I hope that everybody did get it.
It's not on the private chat. Perfect.
So, yeah, that was
it on that side. So again, I mean, a great starting point also, or rather one of
the things that schools do is use scheduling software, where this kind of becomes a
forcing function for people, where because you need to now be explicit about rules,
that they're not going to be invisible, they have to be on the surface.
You have to intentionally document them. Scheduling software helps.
That's what we provide at ScheduleX.
If you're interested for your school in doing some of this work, if this is
relevant, that's what we do. Again, helping solve the Rubik's Cube.
I love this metaphor.
Getting all the colors in the right order in the right sequence to find the right
balance for your school. So that's the kind of work we do.
I hope the webinar was helpful, the continuity audit was helpful.
And with that, we can take some questions if people have some questions.
No.
No questions. I guess that's a good thing or a bad thing.
Yeah.
One of those two extremes. But definitely feel free to reach out to us with
questions as well,
if you have any in terms of the process.
We believe that the continuity audit would be a good starting point.
Have that conversation, have it with your scheduler, have it with your admin teams,
department heads, division heads, associate head of school, head of school if
they're involved.
Those are typically the admins that need to make those decisions, because
ultimately this is scheduling policy.
It's a policy document that's going to get executed by tech and everyone else, so
getting everybody's agreement is the most important.
Sahil, Matt, thank you so much for being here with us today.
I think that you guys have uncovered something that is so big for just business
continuity. We're talking about this through scheduling, but I think this is really
elevating the role of tech as a strategic leader and a strategic thought partner on
the senior admin team, being able to bring back things like this.
We do have a question in the chat from Tina.
She asked, "Does the TGE software support K-8 scheduling?"
I believe she means does the software...
Ah, there you go. Sorry.
I thought we were doing something technical there. My apologies.
Yes, yes. We work with K-8 schools as well as middle and high schools.
Yeah, K through 12.
Tina, I thought you were asking a really deep jargon question, but...
Thank you all. We appreciate attendees, and if you guys have any further questions,
y'all feel free to reach out and stay in touch.
Again, you will see these guys not only engaging year-round with us at Atlas, but
also in person at the annual conference.
So we hope that you will keep that on your calendar and definitely come say hello
and talk to them there. But again, thank you all for being here with us today.
We appreciated it, and we'll send you guys out the archive and the resources soon.
Take care, everybody.