My car navigation uses GTD!

Defining a trip

When I define a new trip destination my car navigation immediately puts it on its Someday/Maybe list because there’s nothing more to do about it yet.

Starting an active project

When I decide to drive to one of the already defined trip destinations my car navigation moves it from the Someday/Maybe list to the Projects list and determines:

• the Successful Outcome (the car reached the destination);
• the first Next Action (for example “turn left”).

Each Next Action is determined after successful execution of the previous one and put on the @moving context list.

Using Contexts

My car navigation uses two “contexts” for its operation:

• @standing — when the car does not move so it’s time to relax;
• @moving — when the car moves and the driver needs accurate driving directions.

What’s really important — my car navigation focuses on one and only one Next Action at a time: providing just the very next hint. It doesn’t try to tell me the whole travel plan.

When not everything goes as planned

When I don’t follow the directions (it happens from time to time) my car navigation doesn’t complain — it just creates a new plan to reach the destination as efficiently as possible and returns to the Next Action doing loop.

Getting Things Done at its best.

Isn’t it a GTD pragmatism in its crystal-clear form? I wish we all could perform GTD so easily as my car navigation does it, don’t you?

Photo: © Pincasso / Shutterstock