Architectural Tension Manager FAQs

Question 1

What is a 'productive tension' in software architecture?

Accepted Answer

A productive tension is a situation where two or more valid approaches optimize for different legitimate priorities, such as choosing between low latency and low cost, where the best choice depends on the specific deployment context.

Question 2

Does this skill provide a format for documenting decisions?

Accepted Answer

Yes, it includes a standardized documentation format for recording the context of a tension, the specific options available, the trade-offs involved, and the triggers that would eventually force a resolution.

Question 3

When should I stop preserving a tension and force a resolution?

Accepted Answer

Resolution should be forced when implementation costs become prohibitive, when approaches fundamentally conflict, when one option proves technically superior for the specific context, or to maintain necessary simplicity.

Question 4

When should I use this skill?

Accepted Answer

Use this skill when you find yourself oscillating between equally valid technical solutions or when stakeholders have conflicting but valid concerns that shouldn't be ignored for the sake of a quick consensus.

Question 5

How does this skill help in the actual implementation phase?

Accepted Answer

It suggests specific code patterns, such as using configuration flags or parallel modules with shared interfaces, to keep architectural options open instead of hard-coding a single choice too early.

Architectural Tension Manager

Architectural Tension Manager

Características Principales

Casos de Uso

Características Principales

Casos de Uso