I am an engineer and I am working in the software industry for many years now. Nowadays I take care for people - developers, team leaders, but even many more employees involved in running a successful business. I try to be a servant leader, who works with the people. Decisions are taken with the people and not for the people. Thereby, my profession has become coaching and mentoring rather than engineering.
“Whenever you’re thinking high level, someone will bring you down to earth and ask you to get into the weeds. Whenever you’re in the weeds, someone will complain that you’re not being high level enough. It’s the burden we bear. Just when you think you’ve figured things out, you’ll encounter a person who needs to see your roadmap, or backlog, or “sprint backlog”, or “project”, or “plan” in a whole new way. So…changing delivery based on context is important. You could argue that it is the biggest challenge facing PMs. It is a design problem!” “11 Ways I Visualize Product Development Work” @johncutlefish
When I was starting with agile teams many years ago, my main motivation has been to create more robust delivery processes. When I was looking at the findings, I was realizing, that I was not able to drive change by myself, so my motivation changed to empower the people in the teams to take actions on themselves. Now I realize, that my motivation has to be to foster a joint understanding of values and create room for the teams to take actions. Agile tools belong to the teams and not to me.