Paying Tech and Human Debt Off Is Adulting
Anti-Impression Management and Clarity practice: I wrote a book called “People Before Tech: Psychological Safety and Teamwork in the Digital Age” and you can find a discount for it at the bottom of this page., Also, we make software that measures and improves Psychological Safety in teams. If...
Anti-Impression Management and Clarity practice: I wrote a book called “People Before Tech: Psychological Safety and Teamwork in the Digital Age” and you can find a discount for it at the bottom of this page., Also, we make software that measures and improves Psychological Safety in teams. If you care about it- come talk to us.
We’re currently running a 4 weeks license-free trial promotion at www.peoplenottech.com come and talk to us.
---------------------------------------------------------------------------------
In this week’s articles on the “Chasing Psychological Safety” newsletter we dissected the notion of HumanDebt™ both in terms of how it manifests itself at an enterprise-level versus a team level in this article and in yesterday’s video, the “now what?” in terms of reducing it.
In today’s discussion here - what are the parallels to the Technical Debt? Left for later as insufficiently explored but mighty interesting- “Is Human Debt in a technical organisation different?” - Is it causing more Tech Debt? Is it the culprit for turnover more so than in other organisations? Is it more closely reflected in a lack of performance/defects/support issues/a culture of fear of testing, etc? Are developers more or less prone to accumulate Human Debt and are they best suited to clear it? Is the psyche of the technical knowledge worker different, are they more used to and accepting of failure and therefore more fearless or are they expecting less on the human work side?