The post is called "The New User Story Backlog is a Map" and it's a good and thought provoking read:
Here is the very short version:
1. Prioritized backlogs work great for development teams that know exactly what needs to be built (that excludes all development teams that I know).
2. Expand the prioritized backlog into a map - with high level activities on the left to right access and a prioritized backlog running down from each high-level activity.
|Image from Jeff's Post|
Read the post and let me know what you think.