My Latest Book

Product Details

Also available on Amazon.com, Amazon.fr, and other Amazons and bookshops worldwide! 

To Think About . . .
You got to be very careful if you don’t know where you’re going, because you might not get there. Yogi Berra
My Other Books

Product Details

Product Details

Product Details

Product Details

Click to order other recommended books.

Find Us on Facebook Badge

Search This Site
Latest Comments
Log-in
« Day Zero Project | Main | Speed Update: Day 4 »
Wednesday
Sep282011

Progress Report

As a result of my testing of the Final Version over the last four days, I’ve felt it necessary to make some changes. The main problem was that I wasn’t satisfied that unfinished tasks were being processed sufficiently often.

To combat this, I’ve slowed the overall rate of progress through the system so that more time can be spent on finishing.

I’ve also re-introduced “dismissal” into the system, which brings back its filtering capability, which was in danger of getting lost.

Reader Comments (12)

Dismissal is back in the system? Very good!
September 29, 2011 at 17:21 | Unregistered CommenterRainer
Perry suggests here that having chronically unfinished tasks on the to do list is useful: http://chronicle.com/article/How-to-ProcrastinateStill/93959
October 3, 2011 at 15:07 | Unregistered CommenterScott
I'm glad there's a lot of progress in your work. But how does the "dismissal" function works? Does it work like "cancel?"
October 4, 2011 at 3:12 | Unregistered CommenterHalley | Business Card Design
Halley:

Dismissal is a feature of most of my systems since the first version of AutoFocus. It is a way of taking tasks off the active list without removing them entirely from the system. They can be reviewed, revised and re-instated or eventually removed entirely.
October 4, 2011 at 9:59 | Registered CommenterMark Forster
It would probably be helpful if We knew the details of this "final version" so We can work together to highlight any pitfalls and/or concerns. Software Engineers have a saying, "Many eyes make all bugs shallow," which means the more People examine a problem, the less likely it is to remain unresolved.
October 4, 2011 at 16:03 | Unregistered CommenterBrian
Sorry to be such a pain in wherever, but it's been one week since you reinstated dismissal into your system. How are you doing sofar?
October 5, 2011 at 13:01 | Unregistered CommenterLaurent
Brian,

I wonder whether the extra effort in explaining the system and going into the feedback would be justified? My gut feel is that trials on a cross section of the community would be a good thing if properly co-ordinated and assessed. However, I'm not sure that many other systems get this level of rigour, and I'm also not sure whether Mark has the necessary expertise on tap. It may well be that his editor does double duty as "voice of the customer".

Mark,

If you ARE looking to pull together a group for early feedback, I'd be happy to drop £20 for a prepublication draft. Which rather implies that I don't think there'll be much wrong with it. I have to say that a neutral bystander probably wouldn't recommend me: I am chronically unreliable and struggle to keep anywhere near my list. Then again, if you're looking for an extreme challenge.

Then again again, are you taking pre-orders?
October 5, 2011 at 18:29 | Registered CommenterWill
Will,

Another point to consider, though, is whether any of the 'untweaked' variants of the 'final version' work for Others. For example, version #46 may be adequate, if not perfect, for Person A while Person B may find version #53 exactly what They need and Person C see exactly the process They want (or are willing to accept) at version #104.
October 5, 2011 at 19:28 | Unregistered CommenterBrian
I for one think Mark's approach is exactly right. Public experimentation was useful for developing and validating ideas. But it also create tremendous fragmentation, and doesn't help to create a coherent community around one concept.

In order to have the coherence, Mark needs to pull back, define everything, refine everything, document everything, and then present the Answer. Once the answer is presented, everyone will naturally adapt it every direction, but there will be a common reference point to rally around.
October 5, 2011 at 22:28 | Registered CommenterAlan Baljeu
Laurent:

Too early to say.
October 5, 2011 at 22:30 | Registered CommenterMark Forster
I agree with Alan!
October 5, 2011 at 22:32 | Registered CommenterMark Forster
Publishing the info on this site could be seen as counter to his goal of publishing a book. On one site there is great benefit for him if he discretely sent the system, via email, to his more loyal fans, and get feedback. But there is the danger of someone blabbing and then going viral with the info.

The best of both worlds might be to create a rough draft, and only send it to people willing to (electronically) sign a non-disclosure agreement for a reasonable time period. Loyal fans eventually could blog and tweet and really get the sales hopping later on.

Yes, tidbits on the secrets can be frustrating, But I appreciate the need for a level of secrecy. Face it, people can spend years developing something, and have it posted for free online in minutes.
October 8, 2011 at 3:12 | Unregistered CommenterCJ

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
All HTML will be escaped. Hyperlinks will be created for URLs automatically.