turntable / as the table turns

Google have released interactive driving routes (found via Human Factors).

I’m certain this is either heavily influenced or entirely based on the Eyebeam NYC Subway map project. It’s using the same Flash overlay technique.

There are more video demos on personalising maps. This lets you add in photos, videos, even ads (see details here).

When I tried mapping across the two islands of New Zealand it also took into account the ferry crossing. Customising it is amazing. Drag and drop simplicity. Right-click context menu. Scroll wheel zooming, with crosshair centering. It’s another piece of mind blowing design from Google.

Grant and I both worked on driving routes for newzealand.com back in the Web 1.0 days. We know how complex maps and routes can get, even in the simplest implementation. That was later updated to include some Flash interactivity first developed by Andy Biggs and more recently given a major overhaul by Barry Hannah which includes extensive geo-coding. They even integrated it with Google Earth.

When I worked on newzealand.com the biggest user request was always more maps, maps, maps. Wisely, Tourism NZ invested a lot of money into building better maps. They could have never predicted (and certainly never relied on) Google developing technology like this. Now it seems like they should be integrating Google maps into newzealand.com, with photos, videos, and driving routes, rather than continuing to use their proprietary system. Of course, they can still take advantage of the database and technology they’ve built, while leveraging Google’s incredible technology and global reach.

Of course, I can only imagine how useful this is on the iPhone. Could some lucky iPhone owner tell me how it really is (cough Wayne cough)? When we were coming up with blue-sky ideas for newzealand.com mobile and mapping were always the big dream. It’s getting much closer to becoming reality, yet it’s still frustratingly out of reach. Especially considering the price of mobile data.

In a last minute change up, Rod won’t be able to make it to Queenstown to present at the Web on the Piste conference. I’ve been asked to take his slot. Sometimes you just have to take one for the team.

Please let me know if you’ll be going.

And in case you’re like me wondering what piste means, thanks as always to Wikipedia.

I’ve been a vocal critic of the Best Awards. When it comes to web design they require entries to be submitted on paper boards which is how they are judged. Unreal. The results have always been completely off the mark.

Well, maybe things have changed this year. For The Masses and Cameron Charles out this year’s winners (because the Best site is down…ay yi yi). It looks like Best have finally gotten it right, showcasing some extremely high caliber web design work. Go NZ!

• Electrocity – A really cute, fun, smart, NZ-ified version of Sim City. Also check out the design of this related site School Gen
• Munuit website – Great band with a super cute, playful, dynamic interface. Inspired by Katamari and Loco Roco
• Radio New Zealand – Great content, made easily accessible through solid information design and elegant visual design
• OBO hockey gear – Refreshingly fun design for a fun looking product
• ACC Sports websites – A web tool for helping you keep fit and healthy
• Action This – (Not featured on Best, but announced today) A project management web app that was just (pre)launched

DATE CORRECTION FOR WELLINGTON:
The Xero UPA presentation in Wellington is happening on Tuesday 7 August.

I’ve been invited to speak next month at UPA events in Wellington and later in Auckland.

I’ll be talking about and showing the interaction design process used to create Xero, providing some insights into the different design techniques used to build a complex online application quickly, yet effectively. I will also discuss how those techniques are evolving as the company and the software grows.

Web 2.0 debate

Last month, I participated on a panel debate at Webstock, arguing the merits of Web 2.0. I thought about making my presentation silly, but I couldn’t help myself and ended up creating a genuine analysis of what Web 2.0 is really all about, what makes it so significant, and why it’s important to understand. I think my slides do explain it pretty well.

I have to admit that our opponents did a much better job of making their case, using their rye cynical wit and deft charisma. Their tactics were extremely effective, but ultimately they were fighting a hopeless cause.

You can watch the full antics here.

There’s another Webstock Mini coming up on June 19th (my birthday!). The line up looks as great as always: a RoR workshop by the legendary Koz, a tour of Second Life, the low down on Firefox 3, followed by a panel “debate”. I happen to be one of the invited panelists for that debate.

The topic of the debate is “Web 2.0 is all fizz and no substance”. I’m not exactly sure what there is to debate. It seems like a pointless folly to me. I’m hoping we’ll have a bit of fun with it.

In the spirit of web 2.0 and user participation, I urge you to contribute to the wiki I’ve created for the occasion. I’m really counting on some user contributions. Please don’t let me down.

This afternoon I met with my fellow debatrs Brenda Leeuwenberg and Che Tibby to plot our triumph, over lunch at Ka Pai (my new favorite lunch venue – I’ve eaten there 3 days in a row – finally yummy, affordable salads in Wellington!).

Maybe we could all do a Meetup prior to Webstock? No flashmobs please.

This is great, accurate description of a typical day in Wellington. Although, I’m not a big fan of Malaysian. Instead, I highly recommend Siem Reap.

Other personal favorites (I’m too lazy to link all of these):

• Matterhorn
• Maranui
• Capitol
• Pizza Pomodoro
• Olive
• Miyabi
• Sweet Mothers
• Salute

When I first started working on Xero, I used sticky notes to help me get a sense of what it would take for us to build an online accounting system. After working on those sticky notes for about two weeks, we felt comfortable that we had a good foundation for the product architecture. Two weeks might seem like a long time to spend scribbling on sticky notes. But it was worth it. Those sticky notes are still a point of reference for us to this day – they still reflect the overall product structure and the product roadmap.

From our earliest plans we mapped out two major milestones: having a beta ready by November 2006 and having the product released by April 2007. We had a vague feeling that those two targets were theoretically do-able under ideal circumstances, but we all knew from our past experiences that theory and reality never align, and ideal circumstances only happen in theory.

That’s why I am so amazed that we pulled it off – hitting both targets to the day! Besides working with an amazing team of talented people, with all the hard work and some good luck, I think one of the most important factors that enabled us to make those targets has been our commitment to an agile design and development process.

If we would have done “proper” software specs for Xero we’d still be bogged down writing and arguing over use cases and flow diagrams to this day. Nothing would have even gotten designed or built yet. Instead, our specs process generally involves an hour at the whiteboard identifying the core requirements for an entire piece of functionality. From there, I go straight into prototyping.

My method for prototyping is doing rough screenflows. These are intentionally rough so that we don’t burn our time on low-level visual details, when we just need to sort out the high-level functional concepts. I quickly mock up screen layouts for each transaction in a typical user scenario, from the start of a task to the end, hitting every transaction along the way. It’s like storyboards for movies, scene by scene you see the plot unfold. I can build these prototypes very quickly, generating lots of ideas as I iterate through dozens of different designs in a few hours.

The screenflow prototypes are done as black-and-white outlines, similar to traditional wireframes. Except you move through it like a slideshow, seeing how one thing leads to the next, getting a feel for how it all flows. Traditional wireframes and written specs take a lot more time to create, plus they force you to intellectually resolve how it all works together in your head, instead of seeing how it flows on screen. Having to work it out in your head, instead of seeing it in action, leaves too many things open to misinterpretation, causing major confusion and delays.

With the screenflow prototypes we quickly evaluate what’s right and wrong about a design, what’s missing and what needs to be ripped out. We put the prototypes in front of users to get their feedback, which quickly gives us a good indication if we’re on the right track or not, and it provides us with some insights on how to make it better. Then we do more iterations.

This passage from an article written by the head of IDEO Tim Brown describes what I’m talking about really well:

People need to have a visceral understanding — an image in their minds — of why you’ve chosen a certain strategy and what you’re attempting to create with it.

Because it’s pictorial, design describes the world in a way that’s not open to many interpretations. Designers, by making a film, scenario, or prototype, can help people experience the thing that the strategy seeks to describe.

Build to Think

Design thinking is inherently a prototyping process. Once you spot a promising idea, you build it. The prototype is typically a drawing, model, or film that describes a product, system, or service. We build these models very quickly; they’re rough, ready, and not at all elegant, but they work. The goal isn’t to create a close approximation of the finished product or process; the goal is to elicit feedback that helps us work through the problem we’re trying to solve. In a sense, we build to think.

When you rapidly prototype, you’re actually beginning to build the strategy itself. And you’re doing so very early in the innovation cycle. This enables you to unlock one of your organization’s most valuable assets: people’s intuitions. When you sit down with your senior team and show them prototypes of the products and services you want to put out in two years’ time, you get their intuitive feel for whether you’re headed in the right direction. It’s a process of enlightened trial and error: Observe the world, identify patterns of behavior, generate ideas, get feedback, repeat the process, and keep refining until you’re ready to bring the thing to market.

The Prototype Tells a Story

Prototyping is simultaneously an evaluative process — it generates feedback and enables you to make midflight corrections — and a storytelling process. It’s a way of visually and viscerally describing your strategy.

So how did I get roped into designing an accounting system? I’ve wanted to develop a web product ever since I started Turntable. I came up with various concepts and prototypes over the years, but for a host of reasons I was never quite ready to make it happen. With web 2.0 fever in the air, I once again got the strong itch to build a product. After brewing up some ideas, I approached Rod Drury with some of my ideas, just to see if I had anything worth pursuing. I only knew of Rod from reading his blog, but everything he wrote resonated with me. We met for coffee and we hit it off immediately. The next time we met, Rod blindsided me with an offer to join his new venture as one of the founding team.

When Rod pitched his idea to me, a “web 2.0 accounting system”, I didn’t have to think twice about it. I hate accounting. Obviously, accounting is a major factor in determining whether or not a venture will be successful. Yet, it’s such an excruciating process. I know that first hand from running my own business. So it was immediately clear to me that this was a perfect opportunity to design an accounting system that I could love rather than hate, while at the same time learning the ropes about building and running a software product from the best mentor in the business.

It also appealed to me because it’s a major business problem that’s begging to be solved. Accounting is something that every business must do. Literally, every business is required by law to do it! There’s no need to convince or educate anybody. Plus, most businesses hate the options that are on the market now. Meanwhile, nothing on the market is taking full advantage of network effects.

Finally, I was on board because Rod had the resources (aka cash) to do it right, to hire the best of the best designers and developers so we can build a great product and build up a strong brand very quickly.

So that sums up why I got involved. Next, I’ll write about how we got things off the ground.

Since July 2006 I’ve been working on Xero, an online accounting system. I can hear your internal dialog now, “A business accounting system? Gee, that sounds real fun.”

Believe it or not, it actually has been lots of fun. Seriously. I rate it as one of the best, if not the best, professional experiences of my life. That’s saying something, considering some of the projects and clients I’ve been lucky enough to work with over the years.

How could it be so fun? For one, the people involved are a true joy to work with. And, two, as Todd Dominey stated so eloquently, “Client / service work has its advantages, but there’s something to be said for pouring all your heart and mind into a product people use and enjoy. It’s the most satisfying work I’ve ever done.”

Last week, we officially launched, moving out of private beta into public release. I have to say that I’m extremely proud of the work we’ve done. Doing an accounting system certainly is a major challenge, so it’s a big thrill to get the get the response we’re getting.

Over the next few days I’ll post some details of how and why I got roped into designing an accounting system, how it got off the ground, and some of the techniques we’ve used to get it done.

Our wedding was all set to happen in Prague. Shortly before our trip, Hadley and I discovered that getting legally married in the Czech Republic required some insane bureaucracy. Instead, we had to get officially married in California, before our wedding.

On April 1 1997 we called City Hall. They required advanced bookings. So we picked up the Yellow Pages, called around, then we popped over the Golden Gate Bridge to the bedroom suburb of San Rafael where we had an unexpectedly emotional ceremony, performed by a minister in his back garden.

Fast forward, two kids and ten years later, we once again found ourselves slightly caught out with our plans. As luck would have it, we were extremely fortunate to be able to make a booking at the Master’s Lodge in Napier.

The Master’s Lodge is an amazing place run by two wonderful people, Larry and Joan. A pair of former Manhattan-ites who have put together a truly special getaway. Everything about it is absolutely exquisite. Impeccable. Flawless. But it is by no means pretentious or stuffy. You are definitely pampered, but they are very careful not to be annoying. It’s set in a lush garden, in the hills overlooking the Hawkes Bay with Napier and the beach just below and the vineyards further in the distance.

The house and the rooms are beautifully curated with period furniture and art. It’s not gaudy or overdone, it’s just right. There’s an incredible attention to detail. They have museum quality pieces everywhere you look, but it still manages to retain a cozy, very livable and intimate atmosphere.

When we arrived Larry made us a couple of highly refreshing Martinis. We then had dinner at the Craggy Range winery’s restaurant, Terroir. That was a big disappointment. To say the food was mediocre is being very polite. The wine was nice, but that just doesn’t cut it. Apparently, we’ve been told that Te Awa is the place to go. Next time, for sure.

The following day we went wine and cheese tasting, as you do. Although, we had never had the chance to do this previously in the five years of living in New Zealand, thanks very much to our blessed little offspring. The boys were with their gran, so almost regardless of what happened, it was going to be heavenly. We didn’t get around to very many vineyards, but we did manage to pick up a few special bottles from Black Barn and Te Awa. The weather could not have been more perfect. Sunny and hot in the day, then warm and still at night. It reminded us very much of Napa.

We came back to the Master’s Lodge and had a short rest before Larry indulged us with a few more fantastic cocktails. I was intrigued by one particular item on offer: a Ramos Gin Fizz. Wow!

Then they served us dinner outside on their beautiful veranda. Did I mention…? We had the Lodge all to ourselves, because the other couple staying at the lodge were off at a wedding. So it was dinner for two, overlooking the Hawkes Bay.

It was easily one of the very best meals we’ve ever eaten, perhaps the all time best, served with superb wines from their private collection – hand picked to match each course.

Please excuse my dilettante attempt at recounting our fine dining experience. This is mostly for Heidi’s sake.

For starters: two small potato pancakes, topped with a slice of tender venison and marbled blue cheese. It was two bites of bliss on a dish.

First course: Bluff Oysters. It was our first time, we were Bluff Oyster virgins. One was served raw on the half-shell. The other two were served in a jelly. Did you catch that? Oyster jelly. Let me tell you how mortified Hadley and I were when we saw that. To be exact, it was oyster cucumber jelly with ginger and caviar. Surrounded by wasabe peas and dabs of fresh wasabe. This was easily the best course. I will never forget that oyster jelly. We were served 2004 Vinoptima Gewürztraminer, a varietal that I don’t particularly care for, but it was the best I’ve had.

Second course: Snapper over fresh peas and lentils with a 2002 Morton Estate Reserve Chardonnay. On the side was a loaf of bread flown up from a baker in Christchurch.

By the end of the second course we were done. We couldn’t imagine eating any more! But somehow we did. It was actually difficult to get it all down, but it was worth it. Even with the extra kilos we packed on.

Third course: Lamb tenderloin on a red wine jus with Swiss chard and roasted parsnip. To go with it, a 2000 Kingsley Merlot.

Dessert: Passionfruit creme brule with home-made palmier.

Everything was super fresh and done to perfection. The flavors were lively, but well balanced. The chef was a woman named Kylie Howard, who is apparently quite renowned in the region.

The next day we went to the farmer’s market and picked up some more gourmet goodies. Then we took a ride out to an art gallery on a beautiful farm estate. Finally, we ended up back at the Black Barn for a great lunch. At lunch, Hadley asked me if I would ever want to be a food critic. I emphatically said no, because I never want to be such a pretentious wanker. I offer you my sincerest apologies for not living up to that promise.

All up, we were extremely lucky to have the weekend work out so perfectly.

I feel the same way about meeting and marrying Hadley. Our life together has worked out so wonderfully. I love her more deeply than ever. Each day after the next it gets better and better. It’s not a fairy tale life, but it’s actually not that far off, when I think about it. I’m extremely grateful to her for being my best mate, a true soulmate.

In 2010, we will have been together for 20 years!! By then, we will have spent most of our lives together. Time really does fly when you’re having fun.