-
TIL new ways to use valence vs salience (thanks rachelnabors). The amygdala is all up in my team conversations every week, and the different about affective or important is key for making decisions. Source: sciencedirect.com/science/article/abs/pii/S0166432821002436On twitter.com
❤️ 1 Favorite 2021 Nov 15 Mood +4 🙂
-
…in reply to @ZekeAranyLucas
Like last week, the team was discussing how to incorporate more automated testing. Advocates want it elevated in priority. Nobody will disagree about the importance of improving the quality of our code. So it’s a no brainer.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
Except it isn’t! Testing is potentially an infinite investment because our scenarios and systems aren’t provably finite. Adding a bullet to guidelines and doc templates doesn’t change behavior, it just makes people feel good. “See, we care about quality, it’s in our docs.”Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
I was proposing that we separate our discussions into conceptual work and project work. Conceptual work answers the impetus from team valence, but project work answers the impetus from team salience.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
Conceptual work * unbounded and evolving over times * Belongs in our documentation. * Needs projects to be proven/accepted * Needs time and endurance to get tractionPermalink On twitter.com
-
…in reply to @ZekeAranyLucas
Project work * bound to time frames * Bound to the business metrics/needles/objectives * Belongs in our roadmap * Needs management approval to get funding.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
I don't want to dismiss the value of feeling good about our attitudes and ideas (valence), but I wanted to make sure we get some outputs that will also make a difference in our outcomes (salience). <3Permalink On twitter.com