[EtCepeyd]

Nice; instead of burdening your boss with a decision, now you're burdening them with a ultimatum, with a deadline. I guess, as a manager, I wouldn't love anything more than a report saddling me with an arbitrary deadline, one I'd have to schedule along with the rest.

One of my managers used to tell me this, instead: ask for forgiveness, not permission. That one seems way saner to me.

[untrust]

Agreed. I actually think consensus amongst the team is more important than your boss. If a group of reports under some manager come to consensus on something they need to do, the opinion of the boss is kind of moot. I tend to operate using a bias for action, and the boss is clued in with information about our decision making, but asking for permission (or forgiveness) really just opens the door for micromanagement. This assumes basic trust has been established between the team and the manager, but in the end the technical decisions should be chosen by those on the team who are technical (read: not management).

Management (in my opinion at least) is primarily for resource allocation, career growth, and shielding the team from endless meetings and acting as a point of contact for upper management

[EtCepeyd]

> Management (in my opinion at least) is primarily for resource allocation, career growth, and shielding the team from endless meetings and acting as a point of contact for upper management

Agreed! (And we can also call "resource allocation" "setting priorities".)

[mooreds]

> One of my managers used to tell me this, instead: ask for forgiveness, not permission. That one seems way saner to me.

So you are suggesting making the change without consultation and then waiting for it to be discovered?

I guess that makes sense for certain kinds of situations, but the ones I can imagine don't sound very pleasant. Maybe I'm missing something. What is an example of a situation where you'd take this approach?

[imajoredinecon]

It’s really about (a) the wording (b) the level of risk.

For something that isn’t risky, I trust my reports to make reasonable decisions and wouldn’t benefit from the “I’m going to do this tomorrow unless you say no” approach. Instead, they can just tell me they’re doing it (or let me know after the fact, or add/FYI me on the code review, or not even mention it, depending on what it is).

For a decision that is more important/higher risk, they should get affirmative agreement rather than just hoping that I see the ultimatum and silently approve.

That’s why I’m with the GP that the ultimatum-with-deadline doesn’t seem like the best choice in any situation.

[EtCepeyd]

The advice refers to situations where you, the report, are both able and (well-informedly) willing to take full responsibility. "Ability" here means that, if your decision backfires, you can revert it, and/or contain the damage otherwise. Otherwise, you may be willing to take responsibility, but are unable to. In other words, this piece of advice applies to things that are ultimately under your control.

The background is that, even when something is (mostly) in your control, you may be tempted to ask for permission, in advance, just to distribute the responsibility to others (shift the blame, cover your ass). That delays things, and usually the manager will sense that they got burdened with the request-for-permission somewhat needlessly. In those cases, it's better to take initiative, and be accountable later on, because the latter is in your power, in the end.

(Of course, if you and your manager have dedicated time slots anyway, then bringing the topic up is prudent, as it will not require them to scramble for otherwise unallocated time.)

Conversely, if containing the potential damage is indeed not in your power, then you shouldn't go ahead without explicit permission. For things where you simply can't bear responsibility, a timeout from the approver is not a default "yes", but a default "no". If you can't bear responsibility, then you need explicit signoff from someone higher up that, should shit hit the fan, they will bear responsibility on your behalf -- and so a timeout is meaningless (it doesn't give you what you responsibly need).

Whenever you can afford to interpret a timeout whichever way you want, then you don't need to ask the question in the first place (--> don't ask for permission, just revert/contain the damage, if needed). Otherwise (--> the potential damage is beyond you), you need an explicit "yes" (which is the only case when you're off the hook).

The problem with your suggestion is that it assumes that you, as a report, are in a position to set deadlines for your superior(s); in other words, to allocate their time and priorities. Usually the exact opposite is true (by contract): it's your manager who sets your priorities. You can consider their (repeated?) failure to respond timely a true failure, but that doesn't give you the right to do whatever you want; it would be in bad faith / a form of vigilantism. Your option is to leave that manager.

[causal]

An ultimatum implies the manager has no choice- but they can just as easily say "hold up, don't do that until I get a chance to look at it".

But if a manager is suspicious of their reports and generally doesn't want them taking initiative, they probably have bigger problems.

[EtCepeyd]

> but they can just as easily say "hold up, don't do that until I get a chance to look at it"

This still requires them to take notice of your query, within the deadline of your choice; and that may not be a given.