Sam Richard
@Snugug
BBQ lead, ChromeOS DevRel. Mostly food, sometimes design and development, especially for the web. 7008px tall. He/him.
An archive of my Twitter timeline up until I moved to Mastodon. You can find me there at @[email protected]
I think I’ve figured out what I dislike about how both Design Thinking and Agile are taught and practiced. In my experience, both have centered the practitioner (designer/engineer) and process over the user, outcome, and purpose of activities being performed.
That’s not to say they don’t talk about the user, outcome, or purpose, but those tend to be more theoretical things that are expected to come by centering the practitioner and process.
tl;dr Agile and Design Thinking and Lean UX and all of that only feel incompatible when they center practitioner and process instead of users and outcomes, which ultimately is the point of all of them.
I think that inverting the focus, and talking about cross-named-thing tools and techniques that may help you achieve things will make it tedious to actually teach and practice user-centered, outcome-driven delivery
The most productive I’ve been on a team is when we didn’t strictly follow Design Thinking or any Agile method, but rather used the practices we found useful from lots of different things to steadily deliver user-centered value.