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


You're totally right. I should have been more explicit in my example. Once in a while, if I have enough admin work to do, I might write a task that says, "administrative tasks," so when I do hit inbox zero and complete all of those little tasks (that do add up to more than an hour), I can keep track of accomplishing it.

I don't think there's any conflict between our two approaches at all. I believe our system is:

- Product based: all tasks that go on the board directly relate to our product - We're ok with resetting on tasks as well. It's just that if it takes more than two days, we obviously got the task wrong, and it is either too big or there's a bottleneck. There's no punishment for not completing a task.

I used to dislike the idea of to-do lists because I wasn't good at following up with them. This idea adds a social element, which has helped me a lot in getting better at organizing my day.

Would you be open to trying this with your team for one day? It's a very low-overhead technique, and you never know - you might just end up enjoying it. And even if you don't get much out of it, maybe someone on your team will.

Can you see some value in that?

So unfortunately I left my engineering team on their own about a year ago to start my own tech services company. My team these days are mostly virtual so the system would break down a bit.

I'd be willing to experiment though I've always been pretty open to trying new techniques.

Our goal is to help teams exactly like yours participate in this technique. We'll be keeping you posted, we should stay in touch. What's your twitter?

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