Pavel @spavel.bsky.social · 10/04/2025This by the way is the most basic of Service Design principles. People are problem-solvers. Rather than impotently wait for a roaming group of heroes to come through their town, they try to fix the problem as they understand it, as best they can. 1613
Pavel @spavel.bsky.social · 10/04/2025The real value-add process looks something like this: - Find out what people are doing. - Understand why they are doing it. - If there's a better thing to be doing, figure out why they are not doing that instead. - Make the desirable behavior possible, visible, preferable, and understadable. 8899
Jesse Farrell @jfarrell.eurosky.social · 10/04/202515 years ago, my then-employer introduced Agile, but only to us folks in the hinterlands, away from the main campus, and in a DIY fashion, tailored to the quirks of the org. No tools beyond whiteboards and post-its—we were blissfully unaware of Agile products. Worked like a charm; I kinda miss it. 020
Keith Avery @slabgorb.com · 10/04/2025I do process like ants - repeat valuable behavior until it is stereotyped 010
Pavel @spavel.bsky.social · 10/04/2025"Your developers should just do Agile" follows the scolding pattern of every "users should just do X" that every bad designer uses to shift the blame from their poor work onto the user. Users will never "just do X" or "simply follow these 10 steps." The job is to understand why not, and fix it. 4704
Brian W Packer @thesmall001.bsky.social · 12/11/2025'Designing for Wants, Needs, and Aspirations is the path to Universal Access', to paraphrase Keates and Clarkson (2001). 010
Jon Asby @jonasby.bsky.social · 10/04/2025This sounds suspiciously like hard work. Incompatible with my values 010
Wanda @itswanda.bsky.social · 10/04/2025Amen. For years I called agile "developer-centered development." We lost focus on quality and writing things down, and while we hired a ton of designers and researchers, their work was too fragmented to matter. 020
