Article is about personal productivity moreso than corporate, but I'm going off on the corporate tangent because I think the HN crowd can relate. A personal fa

Article is about personal productivity moreso than corporate, but I'm going off on the corporate tangent because I think the HN crowd can relate. A personal failing of mine, that I'm working on improving, is progress tracking that's as close to understandable-at-a-glance to management as possible. Historically I've always been focused on progress, moving on to the next thing, keep pressing forward, but this comes at the expense of management understanding when it comes to status updates and awareness around delays. Progress reporting, from a purely technical viewpoint, is a bunch of bullshit that gets in the way of progress, but from a business viability, profitability, and general good-management, it's essential. I have to keep reminding myself of that. How this relates to the article: project task time must be allocated to determining and documenting progress. The best way for this to take up a minimal amount of time is to have a methodology determined up front: give management an expectation of what they'll see, and the technical folks an understanding of where progress milestones are, so they'll know what markers are important to progress reporting. It's got to be collaboratively developed. This, in itself, also takes time. More directly related to the article, continually trying to find "the perfect to do app" is just a distraction. Any app is fine. If you're not getting to your tasks the problem is you and / or your expectations, not the app(s). Been there, still doing that... Apt quote from article regarding personal expectations of productivity: "Present self screws over future self". I've stuck with tiddlywiki / noteself as my Swiss-army-knife note taking and organizational tool. I'm also messing with it for tracking project "threads".