5 Questions Every Enterprise Architect Should Ask the C-Suite

Key Takeaways

• Map each L2 capability to the strategic objectives it enables, then flag any capability that supports zero objectives as candidates for divestment or deprioritization
• Use capability heat mapping to identify where operational performance gaps create the highest strategic risk before executives discover them during quarterly reviews
• Cross-map your operating model components against actual decision-making patterns to surface where governance theory breaks down in practice
• Apply value stream analysis to M&A targets before due diligence ends — integration complexity compounds exponentially after deal closure
• Create capability-based budget views that show executives how technology investments ladder up to business outcomes rather than IT deliverables

Question 1: Which capabilities differentiate us from competitors — and which should?

This question shifts the conversation from 'what technology do we need' to 'what business capabilities drive competitive advantage.'

Most executives can articulate their competitive strategy, but they struggle to identify which specific capabilities make that strategy possible. A aerospace manufacturer might compete on 'engineering excellence,' but that translates to dozens of L2 and L3 capabilities — from requirements management to regulatory compliance to supplier integration. The architecture conversation helps executives understand which capabilities truly differentiate (and deserve premium investment) versus which are table stakes (and should be standardized or outsourced). Start by mapping their stated competitive advantages to specific capability areas using BIZBOK capability domains. Then pressure-test each mapping: Does our actual capability maturity support this competitive claim? Are we investing in the right capability levels? This often reveals uncomfortable truths — like discovering that a 'customer-centric' company has fragmented customer data management capabilities, or that an 'innovation leader' has immature product development capabilities.

Question 2: Where do our operating model decisions contradict our strategic objectives?

Operating models often evolve organically, creating hidden friction that undermines strategic execution.

Executives design operating models during reorganizations, but they rarely validate whether those models actually enable their strategy. This question forces a cross-mapping exercise between strategic objectives and operating model components — organizational structure, governance processes, decision rights, and performance metrics. The disconnects are usually illuminating. A company pursuing 'customer intimacy' might have organized around product lines instead of customer segments. A business focused on 'speed to market' might have approval processes that require sign-off from seven different functions. Use TOGAF's operating model framework to systematically examine each component. Map decision rights against critical business processes. Identify where organizational boundaries create handoff friction in your most important value streams. The goal isn't to redesign the operating model in this conversation — it's to surface the strategic tax that current structural decisions impose.

• Map strategic objectives to required decision speed and coordination patterns
• Identify where current org boundaries fragment critical capabilities
• Trace approval workflows for strategic initiatives to quantify bureaucratic overhead
• Cross-reference performance incentives against strategic priorities

Question 3: What are the hidden dependencies that could derail our strategic initiatives?

Strategic initiatives fail when they encounter unexpected capability or process dependencies that weren't visible during planning.

Executives launch strategic initiatives based on market analysis and financial projections, but they rarely conduct dependency analysis using architecture techniques. This question introduces capability-based planning concepts to strategic conversations. Walk through their major strategic initiatives and map the capabilities each one requires — not just the obvious ones, but the supporting capabilities that enable execution. A 'digital customer experience' initiative obviously requires customer portal capabilities, but it also depends on identity management, payment processing, customer data integration, and service request routing capabilities. If any of those supporting capabilities are immature or under-invested, the entire initiative risks delay or failure. Use cross-mapping techniques to identify shared capability dependencies across multiple initiatives. This often reveals capability bottlenecks that could cascade failures across the strategic portfolio. The conversation shifts from 'can we build this' to 'can our current capability foundation support this' — a much more valuable planning perspective.

Question 4: How will our M&A targets integrate with our current capabilities?

Most M&A due diligence focuses on financials and market position while ignoring capability integration complexity.

This question positions architecture as a critical input to M&A decision-making, not just post-merger integration. Before executives commit to an acquisition, they should understand the capability overlap and integration requirements. Start with capability mapping for both organizations using the same framework — this reveals where capabilities are duplicative (potential synergies), complementary (strategic value), or conflicting (integration risks). Map the target's core value streams against your existing value streams to identify integration points and handoff requirements. Pay special attention to support capabilities like customer data management, financial reporting, and regulatory compliance — these often drive integration complexity and cost. Use heat mapping to assess the maturity gap between corresponding capabilities in both organizations. A mature organization acquiring a startup might need to elevate the target's governance and compliance capabilities. A traditional company acquiring a digital-native firm might need to adopt the target's customer engagement capabilities. This analysis should inform both the acquisition price and the integration timeline.

• Map both organizations' L2 capabilities using identical frameworks for comparison
• Identify capability overlaps that create consolidation opportunities or integration risks
• Assess maturity gaps that require capability elevation in either direction
• Model post-integration value streams to validate synergy assumptions

Question 5: How do our technology investments translate to business capability improvements?

Executives approve technology budgets but rarely see clear connections between IT spending and business capability enhancement.

This question reframes technology investment discussions around business outcomes rather than technical deliverables. Most IT roadmaps present projects in technical terms — 'CRM upgrade,' 'cloud migration,' 'API modernization' — that don't connect to business value in executives' minds. Capability-based planning provides the translation layer. Map each major technology initiative to the business capabilities it's intended to improve, then define specific capability maturity improvements you expect to achieve. A CRM upgrade should improve customer relationship management capabilities — but which specific L3 capabilities will improve, by how much, and with what business impact? Use capability maturity models to create before-and-after assessments that executives can evaluate. This approach also reveals technology initiatives that improve technical architecture without advancing business capabilities — these should be justified as technical debt reduction, not strategic investment. The conversation shifts from 'trust us, this technology is important' to 'here's how this technology investment advances these specific business capabilities that enable your strategic objectives.'

Pro Tips

• Prepare one-page capability heat maps before every C-suite meeting — executives consume visual information faster than written analysis and remember it longer
• Use the Business Architecture Guild's BIZBOK capability reference models as conversation starters, but customize L2 and L3 capabilities to match your industry and business model
• Schedule quarterly 'strategic dependency reviews' where you walk through major initiatives and update capability requirement mappings based on actual execution experience
• Create capability-based business cases that show ROI in terms of capability maturity improvements, not just cost savings or revenue increases
• Build cross-mapping artifacts that connect strategic objectives, operating model components, and capability requirements — executives need to see these relationships visually to internalize them