Startup Weekend Boulder

Lessons Learned

Posted on Jul 08, 2007 @ 11:53 am in weekend

For me yesterday was the day of the excitement (this idea is working!), today is the day of the lesson learned.

Simply put, at the 10:30 meeting I screwed up, big time.

The pressure is on, and if something doesn’t work in such a short period of time, people (like me) start wondering ‘what happens if we don’t launch?’  I jumped the gun with bringing up a backup plan, suggesting a change of a little thing called a ‘platform.’  Huge change, too late, with bad communication with the people that it affected.  Whoops, damn and seriously my fault.  I have talked to all the groups and we are back on the right track.

12 hours until launch and the ‘breakthrough’ hasn’t happened.  It is close, and everything besides one little piece has exceeded my expectations.  We are working on that little piece, and I am excited about a launch.

We now have a solution that is going to work really well.  The devs are doing some amazing work, and I am back to being the happiest guy in the room.

Some great work is going on!  Lesson learned.

Posted by andrew hyde

2 Responses to “Lessons Learned”

1. Rails Rumble: It’s Like Startup Weekend without the Tech Stumble Says:
   August 14th, 2007 at 9:28 pm

   [...] building a web business.  Rails Rumble avoids the major problem Startup Weekend faced – debating what technology to use throughout.  The four-person-per-team limit avoids the other major [...]

2. Tranparency, Its Not Just For Overhead Projectors Anymore Says:
   September 23rd, 2007 at 9:21 pm

   [...] was going to be the case. Sure, we made a major error, and to Andrew’s credit, he blogged about it. But the mix of disappointment and anger in the follow up posts is clearly there because [...]

Leave a Reply