Whether you’re struggling to improve your product, juggling too many conflicting feature requests, or facing growing levels of competition, a values-based approach to looking at those problems may provide the solution you need. Values-based Product Design Design ideas can come from anywhere – user research, ideation, a shower epiphany, brainstorming, a dream. You won’t implement most of them, luckily, but that doesn’t mean that they aren’t useful.
Kanban teams are supposed to “make policies explicit.” I’ve asked at conferences, in forums, and on Twitter, “How do you make policies explicit?” I’ve never gotten an answer. I suspect many teams don’t have a good way of capturing and communicating policies. Most policies come out of retrospectives. They address problems the team identifies. If you have a retrospective every two weeks, and in each one you make two or three improvements to your process, that’s a lot of changes.