How can I use event-based schedules to accomplish goals?
This is an excerpt from my new book, Organizational Psychology for Managers
In chapter 9, we talked briefly about the time component of goals. Without a deadline, goals are not seen as particularly important. If we want a sense of urgency around our goals, we need to put a target date on them and we need to have check points along the way to monitor our progress. But if we become overly specific about scheduling every piece of the goal, we find ourselves back in a clock-based schedule, with all the hassle and headaches that entails. One of the problems with a lot of goals is that components are at least somewhat open-ended. It’s one thing to go out and run on the track for an hour; a software design project may not be at a logical halting point after an hour, making it extremely hard to stop and move to the next thing. Instead, we need to treat goals as events, and use events to trigger our goals. We do this by using implementation intentions.
Now, having read chapter 9, you might be thinking, “Are you nuts? Didn’t you just tell us that intentions are not useful?” Well, it’s certainly true that intentions are not goals and should not be confused with goals. However, properly constructed implementation intentions can help us accomplish our goals. Implementation intentions are a way of linking an arbitrary event to a piece of a goal, linking one piece of a goal to another piece, and linking one goal to another. We can even use implementation intentions to link a goal to a break and a particular leisure activity to a goal as a way of making sure that when we stop, we then start up again. One of the biggest advantages of implementation intentions structured into an event-based schedule is that it becomes very easy to develop the habit of executing the steps in order without having to decide what to do next. When we have to think about the next step, that’s when we become the most vulnerable to distraction. Implementation intentions become the metaphorical cotton in the ears that protect us from the siren song of Facebook and other common time sinks.
We’ve already seen how to construct an event-based schedule. To add implementation intentions, or action triggers, we say or note down on paper, “Once I pour my coffe, I will sit down at the computer” and “Once the computer boots up, I will open Chapter 10 and write,” and so forth. By making the connections explicit, we make them more powerful. We “know” exactly what to do when the appropriate trigger occurs. Writing out the schedule helps considerably, since it means we don’t have to actually remember as many things when we’re busy.
Implementation intentions can also be connected to triggers in our environment: “When the coffee cart comes around, I will close the file I’m working on and make the phone call to Bob,” or, “On Wednesday night after dinner I will review the design for the new Tate GPS.” The more specific the implementation intention, the better. Specific triggers are easier to activate. More general triggers are easier to delay: “After dinner, I will…” is more easily put off from dinner to dinner. Sometimes our implementation intentions are conditional or based on an ongoing experience: “Once I find my way home from wherever this stupid Tate GPS took me, I will fire the person who designed it!” (don’t be surprised; he who has a Tate’s is lost).
Any external event can trigger an implementation intention. The best events are those that require no effort on our part to notice. Thus, “When I look at my watch and see that the time is…” is not a good trigger. Looking at a watch requires us to make a conscious effort to remember to do that and then think about the time. It’s better to trigger off something automatic, like the lights dimming or changing color, the mail being delivered, or that annoying guy who never varies his schedule an iota walking by. Since we so often work in environments with artificial lighting, you do want to be careful about using “it’s getting dark outside” as a trigger, unless you can control the lights. Having the lights automatically clicking on is a good trigger, or having software on your computer that changes your screen brightness according to the position of the sun is another. Even reminders on your smartphone can be very effective, although they tend to be more useful when you want to transition activities at a very specific time.
Some people find it helpful to use objects as triggers: “when I see the Perkins file in the morning, I will…” Like having too many goals, too many such triggers will cause confusion rather than triggering the desired behavior. You don’t want to trigger five behaviors and then have to choose. You want one thing to trigger and then it triggers the next thing, and so on.
It’s worth noting that successful athletes use implementation intentions all the time. When a fencer trains to respond to different attacks by their opponent or a judo player to different throws, what they are doing is setting up a very rapid implementation intention. Teams do it as well, although that does take significant practice since several people’s responses must be coordinated. Some athletes will even use implementation intentions to decide ahead of time how they will feel if certain events take place in the competition: “If I find myself down on points, I will be energized, relaxed, and focused,” or, “If another runner passes me, I will imagine a rubber band pulling me forward and snapping me past him.” As silly as some of these intentions may sound, rehearsing them works. The event triggers the feeling or the action.
