liveBook · Manning

Design decision

A design decision is a deliberate choice that resolves a problem concerning a software system’s structure, behavior, implementation, or user experience.

How 2 Manning books explain it

Collaborative Software Design: How to facilitate domain modeling decisions

A design decision is a chosen resolution to a software design problem or alternative.

How it is used
Uses collaborative modeling to make software and architecture decisions explicit within a technical, social, and business context.
How deep it goes
Distinguishes routine implementation changes from decisions that reshape architecture, and examines ambiguity, tradeoffs, and group consequences.
Examples
Uses BigScreen’s reservation system, EventStorming, ticket purchasing, and the “Anytime, Anywhere” campaign.
What you can do after
Apply collaborative modeling to identify alternatives, weigh tradeoffs, and communicate explicit decisions.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains design decision →

Design for Developers

A deliberate choice that shapes a product's visual, structural, interactive, or experiential characteristics.

How it is used
Guides research, design planning, collaboration, and implementation choices that shape the user experience.
How deep it goes
Explains rationale, research inputs, trade-offs, and wireframe workflow, but stops short of detailed implementation technique.
Examples
Uses research planning, a luxury travel homepage wireframe, content hierarchy, search prominence, imagery, and animation performance as examples.
What you can do after
Apply research, vocabulary, wireframes, and technical judgment to make and explain better product decisions.

Read how Design for Developers explains design decision →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.