Month: August 2026

Public organizations rarely succeed based solely on structure or culture; the most resilient organizations intentionally develop both. The Spartanburg Children’s Cabinet exemplifies this approach, and through my direct involvement in its development, I observed both dynamics firsthand.

The Cabinet was established in May 2026, when Spartanburg City Council passed an ordinance for the city to join the work as the advisory body’s first municipal partner. The ordinance defines the Cabinet as an action-oriented advisory group that unites public, nonprofit, and community partners to share data, coordinate policies, and address systems-level challenges for children, youth, and families. It authorizes the Cabinet to coordinate agencies, review policies for their impact, recommend priorities, and pursue public-private partnerships. Membership is balanced across sectors and includes individuals with direct experience as parents, service providers, or youth. Classical organization theory would describe this as a rational structure designed for accountability and results.

The ordinance outlines Spartanburg Academic Movement as the Cabinet’s administrative and operational backbone. This role is significant, as backbone organizations facilitate collaboration across sectors that typically operate independently. They maintain a stable collaborative environment despite differing institutional mandates. The Cabinet advances this model by moving from convening to shared decision-making with meaningful advisory authority.

This transition began before the ordinance. For about two years prior to the Cabinet’s launch, a small working group focused on building relationships, establishing shared priorities, and reaching consensus on the Cabinet’s structure. As a member of this group, I observed the development of norms around consensus and shared ownership, reflecting what organizational theorists define as culture: the assumptions a group forms while addressing shared challenges.

Those closest to the work had to balance structure and culture, even when they created tension. Deadlines and procedural requirements sometimes conflicted with the slower process of building cross-sector consensus. That tension did not signal failure; it showed that both forces were at work. The ordinance gives the Cabinet advisory authority, but it does not determine which data to track or which populations to prioritize. Partners make those decisions together, guided by a shared commitment to fairness that shapes nearly every Cabinet decision.

Neither piece works alone. Without the ordinance, the Cabinet would have no formal standing relative to local government and no way to guarantee the city’s participation in a change in leadership or politics. Without the relationships partners built before the vote, it would just be another body checking procedural boxes, present but not actually collaborative.

Public administration often treats structure and culture as separate issues. The Spartanburg Children’s Cabinet demonstrates they are inherently connected.

One of the enduring principles of effective design is that solutions should be as simple as possible—but not simpler. Public administration is no exception. Complex problems often lead organizations to create equally complex solutions. New databases, new processes, and additional layers of oversight may look like progress, but they can also introduce complexity without improving outcomes. One of the most valuable leadership lessons I have learned is that innovation is often less about building something new and more about making better use of what already exists.

While leading the design of a long-delayed pilot program, I encountered this challenge firsthand. The existing concept centered on creating a new system of record to share information between partner agencies. On paper, the proposal seemed comprehensive. In practice, it would have required years of development, extensive legal review, and significant resources before a single case could be referred.

As our team evaluated the proposal, we realized the necessary relationships and authorities were already in place – they just needed to be utilized. The participating agencies already had access to the information they needed through established agreements governing authorized use. Rather than creating unnecessary infrastructure, we proposed centralizing coordination through an existing task force, strengthening internal review procedures, providing targeted training, and establishing clear oversight and accountability.

The greatest challenge, however, was not technical – it was organizational. Moving away from a previously agreed-upon proposal required patience, relationship building, and the support of trusted stakeholders across multiple offices. Rather than criticizing the original plan, we focused on demonstrating how a simpler approach could accomplish the mission more efficiently while still maintaining necessary safeguards.

The experience reinforced an important leadership lesson: simplifying a process does not mean lowering standards. Effective public administration requires identifying what is essential, removing what is unnecessary, and creating solutions that allow existing people, partnerships, and processes to work more effectively.

The pilot program ultimately launched successfully and received positive feedback from both internal stakeholders and external partners. Looking back, I believe much of its success came from our willingness to challenge assumptions and resist the instinct to build new structures when existing ones could accomplish the mission.Effective leadership is not measured by how elaborate a solution is, but by whether it achieves meaningful results. Sometimes the most innovative idea is simply finding a better way to use the tools, relationships, and capabilities that are already available