All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Designing Small in Agile: Why Smaller Slices Are Harder Than Full Systems

By

Ideas powered by Invisible Machines

2mo ago· 6 min readenInsight

Summary

Päivi Salminen argues that the real challenge of Agile for designers isn't speed—it's learning to design smaller, more focused slices that deliver immediate value. Drawing on over a decade of experience in Agile marketing teams, she contrasts the designer's natural instinct for holistic, full-system thinking with Agile's demand for incremental, horizontal slices. She explores the tension between wanting to design the "whole cathedral" and the need to deliver "one brick" that works now, offering insights on how to find the smallest slice that still provides real value without losing sight of the bigger picture.

Source

UX MagazineDesigning Small in Agile: Why Smaller Slices Are Harder Than Full Systemsuxmag.com

Key quotes

· 5 pulled
Agile rarely asks designers to move faster—it asks them to design smaller.
Most designers are trained to think in full systems, but agile teams don't want the whole cathedral; they want one brick that delivers real value now.
You think you know agile until you really have to design in agile.
The far less obvious skill of designing smaller, not faster.
Understanding the difference is everything.
Snippet from the RSS feed
Agile rarely asks designers to move faster—it asks them to design smaller. Päivi Salminen on holistic instincts, horizontal slicing, and the smallest slice that still delivers real value.

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.