A few days ago, I was talking to a colleague who was introducing a career ladder in her organization and wanted to know about my experience when rolling out our career graph at Avature.
She introduced this change for many reasons, such as enabling people in their teams to be recognized inside and outside the company and providing managers and team members a guideline to navigate performance and career development.
The whole proposal was being delayed because there seemed to be an endless discussion about whether the job tiles should be private or public. Of course, both sides had strong arguments, be it one way or the other. So my advice was that they start going private first. This way, she can unlock the stuff that matters on the time and progress with all the other great things this change provides. In fact, it is probable that the need to make it public might become more/less evident after implementing it that way.
This is just one of the ways teams can unblock group decisions.
Follow me on Twitter or subscribe to the newsletter for more articles on software engineering leadership and troubleshooting software engineering teams' problems.
