Skip to main content

Time-Boxing

Time-boxing is a technique that helps us direct energy on our priorities. When working on a tight schedule towards a goal, we often face tough choices about how to allocate our time. With time-boxing, we set time limits for performing tasks and stick to those limits by eliminating "fluff". Eliminating "fluff" requires constantly assessing whether each step we are taking to complete our tasks is absolutely necessary.

Let's say you're cleaning the floors of your home before guests come over. You want to mop the hardwood floors and then apply a no-odor finish. Your guests will arrive in a half hour. You decide to time-box the cleaning of your floors to 20 minutes, because you still have some other preparations you want to complete before the guests arrive. You then allocate 10 minutes to mopping and 10 minutes to applying finish.

As you start mopping, you realize you won't be able to mop thoroughly within the 10 minute time-box. What do you do?

By time-boxing your tasks, you have forced yourself to face a tough decision. You have to decide whether to do a less-than-thorough job mopping and applying finish, eliminate from your plan the applying of finish, or re-examine your assumptions even more radically. In the end, you might decide to do a thorough mopping of the most visible areas of the floor, followed by applying finish to that same area. If you're able to complete these tasks sooner than expected, you might consider cleaning and finishing the remainder of the floor. No matter what you decide, time-boxing has enabled you to recognize, and adjust for, your scheduling mistakes before the possibility of achieving your goal has evaporated.

Time-boxing works particularly well in conjunction with iterative processes.

Comments

Popular posts from this blog

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware