What Complexity Teaches
Early in my career, I believed complexity was something to eliminate.
If a system was hard to explain, the instinct was to simplify it: fewer variables, fewer pathways, fewer exceptions. In many situations, that instinct is useful. But over time, I have learned that in certain environments, oversimplification can do more harm than good.
Labor organizations are one of those environments.
They are not complex by accident. They are complex because they are designed to balance autonomy and alignment, local needs and statewide or national priorities, governance and execution, member service and institutional accountability.
Respecting the shape of the organization
One of the most important lessons we have learned at Arrayworks is that effective systems should not force organizations to become something they are not. Technology should adapt to how the organization actually works, not the other way around.
For organizations operating across multiple locals, payment models, data structures, and governance frameworks, the initial objective is not to flatten every difference. The objective is to create clarity across those differences.
That means shared data. Consistent processes. Better visibility. Stronger coordination. And the ability to see the whole organization without erasing the distinct parts that make it work.
This philosophy guides how we think about platform design, customer partnerships, and long-term organizational sustainability.
Complexity at scale is not a theory
Complexity is not a defect to be erased. It is a reality to be understood, respected, and incorporated into the design. We see this most clearly in large, membership-driven organizations operating at scale.
The Florida Education Association supports 120 local affiliates across the state. Before the project to consolidate and centralize membership processing by configuring Arrayworks’ TAP orchestration platform to create a Central Membership System, there were 32 disparate membership systems in place. Within a year of CMS adoption, FEA reduced the number of unique membership systems to 12, and then to 5 a couple of years later, supporting more than 120,000 members statewide.
FEA is now working toward full unified standardization by April 2028, with a modernized, future-facing platform for the entire organization.
What matters most is not just the number of systems involved or the size of the member base. It is the recognition that technology must reflect the real operating model of the organization. Not the abstract version. Not the simplified version. The real one.
Why this matters beyond any one organization
This is not only a story about one customer, one platform, or one implementation. It is a broader lesson for anyone building systems, and eliminating silos, in complex environments.
If you treat complexity as a flaw, your solutions will eventually fall short. People will resist change and silos will be hardened.
That mindset applies well beyond software. It shapes how teams operate, how decisions are made, how leaders prepare for change, and how organizations create the capacity to adapt over time.
Why we are starting this newsletter
We are launching this newsletter to share lessons from the work itself. Not merely announcements. Not product updates. Not marketing slogans.
Our goal is to explore the practical realities of organizational transformation: what we are learning, what complex organizations are navigating, and how technology can better support the way people, systems, and decisions actually work.
Sometimes we will point to public examples. Other times, we will step back and reflect on broader patterns: how to build better systems, stronger partnerships, and more adaptive organizations.
Because complexity is not going away. The organizations that learn how to understand it, design for it, and operate through it will be the ones best positioned for what comes next.
Welcome to the conversation.
