Here is a little thread on words. Words matter. By using slightly different words, you can nudge your organization in a new direction (assuming they take hold).
Take something subtle like replacing "project" with "mission". A mission feels more outcome oriented...(1/n
Take something subtle like replacing "project" with "mission". A mission feels more outcome oriented...(1/n
Or using the word "bet". Bet is nice, because you can attach it to something highly prescriptive. For example:
"Oh, so your bet is if we build this feature we'll see this positive outcome, right?"
Bet conveys uncertainty, value, investment, information...(2/n
"Oh, so your bet is if we build this feature we'll see this positive outcome, right?"
Bet conveys uncertainty, value, investment, information...(2/n
Lots of teams get stuck on problem vs. solution dichotomies. I prefer... "opportunity vs. intervention". Lots going on there. Problem conveys a binary "solving". Intervention feels experimental. Opportunity feels valuable (3/n
Stop shipping features, and start delivering "capabilities" or "accelerators" (etc.). Capability implies something new is possible/potential. It implies use. Feature sounds like a checkbox item (4/n
There are a lot of great hacks you can do on a #kanban board. For example, "done" is almost certainly not done. You've probably entered an adoption phase, or you are running an experiment/validating. Change it! (5/n
Even simply phrasing hacks can be effective ....instead of saying "deliver" you might say "trying" as in "we're trying _______ to see if it will impact _________, which we believe will impact ___________. " (6/n
These are things you can do without asking for permission. By being more impact focused in your language, you can show not tell.
