A merger supplied a new organization. Integration had to supply the relationships.
For two billion-dollar-plus firms preparing to merge, Howard Pearlmutter's integration work connected several kinds of inquiry.
| Part of the work | What it brought into the integration |
|---|---|
| Stakeholder interviews | Perspectives, goals, preferences, and constraints |
| Strategic briefings | A useful foundation for examining technical direction |
| Medium- and long-term architecture | An account of how the combined systems could develop |
| Technical qualification and prototypes | Practical examination of selected mechanisms |
| Pilot and phased rollout planning | A path toward learning and transition |
The pieces informed one another. A stakeholder's operating knowledge could affect the architecture. A technical constraint could change the useful sequence. A briefing could make a consequential distinction available to people outside the implementation specialty.
The architecture had to connect with the organization actually coming together.
This is why a merger question can benefit from a contributor able to move among business context, technical systems, and human understanding. A component inventory alone does not explain how two organizations interpret the work their systems represent.
The important differences can hide inside familiar words: a customer, a transaction, a system of record, or a state called complete.
In separate Singapore work, Howard designed and delivered an enterprise-integration and XML summit for fifty IT executives affected by a merger of two major financial institutions. That assignment used shared learning as the useful bridge.
The right contribution therefore depends on the current need. It can be a briefing, a working session, an assessment, or practical architecture and prototyping.
For your organization, choose one result that has to span the inherited boundary. Ask each side what it means and what must happen for it to work. The difference can reveal a useful next question.
Explore who defines success, whose context matters, and a working session.
An independent perspective earns its place when it makes the combined undertaking more intelligible and the next action more useful.