Design and UX
Design thinking and service design
Design thinking is a way of framing problems before solving them: understand the people involved, define the real need, generate options, prototype and test, then loop back whenever the evidence says so. Service design applies the same attitude to a whole service, mapping what customers see alongside the backstage work that makes it happen. This topic covers both, and how to tell when either is helping or has turned into ritual.
Why this topic exists: Problem framing, ideation and the end-to-end service: IxDF's design-thinking and service-design literature; NN/g's Design Process and Customer Journeys topics; SFIA Customer experience.
Design thinking is less a technique than an order of operations. Before anyone proposes an answer, the team studies the people who have the problem, agrees what the problem really is, and only then generates and tests options. The Interaction Design Foundation credits the five-stage version most people learn to the Hasso Plattner Institute of Design at Stanford, known as the d.school, and insists that the stages are modes a team moves between as the evidence demands, not a corridor it walks once.
The five modes
- Empathise: watch and interview the people involved; UX research supplies the methods.
- Define: turn what was observed into a sharp statement of the need, often phrased as a question the team can work on.
- Ideate: produce many options before judging any, then pick a few worth making.
- Prototype: make each option concrete enough to react to, as cheaply as possible; see prototyping.
- Test: put the prototypes in front of real people and let what happens send the team back to whichever mode needs another round.
Google's UX programme devotes its second course to the first three modes, a fair indication of how the method reaches newcomers: as the front end of a product design process, before anything is drawn in earnest.
From a screen to a whole service
Service design widens the frame from one product to everything that has to happen for a customer to be served: staff, places, objects, partner organisations and internal procedures. SFIA's customer experience skill covers the same ground from the employer's side, quality across every touchpoint and channel. The signature artefact is the service blueprint, which Nielsen Norman Group treats as a map linking people, props and processes to what the customer meets. Its lanes supply most of the vocabulary.
| Lane | What it records |
|---|---|
| Customer actions | The steps a customer takes on the way to a goal |
| Frontstage | What staff or self-service technology do in the customer's view |
| Backstage | Staff work the customer never sees but relies on |
| Support processes | Systems, policies and other teams that make the backstage possible |
The line of visibility between frontstage and backstage is where most service failures hide: a friendly app promising a delivery date that the warehouse system never agreed to. A customer journey map shows only the top lane; the blueprint shows why the journey breaks. In that sense a service resembles a design system, a set of parts whose consistency rests on agreements nobody outside sees.
When the method turns into ritual
The familiar failure is a workshop that produces walls of sticky notes and no decisions. Design thinking without real participants is brainstorming with a vocabulary, and a blueprint drawn without backstage staff in the room is guesswork. Judge the method by what changed afterwards, not by how lively the session felt.
People who practise both disciplines move into service designer, customer experience and innovation roles, and into product management, where framing the problem fills much of the working week. The design hub shows how these roles sit beside research and interaction design.
Next to this topic
- UX researchInterviews, usability tests, surveys, analytics and when to use which: NN/g's Research Methods and User Testing topics; SFIA User research; the fourth course of Google's UX programme.
- UX and interaction designInformation architecture, flows, patterns and the behaviour of interfaces: NN/g's Interaction Design and Information Architecture topics, IxDF's UX and HCI literature, SFIA User experience design.
- UI and visual designLayout, typography, colour, hierarchy and the craft of the screen: NN/g's Visual Design topic, IxDF's UI design, colour theory and Gestalt literature.
- Design systemsTokens, components, documentation and governance so that many hands ship one product: the site's design-system concept, IxDF's brand-guidelines literature, and the meeting point with front-end code.
- Accessibility in designWCAG's four principles and conformance levels, assistive technology and inclusive design: NN/g's Accessibility topic, SFIA Accessibility and inclusion, W3C WAI.
- Prototyping and design toolsFigma, Sketch, Adobe XD and the prototyping loop from paper to clickable: NN/g's Prototyping topic; Udemy's Design Tools shelf; the third and fifth courses of Google's UX programme.
- Graphic design and illustrationComposition, type, image and print, and the Adobe and Affinity toolchain: SFIA Graphic design; IxDF's graphic design literature; Udemy's largest design shelf after 3D.
- 3D, animation and motion designModelling, rigging, rendering and motion in Blender, Maya, 3ds Max, ZBrush, After Effects and Cinema 4D: SFIA Animation development; Udemy's largest design shelf.
- Web designLayout for the browser, responsive design, WordPress themes and the hand-off to code: Udemy's Web Design shelf; the programming field owns the build.
- Design assets and licensingTemplates, stock media and fonts, and the licences that decide what you may do with them: the site's design-assets concepts and the /digital-assets/ partner picks.
Concepts to know
Glossary entries with the reason each one matters here.
- Design system
Services are systems too.
Frequently asked
- Is design thinking only for designers?
- No. It was popularised precisely as a way for mixed teams of managers, engineers and designers to approach unclear problems together. What it does require is access to the people affected and willingness to change course when they show you were wrong.
- How does a journey map differ from a service blueprint?
- A journey map follows one customer's steps, thoughts and feelings through an experience. A service blueprint takes the same steps and adds what the organisation does in view and out of view to deliver each one. Use the map to find where the experience hurts and the blueprint to find why.
- Does design thinking fit agile teams?
- It fits well at the front of the work, when a team is deciding what to build. Short discovery cycles of research, framing and quick prototypes can feed an agile backlog, and testing continues inside the sprints. Friction appears only when discovery is skipped because delivery is already scheduled.
Courses in the directory
63 courses are filed here; the top 6 by our ranking, details and the provider link on each course page.
Transforming Digital Learning: Learning Design Meets Service Design
Deakin University
Last reviewed 26 September 2026 · Getting Digital
