Architecture Use Cases effectively tell the story of your architecture to the people who need to understand it. In our People-Centric Architecture method, we use them to ensure that people are always the key driver for solution architecture decisions.

Any solution architecture is the result of a series of solution architecture decisions. Knowing when and how you document those decisions is a critical solution architecture skill.

We have all been in painful, ineffective meetings that feel like they are needlessly wasting our valuable time. You can stop the madness by setting the standard for effective meetings with these tips.

Nobody likes meetings, so when you schedule meetings, you need to ensure they are effective. This "how to" will help you get off to a good start.

Learn how we use UML component diagrams to show how components are wired together to create solution architectures.

Solution architects document processes to understand business needs and describe system flows and logic. Enter the UML Activity diagram!

We have designed thousands of solution architectures. Here are some field-tested tips for better solution architecture diagrams.

A solution architect uses conceptual solution architecture diagrams to iterate on a high-level design and to share that design with others.

A solution options analysis is an effective format to both evaluate options and present recommendations to decision makers for approval.

Any solution architecture is a series of technology decisions. This is our best practice for evaluating technology solution options.

While they have their place, platform-specific diagram notations are not a good choice for solution architecture diagrams. Learn why and when it is appropriate to use them.

People power your journey to be a world-class organization. Here are 7 practices to nurture excellence and maximize people's performance.