MSFT words I have to unpack in every meeting:
-
MSFT words I have to unpack in every meeting:
- "ask" == "request"
- "inbox" == "include"
- "double click" == "discuss in detail"
- "learnings" == "lessons"
- "delighter" == "feature" (apologies to Kano) -
@slightlyoff "inbox", "double click", and "delighter" strike me as especially org-specific, but at least with the last one I had a chance of guessing the right meaning
Could you give examples of the first two?
-
@slightlyoff tbf kano model itself also just offers newfangled terms
-
@dotproto "One of X team's asks was that we inbox their code in our next release."
Absolutely cursed.
-
@[email protected] I feel like "right click" would be more appropriate than "double click."
-
@slightlyoff my ask is that you not use ask in this way
-
@zachleat May I ask why?
-
@slightlyoff you may but let’s circle back before we deep dive
-
@slightlyoff oh it’s not just you… we have most of those plus the new one just coming in hot is “crisp” == “clear”
-
@zachleat Great, I'll follow up offline.
-
@slightlyoff @dotproto I learned first about these terms when I read that Clipchamp is now a Windows inbox app.
-
@slightlyoff this feels more exec / older lead talk then msft specific. I've definitely heard all except "inbox" and "delighter" (that last one is so cringe omg) at Google.
-
@nsa "delighter" at least has a product theory genesis, but hearing it applied to, like, some tweak to settings UI...
Kano Model Product Prioritization
Prioritize product features for customer satisfaction and delight with the Kano Model
(www.product-frameworks.com)
-
Inbox is actually valid! Back from ye olde boxed software days, something like “calculator is included in the box with Windows” to “in-box” to “inbox”. Losing the hyphen makes it weird though.