Much work on software architectures has focused on how to document them. This has improved the understanding of real-life architectures. However, when multiple stakeholder concerns need to be addressed, they easily become scattered throughout the documentation. One reason might be that architectural views typically don't support the easy evaluation of trade-offs between conflicting quality attributes. When these concerns and related architectural decisions are distributed among many views, they are less obvious to architects and stakeholders. The authors propose an approach to creating architectural views that more prominently communicate the conflicts between key stakeholders' concerns. The approach also tends to reduce the amount of architectural documentation and thus increase its communication value by highlighting architectural decisions made to resolve the conflicts identified.