top of page
Search

Giving every employee a mentor,without adding headcount

  • Feb 27
  • 3 min read

Updated: Mar 1

Case Study: Douglas County School District (GA) 

















District Snapshot 

District: Douglas County School District 

  • Location: Douglasville, Georgia 

  • Size: Mid-sized public school district 

  • Roles using heyC: Teachers, Principals 

  • District leaders involved: 

    • Assistant Superintendent of Teaching & Learning 

    • Director of Instructional Technology 

    • Superintendent (Executive Sponsor) 


The Challenge 

Staff development was heavily centered on instruction, leaving teachers without real-time support for communication, decisions, policies, and day-to-day challenges. 

Douglas County has always believed deeply in staff development—but faced a growing gap. 

The district recognized that teachers needed support beyond instructional coaching. Yet most professional learning focused almost entirely on instruction. 

What was missing was targeted, real-time support across all aspects of a teacher’s role: 

  • Communication 

  • Decision-making 

  • Policy clarity 

  • Day-to-day challenges that surface outside formal training 


And this support was needed not just for new teachers—but for every teacher. 

The district was already using a productivity-focused AI tool (Gemini), but it wasn’t designed to support staff development across roles. It helped with content—but not with practice, confidence, or district-aligned guidance. 

At the same time: 

  • Human coaches for every employee were cost-prohibitive 

  • Qualified trainers were hard to find, expensive, and limited to one-time workshops 

  • Traditional PD didn’t provide support when teachers actually needed it 

Most importantly, Douglas County was clear on one thing: 

They did not want generic AI. 

Any system supporting their employees had to: 

  • Speak the district’s language 

  • Go beyond instruction 

  • Reflect district expectations 

  • Align with how Douglas County expects staff to teach, lead, and communicate 

 


What the District Needed 

The district needed a scalable way to support every teacher beyond workshops—one that worked in real moments and reflected district expectations. 

 

Douglas County wasn’t looking for: 

  • Another PD program 

  • Another tool teachers had to “figure out” 

  • Another generic productivity-focused AI 

  • Answers pulled from the internet 

They needed a solution that could: 

  • Act like a district-aligned mentor 

  • Scale to every employee, not just teachers 

  • Support staff without judgment 

  • Work seamlessly within existing district systems and content 

 

Why heyC 

heyC stood out as a platform purpose-built for staff development in districts, not generic productivity or content creation. 

 

heyC stood out because it was built specifically for staff development in districts—not productivity or content creation. 

Key reasons Douglas County chose heyC: 

 

heyC was grounded in Douglas County’s own policies, frameworks, documents, and language—so guidance reflected how things are actually done in the district. 

Focused on development, not productivity 

heyC supports learning, practice, and confidence-building—not just task completion. 

Not generic AI 

Responses reflect district expectations, not abstract best practices or one-size-fits-all advice. 

Built to scale without headcount 

Every employee can access support—without hiring more coaches or trainers. 

Training all employees and not just teachers 

Ability to train other staff and leaders and not just teachers 

 

How heyC Was Implemented 

The district took a phased, intentional approach to adding teachers in few schools, to all schools and then principals to ensure relevance, trust, and alignment with real school scenarios. 

The rollout was intentional and phased. 

Phase 1: Pilot 

  • Small group of teachers across a few schools 

  • District documents, policies, and instructional resources fully connected 

  • Focus on real classroom and communication scenarios 

  • Close feedback loop with district leaders 

Phase 2: District-wide teacher rollout 

  • Expanded to teachers across all schools 

  • Teachers began using heyC for: 

  • Classroom preparation 

  • Parent conversations 

  • Policy questions 

  • Daily, in-the-moment guidance 

Phase 3: Principals added 

  • Principals gained access for leadership conversations and decision-making 

  • Consistent guidance extended across schools 

  • Fewer bottlenecks for central office leaders 

Throughout implementation, heyC worked closely with: 

  • The Assistant Superintendent of Teaching & Learning - <NAME> (staff development owner) 

  • The Director of Instructional Technology <NAME> (systems integration and adoption) 

 

Impact 

Support shifted from occasional training to ongoing, in-the-moment development that staff could access when it mattered most. 

  • XX% of employees on the platform use heyC weekly 

  • Staff report feeling more confident and supported 

  • Leaders see fewer repeat questions and escalations 

  • Development now happens every day—not just on PD days 

Most importantly: 

Staff get help when they need it, without feeling evaluated or judged. 

 

How Douglas County Is Scaling heyC 

The district is expanding access across roles to make ongoing development and onboarding available to every employee.  

Douglas County is continuing to expand heyC across roles and use cases— building a system where every employee has access to a mentor, every day. 

For the upcoming school year: 

  • heyC will be introduced from day one for all teachers and principals 

  • heyC will serve as the district’s go-to platform for onboarding and ongoing support 

  • Additional district systems will be connected to extend access to more employees, including classified staff such as paraprofessionals and substitutes 

 

District Perspective 


“Development used to mean a workshop. Now it happens every single day—when our staff actually need it.” 


— District Leader, Douglas County School District 

 
 
 

Comments

bottom of page