This post boils down to one statement: "every 100 days we have a 20-day-long crunch time". I'm all for getting things done, but scheduling arbitrary crunch times is a great way to wear the team down until people quit.
I recently did a challenge of 100 days of commits to side projects and I'm now at day 96. I think this was awesome for me, as it kept me really focused on my projects, even if some days I had only small commits.<p>I think my next challenge might be even more focused and look to launch one of my prototype projects in a specific amount of time. This will force me to focus and launch something, even if it isn't perfect.
Anyone else go to Amazon thinking 'hmmm, maybe I'll buy a 100 day goal calendar, it's probably only $5.'<p>The one he has on his wall is <i>$42.50 on Amazon</i>... I think I'll print out 100 pages and tape them to my wall.
A 100 day challenge doesn't make sense for an established company (why would you do that to yourself?)<p>But for a startup, it makes total sense. You're moving quickly, and 100 days is enough time to make substantial progress while keeping yourself accountable to actually shipping. I think it sounds like a perfectly viable strategy. Definitely not for everyone.<p>I took his advice to heart and today is day 1 of my 100 day challenge (yesterday was day 0): <a href="http://iambateman.com/today-is-launch-day/" rel="nofollow">http://iambateman.com/today-is-launch-day/</a>
There seems to be something deeply effective about setting arbitrary constraints. Obvious examples abound: haiku, twitter, 80-char code, screenplays in fixed-width Courier, 25-minute pomodoro, text-only man pages. Also, the metronome of practicing music (cadenzas don't count), the fixed 8 hour workday, the 12-tone music temperament..<p>I've wondered what a piece of software could look like with each function/codeblock written on 1 index card each. Linus seems to prefer one-page functions for C, but I like the extreme of the index card.
This is how I've gotten around my own productivity faults: not with a particular arbitrary date, but by publicly promising to a point of no return. It's incredible how much I've been able to do by setting expectations without too much estimation. By promising what I want to accomplish rather than what I think I am capable of accomplishing, it tends to push me to be more productive than I thought possible.
I work at Thinkful (<a href="http://www.thinkful.com" rel="nofollow">http://www.thinkful.com</a>) - we help people learn to code through coding projects and mentorship.<p>Thinking about using this with my team. I made a PDF so we can print it, thought you gals and guys might be interested too: <a href="https://dl.dropboxusercontent.com/u/34726262/100%20Day%20Goal.pdf" rel="nofollow">https://dl.dropboxusercontent.com/u/34726262/100%20Day%20Goa...</a><p>Edit: Here is a similar option available at Amazon, it's $42 (<a href="http://www.amazon.com/Countdown-Calendar/dp/B004VP6XBK" rel="nofollow">http://www.amazon.com/Countdown-Calendar/dp/B004VP6XBK</a>)
I'm of two minds on this.<p>On one hand, making deadlines as short as possible is a great idea. It's too easy with one-year or two-year projects to six months arguing about infrastructure, requirements, and standards and end up delivering late or not at all. Every project should be required to deliver <i>some</i> value in the first couple months.<p>On the other hand, three or four twenty-day crunch times every year is not sustainable. Unless they're planning a Logan's Run-style turnover of their current team.
Since they are like $40 on Amazon, I'm selling them here: <a href="http://www.ebay.com/itm/321226528853" rel="nofollow">http://www.ebay.com/itm/321226528853</a><p>I think it will cost about $7 to print it and $5 to ship it (free shipping is included, internationally as well I believe) so this is about what I expect my cost to be.