Thank you again Alan for pointing this out. It reminded me of the old Beckhard-Harris Change Equation. At least three things are needed for change, I would probably reframe is at both the Information needs to be there, Opportunity for charge and Mindset as you put it.
The info is out there, and surely is opportunities for improovement. The key factor is imagining that things can be different.
Something I'd like to add is an alternative explanation for why this doesn't happen. While it's often true that "devs don't have a growth mindset", I believe most of the t ime it's more complex than that.
Here are some other possibilities (based on the Six Sources of Influence model):
1) They don't understand what's in it for them
2) They don't know how to make the change
3) They don't have the right people in the org pushing them to do it
4) They think they're alone and have no support
5) They are rewarded for sticking to what has worked in the past
6) They work in an environment that resists change
Another way I've heard this framed is:
1) Do they know they're expected to do X?
2) Do they know how to do X?
3) Do they want to do X?
Saying "devs don't have a growth mindset" feels like jumping to 3), and turning folks into villains without exploring the other possibilities!
Can it be both? I really like the SSofI model - hadn't heard of it before, but I'm going to use it going forward.
In Mindset, Dweck talks about the duality of folks who have growth mindset in some areas of knowledge, but are fixed elsewhere. I'm not saying that devs don't have a growth mindset /completely/ if they don't wanna, but they are certainly fixed mindset in that subject.
I stand by the statement that the best knowledge workers are those that are curious and seeking knowledge in EVERYTHING they try or are given an opportunity to do.
For the I Don't Wanna crowd:
1) Do they know they're expected to do X - yes - we asked them, and they said they don't wanna
2) Do they know how - when you offer to help them learn and they still don't wanna, they're stuck
3) Do they want to do X - Doing X makes them better at their job - but they don't wanna
Folks who answer "no" to those three questions too often are often unemployed.
Thank you again Alan for pointing this out. It reminded me of the old Beckhard-Harris Change Equation. At least three things are needed for change, I would probably reframe is at both the Information needs to be there, Opportunity for charge and Mindset as you put it.
The info is out there, and surely is opportunities for improovement. The key factor is imagining that things can be different.
updated my thougts here: https://leading-testing-activities.ghost.io/information-opportunity/
I really like how you explain things Alan 😙🤌🏾
Something I'd like to add is an alternative explanation for why this doesn't happen. While it's often true that "devs don't have a growth mindset", I believe most of the t ime it's more complex than that.
Here are some other possibilities (based on the Six Sources of Influence model):
1) They don't understand what's in it for them
2) They don't know how to make the change
3) They don't have the right people in the org pushing them to do it
4) They think they're alone and have no support
5) They are rewarded for sticking to what has worked in the past
6) They work in an environment that resists change
Another way I've heard this framed is:
1) Do they know they're expected to do X?
2) Do they know how to do X?
3) Do they want to do X?
Saying "devs don't have a growth mindset" feels like jumping to 3), and turning folks into villains without exploring the other possibilities!
What do you reckon?
Small world wow - ss of I is from JD Meier - I know (knew?) that dude
Dude. That's ridiculous.
Sometimes it seems like you know everyone!
Can it be both? I really like the SSofI model - hadn't heard of it before, but I'm going to use it going forward.
In Mindset, Dweck talks about the duality of folks who have growth mindset in some areas of knowledge, but are fixed elsewhere. I'm not saying that devs don't have a growth mindset /completely/ if they don't wanna, but they are certainly fixed mindset in that subject.
I stand by the statement that the best knowledge workers are those that are curious and seeking knowledge in EVERYTHING they try or are given an opportunity to do.
For the I Don't Wanna crowd:
1) Do they know they're expected to do X - yes - we asked them, and they said they don't wanna
2) Do they know how - when you offer to help them learn and they still don't wanna, they're stuck
3) Do they want to do X - Doing X makes them better at their job - but they don't wanna
Folks who answer "no" to those three questions too often are often unemployed.
Haha! I've definitely been in THOSE situations/conversations before 😬
For the avoidance of doubt, I'm not disagreeing with you. I'm trying to "yes and..." what could be behind the "I don't wanna."
The obvious next question is, how do we deal with teammates and orgs that don't wanna?
Could you share what you do in a future blog post please pal (unless you don't wanna 😜)?