There’s no going back in time, but there are ways to learn from the past rather than live in it.
Every day we walk through a minefield of potential distractions, sometimes arriving on the other side unscathed, sometimes not. One digression leads to another, the cycle repeats, and hours later we wonder where the time went. It’s tempting to criticize ourselves for getting nothing none that day, and even if the criticism is somewhat accurate (it’s unlikely that nothing got done), the diagnosis itself is idle — which is to say, “So what?”
Figuring out the obvious moves nothing forward. On the other hand, recognizing the problem implies recognizing the solution. When I run into this situation, I ask myself to process questions:
* How did I get nothing done today?
* What will I do differently tomorrow?
Since a day’s accomplishments, or lack thereof, is the sum of many behaviors, neither of these questions can be addressed by a single answer — at least to have the level of precision necessary to make a substantial change.
Mental modeling
It’s not enough to know our worst practices in general. To make tomorrow a more accomplished day than today, we need to rewind the film strip to the precise moment where we got derailed.
For instance, I noticed that whenever I boot a computer and don’t seem to get straight to business, the problem usually starts at boot time. Since I can’t do anything on the laptop for two or three minutes, I start to zone out. What I would be doing if boot time wasn’t a factor is doing a daily review on the IPhone Desktop, looking at each of my action lists.
Asking myself, “What would I do differently?”, it took about 10 seconds to realize that I needed to have my lists — especially my @Computer list — available before the computer was. So I started scanning my todo's on my cell-phone, so that by the time the hourglass on my computer’s screen disappears, I can hit the ground running.
I have introduced daily standup meetings on my team at 9:30 where we one by one describe the tasks that we have planned for the day and thereby get a chance to both think the day through at its beginning, but also to use the team to share problems or ideas.
The basic idea is to mentally step through the day, looking for the forks in the road that compelled you to do X when you know in hindsight that you should have been doing Y. When was the precise moment what your attention shifted to the path of less resistance? What precisely was the distraction?
I believe the sequence of behaviors is critical, and that the earlier ones have the most leverage. If you can maintain a chain of focused activity in the first few hours, you create the momentum necessary to minimize the effects of distractions later on.
Sometimes the problems aren’t necessarily distractions, but behavioral patterns that yield predictably regrettable results. Having too many sugared foods or beverages in the morning leads to an energy crash in the afternoon. Driving past a great bookstore on the way home from work leads to the unbearable lightness of wallet. A change of environment or route may be in order.
After reviewing the dysfunctional day, mentally step through what a focused tomorrow would look like, moment to moment, from morning to evening. What better practices will you be implementing? Which behaviors will you avoid doing?
Always make tomorrow a better day.
Idealism is what precedes experience; cynicism is what follows...
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(123)
-
▼
July
(31)
- Adobe Flash Player : MultiThreading
- Adobe Flash Player : Codenames
- Google Gears : WorkerPool
- Google Gears
- Adobe Flex : Change between Debug and Production B...
- Adobe Flex : Code Quality of Flex 4
- Archived Adobe Flash Player Installers
- Debugging WebORB from Visual Studio
- AXIS IP Cameras SWF Streams are not loadable with ...
- WebORB : Installing on Vista
- Adobe MAX 2008 in Milan is now open for registration
- Adobe Flex : MXML 2009 Specification
- Adobe Flex : Documentation for Gumbo (Flex 4)
- Adobe Flex : 3 methods for Deeplinking
- Workaholics United : Push, Pull & Standardization
- Workaholics United : Consider All Factors (CAF)
- Estimation : Off-The-Cuff Estimates
- Flash Player is the most ubiquitous Platform avail...
- Writing Final Classes and Methods
- Workaholics United : Playing the Percentages
- 21 laws of Programming
- Workaholics United : Upgrade an Unproductive Day b...
- Flex : URI Class implementation
- Flex : Pageable ArrayCollection with support for a...
- PV3D : Training in Cologne
- Flex SDK : Skinning in Flex 4 (Codename: Gumbo)
- ILog Elixir 2.0 Beta Program Started
- Google Trends of XAML and MXML
- A Flex SEO contest (by Ryan Stewart)
- Adobe Flex : The Undocumented StaticEventDispatcher
- SWF now supports SEO !
-
▼
July
(31)
My Network
-
-
Stop dragging me into board meetings - Dear Reader : This might be a bit more NEGATIVE than you’re used to. Apologies about that. I love to chair startups and companies, but I hate 95% board m...9 years ago
-
Design practice makes perfect - Evidence gained from research is powerful. It can persuade the most stubborn board members if presented in a way where decisions can be made based on facts...10 years ago
-
-
dutch vs danish politics - First reaction: glad I don’t live there. And then I made this comparison. It doesn’t differ that much actually. CDA 14% – Konservative 10% VVD 21% – Venstr...14 years ago
-
The Next Web – Timothy Ferriss - First speaker on the last day of The Next Web was Timothy Ferriss, author of the ”4-Hour workweek”. I don’t know what I was really expecting from a guy who ...14 years ago
-
Links for Motorcycle enthusiasts - MC travel-blogs: Must see: http://www.kccd.no/ http://4qconditioning.blogspot.com/ Danish blogs: http://www.ossianbuilds.blogspot.com http://wrenchmonkees....14 years ago
-
New Arduino project - I found myself a new Arduino project – an automated car! Well how to go about this. My best approach was to get a cheap RC toy car from the local toy store...15 years ago
-
Unrecognized selector sent to instance - As you may or may not know, I do iPhone/Cocoa touch now... While playing around with something this evening I stumbled across something I thought I'd share...15 years ago
-
-
-
-
-
-
-
About Me
- Peter Andreas Molgaard
- Copenhagen, Denmark
Labels
- Adobe Flex (62)
- Events (28)
- Best Practices (27)
- ActionScript 3.0 (16)
- Adobe AIR (15)
- Tools (15)
- Workaholics United (14)
- PV3D (10)
- Arbitrary Thoughts (9)
- PureMVC (7)
- Adobe Flex SDK (6)
- Adobe Max (6)
- Methodology (6)
- RIA (6)
- State Machines (6)
- .NET (5)
- Adobe Flex Builder (5)
- DFUG (5)
- Google (5)
- WebORB (5)
- Data Visualization (4)
- Flash Platform (4)
- Independent Thinking (4)
- Process (4)
- SEO (4)
- Silverlight (4)
- Adobe Flash Player (3)
- Code Design (3)
- Flash Player (3)
- HCI (3)
- MAC vs. PC (3)
- Microsoft (3)
- Performance Optimization (3)
- Stockholm (3)
- Undocumentation (3)
- Visual Studio (3)
- Windows Workflow Foundation (3)
- ACE (2)
- AUG (2)
- Adobe Thermo (2)
- Ajax (2)
- Bug Report (2)
- Cairngorm (2)
- Commerciel (2)
- Documentation (2)
- Estimation (2)
- Firefox (2)
- Google Gears (2)
- London (2)
- Morphable Interfaces (2)
- SVN (2)
- SoftwareEngineering (2)
- Test (2)
- Admin (1)
- Adobe Flex Adobe Flex Builder (1)
- Facebook (1)
- Graphics (1)
- Hardware (1)
- HelloGroup (1)
- IEEE (1)
- Outsourcing (1)
- Training (1)
- XAML (1)
No comments:
Post a Comment