Hacker News new | ask | show | jobs
by bloblaw 5131 days ago
My point is that "Unicorn" is a reporting tool. It still takes peers (instead of just your manager, aka the "old way) to understand and accurately value your contribution.

My concern is that not all actions are equal, but the recognition seems to be.

My question is do I get more "points" for fixing the thread dispatcher in the kernel...or do I get just as many for helping you understand how to upload a file to Sharepoint?

That's where you can disenfranchise people. However, I like the idea and to me it is a good step in implementing 360 feedback as part of a review and bonus allocation.

IMHO, combine peer feedback as an equal component of bonus allocation along with management assessment and I think then you have a winner.

1 comments

You get more for fixing the thread dispatcher:

"Everyone in the company sees [your] plaudits and can pile on more unicorns if they agree that [you] did an awesome job."

The only person who will be impressed by you helping Bob upload to SharePoint is Bob. Total score: 1-3 unicorns.

Every engineer will be impressed that you fixed the thread dispatcher. Total score: 1-3 unicorns * # of engineers.

Sounds great in theory, but that assumes that every engineer is spending time every day monitoring all of the accomplishments by every other engineer just to make sure everything gets valued appropriately. I suppose the answer to that is, "Well, you (or somebody) could tell everybody that you did this wonderful thing," but then you're right back in the position of having to do self-promotion to get recognition for your work.
Shopify intern here.

I've worked Unicorn in to my daily workflow. I can't say everyone (or even anyone) else uses my system, but Unicorn is my first stop of the day when I sit down at my desk. I look over all the unicorns from the previous day, distribute points as I see fit, and move on with my day. Rinse and repeat daily.

It takes all of ~2-3 minutes out of my day. I can see how this technique wouldn't scale well once employee numbers get too big, but it seems to work well at ~100 employees.