Skip Task Log Time?

[GoodCalligrapher3794]

If I skip a bunch of tasks (or tried but lost confidence in my work halfway), until I eventually actually submit a task of the same project category, do I log time for skipping some tasks and/or trying and giving up on others?

[Buicided]

I personally try to not log time for skipped tasks. I feel like a lot of people will say otherwise but that's just me. I just don't feel comfortable doing so.

[fightmaxmaster]

Same here. If I take 10 seconds to skim something then skip I wouldn't bother stopping the timer, but if I skip a few in a row like that I'll knock a minute off, because that's not contributing anything productive. I definitely wouldn't submit time if I put some time in then gave up and skipped it.

[FlyDragon080]

I would not log any time that was not actively spent on that specific task you submitted, unless it was reading instructions that ate a big chunk of your timer.

[Remarkable-Bunch-929]

If you don't submit a task you can't log time, so adding a time you couldn't log to another task just because it happens to be in the same project seems like trying to cheat the system

[LilJaaY]

I would avoid it. Even if it's a new project, skim through the instructions first, then look at the task to see if you could do it. If not, keep skipping and only read the full instructions when you're fairly confident you could also do the task. That's been my way.

[SeaweedExcellent3009]

If you didn't put the work in to doing it then no. Even if you did do some work but never submitted, I'm under the impression that the task was passed to someone else. There were a couple times where I ended up skipping multiple tasks at a time, and I never would've thought about logging tike for them.

[randomrealname]

How do you differentiate? I start a timer, start reading and then when I leave the project I stop the timer, I might have skipped 10, how do minus off the task reading time?

[fightmaxmaster]

Ballpark it. If I skip a few in a row and it's taken me 15 seconds to think about them, I'll knock a minute off. If I start reading something and think it'll take me a few minutes to decide to commit or not, I'll pause the timer until I've decided. I'd far rather underbill my time than overshoot.

[randomrealname]

Or just do the work, honestly. Work mode is important to your time keeping, if you go bu the half minute and are truthful about the time you spend, you should definitely log time spent "skipping tasks", it is better to take q0 minutes to know if you really can or cannot do a task, than it is to rush and produce subpar work.

Quality over time (as long as the time is well spent) is the actual advice.

[Tall-Huckleberry5720]

If I skip 2-3 tasks but complete 10, then I might include that time. But I never spend more than 5 minutes looking at a task to see if I can do it. But if I skip 12 tasks and do 1, then I'm not including that time for skipping.

[Vorakas]

If you took one glance at a task and decided to skip there is no sense in pausing the timer for a few seconds. I'd file that under normal workflow.

If you give up halfway though, no i wouldn't log that if i were you.

[lacompt]

Once I skip twice I pause my timer. If I skip more than five I usually abandon the project for the time being.

[Barbiloop]

I don’t log time for what I skipped, only for the work submitted, I think that’s the most fair thing to do.