Backward Design Der

Mon, 01 Jan 0001 00:00:00 +0000

What you were doing was closer to backward design derivation:

user need -> required outcome -> user workflow -> what the system must make possible at each step -> system responsibilities -> design

In Intent Driven

Mon, 01 Jan 0001 00:00:00 +0000

In the context of software engineering and architecture, let’s explore approaches where user needs, Jobs-to-be-Done (JTBD), or other product-framing things serve as the foundational framework for reasoning about a system. I raise this because many traditional frameworks–like the C4 model–rely heavily on structural diagrams but often lack an underlying setting (forces, factors, context, etc.). They map out the architecture but fail to articulate why a component exists in the first place. Beyond superficial interactions (e.g., ’the user sends an email, and the system responds’), we need models that clarify the actual problem we are solving.

Progressive on AI Engineering and Architecture

Backward Design Der

In Intent Driven