3 weeks, 1 day ago stephentParticipant
Seth, I noticed in a recent post that you said a time tracking feature was on the roadmap for SkedPal 3 in the second half of this year. I personally think that a well-executed time tracking feature with solid reporting could be one of the most powerful additions to SP. I was just curious about what specifically you envisioned for this feature.3 weeks ago SethParticipant
There are different reasons people use a timer. Freelancers who sell their work by the hour are particularly interested in the billable hours. Productivity enthusiasts are more interested in measuring themselves and analyzing how they spent their day. Others who tend to get drown in their tasks like to see a timer with an alarm that tells them when to start and when to stop. The ADHD folks like to use a timer with the Pomodoro feature to stay focused.
Ideally, a timer should cover all jobs above. What we’re particularly interested in is building a timer that is an integral part of your productivity tool.2 weeks, 5 days ago stephentParticipant
<p style=”text-align: left;”>It’s exciting that you are considering all those scenarios for the timer. Do you foresee a timer report that will show time logged versus time estimated for tasks? I’m sure that would be quite an eye-opener (and tool to affect change) for those of us with a strong planning fallacy!</p>
<p style=”text-align: left;”>And since we’re already talking about SP 3… is June considered the middle of 2020?! 😉</p>2 weeks, 4 days ago SethParticipant
What you’re referring to is part of a more general problem/feature called ‘productivity metrics’. In other words, how do I measure my productivity? How well am I doing? In SkedPal 3, the focus of this metric is on how you actually spent your day/week against your ideal day/week. For example, if your intention was to spend a minimum of 10 hours on creative work during the week, how much did you actually spend? Did your time mostly go to admin work instead?
This is about measure->learn->do cycle and we can come up with a ton of things to measure. Estimated duration vs actual duration is one of them. The data is sourced from the timer, of course. So, once we succeed in implementing a good timer, the next natural step is to introduce metrics.2 weeks, 4 days ago SethParticipant
Forgot to answer your last question. We’re aiming to release SP 3 beta by June/July. This will be the core system and excludes the timer as you mentioned it yourself.2 weeks, 4 days ago stephentParticipant
Yes, in general, ‘productivity metrics’ which compliment the ‘measure->learn->do cycle’ summarizes the intent of my question. I look forward to how these metrics will develop in SP 3. I know I’m one of many who appreciate your thoughtful replies. Thank you. Keep up the good work!
We have a more specific date range! 🥳 Thanks for throwing us a bone. Hope the best for this last stretch of development.1 week ago yreuvekampParticipant
Bit off-topic: will we need to sign up for a beta program, or will it be public?
You must be logged in to reply to this topic.