Complexity is a structural reality, but it does not stay still. Priorities shift, dependencies appear midstream, and the plane gets built while in flight. As systems take a more active role in execution, coordination becomes the hard part.
Labor organizations are not complex by accident. They are complex because they balance autonomy and alignment, local needs and statewide priorities, governance and execution. When technology ignores that, it creates friction rather than efficiency.
Posts on modeling organizations, operating models and why software should follow the business rather than the reverse.
Approval structures get redesigned to match predefined workflows. Data is forced into rigid formats. Over time that reversal creates friction.
Read the post →Policies, workflows, governance rules and data relationships span multiple systems. Fragmentation makes it harder to see how the organization truly operates.
Read the post →Policies evolve, regulations shift, expectations grow. Much of the enterprise software still in use was designed around none of that.
Read the post →Governance, compliance, financial management, member services and advocacy, across dozens or hundreds of semi-autonomous locals.
Read the post →National bodies provide oversight while locals keep the autonomy to represent members. That balance is essential, and it is what makes the operation complex.
Read the post →Many unions are still supported by rigid systems with hard-coded logic that struggle to keep pace with how unions actually work.
Read the post →Longer-form thinking from the Arrayworks archive on connected ecosystems, platform architecture and the operational role of data.
A monthly perspective on complexity, Digital Twins and governed AI.
Subscribe on LinkedIn