Funding approval narrows the enterprise’s choices.

Vendor selection narrows them again.

Engage architecture while the decision can still change.

I have seen architecture depend on one sponsor remembering to make the call. When that person changed roles, early engagement disappeared. The durable fix was to connect architecture to funding, procurement, platform, data, and operating-model triggers so the enterprise asked the right questions while choices were still open. Read more at https://www.cornerstonea.com/.

Architecture is often invited late because the enterprise treats engagement as a relationship rather than a rule. Someone must remember the architect, recognize the issue, and make the call. That works until leadership changes, delivery pressure rises, or a decision looks smaller than its consequences.

The overarching theme of this episode is simple: architecture should not wait for an invitation. It should be triggered by the commitment.

An Enterprise Architect can help with a small set of early-engagement triggers into portfolio, business-case, and procurement workflows. A trigger should fire when leaders are about to narrow the enterprise’s choices: approving significant funding, entering the vendor market, changing a shared capability, selecting a platform, creating a cross-unit data dependency, altering the operating model, or accepting a hard-to-reverse exception.

The response must be proportional. Not every trigger needs a review board or complete target architecture. Within a short service window, the architect can provide a one-page consequence scan: the decision being made, affected capabilities, dependencies, ownership questions, irreversible elements, options still open, and evidence required before the next gate. If no material enterprise issue exists, release the decision quickly.

Consider a customer-platform business case that already names a preferred SaaS product. Waiting until contract review turns architecture into validation. A procurement trigger at market engagement creates a better moment. The architect can test customer-data boundaries, integration obligations, channel impacts, vendor dependency, support capacity, and operating-model consequences while the shortlist and commercial position are still flexible.

This changes the conversation about governance. Early architecture is not another approval layer. It is a way to protect reversibility before money, reputation, timelines, and organizational promises make one answer politically difficult to change.

It also makes EA less dependent on personal access. New executives, project leaders, and procurement teams inherit the same decision triggers. Architecture coaching and independent transformation assurance can then improve the trigger thresholds, response quality, and evidence without turning every initiative into heavy process.

Before the next portfolio meeting, review the last five commitments that reached architecture late. Identify the earliest observable event that could have triggered a lightweight consequence scan. Put that event into the workflow.

The right invitation is an enterprise rule, not a calendar request.

Reflection

Which current decision still depends on someone remembering to involve architecture before the commitment hardens?

Practice

Review the last five commitments that reached architecture late. For each, identify the earliest observable funding, procurement, platform, data, operating-model, or exception event that should have triggered a one-page consequence scan. Add the highest-value trigger to the workflow with a clear owner and response time.

Welcome Comments

Darin Paton is the Owner of Cornerstone Consulting Inc., an Alberta-based enterprise architecture and SAP ERP transformation advisory firm serving organizations across complex business and technology change for over 15 years. 30+ years as an EA and advising SAP transformations.