Archive for November, 2006


Reno Project Management

That’s “reno” as in “renovation”, not “Reno” as in gambling and vice.

I’ve been absorbed the last few months in renovating our Toronto home. It occurred to me the other day, while standing in one of the many piles of dust and rubble that used to be our kitchen, how renovation projects are much like software engineering projects. Or any other kind of engineering project, for that matter. Fun, messy, sometimes chaotic, and generally more expensive than you wanted it to be.

Lessons learned so far:

Plan, plan, and plan again before you implement, because it is orders of magnitude less more expensive to correct a mistake in the planning phase than afterwards. Downstream fixes might mean moving wires, or pipes, or even walls. Twice. Hypothetically speaking, of course.

People standing idle is money being burned. And if they happen to be carrying power tools as well, they’re probably going to find something dangerous to work on.

Minimize dependencies. Case in point: 8 weeks to get our building permit. The dance of annoyance began with numerous frustrating trips to the Toronto building department. The building department hasn’t yet discovered the magic of email, but does have a website where you can use the power of the Internet to download PDF forms (which must subsequently be printed out and filled in by hand, in triplicate). I should have figured out it would take a while when I met an architecture firm employee there whose full time job is to petition the city for permits.

Anyway, after much money and 5 weeks of… er… supplicating, we were told our permit was ready, save for “getting a letter” from the Toronto Ravine Conservation Authority. (Tip: “getting a letter” is code for getting another permit.) This seemed a little odd, because our property is almost entirely flat. Nevertheless it was a ravine in the early 1900’s, so the entire area is controlled for all time by the TRCA. The helpful person there informed us that the permit almost certainly would take a few weeks before even being looked at, on account of how they had an executive review coming up. And by the way, we would also have to talk with the Urban Forestry Department, who it turns out wanted us to “reforest” our back yard. Sigh. 8 weeks. Eight weeks. Eight w8@*s! License Raj, eat your heart out.

Scope creep is the enemy of the budget. We thought we had a fine plan for our kitchen. Then a family friend popped in and pointed out that we had not built the much-vaunted “kitchen triangle” into our plan. (For those of you who don’t know, the triangle has something to do with positioning your fridge, sink, and range at the points of a triangle within easy arm’s reach, and then further aligning that triangle with the movement of the outer planets.) So we changed the plan. Then we had to move the wall that separates the kitchen from the dining room. That required ripping into the dining room ceiling. Which in turn suggested removing, relevelling and replacing the rest of said ceiling. You get the picture. Scope creep bad.

Good contractors are worth their weight in gold. But only if they keep promises, and work well with others. Our contractor is a dream to work with, and no I won’t tell you his name until he’s done at our place.

If it ain’t broke, don’t fix it. While it’s tempting to rip out all the existing infrastructure of your house and replace it with shiny new stuff, you must resist. Rule of thumb: it’s not worth doing unless it will end up at least twice as good when you’re done.

Sometimes you really ought to pay an expert, rather than doing it yourself. Flat roofs. Basement insulation. Things involving natural gas pipelines. Pay an expert.

There’s nothing like a hard deadline as a motivator. Near the beginning of the project we committed to hosting our families for Christmas dinner. Now we’ve got three weeks left. We’re coming in on a steep angle of attack. The kitchen isn’t in yet. We’re telling everyone it’s going to be “rustic” this year.

Dear MaRS… Revisited

Back in April of this year a friend who works at Toronto’s MaRS tech incubator kindly gave me a tour of the facility. I walked away feeling a little conflicted; I wrote: “…Mars is an incredibly well-funded tech incubator, but it isn’t yet offering much in the way of educating the broader community of people outside the four walls of the building…”. And I sent my tour buddy a way-too-long mail with some ideas for improvement.

I had all but forgotten about the visit, since I haven’t been tracking MaRS since then. But Veronika, who coordinates the MaRS venture services programs, just posted a response to my April comment: “It is frustrating to see such remarks because we’ve been getting amazing feedback from participants in MaRS programs and clients of the MaRS Venture Group. … So, what more should we be doing to reach this “broader community ?”

Well, I don’t know how useful my April thoughts are any more (or ever were!) but I did manage to find the email I sent after that first visit. Below is the “Ideas / suggestions for improvement” portion of that mail, with the outreach-related stuff bolded. Beyond what I wrote then, I would also push to get all the information resources online, for free, and I would broaden the focus beyond bio-tech. Veronika, I hope some of this is helpful.

We talked about the desire to get companies collaborating. I suspect MaRS may struggle with this because the tenants may well be competitors, and many of them will anyway be very secretive about certain areas of intellectual property. To get past this you might consider asking them to share with you what help they need and would like to receive, both from you and from other tenants. Then it will be obvious where the safe ground is for group collaboration.

Workshops: you said you’re already doing some of this… public speaking, how to pitch to VCs, etc. More is good. Entrepeneurs need that help and people are often embarassed to ask. This is definitely an area where all the tenants’ interests will be aligned and they should be able to collaborate.

Mixers:

  • Regular weekly “unwinder” events with beer and cheap eats
  • Weekly “brown bag” speaker series: invited speakers, talking to tenants, 45 mins + 15 min q&a, bring your own lunch (hence “brown bag”)
  • Host more events that invite the external community in. maybe see what ROM does in this regard?

Techfest / Science Fair
Read about it here and here. This concept may not work because of the IP disclosure issue, but perhaps you can approximate it in some other way. Basic idea is to get everyone to understand what everyone else is doing, and thereby foster connections and collaborations. It was an incredible success at Microsoft in that regard. It was also a lot of fun… a great big nerdfest social event. :-) (And I can say that because I was one of the nerds loving every second of it.)

Cafeteria: really high quality food, and an upscale ambience. It’s amazing how much of a difference this makes.

Business Resource Center
Need a physical space – already in the works I’m sure, but this is a high priority. If someone has to make an appointment with a BRC staff member and then travel three floors to meet them, the interaction is less likely to happen. I’m sure I just don’t fully understand what’s available today and how it works.

Improving the space

  • Something to fill up the atrium and make it feel warm and welcoming. Chairs, lounge area? Like a hotel lobby.
  • Other common areas in/near incubator: lounges, places sit down to chat, have coffee, etc. whiteboards, pens. Lego blocks. Toys.
  • Art
  • Add carpets in the incubator (linoleum right now, I think? Dismaying contrast with the granite and marble everywhere else.)
  • From the atrium you can see right into everyone’s offices. Consider curtains or blinds for privacy.
  • Mix and match incubator offices w/ other spaces in the building. Current setup is super corporate, most powerful people in outside and corner offices. And I understand why this is the case, I just think you have an opportunity to do something more egalitarian.

To sum up here, with the financial resources available to MaRS, a much bigger share should go into making the current incubator space great. Do this before further buildout. Otherwise you are sending a message to tenants that they don’t matter as much as everyone else… which is exactly the opposite of the goal, right?

Improving the Web site

  • The site marsdd.com is quite hard to find on all of the major search engines. You need to know the exact title to find it.
  • The title of the marsdd.com homepage should state what Mars is, e.g. “MaRS – [descriptive tagline here]”. Right now it says “Marsdd.com”. This will help site visitors know they’re at the right place. It will also help search engines make the site discoverable.
  • The site content might be better organized around target audience segments. That would make it easier to understand and navigate. Maybe think about “Entrepeneurs”, “Investors”, etc. as more logical top-level tabs.
  • The site content needs to be written more in plain English. Example (not to pick on anything in particular): “The MaRS Business Resource Centre (BRC) is your entryway to the core of MaRS: the convergence of resources, people and ideas to spur innovative collaboration. MaRS BRC is comprised of a set of physical and virtual resources designed to make the commercialization ecosystem more robust. The BRC is the strategic hub for the development and coordination of all MaRS commercialization programs.”

My 2 cents.

Thanks for the opportunity to see MaRS.

Yegge Writes About How Google Works

Google’s Steve Yegge wrote a lengthy critique on Agile development about a month ago. The piece is ostensibly about agile development, but it’s really more about how Google works and why it doesn’t need capital-A Agile methods.

My favorite bit: “developers can switch teams and/or projects any time they want, no questions asked; just say the word and the movers will show up the next day to put you in your new office with your new team.”

Sounds like fun. It’s not something every company can do, though, especially not well-established ones. The way I see it, this amazing degree of freedom stems from two particular luxuries.

Luxury #1: Incredibly deep pockets. When you’re flush with cash you can hire the best and brightest, and reward them heavily. Google is so rich that it can spend disproportionately on acquiring and retaining talented people, even when going head to head against its richest competitors. And its business model is so highly profitable — again, compared to competition — that it should be able to continue doing this indefinitely.

Luxury #2: Very few dependencies. Google delivers software straight to the web and millions of largely nameless customers, rather than into the hardware production pipelines of a handful of OEMs or the IT integration pipelines of a few thousand corporate clients. That’s why they can pick and choose what to build, and when to ship it, if ever. That’s why they can label products as “beta” in perpetuity if they wish to: their customers aren’t yet demanding any more than that. And that’s why Google developers can vote with their feet on which projects to work on: at the end of the day, there isn’t a customer on the phone line holding them accountable for a slip in the schedule of Project X.

Lucky ducks.

Domain Snatching

Mike Davidson, CEO of Newsvine.com, tells the story of how he got the newsvine domain and in the process found out a lot about how to grab a soon-to-expire web domain. A useful and quick read if you are domain-hunting.

See also: