Hacker News new | comments | show | ask | jobs | submit login

It's an interesting workflow, but I think the granularity they are suggesting feels a little too micro-management like.

If you need to track whether your (presumably non-tech) employees have written 3 emails, your team have a motivation/time-management problem.




Hey there, yeah that's why I wrote that we try very hard to avoid micro-management in this activity, and I specifically included emails in the "bad tasks" example. It's definitely not a top-down initiative, or anything to do with tracking our employees.


Max - I think you'd avoid this a bit if you changed your initial anecdote (your interaction with Jason) to be more engineering and product focused, I think thats where the micro-management concerns are stemming from.


Totally. Is it ok to go in and edit my blog post? Are there any rules to follow when changing something you've released? Or can I just treat it like a bug in the software we deployed?

Any chance you'd try this system out for a few days? I'd love your feedback.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: