Conversation

Notices

1. Embed this notice
   mekka okereke :verified: (mekkaokereke@hachyderm.io)'s status on Tuesday, 26-Nov-2024 12:49:59 JST mekka okereke :verified:

   in reply to

   • SlightlyCyberpunk
   • David Megginson

   @admin @david_megginson

   Fair question, but it sounds like several related but slightly different topics.

   1) How do we properly recognize and reward "plus minus" teammate accelerators in technical orgs?

   2) How do we retain those accelerators, and make sure that they get to work at an enjoyable, sustainable, pace?

   3) How do we build organizational resilience? How do we reduce dependence on these accelerators to increase non-accelerated velocity?

   • Embed this notice
     SlightlyCyberpunk (admin@mastodon.slightlycyberpunk.com)'s status on Tuesday, 26-Nov-2024 12:50:05 JST SlightlyCyberpunk

     • David Megginson

     @david_megginson @mekkaokereke Sure, but what happens when this person quits because they're working 14 hour shifts seven days a week because nobody can get anything done without running it by them first? I have seen these people get a coworker coming to their house and pounding on their door to get them to login to help with something on their day off. That shit gets bad very fast.

     So perhaps your org can afford to say that this task is getting delayed a week because that essential person is out...but otherwise, if deadlines aren't gonna move for them alone, if whoever is there at the moment is going to be pushed to get that info however they can, then you need a different solution then just letting it all sit on one guy.