Design decision

As explained in Design for Developers

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

A design decision is a deliberate choice about how a product looks, works, or feels. Developers make these choices too: technical constraints, performance, and interaction quality can change the user experience. section 1.1.1 section 12.0

Make design decisions more useful by:

• Starting with user research so decisions address a real user or business need. section 4.3
• Using shared design vocabulary to explain trade-offs and reduce unproductive back-and-forth. section 1.1.1
• Checking technical effects, such as slow-loading animation, before treating a visual idea as final. section 1.1.1 section 12.0

Travel website homepage

A wireframe turns requirements into visible decisions: place a hero image below the header, emphasize vacation-package search, show benefits immediately afterward, feature trending destinations, and give group travel lower priority. Review the wireframe before refining it into measured mock-ups. section 10.2

Figure 10.1 We loosely place our blocks of content to figure out how we will group content and the basic hierarchy of the page.

Inspect the loose content blocks to see how grouping and hierarchy make early design decisions concrete before visual refinement. section 10.2

How Design for Developers covers it

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 it assumes

Assumes basic participation in product development while teaching design vocabulary and principles for developers from practical examples.

What you can do after

Apply research, vocabulary, wireframes, and technical judgment to make and explain better product decisions.

How it connects

Connects user research, visual design, user experience, wireframes, accessibility, performance, and developer communication.

liveBookmanning.com

Read Design for Developers on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Collaborative Software Design: How to facilitate domain modeling decisionsA design decision is a chosen resolution to a software design problem or alternative.

Compare how 2 books explain design decision →

Related concepts

• collaborative discovery and modelingused by · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
• researchused by · Research is the systematic investigation of a subject through gathering and evaluating information or evidence to develop understanding or answer questions.
• architecture decision recordused by · An architecture decision record is a document that captures an architectural decision, its context, rationale, and consequences.
• pro-con-fix listused by · A pro-con-fix list is a decision-making technique that records an option’s advantages, disadvantages, and possible remedies for its disadvantages.
• implicit architectureproduces · Implicit architecture is a software architecture whose significant design decisions emerge without explicit, shared, or deliberate design and governance.

This explainer was generated by Manning's knowledge graph from the text of Design for Developers. The section links point to the parts of the book it draws on.