Probably not as interesting now that you can play with the actual tool, but we also wrote several blog posts describing our thinking and goals for solving this problem:<p><a href="https://www.expectedbehavior.com/building-burndown/keep-the-big-picture-separate/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/keep-the-...</a><p><a href="https://www.expectedbehavior.com/building-burndown/schedule-important-work-first/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/schedule-...</a><p><a href="https://www.expectedbehavior.com/building-burndown/many-hands-make-light-work/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/many-hand...</a><p><a href="https://www.expectedbehavior.com/building-burndown/where-tasks-and-projects-go-to-die/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/where-tas...</a><p><a href="https://www.expectedbehavior.com/building-burndown/you-can-only-learn-from-your-mistakes-if-you-know-what-they-are/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/you-can-o...</a><p>This is just v0.1 of the tool, so we haven't solved/built all the above yet, but maybe it shows some of our thinking process.