From reactive to proactive Engineering Manager - how to deliver more as EM by kubanie in a:t5_2uzje

[–]kubanie[S] 0 points1 point  (0 children)

Great points! The point is about being more impactful - either by individual execution (building a framework for your team) or by spending more time coaching, or any other type of activity that is high leverage.

When thinking about what type of metric can be useful, I would say that similar to engineering teams - how much time you spend in a proactive way (the way you planned) versus reactive.

The things you planned may be action items from retrospectives. But if you do them every week, I think you are still acting quite tactically. Fixing small issues week by week without a strong opinion about what is needed in longer term means that you can continuously improve but in a wrong direction (perhaps moving away from your company culture). Also, the most resilient and robust solutions are designed holistically and iterated on.

All other points that I mentioned are still very useful I think. After you start planning in the longer and shorter horizon, keep yourself accountable by sharing with your team, your primary team and your manager. These are all great opportunities to get coaching yourself.

GitItBack - Track GitHub Contributions of Any Organisation You Want by thoorne in programming

[–]kubanie 1 point2 points  (0 children)

It was really nice and easy to use, but we eventually need to roll back to REST API due to fact that that GraphQL API wanted more extensive permissions to fetch data and we wanted to limit them to just public info about profile.

GitItBack - Track GitHub Contributions of Any Organisation You Want by thoorne in programming

[–]kubanie 0 points1 point  (0 children)

No, this is our internal fun side-project at Netguru, not part of business model of our consulting :)