An architect faces conflicting requirements from sales, operations, finance and compliance. What method resolves this without deferring to seniority?

The method

• Separate positions from interests. Sales wants a custom integration for a large customer; their interest is closing the deal. Operations wants fewer variants; their interest is a supportable estate. Positions conflict far more often than interests do, and the resolution usually exists at the level of interests — a configurable capability that closes the deal without creating a bespoke variant.
• Make the trade-off explicit and quantified. "This custom integration takes six weeks and adds a permanent maintenance obligation, against a deal worth X" converts an argument into a business decision.
• Identify who decides. Not who is most senior or most insistent, but whose accountability the decision falls under. An architect's job is frequently to route the decision to the right person rather than to make it.
• Record the decision and its rationale, so it is not relitigated monthly and so the person who inherits it understands the constraint.

The specific pattern in B2B commerce

Enterprise customers ask for bespoke behaviour, and each request is individually justified by revenue. The aggregate is a platform that is different for every large customer and cannot be changed.

The architectural response is a configuration surface deliberately designed to absorb the common requests — approval workflows, catalogue restrictions, pricing agreements, invoice formats, integration formats — so that the answer is "yes, configured" rather than "yes, built".

The requests that fall outside it should be refused or priced, and the discipline is to expand the configuration surface based on repeated requests rather than to build a one-off each time.

The failure to name

Compliance treated as an obstacle rather than a stakeholder. A compliance requirement discovered in month five replaces a design rather than adjusting one, and the cost of that discovery vastly exceeds the cost of including compliance in the design conversation.

The same is true of operations, which is routinely omitted from architecture discussions and then absorbs the consequences — a system that is elegant to build and miserable to run is a stakeholder analysis failure rather than an engineering one.