Markus Greiter | Business & IT Transformation Management

EAM and BPM: The Strategic Foundation of Successful Transformation

Markus Greiter — Wed, 11 Mar 2026 07:00:52 +0000

Why Enterprise Architecture and Business Process Management Are Critical to Success

Transformation – The New Normal

The question is no longer whether a company is undergoing transformation – because transformation has become the new normal – but rather in which dimensions, and above all, on what foundation.

Whether it’s an operating model realignment, a digital scaling initiative, a regulatory-driven restructuring, a full-blown business model shift, or a post-merger integration or carve-out: the triggers for transformation are many. Yet they share a common denominator. They are always multidimensional change efforts that simultaneously address multiple design dimensions – often all of them at once, spanning strategy, organization, architecture, processes, data, and systems. And they share something else: none of them can be managed by classical program and project management alone.

When transformations fall short of their goals, the causes are quickly attributed to a lack of organizational willingness to change, insufficient investment, or inadequate competence. But the real root cause is often something more fundamental: the absence of a solid, reliable basis for the decisions and controls on which transformation is built.

Enterprise Architecture Management (EAM) and Business Process Management (BPM) are the methodologies that create exactly this foundation – not as technical disciplines, but as strategic management instruments. And as such, they are a leadership responsibility that must be owned at the senior executive level.

The Structural Challenge in Transformation Programs

In most organizations, organizational structures, business processes, data flows, IT architectures, and IT systems have grown organically over time – developed on a project-by-project basis. They are rarely fully documented, and even where documentation exists, it seldom reflects the current state of implementation.

As a result, decisions are frequently made on basis of assumptions rather than data and facts. “There was no time for a proper baseline assessment” – so goes the argument – this reasoning typically surfaces latest when transformation targets must be reported as missed and explanations are sought.

This structural transparency deficit is not an exception in organizations. It is actually more the norm. It becomes a serious liability, especially where deep, far-reaching transformations are initiated.

And that is exactly where a pattern emerges that shapes many transformation programs: individual change initiatives are launched in parallel; dependencies between them remain invisible; and sequencing that may be critical is not recognized in time.

The consequences are predictable: cost and effort overruns accumulate; goal conflicts between concurrent initiatives surface too late; and not infrequently, the point of no return has already been passed – decisions have been locked in before the full picture was clear. Despite substantial investments of time and budget, the transformation outcomes no longer fully deliver on the intended strategy.

“The issue, then, is not a lack of willingness to change or to execute. It is a lack of visibility into what needs to change – and therefore a deficit in the quality of the transformation decisions themselves.”

Anyone who recognizes this pattern – or who has lived through it firsthand – knows: it takes more than sound program and project management. It takes a reliable foundation for well-founded transformation decisions.

EAM and BPM: Two Perspectives – One Impact

Enterprise Architecture Management and Business Process Management answer different but complementary questions. That is precisely where their strength lies. And that is exactly why their true value only emerges when they work in concert.

EAM: The Structural Frame of Reference

EAM answers the structural question: How does the organization hold together? Which capabilities, processes, applications, data, and technologies support which strategic objectives?

“Enterprise Architecture Management provides a holistic, consistent picture of the organization – from business strategy through to technical infrastructure.“

In doing so, EAM establishes the frame of reference for transformation decisions: a shared, authoritative view of the current state and a structured basis for defining the target state. Investment decisions, prioritization, and dependency analysis become substantially more reliable as a result.

BPM: The Operational Logic of Change

BPM answers the operational change question: How is value delivered end-to-end? Where do friction, process breaks, governance gaps, and the need for change arise?

“Business Process Management makes processes visible, manageable, and deliberately changeable at every level – from strategic process architecture and value stream design to operational execution.“

BPM is therefore far more than only a tool for process analysis and documentation. It is the methodological instrument through which the need for change is identified, prioritized, and translated into manageable implementation steps – consistently, transparently, and in alignment with how the organization actually delivers its services.

The Combination: Aligning Business and IT

It is only in combination that the decisive impact emerges: EAM provides the structural frame of reference, while BPM delivers the operational logic of change. Together, they create the alignment of business and IT – that is, consistency between strategic objectives, organizational capabilities, processes, and technology implementation.

“EAM and BPM create what every transformation requires: a shared understanding of where the organization stands – and what must change for it to get where it needs to go.“

This alignment is not an end in itself. It is the prerequisite for ensuring that transformation decisions do not contradict each other, that dependencies can be identified early, and that the path from strategic vision to operational reality remains consistent and manageable throughout.

Where EAM and BPM Make the Critical Difference

In many organizations, EAM and BPM are present in some form – but they are not embedded as holistic, strategy-level methodologies. They are frequently understood and treated as purely IT disciplines. This limits their reach significantly, and their true strategic leverage goes untapped. Because:

“The domain where EAM and BPM deliver their greatest impact is at the two interfaces where transformations most commonly break down: between business and IT, and between strategy and execution.“

Their value contribution can be described in management-relevant terms:

Better investment prioritization: Transparency across capabilities, architectures, systems, and dependencies provides the basis for more targeted allocation of resources – helping to avoid redundant development efforts and misguided investments.
Reduced transformation risk: Goal conflicts between initiatives and critical dependency paths become visible early – before they require costly corrections.
Greater execution capability: A shared target picture for business and IT reduces friction at organizational boundaries and improves decision quality.
Faster time-to-value: A coordinated and appropriately sequenced approach to change avoids setbacks and generates usable results sooner.
Higher consistency between vision and operational reality: Strategic decisions become traceable and translatable into operational action.

This value contribution is particularly tangible in multidimensional transformation scenarios – precisely where the pressure for change and the complexity of managing it are highest:

In business model transformation, where value streams, customer relationships, and service architectures are being redefined, the ability to develop processes and system landscapes in a consistent and coordinated manner determines whether the new model will hold operationally – or whether it will fail at the point of execution.
In regulatory-driven transformations requiring deep changes to processes, systems, and governance structures, the traceability of change – who changed what, and why – is not merely an operational requirement. It is a matter of governance and compliance.
In post-merger integrations and carve-outs, organizational structures and operating models change simultaneously. Which capabilities, processes, and systems are retained, which are merged, which are rebuilt? Without a reliable picture of the existing architecture, these decisions cannot be made on solid ground – with direct consequences for transition stability, governance, and goal attainment.

A Strategic Leadership Responsibility – Properly Understood

EAM and BPM are strategic leadership responsibilities of senior management – not in the sense of hands-on methodological work, but in the sense of executive accountability for the quality of the decision-making foundation. As such, they are core elements of both corporate governance and organizational development. The responsibility lies in ensuring that EAM and BPM are embedded in the organization as the basis for decision-making and governance – thereby creating the conditions for well-informed transformation decisions.

The crucial question executives must therefore ask is not: Do we have an enterprise architecture team and a business process management team in our organization? It is: Do we have a reliable, current foundation for transformation decisions – and are EAM and BPM embedded in a way that makes them genuinely effective as management instruments at the moments that matter most?

“Management’s responsibility is to create the structural preconditions for sound transformation decisions.“

This is not a question of organizational size. Whether mid-market or large enterprise: EAM and BPM are not optional methodological refinements. They are the prerequisite for any change effort with multidimensional impact.

And this responsibility cannot be delegated. Organizations that treat EAM and BPM as purely operational IT disciplines forfeit their strategic leverage. Those that discuss them exclusively at the business level, without incorporating the technology dimension, create precisely the gaps where transformations break down: at the intersection of strategic ambition and operational execution capability.

Conclusion

Successful transformation takes more than good intentions. EAM and BPM create the reliable foundation needed to make decisions on the basis of data and facts. That alone is by no means an automatic guarantee of success. But it does provide a solid methodological underpinning that substantially increases the likelihood that transformation will actually achieve its objectives.

“EAM and BPM – anchored at the senior executive level as strategic management instruments – are the foundation for successful transformation.“

Key Takeaway

Before you evaluate, prioritize, or approve your next transformation initiative, consider three questions that will significantly shape the quality of your transformation decisions:

Do you have a complete, current picture of your enterprise architecture – [MG1] processes, systems, data, and dependencies – that can serve as a reliable decision-making foundation?
Do you know which of your current transformation initiatives depend on one another – and in what sequence they must be executed to avoid undermining the strategy you are pursuing?
And if not: on what basis are you making your investment decisions today?

“These questions are uncomfortable. But they lead exactly to where successful transformation begins: a reliable foundation for decisions.“

Get the latest insights on Business & IT Transformation.

Subscribe to email updates and get notified as soon as a new blog post goes live.

Subscribe now

Ethical Responsibility in AI Transformation Projects

Markus Greiter — Sat, 20 Sep 2025 10:39:51 +0000

… my kick-off blog article on my new website couldn’t start with a more lasting topic.

While heading back from Berlin to Munich, I am reflecting on the past days at the IPMA World Congress (organized by IPMA, the International Project Management Association and our German institution GPM Deutsche Gesellschaft für Projektmanagement e. V.). Days filled with valuable network connections – both old and new – and inspiring impulses on Shaping the Future with Project Management.

I will share with you in this and the next blog articles some of my personal highlights of the IPMA world congress. Insights that struck me deeply – whether by accelerating my learning curve, making me nod in agreement, triggering a pause for thought, or simply creating one of those ‘aha’ moments. My reflections and key takeaways in this article build on impulses from one of the keynotes:

IPMA World Congress Keynote – Ethical Responsibility in Innovation, by Prof. Dr. Alena Buyx

Alena Buyx – one of the leading ethics professors in Germany (Technical University of Munich, former chair of the German Ethics Council) – shared in her keynote insights from her work on “Ethical Responsibility in Innovation”, especially in respect to AI. She reminded us that November 2022, when ChatGPT popped up, changed everything – for all of us. Buyx calls it an Oppenheimer moment. She emphasized that this moment marked an era-defining change, bringing ethical responsibilities to the forefront when it comes to powerful innovations like AI.

Against this backdrop, she highlighted why AI can never be considered superior to human beings. It possesses impressive statistical intelligence, but this cannot be equated with human intelligence. Human intelligence may not be as fast or as good in pattern recognition, yet it is far broader in scope. Fear, pain, doubt, and above all our social nature – our constant orientation toward other human beings – make us conscious beings. AI, by contrast, is a stochastic machine, operating on probabilities, that can only simulate human qualities. This is why the final decision must always rest with humans. AI will never be capable of assuming responsibility for a decision. As Buyx put it:

“Rule of ethics: AI applications must enhance human action, never diminish it, and under no circumstances replace human beings.”

As a final point, she stressed that AI models are deliberately designed to appear empathetic, caring, and affirming – always with the goal of keeping people engaged on the platform. It is therefore no surprise that “relationship AI” is rapidly becoming one of the most popular consumer uses of AI – which I see as a symptom of the lack of social connection and belonging in contemporary human society.

My Key Takeaways – How To Proceed With AI

As an individual:

AI will not replace the human as such. But humans who don’t use AI at all or who don’t use AI responsibly and consciously will be replaced by those who do.
The technology is here to stay, so make it part of your processes.
Always remember: Every AI is based on its implemented objectives. Model alignment heavily influences the output. Not knowing its characteristics – and not being able to influence them – is the major risk.
Apply AI with a healthy skepticism and a no-trust approach: Be aware that handling the AI output is your responsibility. Stay in the driver’s seat by performing critical reviews on any AI output and making the final judgment yourself.

As an organization:

Push hard for the needed culture change – every employee must act with a leadership mindset by taking over a dedicated level of responsibility for their own actions taken with AI.
Employees who combine ethical awareness and technological knowledge, who use AI responsibly and consciously, are your key assets for a future-proof organization.
Long-term competitive advantage does not come from replacing employees with AI, but from enhancing your team with AI-trained employees who add their indispensable experience and social dimension to AI outputs.
And – last but not least – the most important key takeaway: Act with awareness and ethical responsibility in your transformation projects – also at the organizational level. That’s the only way they can become outstanding success stories.

Get the latest insights on Business & IT Transformation.

Subscribe to email updates and get notified as soon as a new blog post goes live.

Subscribe now

Issue Management – The Underestimated Key to Transparency and Control in Complex Projects

Markus Greiter — Tue, 02 Sep 2025 08:17:52 +0000

This article builds on a professional piece I originally wrote in 2005, focused on managing complex IT system integration projects. Today, the topic of issue management is more relevant than ever – particularly in the context of modern agile practices, DevOps, enterprise architecture, project governance, and digital transformation. Its importance continues to grow as system complexity increases across highly integrated, heterogeneous solutions and multi-stakeholder project environments. Although the original article was written from the perspective of a traditional project manager, its principles apply equally to product managers, architects, developers, business owners, and Scrum Masters. In that sense, issue management can truly be considered an “evergreen” topic – one that has maintained its relevance across methodologies, technologies, and decades.

The Challenge – Making the Invisible Visible

Project managers are expected to plan, steer, and — above all — ensure that no work is left undone. Achieving this requires knowing exactly where progress is stalling and who is responsible for the next step.

In dynamic environments with high levels of interdependence and change, maintaining transparency in project management is essential for staying in control and ensuring accountability.

Without suitable management tools, only larger work packages can typically be planned and tracked – the kind usually represented in a project plan.

However, when complex initiatives fail to move forward, it is often because a multitude of smaller sub-tasks remain unaddressed – and unnoticed for too long. Precisely because these activities are so granular, they tend to escape a project manager’s direct oversight. And given time constraints, it’s virtually impossible for any manager to personally drive every micro-level task to completion.

The Solution

This is where issue tracking systems come into play. These solutions make it possible to capture and manage even the smallest tasks in a structured way, ensuring that it is always clear who is responsible for the next step. In fact, such systems can take over — only on the micro level — the role of the project manager, automatically alerting the responsible person when an action is overdue. In doing so, issue tracking systems make a vital contribution to effective task management and help establish clear structures for agile delivery — particularly in environments where teams work in parallel across multiple workstreams.

Put simply, just as project managers drive progress at the macro level, issue tracking systems can do the same at the micro level — precisely where human oversight reaches its limits.

These tools have evolved from traditional bug tracking systems and – unlike those – can be used

not only for defect management,
but more broadly to manage and track all types of work items that require collaboration between multiple people over time — the so-called issues.

As of 2025 – twenty years after I wrote the original version of this article – issue tracking systems have become a core component of modern work management and collaboration management platforms. Yet, many organizations still fail to harness their full potential. In my experience, both the value and user adoption of such tools often fall short because teams do not adequately distinguish between trivial, low-value tasks and the micro-level actions that truly drive project progress.

Why Issue Management Pays Off for All Stakeholders

Now that we’ve outlined what issue tracking systems can do, the next logical question is whether the effort is truly worth it. Capturing, managing, and systematically tracking all issues are the three foundational pillars of effective issue management:

In complex IT projects – starting as early as the planning phase – teams must coordinate and resolve a multitude of fine granular questions and planning activities. Later, during development and into operations, new issues and defects frequently emerge that cannot be immediately assigned to a specific system, application, or service. At first, it may not even be clear whether a problem stems from hardware limitations, software defects, or integration challenges.

To track such questions, planning items, or defects over days, weeks, or even months – and always know their exact status – requires a comprehensive approach to issue management, particularly as an integral element of modern project governance.

Managing numerous issues in parallel, quickly, effectively, and cost-efficiently depends on three critical success factors:

Systematic Capture
Effective Management
Consistent Tracking

Systematic Capture means:

Capturing all relevant information about an issue in a structured and traceable way.
Ensuring clarity and accountability through precise documentation.
Categorizing issues appropriately (e.g., Task, Bug, Change, or Feature Request).

Effective Management aims to:

Consolidate captured issues (including quality assurance and duplicate elimination).
Enable all stakeholders to work from a Single Source of Truth.
Allow multiple contributors to read and update data in parallel within a centralized platform.

Consistent Tracking enables:

Rapid handover of issue tickets to the responsible organizations or individuals.
Prompt responses from assignees — enabling
Swift, targeted resolution.

„Ultimately, systematic capture and effective management form the foundation for consistent tracking and timely resolution – which, in turn, drive customer satisfaction and reduce project delivery costs.“

Transparency in Collaboration Between Client, System Integrator, and Delivery Partners

Any project aiming for smooth, efficient, and cost-effective delivery cannot afford to overlook issue management.

Achieving this requires close collaboration between all parties involved – the client, the system integrator, and the various delivery or technology partners.

These essential coordination tasks become significantly easier when:

appropriate tools are in place,
both client and contractor use them jointly, and
all parties agree on a common process for doing so.

Equally important is that both client and contractor share all relevant information they generate or process – ensuring it remains consistently up to date and accessible on a shared collaboration platform.

Shared access to a common issue database means that:

The client can, at any time, check the detailed status of each issue. This transparency encourages active participation and builds trust in the process — often motivating clients to log issues directly within the system.
For the contractor (system integrator), this reduces the burden of time-consuming reporting obligations, as well as duplicate entry of issues originally raised by the client.
If additional delivery partners – such as subcontractors or product vendors – are also granted access to the issues relevant to them, the general contractor’s role in issue management can focus on consolidation and schedule control, rather than having to re-enter and re-communicate data.

The System Solution – A Cloud-Based Issue Management System

Because issue management extends beyond organizational boundaries, a web-based system is essential – one that allows every participant to access and update information from anywhere, at any time. Whether working from their own office, a partner’s site, or while traveling, all stakeholders must be able to stay connected and informed. To achieve this, the solution should be securely hosted and designed with responsive, user-friendly interfaces that adapt to any device.

It must also support role-specific views, allowing each participant to focus on the information most relevant to their responsibilities. In addition, the system should automatically send email notifications (alerts) at configurable intervals — reminding responsible individuals when action is overdue and keeping managers informed of overall progress. These alerts should act as concise, actionable reports, clearly identifying where workflows are stalling and prompting timely intervention. A solution like this not only enhances efficiency but also strengthens accountability across all stakeholders.

Key Takeaways

An issue tracking system tailored to the specific needs of a company’s projects fulfills all these criteria – providing the foundation for transparency in project management, informed decision-making, and seamless collaboration across teams and organizations. With such a system in place, both internal and cross-company processes become significantly easier and more efficient to manage. Ultimately, the result is greater visibility, faster resolution cycles, and measurable gains in project performance and governance maturity.

“Clients, general contractors, and delivery partners all benefit equally from these advantages – including the cost savings achieved through streamlined project execution. A truly classic win–win situation.”

Get the latest insights on Business & IT Transformation.

Subscribe to email updates and get notified as soon as a new blog post goes live.

Subscribe now

Markus Greiter | Business & IT Transformation Management

EAM and BPM: The Strate­gic Foun­dation of Success­ful Trans­formation

Transformation – The New Normal

The Structural Challenge in Transformation Programs

“The issue, then, is not a lack of willingness to change or to execute. It is a lack of visibility into what needs to change – and therefore a deficit in the quality of the transformation decisions themselves.”

EAM and BPM: Two Perspectives – One Impact

EAM: The Structural Frame of Reference

“Enterprise Architecture Management provides a holistic, consistent picture of the organization – from business strategy through to technical infrastructure.“

BPM: The Operational Logic of Change

“Business Process Management makes processes visible, manageable, and deliberately changeable at every level – from strategic process architecture and value stream design to operational execution.“

The Combination: Aligning Business and IT

“EAM and BPM create what every transformation requires: a shared understanding of where the organization stands – and what must change for it to get where it needs to go.“

Where EAM and BPM Make the Critical Difference

“The domain where EAM and BPM deliver their greatest impact is at the two interfaces where transformations most commonly break down: between business and IT, and between strategy and execution.“

A Strategic Leadership Responsibility – Properly Understood

“Management’s responsibility is to create the structural preconditions for sound transformation decisions.“

Conclusion

“EAM and BPM – anchored at the senior executive level as strategic management instruments – are the foundation for successful transformation.“

Key Takeaway

“These questions are uncomfortable. But they lead exactly to where successful transformation begins: a reliable foundation for decisions.“

Get the latest insights on Business & IT Transformation.

Ethical Responsi­bility in AI Trans­formation Projects

IPMA World Congress Keynote – Ethical Responsibility in Innovation, by Prof. Dr. Alena Buyx

“Rule of ethics: AI applications must enhance human action, never diminish it, and under no circumstances replace human beings.”

My Key Takeaways – How To Proceed With AI

As an individual:

As an organization:

Get the latest insights on Business & IT Transformation.

Issue Manage­­ment – The Underesti­mated Key to Trans­parency and Control in Complex Projects

The Challenge – Making the Invisible Visible

The Solution

Why Issue Management Pays Off for All Stakeholders

„Ultimately, systematic capture and effective management form the foundation for consistent tracking and timely resolution – which, in turn, drive customer satisfaction and reduce project delivery costs.“

Transparency in Collaboration Between Client, System Integrator, and Delivery Partners

The System Solution – A Cloud-Based Issue Management System

Key Takeaways

“Clients, general contractors, and delivery partners all benefit equally from these advantages – including the cost savings achieved through streamlined project execution. A truly classic win–win situation.”

Get the latest insights on Business & IT Transformation.

EAM and BPM: The Strategic Foundation of Successful Transformation

Ethical Responsibility in AI Transformation Projects

Issue Management – The Underestimated Key to Transparency and Control in Complex Projects