What specific actions are you taking toward improving developer productivity?
Do you have a written plan?
Are you setting up an enablement team with the hopes of eventually getting around to reducing friction for developers?
Are you setting up the organizational structure before getting a real plan together?
or
Maybe you have a couple of high-level ideas about the problems you want to solve.
Let me ask a blunt question:
How do you know if your ideas really resonate with developers?
What if there are other friction points that are more costly and more detrimental to engineering productivity?
Before you dedicate resources to an engineering enablement team.
Speak with your developers and understand what they are actually dealing with.
Do a Gemba walk, sit in on a few retrospective meetings, send an email, do a survey, conduct a workshop.
The point is to do something now and get a solid plan in place to maximize your investment in reducing developer friction.
Best,
Andre
P.S. I just launched a free 5-day email course to help engineering leaders get a clear plan on the most impactful issues that are holding their developers back.
Go to https://southsoftwaresolutions.com/developer-productivity-launchpad/ to get it now.