3 ms·
I even setup my reports with a skills matrix which shows the skills they need to get to. Still find them not really pushing themselves.
by keeptrying 7y ago
I even setup my reports with a skills matrix which shows the skills they need to get to.
Still find them not really pushing themselves.
- commandlinefan 7y agoWell, I’ve been in situations where I was expected to learn this or that, but I was also expected to complete 30 or so “story points” per two-week sprint, and be available to troubleshoot production problems, and attend planning meetings - and the only things anybody ever asked for statuses on were the bug fixes and new features, so I always had to end up choosing before meeting my mandatory learning goals, meeting my mandatory feature implementation goals, meeting my mandatory bug fixing goals or meeting my mandatory meeting attendance goals; “learning” always ends up taking a back seat.
- keeptrying 7y agoYes. Very true. Scheduling learning is hard. And incentivizing it is even harder. I personally love to learn. It’s what I do best. If I don’t do it I get bored.
- tilolebo 7y agoI got the same idea during my last team lead gig. I introduced a "interests & responsibilities" matrix, supposed to align team members skills with their interests. Goal was to: * ensure all needed skills are covered within the team * foster collaboration between knowledgeable persons and those wanting to gain more expertise. But it's quite hard to use if you don't tie it to the team processes. It has to be visible and integrated to the team's workflow.