3 ms·

Earlier in my career, I would hear my manager say something about a specific situation and I would extrapolate that into a general belief and theoretical/academ

by bwh2 5y ago

Earlier in my career, I would hear my manager say something about a specific situation and I would extrapolate that into a general belief and theoretical/academic debate that frustrated everyone. Make sure you're not doing that. As a manager, sometimes you need to say things like, "This bug needs to be fixed by EOD tomorrow" so that your team understands the urgency and your expectations. The more technical the manager, the more likely they can understand whether that expectation is reasonable.

decebalus1 5y ago
> As a manager, sometimes you need to say things like, "This bug needs to be fixed by EOD tomorrow" so that your team understands the urgency and your expectations. I'm sorry but you can do that without sounding both clueless and unreasonable. You can put everything else on hold, stop the line, explain why it's important for this to be fixed, etc.. to get the point across. "This bug needs to be fixed by EOD tomorrow" would chip away at the trust I have with management and depending on other factors would lead me to brush up my resume...
- tyingq 5y ago
  I agree, and I've been the manager in this situation. There's some reason he's saying "EOD tomorrow", so he should just share that. Like "It's likely we will lose this customer if this isn't fixed by EOD tomorrow...so please make this the only thing we're working until then".
  - sdgasg 5y ago
    Usually, you don't lose a customer over a bug in two days. Customers are reasonable usually and understand that it takes time to fix bugs. Most of other reasons like CEO doing a demo at a conference can also be managed. I really don't see a reason for hard deadlines ever. In fact, hard deadlines is sign of bad management with notable exception of startups and other young companies with no managers or new managers.
    - tyingq 5y ago
      Sharing the reason allows for that debate, or alternatives. Maybe the customer has some sort of demo or something, and you could offer a workaround in that case. Hard deadlines for some sort of fix or workaround do exist. Like "Earnings Call Tommorrow, and I can't just say ' I Dunno'"
      - sdgasg 5y ago
        I agree with statement "Hard deadlines for some sort of fix or workaround do exist". Key being get this done before CEO's big presentation or hard code something or CEO doesn't demo this feature. The point is no one dies if CEO doesn't demo it or feature is not complete by earnings call. Earnings call is known event, one should have better planned for it. And that bring me to people literally dying because of bugs in software like in cars or medical devices etc. That might be one time where I would have no problem sacrificing my family time for getting bug fixed. But most other situations are just artificial and deserve no extra stress.
- deleted 5y ago
  [deleted]

by bwh2 5y ago

decebalus1 5y ago

> As a manager, sometimes you need to say things like, "This bug needs to be fixed by EOD tomorrow" so that your team understands the urgency and your expectations. I'm sorry but you can do that without sounding both clueless and unreasonable. You can put everything else on hold, stop the line, explain why it's important for this to be fixed, etc.. to get the point across. "This bug needs to be fixed by EOD tomorrow" would chip away at the trust I have with management and depending on other factors would lead me to brush up my resume...

tyingq 5y ago
I agree, and I've been the manager in this situation. There's some reason he's saying "EOD tomorrow", so he should just share that. Like "It's likely we will lose this customer if this isn't fixed by EOD tomorrow...so please make this the only thing we're working until then".
- sdgasg 5y ago
  Usually, you don't lose a customer over a bug in two days. Customers are reasonable usually and understand that it takes time to fix bugs. Most of other reasons like CEO doing a demo at a conference can also be managed. I really don't see a reason for hard deadlines ever. In fact, hard deadlines is sign of bad management with notable exception of startups and other young companies with no managers or new managers.
  - tyingq 5y ago
    Sharing the reason allows for that debate, or alternatives. Maybe the customer has some sort of demo or something, and you could offer a workaround in that case. Hard deadlines for some sort of fix or workaround do exist. Like "Earnings Call Tommorrow, and I can't just say ' I Dunno'"
    - sdgasg 5y ago
      I agree with statement "Hard deadlines for some sort of fix or workaround do exist". Key being get this done before CEO's big presentation or hard code something or CEO doesn't demo this feature. The point is no one dies if CEO doesn't demo it or feature is not complete by earnings call. Earnings call is known event, one should have better planned for it. And that bring me to people literally dying because of bugs in software like in cars or medical devices etc. That might be one time where I would have no problem sacrificing my family time for getting bug fixed. But most other situations are just artificial and deserve no extra stress.
deleted 5y ago
[deleted]