"Everybody's working hard. We want to make sure they're doing the right work at the right time for the right people. Having everything housed in one spot is what lets you see whether that alignment is there, or where it's not."
When Dr. NaTasha Crain joined Marshall ISD as Assistant Superintendent of Curriculum & Instruction, she came in with a picture of what she wanted the district to be able to do, and a plan for getting there. Within a year, Marshall had moved its coaching, walkthroughs, evaluations, and PD into one system in KickUp.
This is the story of why they consolidated, and how they took on a big year without overwhelming their team.
Before KickUp, Marshall wasn't running three tidy platforms that just needed to be replaced. The work was happening in a mix of tools that had accumulated over years: coaching in one place, evaluations in another, PD split between a system and a spreadsheet, with no line of sight between them.
For Dr. Crain, the cost of that scatter was strategic. If PD was teaching one set of practices, coaching was reinforcing a different set, and evaluations were measuring a third, the district recognized that coaching, professional learning, and evaluation needed to reinforce one another in order to create instructional coherence across campuses.
Her framing was consistent: this wasn't a tooling swap. It was a systems decision. Before deciding what to build in KickUp, she named the questions she wanted the district to be able to answer. Where are teachers strongest, and where do they need support? Is coaching landing where the need is greatest? Is our PD aligned to what we're seeing in classrooms? Every form, every dashboard, every cycle would get designed backward from a decision someone needed to make.
With coaching, walkthroughs, PD, and evaluation in one place, the alignment that had been a leadership intention could become a leadership practice, and the questions Dr. Crain had named could be answered directly from the data.
A rollout of this scale usually fails one of two ways: staff get overloaded, or leaders lose faith in the plan when the first wave of pushback hits. Marshall avoided both, mostly by doing ordinary things well.
Marshall consolidated coaching, walkthroughs, PD, and evaluation in year one, but they didn't try to launch every piece on the same day. Campus leaders always had one thing to focus on, not four.
They designed learning around how their staff work. Tyrone Robinson, the district's K-12 Science Coordinator and Instructional Technologist, worked with Marshall's KickUp CSM to build async training resources teachers could complete on their own time. Principals and instructional coaches got role-specific paths into the system, so nobody was learning things they'd never use. And because the platform was easy to use, staff always had a knowledgeable colleague on hand.
They built the data dashboards with the people who'd use them before they began using the system.
Tyrone sat down with the math coordinators and asked what they needed to see on a Blue Bonnet math walk. He was after what was useful at a glance, not every possible detail. He set it up so leaders could slice the data by grade level, by school, by evaluator. The dashboards were tools campus leaders had helped design, not reports handed to them.
The most visible payoff shows up in principal meetings. Marshall built a dashboard that puts their coaching feedback model next to T-TESS, so district leadership can see in one view whether coaches are working on the same instructional practices that evaluations are measuring. The connection that used to be anecdotal is now sitting in front of them before the conversation even starts.
A second dashboard quietly changed how principals managed their own work. When campus leaders could see their walkthrough and evaluation completion numbers next to one another's, the dynamic shifted. HR didn't need to send the reminder anymore.
The compliance numbers reflected the shift. Marshall completed 35 evaluation cycles across all staff in year one, well past the minimum. The work didn't get heavier. It got faster, so leaders could do more of it.
Across the district, patterns that used to look like a single-campus problem could finally be checked against the rest of the system. Three campuses with the same need was a district-wide PD decision. One campus was a coaching conversation. For Marshall ISD data was never the destination. Better instruction was. They wanted every walkthrough, every coaching conversation, every professional learning session, and every evaluation to reinforce the same instructional expectations so teachers experienced one coherent system of support.
Marshall is heading into year two as their first full year with everything running in one place. The plan is to consolidate walkthrough forms for more consistency across content areas, add Blue Bonnet reading to the walkthrough system, and lean into KickUp's AI features for coaching and evaluation write-ups.
There's also one more lever in play. Texas's Teacher Incentive Allotment turns alignment between coaching, PD, and evaluation into a financial decision, not just an instructional one. For Marshall, that's where year two leads.
Marshall's year offers two things worth taking with you if you're staring at a fragmented stack and wondering whether to consolidate.
The first is that consolidating is a strategic decision before it's a technology one. Dr. Crain didn't arrive and start evaluating platforms. She arrived with a picture of what she wanted the district to be able to answer, and picked a system that could hold all of it. When coaching, walkthroughs, PD, and evaluation live apart, the district ends up doing a lot of work that doesn't add up. Bringing them under one roof is what lets alignment become visible, and visible alignment is the kind that holds.
The second is that a rollout of that scale lives or dies on the change management, not the technology. Marshall did the ordinary things well: staggered training so campus leaders weren't overloaded, made async resources so teachers could ramp on their own time, sat down with the people who'd use the dashboards to help design them, and handled the predictable pushback with patience. None of that is technology. All of it is what keeps a big year from overwhelming your team.
Marshall ISD's first year wasn't simply about implementing a new platform. It was about building a more coherent system of instructional support. By aligning coaching, Learning Walks, professional learning, and evaluation around a shared vision of quality instruction, the district created a system where data informs action, leaders speak a common language, and support is intentional. Marshall ISD's experience demonstrates that lasting instructional improvement isn't driven by a single initiative, but by aligning every support around a common vision for teaching and learning. That's what makes improvement sustainable.
.svg)
You can't trust everything you read on the internet.
.png)
