I’m not satisfied with the current state of personal time management. I think it’s just fundamentally wrong, and something that could benefit from a probabilistic approach. So, I’ve decided to start from square one and create my own system of time management; I could certainly use one. The ideas I’m writing down are rough, untested, and unconventional; take them with a grain of salt until they’ve led somewhere useful, and bear with just a tiny bit of kookery until then, since I’ll admit that my knowledge of time management comes mostly from observing conventional time management tools rather than reading literature.
First of all, I consider time to be a finite resource into which events may be placed. I will define what an “event” is shortly. Time is not a tangible resource, nor is it a physical thing. Although modern physics tells us that time may be experienced differently by different observers, I take time as a constant, since people do not typically move at relativistic speeds relative to one another in every day life. Time can be measured by the passing of events.
An event is anything that takes up some amount of time. An exceptionally durable rock remaining motionless and unchanging for tens of thousands of years is an event. So is a person blinking. Events can be thought of as consisting of other, smaller events, such as the rock remaining motionless and unchanging for an hour, or the first twitch of an eyelid. The present can considered an atomic, universal event which consists of the state of everything. Events closer to the present are more certain to occur than those further way. If an eyelid goes down, it is almost certain to go back up next. If the rock is in front of me now, it almost certainly will not be halfway across the earth a minute from now. It follows that present actions have a greater potential to affect events which are further into the future. Past events are also uncertain, in that the further back in time an event is, the more difficult it is to determine the nature of the event; this is of less interest for time management, except to the extent that we can use a record of the past to inform future decisions. To this extent, we can take past events as recorded as they are observed, and consider this record to be “certain.”
Because events can be broken into subevents, the creation of such subevents makes those events more likely to occur — A seed planted makes a tree more likely to grow and live out its entire lifecycle in a particular location, for example. Because events do not occur in a vacuum, they may require a certain environment in order to occur with any reasonable probability, and may therefore require prerequisite events which are not subevents. The creation of Earth is a prerequisite to forests growing on its surfaces, but the creation of Earth is not a part of the trees growing (but the growing trees may considered be a subevent of the existence of the Earth).
Implicit in the above is that more than one event can occur simultaneously. However, some events cannot reasonably occur together. Others are simply unlikely to occur together. It is not possible for a person to spend a week vacationing simultaneously in Japan and Florida. These can be considered contradictory events.
All of this means that any system that assumes the certainty of future events cannot be satisfactory for time management. One of the things that has persistently annoyed me about Sunbird is that it assumes that future scheduled events inevitably occur (it also has a less than impressive concept of the present, limited merely to the current day).
Looking at the Wikipedia entry for event, one of the definitions given is an entry within the iCalendar standard, defined in the IETF’s RFC 2445. Although I’ve only given a quick glance to this specification, it does not appear to support an uncertain view of time. A new file format therefore makes sense given the current environment.
Browsing through various pages on project management on Wikipedia, the thoughts I’ve outlined above bear at least a superficial resemblance to the thinking behind Event Chain, but with a different emphasis.