The Crossover Episode: What Child Welfare Taught Me About Systems That Move Together

When systems thinking crosses sectors

Rethinking regulation through systems, workforce, and collective capability:

A lesson in cross-sector transferability.

“Well, this wasn’t on My Bingo Card.”

If you had mapped my career ten years ago, cannabis regulation wouldn’t have made the list.

My foundation is in Health & Human Services, specifically child welfare. A field shaped by decades of reform, federal oversight, practice model redesign, and continuous change. It’s a system that knows how to rebrand, rebuild, reinvent, reform… wash, rinse, repeat.

At the same time, cannabis regulation has emerged rapidly across the country, with states like Illinois building integrated regulatory systems from the ground up. So, stepping into a public sector space that’s still defining itself, still building, felt like crossing into entirely new territory.

In many ways, it was all new. The statutes, policies, and processes all differ from what I'd grown accustomed to over the years in HHS spaces. Yet the longer I’ve been here, the more it feels like something else entirely: A crossover episode.

What makes it a crossover isn’t the subject matter. Cannabis regulation is not child welfare, and it shouldn’t operate like it. But emerging regulatory systems are encountering many of the same human, operational, and workforce realities that Health & Human Services has spent decades learning through painful iteration: how people adapt to change, how systems shape behavior, how trust influences outcomes, and how workforce, policy, practice, and technology either align — or fail together.

That’s the crossover.

Setting the Stage: Public Sector = Public Service

Let’s start with something simple. As far as I’m concerned, all public sector work is human services work.

• Not conceptually...not in how we categorize it.

• But operationally...in how people are engaged, how decisions are made, and outcomes achieved.

  
  

Regulation and care aren’t opposites; they’re aligned through public protection, whether we’re talking about protecting children or ensuring consumer safety. And when care, or human-centeredness, is placed at the forefront of that work, regulation becomes more precise, more consistent, and more effective. Because how we engage determines not just how the system performs, but how trust is built, sustained, and carried through every level of the work.

In human services, we call this a parallel process. What happens at one level of the system is reflected at the next. Leadership sets the tone for the workforce. The workforce carries that forward in their interactions. And those interactions shape how stakeholders experience the system and, in turn, how they engage with it. It’s a ripple effect.

When trust, clarity, and consistency are modeled internally, they don’t stop there; they extend outward. That’s how regulation moves beyond oversight. It becomes something people can understand, engage with, and ultimately uphold.

Because systems don’t just enforce behavior — they model it.

And we’ve learned that over time. Sometimes the hard way.

What We Learned the Hard Way

In child welfare, we’ve learned this lesson over decades of well-intentioned trial and error.

Systems built around protection have, at times, leaned heavily on intervention: removals, rigidity, and pressure to demonstrate change quickly. Over time, the field has evolved to strengthen families, support their systems, and invest in communities. Because lasting protection doesn’t come from disruption alone, it comes from stability, support, and sustainability.

That shift matters here.

It changes how we define success.

It changes how we engage.

And it changes what we build systems to do.

Not just intervene — but build and sustain.

Not just enforce — but model and support.

Not at a distance — but in relationship.

And the values that make that possible — dignity, respect, partnership, equity — aren’t sector-specific. They’re foundational. Different settings. Same fundamentals.

Building vs. Rebuilding

While the values translate seamlessly, the systems themselves are at very different stages of evolution. Child welfare operates inside layers of history. Policies rewritten time and again. Practices redesigned. Systems replaced — then replaced again. It carries the weight of iteration. Cannabis regulation is different.

It is not rebuilding.

It is being built in real time.

• Defining regulatory models

• Building workforce capability and professional standards

• Translating statute into policy, process, and applied practice

• Designing integrated systems and workflows from the ground up

And yet, despite those differences, the pressure points feel familiar — just not in sequence.

They’re happening all at once.

• High visibility

• High stakes

• Evolving policy

• Workforce expectations that outpace infrastructure

All moving in parallel.

All requiring alignment.

All under pressure to deliver in real time.

Different lifecycle stage. Same level of complexity.

And that complexity doesn’t resolve itself — systems must be built to withstand it, move through it, and evolve within it.

Because none of these pressures exists in isolation. Workforce challenges shape practice. Practice shapes technology needs. Technology influences consistency, decision-making, and engagement. They are not separate workstreams. They are parts of the same system.

It’s a concept I’ve written about before, often called the “Three Keys”: the interconnected relationship among workforce, policy & practice, and technology. Not as independent initiatives — but as the operational foundation of systems that can adapt, align, and evolve over time.

In more established systems, we’ve often tried to address these elements one at a time — layering technology onto misaligned processes, or expecting the workforce to adapt to systems that weren’t built with their work in mind.

In child welfare, caseworkers were often expected to navigate systems designed without a full understanding of field realities — documenting practice in ways that didn’t always support the work happening in real time.

The same dynamics can emerge anywhere.

Regulatory teams are balancing far more than inspections and workflows.

They’re building continuity across disciplines, aligning operational practices, creating shared visibility across functions, and establishing the communication, coordination, and collective processes required for high-functioning systems — all while the broader structure is still taking shape.

Yet when these elements evolve separately, fragmentation follows. The workforce adapts around systems instead of through them. Processes drift from practice realities. Technology reinforces inconsistency instead of supporting alignment.

When systems fragment, nobody wins.

And over time, the disconnect becomes operational, cultural, and increasingly difficult to untangle.

What makes this work different is that workforce development, practice design, operational alignment, stakeholder engagement, and technology enablement are not being treated as separate initiatives.

They’re evolving together.

And yes, it’s complex and can feel chaotic.

There are constantly moving parts, competing priorities, operational demands, evolving expectations, and real people navigating all of it while simultaneously building the structure meant to support it.

But that’s okay.

Systems were never meant to evolve as disconnected parts.

They were meant to move together.

That’s not the problem.

That’s the model.