Behavioral Health

Building a Practical AI Foundation for Children's Behavioral Health

How a behavioral health provider went from AI overwhelm to a clear strategy with internal champions, governance policy, and a phased Copilot rollout. Here's what that actually looked like.

CLIENT
First Children Services
Family-owned behavioral health provider delivering life-changing outcomes for exceptional kids
First Children Services
Behavioral Health
Industry
M365
Platform
Strategy
Engagement Type
Phased
Rollout Approach
"Automation Tactics helped us cut through the noise and build a realistic AI strategy that actually fits our organization. They guided us in standing up internal AI champions, developing an AI governance policy, and rolling out Microsoft Copilot strategically. We now have a clear timeline, budget, and success metrics for our long-term rollout."
Matt Hess, CEO, First Children Services

The Challenge: Everyone's Talking About AI, Nobody Knows What to Do

First Children Services faced the same problem as most mid-sized organizations. Leadership knew AI could improve operations. Vendors kept calling with promises of transformation. But nobody could explain what AI implementation would actually look like for their specific situation.

The internal team didn't have the expertise to separate realistic opportunities from marketing hype. And with limited IT resources and a workforce focused on delivering life-changing outcomes for kids (not technology), the risk of wasted investment was real.

What This Looked Like in Practice:

  • Vendors promising transformation without explaining the actual work involved
  • Staff unsure what AI tools they could use or how to use them appropriately
  • Microsoft 365 already in place but not being used to its potential
  • No framework for evaluating which AI opportunities made sense

"We kept hearing about AI, but nobody could tell us what it would actually look like for our organization," said Matt Hess, CEO. "We needed someone to help us understand what was realistic and what was just hype."

The Approach: Four Pillars of Practical AI Strategy

Here's what actually happens when you build an AI strategy that fits your organization. Not vendor promises. Reality.

PILLAR 1

Creating Internal AI Leadership

The goal wasn't to rely on external consultants forever. It was to build sustainable internal capability that would last long after the engagement ended.

1. Formed an AI Steering Committee

Cross-functional leaders who would own AI decisions. Not a rubber-stamp group. Real authority to evaluate opportunities and allocate resources.

What This Changed:

"The steering committee changed how we think about technology decisions. We're not just reacting to the latest trend anymore. We have a framework for evaluating what makes sense for us."

2. Identified Internal AI Champions

Staff members who could support their colleagues through adoption. Not IT specialists. People who could answer day-to-day questions and help others get comfortable with new tools.

The Part Nobody Mentions:

Your best AI champions are rarely who you expect. They're the people already finding workarounds, already curious about new tools. The job is finding them and giving them structure.

Related: Internal AI Leaders Program

PILLAR 2

Developing an AI Governance Policy

Before rolling out AI tools, First Children needed clear guidelines for responsible use. Not a 50-page legal document nobody reads. Practical rules that staff would actually follow.

What the Policy Covered:
  • • Data privacy requirements specific to children's behavioral health
  • • Appropriate use cases (and what to avoid)
  • • Human oversight requirements for AI-assisted decisions
  • • Compliance considerations for healthcare and behavioral health
  • • Review process for evaluating new AI capabilities
In Human Terms:

"The governance policy gave our team confidence. They know the guardrails, they understand what's expected, and they're not afraid to start using the tools."

Related capability: Company-wide AI Policy

PILLAR 3

Strategic Microsoft Copilot Rollout

First Children already had Microsoft 365. Like most organizations, they weren't using its full potential. The question wasn't whether to add AI. It was where AI assistance would deliver the most value for their specific workflows.

Think of It Like This:

Buying Copilot licenses for everyone at once is like buying gym memberships for your whole company. Some people will use it daily. Others won't touch it. Smart rollout means starting where the impact is highest.

What Most Companies Do
  • • Buy licenses for everyone
  • • Hope people figure it out
  • • Wonder why adoption is low
  • • Question the investment
What First Children Did
  • • Assessed workflows for AI fit
  • • Prioritized by impact and cost
  • • Started with high-value roles
  • • Built internal expertise gradually
What This Meant:

"We discovered we were sitting on capabilities we'd already paid for, and Copilot gave us a clear next step. Automation Tactics helped us turn those on in a way that made sense for our team and our budget."

Related capability: Access to Approved LLM (Copilot)

PILLAR 4

Developing a Long-Term Roadmap

Strategy without execution is just a presentation. The roadmap translated vision into phases with realistic timelines, defined budgets, and measurable success metrics.

What the Roadmap Included:
  • Phased implementation - Clear milestones for each stage
  • Budget allocation - Costs tied to specific outcomes
  • Success metrics - How to know if it's working
  • Decision points - Where to evaluate and adjust
The Part Nobody Mentions:

The plan acknowledged that AI adoption is iterative. Success comes from learning and refining, not from a single large deployment. Each phase included checkpoints to evaluate progress and adjust course as needed.

The Outcome: From Overwhelmed to Confident

The real measure of AI strategy isn't the plan itself. It's whether the organization can execute without constant hand-holding.

Here's where First Children stands now:

Clear
AI Strategy
Tailored to their size, budget, and capabilities
Published
Governance Policy
Staff know the guardrails and expectations
Trained
Internal Leaders
Knowledge and authority to guide adoption
Phased
Copilot Rollout
Starting with high-impact users

What Actually Changed:

Leadership has a framework for technology decisions
Steering committee evaluates opportunities against clear criteria instead of reacting to vendor pitches
Staff aren't afraid to use AI tools
Governance policy provides clarity on what's allowed and expected
Champions support adoption from within
Internal experts answer questions and help colleagues through change
Budget and timeline are defined
No more guessing what AI will cost or when benefits will materialize
The Part That Matters Most:

"We went from feeling overwhelmed by AI to feeling confident about our next steps. That shift in mindset was as valuable as any specific recommendation."

Matt Hess, CEO, First Children Services

Key Takeaways: What You Can Apply to Your Organization

1. Build internal capability before buying tools

First Children didn't start by purchasing AI software. They started by forming a steering committee and identifying internal champions. The tools came after the capability to manage them.

See: Internal AI Leaders Program

2. Governance enables adoption, it doesn't block it

The AI policy wasn't about saying no. It was about giving staff confidence to say yes. When people know the guardrails, they're more likely to experiment within them.

See: Company-wide AI Policy

3. Start where you already are

First Children didn't need a new platform. They needed to use Microsoft 365 better. Copilot built on infrastructure they'd already paid for. Sometimes the best AI strategy is maximizing what you have.

See: Access to Approved LLM (Copilot)

4. Phase the rollout based on impact, not convenience

Not everyone needs AI tools on day one. First Children prioritized roles where AI assistance would have the greatest impact. This avoided overspending while building internal expertise gradually.

See: Steering Committee

5. Plan for iteration, not perfection

The roadmap included checkpoints for evaluation and adjustment. AI adoption is iterative. The organizations that succeed are the ones that learn and refine, not the ones that try to get everything right the first time.

See: Change Management Program

Want to Build Your AI Foundation?

Stop wondering where to start. Get a 30-minute consultation where we'll discuss your current state and identify realistic next steps.

See where your organization stands across 8 key AI capabilities