5 IN 5 said:
However, what if your stack in "IN" contains 70 pieces of material and contains 30 pieces of paper that will take 8-20 minutes just to read or review so you can pick out the nuggets as either projects or next actions?
The purpose of processing a paper is to
identify whether or not it's actionable, to identify the successful outcome, and to identify the next action. What's the nature of the paper? Is the action necessarily buried in the middle of the document, or is it fairly obvious just by looking at it? If you feel obliged to
read each paper in its entirety, and the reading takes over two minutes, you'll get caught in the
doing phase of workflow and never get to the rest of your pile. So if you come across a report, you determine that your next action is the read the report, put that action on whatever context list works best, and move on to process the next paper.
Ultimately you want to have a topographical view of your projects and actions so that you can make intelligent choices about your priorities, and to do that you need to complete the lists before acting on the items in the arbitrary order you came across them. The last paper you come across might be the one that really needs to be read first, but you'll never know that if you're reading everything in chronological order.
The exceptions are the two-minute items, because it takes longer to list, review and delete them than just read them in the first place.