Why I Chose Partnership After Trying to Build AI Alone

By Kyle Carlin, Director of Special Education, West Central Kansas Special Education Cooperative

When I first started exploring AI tools for special education, I did what a lot of tech-forward administrators do. I built my own solution.

I created an AI chatbot using our own development resources. This eventually became Scout, and staff used it to answer questions that used to only come to me. Early feedback was positive, but building the tool was the easy part. The real work was figuring out a solution that could be used with student information, not just generic questions.  This required a focus on data security and FERPA compliance that went beyond my technical skills. After looking at a few options, I learned about Creatively Focused at a conference.

After a couple of conversations with their staff, I decided to partner with Creatively Focused to move Scout from a homegrown experiment into a sustainable AI support system for special education staff.

The Challenge of AI in Special Education Workflows

Like most special education directors, I was watching my staff balance individualized student support against documentation demands. Progress reports, evaluations, IEP amendments, prior written notices, meeting preparation. It adds up quickly.

I believed AI could reduce some of that burden. But there was an important distinction I did not want to lose sight of. AI can generate compliant work relatively well. It does not generate individualized work well without thoughtful structure, guidance, and human oversight. That tension sat at the center of what I was trying to solve. I was not looking to replace professional judgment. I was looking to give staff better tools so they could spend more time focused on students and less time on repetitive administrative tasks.

I was also increasingly concerned about educators turning to public AI tools without district guardrails. Even when information is redacted, there are legitimate concerns about sensitive student information being reverse engineered or improperly exposed. I wanted a FERPA-conscious environment where staff could safely access AI support built around our actual workflows.

Why Building District AI Internally Became Unsustainable

At first, Scout lived on our own infrastructure. From a technical standpoint, it worked.

But over time, I became uncomfortable with what that responsibility meant. Once we became the ones developing, maintaining, and hosting the system, the liability sat with the district. Suddenly, I was not just serving as a special education leader. I was navigating infrastructure questions, security considerations, maintenance planning, and long-term technical sustainability.

That was not where my energy was best spent. I did not need to become an AI engineer to bring responsible innovation to our staff. I needed a trusted system and a partner who understood the realities of education. Creatively Focused offered a closed-source environment, a security structure, and an ongoing support model that let us keep innovating without placing the full technical burden on the cooperative.

Why I Kept Adoption Optional

One of the most important decisions I made was keeping Scout optional.

I never wanted teachers or related service providers to feel forced into using AI. I wanted them to choose it because they found it genuinely useful. From the beginning, I viewed Scout as a professional resource, not a mandate. People solve problems differently, and I wanted this to become one more trusted option available to staff.

So instead of requiring participation, we invited volunteers. That decision played a major role in the rollout. Buy-in developed organically because people experienced value firsthand. Creatively Focused later told me our volunteer-based approach became a reference point they used with other districts.

That matched my philosophy from the beginning. If a tool truly helps people, they will continue using it. If it does not, no policy will save it.

What Happened After Launch

As usage expanded, staff engaged with Scout across the categories I had hoped they would. 

• Accommodations. 

• IEP amendments. 

• Academic goals. 

• Intervention planning. 

• General compliance guidance.

I also noticed a change in my own workload. Fewer repetitive questions came directly to me. That told me staff were finding answers and support independently through the tool. It freed time for deeper leadership work while staff still felt supported in the moment they needed it.

One staff member integrated Scout into her workflow almost immediately and started talking about it with colleagues without being asked to. That kind of adoption matters. When educators find something that genuinely helps them do their jobs more effectively, they share it.

How I Encouraged Staff Adoption

I wanted adoption to feel supportive, not heavy-handed.

When staff emailed me a question that Scout could answer, I would sometimes respond by saying I had already thrown it into Scout, and I would include the response it generated. That gave people a simple reminder that the tool existed and showed them I trusted it enough to use it myself. I kept Scout visible through small reminders in weekly staff communication. Over time, that repetition helped people connect Scout to the other reliable support systems available to them throughout the workday.

People should get support in the way that works best for them. The goal was never to replace human leadership or relationships. The goal was to make sure staff had another dependable avenue for guidance when they needed it.

How Partnership Improved Long-Term Support

Working with Creatively Focused gave us support structures that would have been difficult to build internally. 

• They updated content. 

• They surfaced usage trends. 

• They helped us identify gaps and improve workflows. 

• They pushed us to think strategically about long-term adoption rather than initial excitement.

One of the most valuable conversations centered on reducing friction for hesitant users. Adoption is not just about first impressions. People will use a tool once, find it helpful, and then forget to return unless the next step feels immediate and accessible. The partnership helped us shorten that distance over time.

Building Something Sustainable

Even as I prepared to transition into my next leadership role, I remained committed to this model because the long-term value had become obvious.

Trying to hand off a fully self-managed internal system would have been far more difficult. The partnership model created sustainability beyond a single administrator or leadership team. That mattered to me. This was never just about experimenting with AI for a single moment. It was about building support that could continue helping staff over time, even through leadership changes and organizational transitions.

Why I Would Make the Same Decision Again

I still believe educational leaders should explore innovative tools that can improve staff support and efficiency. But the strongest long-term solutions are not always the ones districts build entirely alone.

Choosing a partnership meant choosing a FERPA-conscious environment where staff could safely engage with AI tools designed around special education workflows. It meant inviting educators to opt in rather than forcing them to participate. It meant trusting that when a tool genuinely helps people, they will continue using it because it makes their work better.

Educational leaders do not need to become AI engineers to bring innovation into schools responsibly. They need trusted systems, clear guardrails, and partners who understand the work.

Kyle Carlin is the Director of Special Education for the West Central Kansas Special Education Cooperative.