The combined organization needed more than connected applications.

For two billion-dollar-plus firms preparing to merge, Howard Pearlmutter's integration work connected stakeholder knowledge, strategic understanding, architecture, and practical qualification.

He interviewed participants to understand perspectives, goals, preferences, and constraints. He prepared and delivered high-level briefings and developed medium- and long-term integration architecture.

The work also included technology research, hands-on qualification and prototyping toward demonstrations and pilot stages, and planning for parallel and phased buildouts and rollouts.

The architecture had to fit an organization coming together from different systems and operating histories.

The enterprise supplied more than one interpretation.

A common word can have different meanings across organizations. A transaction can represent different responsibilities. A familiar exception may exist in people's experience rather than an obvious data field.

Stakeholder knowledge therefore belongs in the architecture discussion. It helps explain what the integration must preserve and what the future system must make intelligible.

Technical prototypes can then examine a particular crossing. The result can inform both the implementation and the operating account.

Another merger called for shared executive understanding.

In separate Singapore work, Howard designed and delivered an enterprise-integration and XML summit for fifty IT executives affected by the merger of two major financial institutions.

That contribution addressed a different need through learning and a common frame. It was distinct from the hands-on architecture engagement above.

The useful form follows what the organization needs at the time.

Carry the enterprise lesson into a new initiative.

Climate and sustainability work may enter organizations whose systems already embody established knowledge and responsibilities. A new purpose has to connect with that environment.

The practical task may involve information meaning, architectural boundaries, platform choices, or human understanding across roles.

Explore coordination models, missing context, platform options, and review.

Begin with the result that has to hold together across the boundary. Give the people and systems a clear relationship to that shared work.