Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
4 to work through
-
advanced
A company operates one platform across many countries with different regulatory regimes, payment rails and tax rules. How should the architecture handle variation without forking per country?
2 min answer -
advanced
A financial-services group has 14 months before a new operational-resilience regime applies. It must hold a complete register of third-party arrangements supporting critical functions, documented and tested exit plans for each, and contractual clauses that roughly 40% of its 180 supplier contracts do not contain. The programme plans to build the register first because it is the visible deliverable. Sequence the work properly and name the point of no return.
3 min answer -
advanced
A mobility platform operates across several countries with different licensing, data residency, payment and labour regulations. How should regulation shape the architecture?
2 min answer -
advanced
An insurance platform's product roadmap is repeatedly disrupted by regulatory change. How should regulation be incorporated into the architecture rather than reacted to?
2 min answer
4 terms in this topic
Compliance Obligation Mapping
Translating regulatory text into specific, testable technical requirements attached to the systems they apply to.
conceptConfiguration Over Fork
Expressing per-market or per-tenant differences as configuration data and adapters behind stable interfaces rather than as separate codebases, so tha…
patternEffective-Dated Rules
Storing business and regulatory rules as versioned configuration with effective dates, so a record remains governed by the rules that applied when it…
conceptRegulatory Constraint as Architectural Driver
A compliance obligation that removes design options entirely, and therefore belongs among the first constraints identified rather than checked at the end.
Neighbouring topics
Business Architecture
General material on the business side of architecture.
Business Capabilities
What a business does, stated stably and independent of implementation.
Capability Mapping
Overlaying systems onto capabilities to expose duplication and gaps.
Business Processes
How work actually flows, including the handoffs nobody documented.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
Domain Boundaries
Where the language of the business changes, and services should too.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Product Thinking
Treating platforms and services as products with users and a lifecycle.
Business KPIs
The numbers a design is ultimately judged against.
Organisational Constraints
Team structure, skills and budget cycles as architectural inputs.
Time to Market
The constraint that dominates most products, and how to trade against it.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Business Cases
Expressing an architecture proposal in the currency that gets funded.
Operating Models
How delivery, platform and governance functions fit together.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Outcome Measurement
Knowing whether the thing you built achieved what it promised.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Business Continuity
What the business does while the system is unavailable.