Comments on: OmniFocus and the Way of the (Support) Ninja http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/ The Omni Mouth: standing outside your bedroom window playing \"In Your Eyes\" since 2006. Mon, 13 Oct 2008 00:10:45 +0000 http://wordpress.org/?v=2.6.2 By: Brian http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63687 Brian Thu, 25 Oct 2007 17:53:31 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63687 We generally don't announce ship dates until the possibility of that announcement being wrong is approaching 0%. We're not quite to that point yet on OmniFocus. We generally don’t announce ship dates until the possibility of that announcement being wrong is approaching 0%. We’re not quite to that point yet on OmniFocus.

]]> By: Neil J. Squillante http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63672 Neil J. Squillante Tue, 23 Oct 2007 22:35:08 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63672 Someone told me that OmniFocus 1.0 would be more like 1.5 and that it could have shipped already. If true, aren't you far enough along that you can announce a ship date? Someone told me that OmniFocus 1.0 would be more like 1.5 and that it could have shipped already. If true, aren’t you far enough along that you can announce a ship date?

]]> By: Dave http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63640 Dave Wed, 17 Oct 2007 19:04:02 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63640 http://www.apple.com/hotnews/ A real iPhone SDK is scheduled for February! Great news for OmniFocus, I'd think... http://www.apple.com/hotnews/

A real iPhone SDK is scheduled for February! Great news for OmniFocus, I’d think…

]]> By: Erik http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63632 Erik Mon, 15 Oct 2007 21:57:57 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63632 Perhaps all that you Ninjas need to help with prioritizing/organizing all the Alpha feedback is a nifty new program called OmniFocus... Perhaps all that you Ninjas need to help with prioritizing/organizing all the Alpha feedback is a nifty new program called OmniFocus…

]]> By: Ward http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63630 Ward Sun, 14 Oct 2007 18:06:50 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63630 I really like the OmniFocus (and now OmniWeb) rapid release cycle, especially now that it's automated. My vision of alpha tester heaven: Each feedback report is entered a tracking database and is classified as new problem, duplicate report, user error, what???, out-in-left field, ... Testers are encouraged to classify their feedback: bug report vs. feature request, priority/impact (e.g., showstopper, important, moderate, minor). When a problem is resolved, a message is sent to those who submitted feedback. Although I scan all of the release notes (aka messages of the day) for fixes to the bugs I've reported or features I've requested, I know I've missed some because I've scanned too quickly or because I didn't recognize that a fix/feature corresponds to my feedback. I really like the OmniFocus (and now OmniWeb) rapid release cycle, especially now that it’s automated.

My vision of alpha tester heaven:

Each feedback report is entered a tracking database and is classified as new problem, duplicate report, user error, what???, out-in-left field, …

Testers are encouraged to classify their feedback: bug report vs. feature request, priority/impact (e.g., showstopper, important, moderate, minor).

When a problem is resolved, a message is sent to those who submitted feedback. Although I scan all of the release notes (aka messages of the day) for fixes to the bugs I’ve reported or features I’ve requested, I know I’ve missed some because I’ve scanned too quickly or because I didn’t recognize that a fix/feature corresponds to my feedback.

]]> By: Rob Record http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63616 Rob Record Sun, 07 Oct 2007 20:34:36 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63616 LOL @ chris ;) Funny, I just watched that movie yesterday. LOL @ chris ;)

Funny, I just watched that movie yesterday.

]]> By: Patrick http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63614 Patrick Fri, 05 Oct 2007 22:12:53 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63614 Hey, Brian..."Filing that away in the mental rolodex." You guys will never get GTD right if you keep thinking like this! Hey, Brian…”Filing that away in the mental rolodex.” You guys will never get GTD right if you keep thinking like this!

]]> By: Brian http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63612 Brian Thu, 04 Oct 2007 19:10:40 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63612 Craig: Don't hesitate - just go ahead and send the feedback in. For feature requests, additional votes always help. Customer demand is plays a tie-breaker role when we have two features we're considering implementing. Given equal difficulty/time required to add them, the one with more demand behind it is more likely to make it onto the schedule. All of my theorycrafting above is about what we can do on the back end to get responses (email and/or code changes) out to you guys as fast as possible. Just tell us what you want/need; we'll take it from there. ;-) Craig: Don’t hesitate - just go ahead and send the feedback in. For feature requests, additional votes always help.

Customer demand is plays a tie-breaker role when we have two features we’re considering implementing. Given equal difficulty/time required to add them, the one with more demand behind it is more likely to make it onto the schedule.

All of my theorycrafting above is about what we can do on the back end to get responses (email and/or code changes) out to you guys as fast as possible. Just tell us what you want/need; we’ll take it from there. ;-)

]]> By: Craig http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63611 Craig Thu, 04 Oct 2007 18:39:49 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63611 I'm an alpha-tester wondering whether the feedback mechanism should be used for "voting" for particular development. For example, if I read on the OF forum that somebody has an idea for a feature and has submitted to Omni, how welcome or unwelcome would additional feedback be? If I send additional feedback myself, is that helpful in generating a good picture of the desires of the userbase in aggregate, or is it unhelpfully clogging up the system? I’m an alpha-tester wondering whether the feedback mechanism should be used for “voting” for particular development. For example, if I read on the OF forum that somebody has an idea for a feature and has submitted to Omni, how welcome or unwelcome would additional feedback be? If I send additional feedback myself, is that helpful in generating a good picture of the desires of the userbase in aggregate, or is it unhelpfully clogging up the system?

]]> By: chris http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63609 chris Thu, 04 Oct 2007 01:58:39 +0000 http://blog.omnigroup.com/2007/10/02/omnifocus-and-the-way-of-the-support-ninja/#comment-63609 I'm just wondering if you got the memo about how we're handling TPS now. I’m just wondering if you got the memo about how we’re handling TPS now.

]]>