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.

An information flow diagram is an effective way to understand a solution architecture - it is easy to create and intuitive for your audience. This "101" will get you creating them in no time!

We have a track record of hiring great people. How do we do it? Learn about the principles and process that helps us find the Wittij Consultants you love.

The solution user diagram is a quick and easy way to understand the scope of people's needs and the first critical step in designing a solution.

Here are some examples of non-functional requirements to help you on your journey to more successful technology projects.

Writing non-functional requirements can be a breeze if you know the tricks. Here are best practices for authoring and launching them.

Understanding non-functional requirements starts with understanding what they are, why they help, and how to apply them. This a 101 article on just that!

Technology guiding principles are the easiest way to start making better technology decisions that result in better business outcomes.