Layers for design work (v 0.91)

I need to refer to this description of design work in my job so often that I decided to get it online to access it when needed.

Each of the layers feeds and challenges other layers.

Strategic layer (that should be to the right of the service layer) is intentionally left out. It feeds design work and design work challenges it. Designers can work with strategy, but ultimately assignment calls for some one else to resolve and decide strategy.

This set of layers is based on idea presented in Simplicity Shift (by Scott Jenson). Hopefully this framework helps you to clarify things as much as it has helped me.

→ If you want to share insights or experience tweet a link at #4layers and/or directly to me @vesa_YLE.
→ Comments and thoughts in 4layers blog.

Presentation layer Task layer Infrastructure layer Service layer
ensures… visual integrity coherency feasibility suitability
observes… aesthetics & understanding tasks & actions efficiency goals & acceptance
works with…
  • displays
  • controls (appearance)
  • layout
  • visual style
  • use cases
  • key path
  • controls (input and feedback)
  • framework
  • processes
  • roles
  • organisation
  • hardware & software
  • personas
  • value hypothesis
  • requirements
  • scenarios
example 1, video player: what kind of buttons would be good for these controls and this player and how should they be arranged? how should this kind of video player be controlled and what would be the best controls? what kind of video activities can we support and which of them we are good at? is video player best way to support the users' goals, and if so what kind of a video player should it be?