Hacker News new | ask | show | jobs
by AllegedAlec 2931 days ago
I think a lot of advice here implicitly assumes the following:

1: You are invested in the company in a serious way.

2: Your company is invested in you and wishes the best for you.

However, I think those are quite optimistic assumptions. There's a inherent tension between what you want and what the company wants. The company wants to invest into you the minimum required to both keeping you as an employee as well as allowing you to function as an employee. However, you have an incentive to keep learning as much as possible and broadening your horizons.

A manager's task is (at least in part) to try to resolve this tension. Your manager, however, has apparently decided to side with the company on this. There could be several reasons for this.

It's possible that he's a through and through company man, who believes that the company will do right by him and all other employees and that it would not be beneficial for the company (and thus not for any of the employees of this company) were you to go give this talk.

Another possibility is that he believes that you will not complain when being told that your wishes do not matter. This is quite common in IT related businesses, since in general these people are more agreeable and less likely to voice their opposition to someone they believe to have authority over them.

A third option will be is that he is afraid that if you are to give this talk and network at the event, you may find out that you're not being respected properly in your current company and may try to find your luck elsewhere.

I'd say that if you want to have a chance to establish a long-term working relationship with this manager, you need to find out what your manager's motivation is from keeping you from such events and based on that formulate a strategy for dealing with him/her.

1 comments

> you need to find out what your manager's motivation is from keeping you from such events and based on that formulate a strategy for dealing with him/her.

That's a pretty adverserial approach. Why not understand the manager's motivation and then work with him/her?

The "adverserial-ness" is also apperant in the possible causes you raised for the manager's decision (he's a company man / he's taking advantage of the fact that you're agreeable / he doesn't want you to work elsewhere). There can be other reasons, even with a manager that's 100% on your side. For example, maybe he worked hard to get approval for you to go to that conference, even fought his supervisors, but at the end he lost? That's why the best advice is to ask him to explain the decision, and not to come to the conversation with any assumptions.

Shouldn't the manager as a decent human being, upon so blatantly encroaching on another human being's personal time, be the one to explain himself and his reason for his refusal?
> There can be other reasons, even with a manager that's 100% on your side. For example, maybe he worked hard to get approval for you to go to that conference, even fought his supervisors, but at the end he lost? That's why the best advice is to ask him to explain the decision, and not to come to the conversation with any assumptions.

Fair enough. Maybe I should have said "managerial layers" when I said management.

TBF a manager that tried to get approval but got refused usually won’t reject the original request without explaination.

It’s poisonning the relation with the managee, so if it’s by mistake or from good intent, it’s such a bad move that maybe it’s best to not expect them to have a positive impact going further.

If it’s just some misunderstanding, there is a clear communication problem anyway, so situation would still be dire.

> That's a pretty adverserial approach. Why not understand the manager's motivation and then work with him/her?

That we are here suggests a critical disconnect with the manager already, so that's already failed.

The manager just pissed on the employee from a great height. It's the manager's job to explain exactly why this was reasonable (and it probably wasn't).