Business Understanding
Connecting a design to the outcome that pays for it.
4 to work through
-
intermediate
How does knowing a company's business model change your architectural choices?
2 min answer -
intermediate
Why does an architect need to understand the business model, and what specifically changes in the design if they do?
2 min answer -
intermediate
Why does business understanding change an architect's technical decisions, not just their communication?
2 min answer -
advanced
A food-delivery marketplace takes a 12% commission on an average order of 400 rupees, and its contribution after paying delivery partners and payment fees is about 15 rupees per order. The platform team proposes a design that costs 3 rupees per order in infrastructure. Is that acceptable, and what does the answer change about the architecture?
3 min answer
3 terms in this topic
Business Understanding
Knowing how the organisation makes money, what it is trying to achieve, and what would damage it — without which architectural judgement has no basis.
conceptCommercial Literacy
Sufficient understanding of how the business makes money and what it is measured on to translate technical work into terms that compete for funding.
metricUnit Cost Ceiling
The infrastructure cost per transaction that the business model can bear, derived from contribution margin and fixed before design, which decides how…
Neighbouring topics
Meta-Skills
General material on how architects think and work.
Systems Thinking
Interactions and feedback loops rather than isolated components.
Trade-off Analysis
Making costs explicit and comparable rather than asserting a preference.
First-Principles Reasoning
Reducing to physics, mathematics and economics, then reasoning up.
Failure Thinking
Asking of every box and arrow how it fails and how you would know.
Constraint Thinking
Designing for the budget, skills and regulations that actually exist.
Pattern Recognition
Seeing a familiar problem, and checking whether the forces match.
Pragmatism
The simplest architecture that meets the requirements usually wins.
Judgement Under Uncertainty
Choosing the best worst case when information is missing.
Influence Without Authority
Getting decisions adopted when you cannot mandate them.
Mentoring
Growing architectural judgement in other people.
Continuous Learning
Staying current without chasing every new thing.
Estimation
Sizing work and cost honestly, with the uncertainty stated.
Prioritisation
Choosing what not to do, and defending it.
Research & Evaluation
Assessing a technology quickly without adopting it by accident.
Handling Ambiguity
Making progress when the requirements are not yet knowable.
Technical Leadership
Setting direction and carrying accountability without a team reporting to you.
Ethics in Architecture
Privacy, accessibility, sustainability and the consequences of a design.
Career Development
Growing from senior engineer to architect and beyond.