Live data from Hacker News

Ask HN: My boss doesn't think I'm doing good work, how to proceed?

news.ycombinator.com

61–70 of 506 posts

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#61
post #5

Talk to your manager about it, 1-1.

Indeed, this is what you should do. Proceed a bit carefully if you don't have a good relationship yet with your manager: by good relationship, I mean knowing them enough to figure out how much you trust them.

You would also benefit from talking to other engineers who have more experience, especially in that company. It is easier to talk casually to people you don't report to.

It is difficult to give more concrete advice w/o more context:

* a "best case" scenario is that the senior manager (your manager's manager) was having a bad day, maybe got themselves into trouble for X reason. Managers are human too.

* another scenario is that your senior manager is actually still inexperienced. E.g. did not have time to talk to your manager first and then decided to skip directly, etc.

* a worst case scenario is that there is something weird going on between your manager and his manager.

[edit] A manager's manager talking to an individual contributor (you), especially about technical details of a project is just weird. It is hard for me to think of a scenario where I would do this. Why ? Because as a Manager's manager, you lack context about why certain things happen. And the person responsible for your outcome is by definition your manager. You mention both manager being smart people, "knowing their stuff": they may lack experience on the "people manager" side of things. That's often a drawback of working in very technical environments.

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#62

If you are writing code every day, it works, and your peers (not your manager) are using it to meet deadlines and ship more working code, don't listen to your manager. If your code has observations and design issues it shouldn't get merged unless everyone is ok with the tradeoffs, if it's being merged and people are not ok and you are junior developer, it's your managers fault and you probably need better process in…

OP's description sounds like they are working alone on this project and that there's no peer review. Which sounds like a weird thing to do for a junior dev that just got out of college.

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#63
post #8

The first meeting where your manager just abandoned you and you ended up talking to your manager's boss is totally inappropriate. Being so new to the job basically all the responsibility is with your direct manager and her boss is wrong to dump on you without your manager present. I'd give it another chance though, sounds like the work is fun and maybe you can communicate your concerns to your direct manager.

Anytime your skip-level steps in to guide your work directly, it’s either a failure of your manager or the skip-level themself.

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#64
Highest order bit:

This sounds like you have an inexperienced manager. You should be given baby projects, with clear (generous) deadlines when you’re this junior.

Second order:

The most common failure mode I see in new employees (some of them quite senior!) is, given a 12 part project, thinking it makes sense to spend 1/4 of the allotted time on part one. This is almost never the right thing to do.

You have to spend much less than 1/12 of the effort on each individual piece, even if this means you’re hacking it together, THEN fill in the gaps, or you are setting yourself up for disaster.

A really good manager would’ve given you a 2-3 part project, as your first “real” project, so that you could learn this lesson without much harm done.

If, in fact, you got a project that needed only a few things done, and you committed way too much time to the first part, then this is just a lesson you’re learning about shipping real projects!

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#65
Your boss has a problem of some kind and is trying to scapegoat you. Write up notes in as much detail as you can recall and store a copy somewhere with a date stamp - if you're not comfortable putting it on the internet, send yourself a letter by registered mail and don't open it when it arrived.

Then keep it on file and return to work. Change tack as explicitly instructed by otherwise just keep doing your job. Your contemporaneous records of the conversation are insurance that you can mention if/when you find yourself having an uncomfortable conversation in a HR office.

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#67
Former individual contributor, former middle-manager and former "VP-level boss" here. I've seen all this before, several times over.

Know that this will recur throughout your career, most likely. Your boss is disconnected from the project and the manager, and the boss has no idea what's happening at the individual contributor level. It's always "you shoulda done this, you shoulda done that" It's always in retrospect from a boss like this, never, ever in anticipation. Did the manager or boss say: "Hey dazeandconfuse, we've seen this before, you can look at how the Widgetspinner project solved that issue for guidance." No. They're not there for you. They're there to blame you when their failure to support you manifests itself.

I'd bet that the manager and the boss don't have productive 1-1 sessions on any regular basis (or even very good communication) and thus the boss doesn't know the status of things. The boss ultimately is too lazy to care or really be involved, doesn't listen, or the manager sugarcoats things, or lies outright, or a combination of all these things. No one is accountable on a day-to-day basis. The boss never, ever looks at the project plan with any comprehension - even though they're constantly insisting you document stuff that they'll never read. Especially action items from meetings.

In cases like this, the boss will pretty much always over estimate how quickly things can get done, and under estimate how much work and complexity is involved, or what the real bottlenecks are (and in all likelihood that the boss is a big bottleneck themselves. They are overconfident in the resources they have, and probably don't institute positive processes for a happy, productive workplace. The boss will ignorantly sabotage things by withholding information, failure to be involved, fail to communicate, fail to have clear goals, failure to identify outcomes, failure to see the big picture.

We used to have a phrase about changing requirements, the case of "The Executive Drive By". The boss will make a suggestion for an enhancement: When that enhancement changes the schedule and delays a project then "It was only a suggestion, I didn't set a new requirement", or if the project stays on time without the suggestion then it's "Hey you guys screwed up, where are the blinkenlights I asked for, can't you guys get this right? Who is running this project?!?" Win-win for them, lose-lose for you. Just like they want it to be.

I'd take it as a signal of poor communication up-to and down-from the boss, and in all likelihood the boss isn't really interested in ensuring the manager's success. If the boss was unhappy with progress, the manager should've known long ago, before the deadline slipped, and it should've been communicated by the manager down to everyone with new expectations and goals and a plan that eveyone was on board with -- including the boss. That that didn't happen tells you everything you need to know. There are problems. Probably systemic, and unlikely to change.

It's a sign of typical dysfunction and the natural adversarial relationship between manager and boss. Eventually the boss will seek scapegoats down the line when things don't go well, never accepting any blame themselves. Never.

Eventually won't go well enough that a "reorg" will happen and people will be shuffled around, someone will get fired, and ultimately nothing will change. I've seen it happen over and over again.

Also, know that you don't owe your company jack shit. They are not, and will not be loyal to you, ever. Ever. They will cut you at first necessity. Be prepared to do the same at any time. Boss will blame manager, manager will blame you, people will get fired, unjustly or not. Probably unjustly. Bosses never fire themselves, ever. They will always place blame down the line. Always. Bank on it.

PROTIP You're new in your career: As long as you are employed, powersave a portion of your income into a separate savings area as F-U money -- so you can go 6 months or more that you can live on in between gigs. This gives you ultimate power over the boss: "If you don't like my work or my performance, F-U, I'm out."

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#68
This is not how a serious professional would provide feedback to a junior level engineer fresh out of college. If your boss is tearing you down instead of building you up, I'd go look for something new. You need mentors and people that want to see you grow.

As a director if I had the same thoughts, I'd approach it much differently.

  - What do you think were the major blockers?
  - What do you think we can we do differently to speed up next time?
  - Have you had an opportunity to see , looks like some really cool ideas and examples
  - What were the good parts of this project in your opinion?
He had an opportunity to build a rapport with you and decided instead to instill fear and doubt. I have never called myself the boss, I'm on your team, my goals are just a little different, but most of them hinge on the fact that you'll be successful, and that it's my job to ensure that success.

Plenty of people are hiring, you shouldn't have to feel like this for weeks on end because he lacks intelligence and empathy.

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#69
All the criticisms you mention concern the responsibility of others and do not reflect on the work you have put in (expected scope change, deadline changes) so it sounds like there is a communication issue between your manager and the boss. It was therefore ‘unfortunate’ they werent at the meeting. I don’t see how you could have produced anything more based on your account. Perhaps you’re able to reflect similarly.

Besides remind yourself you are all working towards the same goal and put your best into the job, projects are never ideal, that’s ok

Re: Ask HN: My boss doesn't think I'm doing good work, how to proceed?

#70
First, make sure you’re not over reacting to negative criticism. Remember, you paid your university and rated your professors. As a result, they probably coddled you to an extent. Now you’re in the real world, people are going to be brutally honest.

Second, ask for constant feedback. I try to ask my boss what I should keep doing and what I should start doing and if there’s anything I should change.

This serves two purposes. It helps me grow and make sure I’m meeting expectations. But it also serves as an anchor for your boss to also think about you in a positive frame (I’m assuming your boss likes at least some of what you’ve done, otherwise you’d be gone).

Post reply on HN