Resolving Architecture Clarity in Design Contact

About

Resolving Architecture exists to make architecture decisions clearer, more accountable, and more usable.

Resolving Architecture provides senior architecture consulting and structured product support for technology leaders facing consequential design decisions.

The work centers on stakeholder understanding, trade-off clarity, risk visibility, decision ownership, and practical implementation guidance.

Contact Resolving Architecture View engagements

Experience

Senior architecture experience across complex technology environments.

25+ years

Principal-level experience across enterprise, solution, application, integration, security, data, platform, and product architecture.

Meridian

A product created by Resolving Architecture to make architecture evaluation, decision capture, and governance more repeatable.

Professional background

Led by Brian Taylor.

Senior architecture background

Resolving Architecture is led by Brian Taylor, whose architecture experience spans more than 25 years across enterprise, solution, application, integration, security, data, platform, and product architecture.

Past engagements have included architecture evaluation, modernization planning, solution design, integration strategy, security alignment, data architecture, scalability work, governance, product prototype architecture, and complex technology decision support.

View Brian Taylor on LinkedIn

Architecture decisions, not architecture theater

The focus is not producing documentation for its own sake. The focus is helping leaders and teams identify the decisions that matter, understand why a direction is chosen, preserve the rationale, and create implementation guidance that can survive delivery pressure.

See representative architecture engagements

Point of view

Architecture is the design decisions required to achieve stakeholder consensus.

Architecture becomes useful when it helps people decide. Diagrams, documents, standards, tools, and reviews can all help, but they are supporting mechanisms. The central work is clarifying what must be decided, why it matters, who owns the decision, and what trade-offs are accepted.

Resolving Architecture helps teams understand the architectural landscape, make better decisions, preserve important context, and create accountable ownership for implementation.

Customer leaders remain accountable for their decisions. Resolving Architecture helps make those decisions clearer, more defensible, and more actionable.

Operating principles

Practical architecture without unnecessary process.

  • Start with the decision: define what must be decided before producing artifacts.
  • Make trade-offs visible: every meaningful architecture choice has consequences.
  • Respect current reality: target-state architecture only matters if the transition path is practical.
  • Preserve rationale: decisions lose value when teams forget why they were made.
  • Support implementation: architecture should guide engineering work, not sit apart from it.
  • Keep governance lightweight: use just enough structure to make decisions repeatable and accountable.

Why Meridian exists

Structured product support for repeatable architecture governance.

Meridian brings structured architecture evaluation and governance into a product workflow. It is grounded in practical architecture experience, but customer leaders remain accountable for their own architecture decisions.

Consulting and Meridian are complementary ways to improve architecture decision quality: senior judgment when the decision is consequential, and structured product support when governance needs to become repeatable.

Explore Meridian

Start a conversation

If an architecture decision needs to be clearer, Resolving Architecture can help.

Discuss an assessment, modernization challenge, integration concern, governance need, or a specific decision your team needs to resolve.

Discuss an architecture challenge View engagements