Portfolios in EAM, made visible with the IPO-model

From IPO to EAM – How Architecture Portfolios Can Be Derived from Simple Questions

The IPO model (Input – Processing – Output) describes a fundamental pattern of information processing.
It is deliberately kept simple and precisely therefore universally applicable – far beyond technical systems.

When this mental model is transferred to Enterprise Architecture Management (EAM), a surprisingly clear logic emerges:
Basic guiding questions can be derived from IPO, which in turn lead directly to the well-known architecture portfolios.

IPO as a Starting Point

At its core, IPO describes three aspects:

• Input – what information is available?
• Processing – what happens to this information?
• Output – what results are produced?

Applied to architecture work, this initially yields three central questions:

• Which information is relevant?
• How is this information processed?
• With what means is this processing implemented?

These three questions form the substantive core of the consideration.
They describe what is being examined and how information processing fundamentally works.

In practice, however, it quickly becomes apparent:
This perspective alone is insufficient for robust architectural decisions.

Architecture does not exist in isolation, but rather:

• within organizations,
• with a specific purpose,
• and over an extended period of time.

Therefore, the three core questions must be supplemented by additional perspectives that take context, responsibility, and time into account.

From this extension arise three additional guiding questions:

• Who bears responsibility?
• Why is something designed in a certain way?
• When is something relevant or valid?

Together, these six guiding questions form a complete, yet simple, foundation for systematically exploring enterprise architectures.

The Derived Guiding Questions

Thus, six fundamental guiding questions emerge from EVA thinking:

1. Which information is relevant?

This question arises directly from the Input perspective.

It forms the basis for:

• business objects
• information
• data structures
• data flows

Assigned Portfolio:
Information / Data Portfolio

2. How is information processed?

This question is derived from Processing.

It describes:

• business processes
• business rules
• functions and services
• their implementation in applications

Assigned Portfolio:
Business & Application Portfolio

3. With what means is processing implemented?

This question is also part of Processing, but with a focus on the means.

It addresses:

• technologies
• platforms
• infrastructure
• technical standards

Assigned Portfolio:
Technology / Infrastructure Portfolio

4. Who is responsible?

This question supplements EVA with the organizational dimension.

It clarifies:

• roles
• responsibilities
• ownership

Assigned Portfolio:
Organisation / Capability Portfolio

5. Why is something designed this way?

This question establishes the purpose.

It relates to:

• goals
• principles
• strategic drivers
• value arguments

Assigned Portfolio:
Strategy / Motivation Portfolio

6. When is something relevant?

This question introduces the time dimension.

It describes:

• temporal validity
• transitions
• dependencies
• lifecycles

Assigned Portfolio:
Roadmap / Lifecycle Portfolio

Graphical Classification

The following diagram shows how the guiding questions can be logically derived from the EVA principle and assigned to the respective portfolios:

flowchart TB
    EVA["EVA Principle<br/>Input · Processing · Output"]

    Q1["Which information?"]
    Q2["How is it processed?"]
    Q3["With which means?"]

    Q4["Who is responsible?"]
    Q5["Why is it done this way?"]
    Q6["When is it relevant?"]

    IPO --> Q1
    IPO --> Q2
    IPO --> Q3

    Q1 --> P1["Information / Data Portfolio"]
    Q2 --> P2["Business & Application Portfolio"]
    Q3 --> P3["Technology Portfolio"]

    Q4 --> P4["Organisation / Capability Portfolio"]
    Q5 --> P5["Strategy / Motivation Portfolio"]
    Q6 --> P6["Roadmap / Lifecycle Portfolio"]

The diagram does not show a hierarchy, but rather a conceptual derivation:

• EVA provides the basic pattern
• the guiding questions explore the context
• the portfolios structure the content

Commonalities and Dependencies

In practice, these portfolios do not exist in isolation:

• Without clarity about information, processes and systems remain vague.
• Without understanding processing, the connection between business and IT is missing.
• Without suitable technology, requirements cannot be implemented.
• Without defined responsibility, knowledge is not sustainable.
• Without strategic purpose, legitimacy is missing.
• Without time reference, no steering is possible.

The guiding questions act as the connecting element between the portfolios.

Conclusion

The IPO principle shows how information processing fundamentally works.
By deriving simple guiding questions from it and assigning them to the well-known EAM portfolios, a clear and understandable structure for architecture work emerges.

The added value lies not in new frameworks, but in the consistent application of simple questions:

Good architecture work begins where
connections are understood –
not where additional complexity is created.

Sometimes, it is enough to reorder what is already known.

• ←Previous
• Next→