get it out, so we could learn how people use it and make improvements.  As such, we released a minimum viable product rather than a perfect one. But I can't help it -- I want a perfect product!  Late on the launch night, I noticed a hyphen out of place on the 'About Us' page, and that Facebook Share didn't work if you were on Safari.  I lay in bed fretting about these things and lost at least half a night's sleep.  It's even more frustrating because, not being technical, I don't know how to fix those things.  I don't understand how hard it is to avoid these pitfalls, so my tech team gets frustrated with my frustrations. I've learnt in the past couple of weeks that moving fast is more important than being perfect.  Our head of engineering, Alex, pointed out a Mark Zuckerberg quote, 'Move fast and break things. Unless you are breaking stuff, you are not moving fast enough.' It makes a lot of sense. Every week our site will improve, but there will always be mistakes along the road. 2. Reacting to feedback Twitter criticisms started the day after we admitted people into the site.  Some people didn't like the dog, one said our pivot was 'hilarious', others couldn't figure out how to scroll their town map.  Clarissa, who runs our Facebook and Twitter, also runs user tests and site support so she invited critics into the office to tell us their concerns. In addition to