liveBook · Manning

Goal

As explained in Design for Developers

A user goal is a specific outcome that a user seeks to accomplish through a product or interface.

A user goal is the specific outcome or task a person comes to a website or application to accomplish. Good interface decisions satisfy these goals while also contributing to relevant business goals. section 4.1.5

Define user goals clearly enough to guide design, development, and evaluation:

  • Make the goal specific rather than general or vague. section 4.1.6
  • Make success measurable with data or analytics. section 4.1.6
  • Make it actionable by connecting it to concrete design and development tasks. section 4.1.6
  • Keep it relevant to the user’s needs, realistic, assigned to an owner, and tied to a time frame. section 4.1.6

Retail product page

A shopper may want to find a clothing item, check its availability, sizing, and price, and purchase it. A product page can support these goals with product information, images, and purchasing controls. Related-product components can also encourage additional items in the cart, connecting user needs to a measurable sales objective. section 4.1.5

How Design for Developers covers it

How deep it goes
Defines goals, distinguishes them from business goals, and specifies measurable criteria without detailing implementation internals.
Examples
Uses a clothing retailer’s product page, product information, purchasing controls, and related-product components.
What you can do after
Apply the S.M.A.R.T. framework to write specific goals and evaluate whether page features help users succeed.
How it connects
Connects user goals with business goals, wireframes, analytics, user research, and scope control.

Also explained in

Compare how 11 books explain goal →

Related concepts

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.