Cody Pools, Inc

Bryan Brooks

Complexity Reduction Architect

Common Sources of IT Complexity

The most common sources are disparate systems, siloed data, and inconsistent operating models. Each acquired business brings its own CRM, ERP, file storage, identity approach, and reporting structure.

Individually, these environments may function effectively. Collectively, they create operational fragmentation. Over time, that fragmentation results in manual reconciliation, inconsistent reporting, rising support overhead, and increased security and governance risk. The issue is rarely the technology itself; it is the absence of alignment across the enterprise.

Where Flexibility Adds Value and Where It Doesn’t

The key is distinguishing where flexibility creates business value and where consistency is non-negotiable. Autonomy should exist in customer engagement, sales execution, and localized operations. Standardization should be enforced across identity, infrastructure, security, data models, and endpoint management.

This creates a federated operating model where business units retain agility while operating on a unified foundation. The objective is not uniformity; it is alignment at scale.

The SIMPLE framework provides a practical approach to reducing complexity:

• Standardize the foundation (identity, infrastructure, security)

• Integrate around business workflows

• Minimize redundant tools and unnecessary variation

• Partner with MSPs to scale execution

  Moving too quickly disrupts operations, while moving too slowly allows complexity to grow.  

• Lead with discipline and enforce standards

• Evolve through intentional convergence over time

This framework establishes a consistent lens for decision-making and prevents environments from drifting into operational fragmentation.

Governance Cannot Be Outsourced

Integration ensures systems support end-to-end workflows while reducing data silos. Managed service providers help organizations scale through operational consistency, proactive monitoring, and standardized support. However, they cannot replace internal ownership.

For this model to succeed:

• IT defines the architecture and standards

• Governance is clearly established

• The MSP operates as an extension of Enterprise IT

Execution can be outsourced. Accountability cannot.

Speed and Discipline Are Not Opposing Forces

Scalable transformation is driven by intentional convergence, not forced standardization. Moving too quickly destabilizes operations, while moving too slowly allows complexity to compound. Effective leaders define a target architecture, allow temporary coexistence where necessary, and prioritize high-impact standardization first.

Speed and discipline are not opposing forces. Organizations scale successfully when they move with urgency inside a defined operational framework, ensuring growth never outpaces clarity.