Hacker Newsnew | past | comments | ask | show | jobs | submit | more datasmash's commentslogin

I've found describing the kinds of problems you'll solve (not in a salesy way) and what the company actually needs help doing can really engage the minds of potential hires.


I'd actually like to see some examples of over-describing problems to engineers in a salesy way. That could be a fun follow on post.


Neat concept. In my experience its helpful to reset the clock and remember the mindset you were in when you were happiest to help guide you towards where you should go next.


This is awesome!


Thanks!


It all depends what your end goals are. A new technology paired with a new market is doubly risky.

New technology applied to an existing market or a new product aimed at an existing market is a lot safer of a bet if you're trying to build a business.


Recognizing people's successes and what they are doing well is a 1000% more effective than harping on what people have messed up. It's very easy find yourself in or create a toxic culture that is overly focuses on the negative, but it instantly kills motivation.

People who feel like they are doing great work and motivated to do great work.


>Recognizing people's successes and what they are doing well is a 1000% more effective than harping on what people have messed up

Yes, this is (verifiably) true. One must be aware, however, that positive feedback is usually going to be ineffective, thanks to natural "regression to the mean" effects, elucidated wonderfully in this Veritasium video[1].

(The point, in the end though, is that performance is going to statistically improve if people do worse than average, and do worse if they do really well, regardless of the feedback you give them", which is called "regression to the mean". The net effect is that you might get a false positive for negative feedback, and a false negative for positive feedback if you don't account for the natural tension that brings everything back to average.)

[1] https://www.youtube.com/watch?v=1tSqSMOyNFE


It is extremely important to celebrate successes (of the team and individuals), but a good manager needs to know when and how to correct behavior as well.

One of the best ways I've ever seen is simply asking the right questions (What did they think of the <recent event>? How could it have been handled better? How could it have been prevented?) People get very defensive and find excuses if you tell them they fucked up, but if they can admit it themselves they tend to correct their own behavior.


Yo


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: