Why architects start with the business
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
show that a design without a business anchor optimizes the wrong thing.
Planned topics
- Technology exists to enable capabilities the business needs; start there.
- Business architecture gives a stable vocabulary shared with non-technical people.
- It shows where investment matters most and where "good enough" is fine.
- Org charts and system lists change often; capabilities and value streams change slowly.
Draft outline details
Demonstration
two pitches for Larkspur: "move to microservices" versus "improve click-and-collect so store pickups succeed first time". Ask which the CFO can fund.
Check your understanding
Why start from capabilities rather than systems?
Show answer
They are stable and in business language, so they anchor scope and priorities.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.