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

Post a Comment

Popular posts from this blog

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
32 comments
Read more

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to
12 comments
Read more

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem
9 comments
Read more