D is for Deadlines
Probably one of the most universal wellbeing drivers: the dreaded deadline.
I remember, many years ago, a new manager came in and told the engineering team that if the tight deadline wasn't met, he would resign his position.
His motive was to get everyone on the team to agree to work harder and longer to get it all done.
The deadline was never met, and he never resigned his position. Surprise, surprise.
This is NOT how you run any team. A real leader would push back and protect his team from overwork.
As engineering leaders, the mental wellbeing of your team must come before unrealistic deadlines.
E is for Expectations
In the age of AI, speed is probably one of the first expectations organisations have for their tech teams.
If you ship something quickly once, that becomes the new normal for every piece of work after it.
Better education of stakeholders about what is realistic is needed to avoid the mental pressure that unrealistic expectations put on dev teams.
It is not just about getting the work done but getting it done right.
F is for Fatigue
Maybe a little contentious, as some may argue that with AI the job of a software engineer is less tiring.
Before, developers were expected to hold whole systems in their heads all day. Now, with AI, there is a new challenge: keeping up with your agents.
Then there's the mental strain of not wanting to stop working, because you can keep telling agents what to do from your phone, your laptop or anywhere else.
Originally posted on LinkedIn.