Course contentsShow
← Software Engineering
Lesson 1229 of 1,93337. Software Architecture FundamentalsFree lesson

Stakeholder Concerns as Drivers

How different stakeholders' needs and priorities influence architectural decisions and trade-offs.

Stakeholder Concerns as Drivers

You'll learn how different stakeholders' needs and priorities shape the architectural decisions and trade-offs you make when designing software systems.

The Core Idea

Architecture doesn't exist in a vacuum—it serves people. Every software system has stakeholders: the CEO who wants fast time-to-market, the operations team that needs to maintain it at 3 AM, the developers who'll extend it next year, the security team worried about breaches, and end-users expecting speed and reliability.

Each stakeholder has distinct concerns that drive what the architecture must achieve. These concerns become your architectural drivers—the forces that shape your decisions about structure, technology choices, and trade-offs.

Balancing Competing Priorities

Think of architecture as a tug-of-war where multiple teams pull in different directions:

  • Product managers want features shipped quickly (speed to market)
  • Operations wants simplicity and monitoring (maintainability, observability)
  • Security wants defense-in-depth (complexity, latency overhead)
  • Finance wants low cloud costs (resource constraints)
  • End users want fast responses (performance, SLOs)

You can't maximize everything. If security demands encryption everywhere, you'll trade some performance. If operations needs simple deployments, you might sacrifice some cutting-edge optimization.

The Architect's Job

Your role is to elicit these concerns, understand their relative priorities, and make explicit trade-offs that serve the most critical needs. Document why you chose microservices over a monolith, or why you accepted higher latency for better security—these decisions trace back to stakeholder concerns.

When stakeholders conflict, architecture becomes negotiation: "We can deliver this fast OR this secure, but not both immediately. Which matters more for launch?"

Key Takeaway: Architecture succeeds when it addresses the right stakeholder concerns at the right priority—understanding WHO cares about WHAT drives better decisions than technical preferences alone.