We Are Agile - Let Us Count the Ways
***Warning the following can read very self-serving but it’s really just our reminder of how fortunate we are on what is a periodic self-reflective Agile audit we hope everyone does at times, so if you just wanted to read a rant or some solid practical tips, maybe come back next week.*** This...
***Warning the following can read very self-serving but it’s really just our reminder of how fortunate we are on what is a periodic self-reflective Agile audit we hope everyone does at times, so if you just wanted to read a rant or some solid practical tips, maybe come back next week.***
This week’s articles on our Chasing Psychological Safety newsletter were about two things: lessons thanks to being Agile and servant leadership and I wrote them both as an experiment.
You see, last week, multiple people were rather surprised when they realised I was writing two different newsletters. These were awesome people who were up to date with what | was writing week in and week out but on only one of the two. At the risk of sounding both immodest and naive, I had assumed there’s almost complete overlap between subscribers which is why I was double-careful not to repeat topics ad nausea and to adapt the tone to the topics. That assumption was wrong, but thinking about it, it’s not strange, as even if anyone finds my writings through some magical place that says “For clarity: Duena writes 3 times a week in these 2 different newsletters - Subscribe to both” - once people click on one, they won’t go back to look for the other. Before you wonder why I’m not simply checking the data to confirm or infirm this, it’s because LinkedIn offers no visibility to analytics of any kind when it comes to Newsletters.
As for the experiment, it was yet another one relating to my theory that we’ll never be able to quickly pay off some of the huge HumanDebt™ we have amassed before these two sides of “the people” coin - HR and IT (namely DevOps) start truly working together, so I wanted to see if those two topics, which would have seen a lively discussion here, would be creating as much of a buzz on there and unsurprisingly, proving what I was fearing - they didn’t.
Monday’s one was telling the -step-by-step- story of how we kept adapting our product to valuable customer feedback until we realised we ended up making an “accidental servant leadership development tool”, whereas the one on Tuesday has a video on how those feedback-ing customers had deep insights into why this new leadership mindset is essential.