Date: Monday, February 25th, 2008
Time: 6:00pm to 9:00pm
Location: Toronto Board of Trade, 1 First Canadian Place, Toronto, ON
Cost: Free (cash bar if you're thirsty)

Dinner will be served, the Demos will be excellent, the Ignites will ignite, and then we'll adjourn to The Duke of Westminster for more food and drinks.

As always, details are available at on the BarCamp's  DemoCampToronto17 page, 'tickets' are at Eventbrite, and those wishing to sign up for a demo or ignite session can do so via the Wufoo DemoCamp form.

We've seen a lot of turnover at recent DemoCamps and we're always happy to welcome new faces into the crowd. Since this is the first DemoCamp of 2008, we're going to change the old "bring a new person" rule around a bit and ask everyone to "bring a new person AND an old friend who hasn't been out in a while". Things have changed a lot since our humble beginnings around the BubbleShare board room table, so let's bring them back and show them what's new!

Lastly, we're always looking for individuals or companies who would like to put up $200 and help make the event possible. If you're interested, please contact me directly and I can give you a rundown of what's involved.

Hope to see everyone there!

1. Tractability: How difficult will it be to launch a worthwhile version 1.0?
2. Obviousness: Is it clear why people should use it?
3. Deepness: How much value can you ultimately deliver?
4. Wideness: How many people may ultimately use it?
5. Discoverability: How will people learn about your product?
6. Monetizability: How hard will it be to extract the money?
7. Personally Compelling: Do you really want it to exist in the world?

If you're developing a new product — or even just thinking of doing so — do yourself a favour and read the post to get a sense of where you stand. It's obviously not gospel (and sometimes the best ideas come out of left field and can't even be charted on existing metrics), but it's a really good step further down the road and will help you prepare for some of the questions investors are likely to ask if you go in that direction.

We stayed at the City Inn, which turned out to be a refreshingly modern and simple hotel with free ethernet in the room (courtesy of a lovely pink CAT5 cable). We rallied the troops for a fun night on the town, taking advantage of The Commercial House's pretty fantastic pint, burger, and chips for £4.95. Tuesday morning saw us up bright and early for a walk to the University of Bristol campus, to pay a vist to 3CResearch, a member company doing "convergent technology research for digital media processing and communciations" (in case you're wondering — and I certainly was — the three C's are Communications, Content, and Creativity). We were given a demo of their Visualise project, which delivers streaming video to mobile devices (currently over WiFi but soon over faster and more pervasive delivery channels like HSDPA and WiMax). It was designed to offer a better experience to fans of events like rally racing, which generally involves standing in a cold, wet field for hours on end in the hopes that a car will hurtle past you for an exhilirating 15 seconds. Visualise means you can still stand in the same damp glen, but now you can watch the race from multiple viewpoints on your mobile, as well as peruse stats and driver info (assuming the touchscreen still responds to your frozen fingers). In all seriousness, the technology can be applied to any kind of event and would be great for things like music festivals like Coachella, at which you would need to clone yourself several times over just to catch half the bands you wanted to see. The demo was followed by a presentation by Dr. Geraint Jones about a number of the other 3CResearch projects, including Intelligent Content Based Retrieval (ICBR) (analyze video archives and index based on content, motion, etc.) and Motion Ripper (extract motion data from video and apply captured motion signals to computer animation — i.e.: analyze a video of birds flying and animate an electronic bird). Their research is very interesting, if not entirely cutting edge, but I thought the more interesting part was the conversation which erupted over licensing of technology and how pure research facilities can successfully commercialize their ventures. Sutha suggested they take a look at the MIT Media Lab model, which is basically pay-for-play (i.e.: companies can pay an upfront and quite large fee and then have access to all of the research), and I would think there's a lot to be learned from the MaRS Discovery District and from the University of Toronto's Innovations Group.

We spent the late afternoon and evening at Watershed Media Centre, a facility that reminded me of The Bookshelf in Guelph, a favourite haunt during my University years. Watershed includes a few cinemas, a caf&eaccute; and some meeting facilities, and was our home for a great mini-trade show event which consisted of 40 South West companies meeting and greeting our Canadian crew. Steve Collett (International Trade Advisor from UKTI) started us off, Ian Kelso (from Interactive Ontario) gave a quick state the union of New Media in the New World, and I followed him with a quick Introducing the Canadians rundown of the companies in the mission (and including a photo of a polar bear cub, two bears making out in the woods, and the poster from South Park: draw your own conclusions). I was followed by Mark Leaver (Director of Development from South West Screen), who mirrored Ian's talk but focused on the South West region of the UK, and then we were treated to a fantastic presentation by Adam Montandon, Director of HMC Interactive, who have built some truly amazing interactive experiences for Cadbury's Purple Planet and The Royal Obeservatory. He also has the excuisitely good taste to have fallen in love with a Canadian girl and is working on a (longish) term plan to move to our fair lands to be with her. I cornered him after and insisted that we line up a DemoCamp demo on his next visit, which he heartily agreed to (or maybe defensively, so I'd let him out of the corner — hard to tell). The trade show was a great success and I met a number of interesting people doing interesting things in which we might well take an interest, including John Bradford from jbsh, LLC (who are working on an educational product for the Canadian market), Paul Bason from University College Falmouth (who was delighted by Michael Wesch's latest and who was really interested to hear what we looked for in students and in whether we'd be into a distance-learning based partnership), David Karney from Potential Difference (a swank Bristol web shop who are basically Radiant Core's British counterparts, but on .NET), and James Ovenden from Ball Fusion (who are marketing an amazing video on street soccer skills — check out some of the tricks on their homepage). Apologies to the gentleman from Sanoodi, whose slightly odd application name I've managed to easily remember but whose much less odd personal name I've completely forgotten (owing to his lack of business cards, of course). We had a great chat about his app and where it's headed, and I showed him Toronto's own Planet Eye and the Specialized Riders Club (run by our friend Chris Matthews) for some inspiration. We ended the evening with a delicious dinner for fourteen at the Severn Shed (don't worry Mike: I didn't pick up the tab!), during which I had the pleasure of chatting about documentaries, music, books, and television with Julia Bennett (from White Pine Productions), Jason Krogh (from Zinc Roe), and Paige Chambers (from the Canadian Business College).

Stay tuned for Day 3, which will mostly be a train ride to Glasgow!

Some of those things are familiar from my own days as a student (7 hours of sleep was definitely not), but some of them have definitely changed. I think, to me, the most compelling series of sheets in this movie is the one about graduating into a job that doesn't exist yet. Stop and think about for a moment: are you doing what you trained to do in school?

A quick poll of the office shows that we're feeling ready. Are you?

Rachel Hinman's post on their research reads like a textbook approach to requirements gathering phase, including 2-3 hour interviews, some in-home ethnographies, some in-person interviews with a total of ten people (a combination of type 1 and 2 diabetics and two diabetes educators). I didn't know much about diabetes before I started reading their reports, other than that diabetics have to monitor their insulin levels, usually by pricking their finger with a test device or by using a test strip, and have to add insulin to their bodies to compensate and be able to digest carbohydrates. I had no idea, for example, that most type 1 diabetics come in contact with a needle 10 - 14 times a day (between testing themselves and injecting insulin). I had also never heard of an Insulin Pump, which is an external device, connected to the body via tubing and a cannula implanted subcutaneously (under the skin). Although most of the pumps currently available are big, bulky, and really great examples of industrial design gone bad, their users love them for the control they bring and the positive impact they have on managing their condition. After building an understanding of the day-to-day realities of living with diabetes, and of the current approaches to controlling and managing insulin, the team moved into the design phase (as documented in Dan's post Charmr: Creating Concepts).

The romantic notion of design and designers is that they sit down at a blank white sheet, sketch and draw and create, some magic happens, and a beautiful design is born. Although that's fairly close to the truth, one of the biggest stumbling blocks is actually the blank white sheet itself. Unconstrained design spaces — spaces which have no limits in any direction — are difficult for the mind to grapple with. Questions like Should we make it 100 feet tall? Bright purple? Does it need to fly or swim or make flawless espresso? can destroy your forward motion and lead to designus procastinus: the incredible ability to return phone calls and emails and catch up on mundane tasks in lieu of producing a design. Blank sheets are scary, which is why we always try to go into the design phase with some hard constraints in place. Although it may seem counter-intuitive, the more our design space is shaped by the reality of our clients' requirements, the easier it is for us to do our jobs. The design crew at Adaptive started out by extracting six principles from their research:

1. Users had to be able to wear it during sex (elegant, discrete, comfortable)
2. The device had to make better use of data
3. Easy to learn/teach. No numbers (diabetes affects a wide range of people so it has to be simple and downplay numbers in favour of smarter information like status and trending)
4. Less stuff (physically speaking)
5. Keep diabetics in control (no automatic pumps — give people the ability to control what's going into their bodies)
6. Keep diabetics motivated (you never get a day off from your diabetes, so try to have the device keep people motivated to control their condition)

Alexa Andrzejewski takes over from there, describing how her and Dan took that inspiration through design of the user experience, in a post called Charmr: Interaction and Visual Design. Although I lack the understanding to assess how well their concept would work for a diabetic, it looks like they've done a great job of satisfying their six principles (with a possible exception of the first one: I'm not sure how the rubber patch over the pump would live up to being worn during sex from a comfort perspective). There's an Experience Blueprint PDF available (4mb) which sums up the project as a whole, including photos and interface mockups. I think their video speaks does a great job of showing off their design:

Amy was very impressed with the results (see NEWS FLASH: SF Design Firm Unveils the Diabetes "Charmr") and the reaction has been pretty much positive across the board. The point of the exercise wasn't really to create a product specification, so much as it was to lead the manufacturers of devices toward a more user-friendly approach to product design. The Charmr has some critics, particularly ones who have wondered why Adaptive Path didn't apply themselves to solving the problem now rather than in a few years, to which Dan has responded that they felt they would have the most impact leading future products rather than fixing current ones (and I whole-heartedly agree). Our industry has a long history of using our skills to help solve bigger problems, including recent examples like the searches for Jim Gray and Steve Fossett, and more local initiatives like OpenTransit, Zerofootprint, and StartupWeekendToronto's LobbyThem. It's inspiring to see firms use their spare cycles for the power of good, and I encourage firms everywhere to do the same. And yes, before you ask, we're eating our own dog food here too and have a project underway with Zerofootprint which we can't talk about just yet. Stay tuned for more details!

6:00	Social/Mingling
6:30	Introduction by Colin, Roy & Andrew
6:40	Best Practices around Product Design and Viral Marketing (Meagan Marks, Facebook.com)
7:30	Anatomy of a Facebook Application (Jay Goldman, Radiant Core)
7:50	FBML Overview (Sunil Boodram, Trapeze Media)
8:10	FQL Overview (Craig Saila)
8:30	Updating the Facebook Profile (Colin Smillie, Refresh Partners)
8:50	Demo: .Net Sample Application (Ricardo Covo)
9:00	Demo: Carpool by Zimride (Rajat Suri)
9:10	Demo: My Aquarium by Greg Thomson
9:20	Wrap-up & drinks

If you're reading this after the fact, welcome to Radiant Core! Don't forget to check out our Careers section for some great positions, including Facebook app development :)

That's right folks: it's that time again! We've just about finished our massive office renovation and now we have all this empty space to fill, so we sat down and filled up an entire white board of things we could fill it with. A sample:

• Elephants (too heavy, too many peanuts)
• Clowns (too scary, too many clown cars)
• Origami Cranes (too many paper cuts, too many dead trees)
• A Bigger Team (too much... fun?)

And there you have it! We settled on a bigger team, though I still haven't ruled out elephants provided we can build some kind of code input device that doesn't get crushed under their massive feet (Ed: trunk based?).

Effective immediately, we're looking for two key positions:

• Integrator/Web Developer
• Business Development Manager

All the instructions you need are in the posts, so go read 'em and send in your info! If you know someone who matches the description, please forward along, and if you write a blog which gets read by the kind of people we're looking for, please make a quick post on our behalf.

UX Report: The Series!

Since there's a lot to talk about, I'm going to break this up into a series of posts over the rest of the week. While many of my colleagues are down in Austin frolicking at SXSW, I'm going to stay where it's still cold and wet and tell you all about a trip to the one place in the tech industry that's pretty much the complete yang to the SXSW ying. I do it for you, really. Can you feel the love?

Today's post is about the setup and format of the two days, while the rest of the week will tackle specific sessions and presentations. Here's the breakdown:

    
• Today: Format (c:)
    
• Tuesday: The New Microsoft (Again)
    
• Wednesday: Design Matters (Maybe?)
    
• Thursday: Expression
    
• Friday: Wrapping Up

I'll come back and turn those into links as the rest of the pieces get published so you can always just tune back into this post to find them again.

Behind Enemy Lines

Let's get the bit about being the contrarion out of the way first: As a lifetime Mac user and passionate believer in Open Source, Culture, and Community, I viewed this trip as an opportunity to visit the beast's lair and to peek behind the curtain at what it contained. Back when my youthful naievity hadn't been dulled by the wisdom of time, I fought the Holy Religious War of the Operating System with all of the passion that a teenaged fan boy can muster.  I lost the need to convert the Great Unwashed Masses to the One True Jobsian Way sometime around the point where I became really interested in the User Experience of technology. As I got older, I realized that they're all just tools - some nicer than others - but in the end the importance is the outcome. I still think Apple makes better machines and software (although it has plenty of faults of its own), and we run our business almost entirely on Macs, but I'm happy to admit that there are plenty of times when their technology is not the right answer. This was a chance for me to go spend a few days with people who I respect a great deal, in a friendly and welcoming environment, and to learn what the other half will be up to for the next few years. It was interesting to note that there were four MacBookPros out of fifteen attendees and that four or five other people around the table admitted to owning a Mac at home (just for the kids to play on, of course).

Around the Table

Since the event was organized by Microsoft Canada, the Round Table consisted of some of the best and brightest Canadian UX minds. A quick introduction:

    
• Ryan Apps, Traffik Group
    
• Colin Bowern, Official Community
    
• Audrey Carr, Organic
    
• David Crow, Radiant Core
    
• Nicole Flippance, High Road Communications (Microsoft Canada's PR Company)
    
• Tom George, Design Axiom
    
• Dave Goodwin, University of Waterloo
    
• Anthony Hempel, Blast Radius
    
• Bryce Johnson, Navantis
    
• Kerri McKenna, imason
    
• Ben Skelton, Haberñero
    
• Gene Smith, nForm

Our Hosts

We were graciously hosted by a number of Microsoft Canada folk in addition to the great list of speakers. Thanks go out to:

    
• John Oxley, Microsoft Canada Director Community Evangelism
    
• Daniel Shapiro, Microsoft Canada Audience Manager
    
• Jerome Carron, Microsoft Canada Developer Evangelist

Format (c:)

As per my Reporting Live from Bellevue post, the event was held at the beautiful new Westin Bellevue hotel. We camped out in one of their conference rooms for two days and heard presentations from an amazing group of speakers:

Day One: UX at Microsoft

    
• Darren McCormick, Worldwide UX Role Owner for Microsoft: What’s up with UX at Microsoft?
    
• Will Tschumy, West Coast User Experience Evangelist (formerly Director of Experience for Flock): User Experience in Research - the Ribbon in Office 2007
    
• Jeff Pettiross, Senior Program Manager: User Experience in Practice - Health Explorer
    
• Kevin Gjerstad, Group Program Manager (WPF Reader): A User Experience Story – NY Times Reader
    
• Michael Suesserman, Technical Evangelist: Windows Vista Desktop and Live Gadgets

Day Two: Expression

    
• Erich Zocher, General Manager Tools (Expression): Turning UX Ideas into Reality (The Tools Roadmap
    
• Arturo Toledo, Technical Product Manager (Expression): Expression Design and Expression Blend
    
• Wayne Smith, Senior Product Manager (Expression): Expression Web
    
• Angela Baxley, Product Manager (Expression): Expression Media

The presentations largely consisted of someone speaking to a PowerPoint deck, followed by a Q&A with the Round Table panelists. These posts are based off my extensive notes taken during the presentations, but if I missed something and you were there to catch me on it, please add it in the comments!

That's it for Day 1 - tune in tomorrow for The New Microsoft (Again)! I'll leave you with a neat PictoBrowser of all my shots from the event:

Turns out that the folks who work at Microsoft are good people! We're particularly enamoured with John Oxley, Director Community Evangelism Microsoft Canada, who graciously ignored the above mentioned glowing fruit and invited yours truly down to Bellevue to participate in the first Microsoft User Experience (UX) Round Table. Despite any harsh criticisms of the past, I'm not above turning a new leaf and it's definitely true that Microsoft's UX Research teams are the hot spot du jour (not disimilar to Xeorx PARC in days of yore). Besides, free trips are always good trips, particularly when accompanied by Mr. David Crow, whose penchant for double bourbons is well known (particularly to my own precious liver who strains vainly to keep up).

We caught an Air Canada flight from Pearson to Settle-Tacoma which turned out to be delayed an hour. The plane was an Embraer 190 which was equipped with the very latest in En Route Inflight Entertainment systems, a topic which I'm becoming increasingly familiar with (see my recent I've-never-even-touched-it review of Virgin America's Red). The E190s feature the Thales Group's TopSeries Inflight Entertainment system, in this case heavily branded with the Air Canada livery and delivered in both English and French. I wasn't able to snap any shots on the way down (I'll try to grab some on the way back), but picture your basic 9" touchscreen embedded in the seat in front of you. These units lacked remotes and many of the features were "Unavailable" (including the Map, News, and Games), though they did feature a USB plug to the left of the screen for charging your ever present array of electronica. Placing the plug at eye level guarantees you'll see it - though the lack of markings might make you hesitate before you plugged in your trusty iPod. Not I! In the interest of journalism, I can confirm that it provides a steady charge but no much else (it might be more natural to place the plug in the armrest, nearer to where the iPod is likely to rest, but progress is progress and who are we to stand in its way?).

The system seemed a little buggy - David's seatmate crashed his twice (though no Blue Screen of Death, so one supposes that it's running on some Linux derivative). There's some markedly weird Information Architecture in the menu system (e.g.: going into the Kids section and selecting Movies drops you into a hidden section of the Movies menu, bizarely merging the first and second level menus), and the touch screens weren't overly responsive (the "Fullscreen" button in movie mode had to be mashed at least three times before it stuck, as did the "Turn off Display" button in the "Screen Brightness" control), but the fact that you can watch or listen to (almost) whatever you'd like elevates airtravel from tedious to almost pleasant. As noted in the review of Red, introducing this kind of tech into a cramped space repleat with expected interactions can bring some unexpected behaviours into play. The screens definitely pumped out a fair amount of heat - noticeable by placing your hand near them - and the cabin was a fair bit warmer than usual, bringing to mind all kinds of stories about library architects not taking into account the weight of books. I also found it surprisingly difficult to settle into Clint Eastwood's excellent Flags of our Fathers after my seatmate started the same film about three minutes before me. Whenever the action lulled, my eyes were inevitably drawn to his screen where the future was foretold in off-colour, angled LCD watching. All the same, the mere fact that I could choose to watch a seemingly unedited print of a great film instead of a heavily censored version or poorly selected rubbish more than made up for it. Sure, it lacks the über cool social chat features and inseat food ordering from Red, but it's aeromiles ahead of craning over heads and seatbacks to see a blown out projection and listening to a tinny soundtrack through a set of hollow rubber tubes.

Further excitement lurked in our shuttle when we blew out a tire on the highway from the airport to the hotel. It was pretty uneventful in the end; a fifteen minute wait on the shoulder until a different van - complete with cracked windshield and flaming skull license plate frame - picked us up. The Westin Bellevue hotel itself is brand new and beautifully decorated and I'm moments away from crashing in the Heavenly Bed. More tomorrow as we start the sessions!

We were really inspired by our good friend Robert Ouellette's post How Would You Improve The TTC Web Site? and thrilled at the ensuing support and coverage it collected during the first few weeks of the New Year. Some of Toronto's leading blogs leapt to support Robert's cause and quickly asked their readers to provide their ideas in the comments of the following posts:

• Spacing Wire: Help improve the TTC's website
• Torontoist: Help Make the TTC's Website The Better Way
• BlogTO: Bloggers Help TTC Website
• Transit Toronto: Giambrone Turns to Transit Fans for Suggestions

The Press rallied shortly thereafter, providing some pretty good coverage about Adam Giambrone, the TTC's new Chair, accepting Robert's offer and offering to review the feedback. Amongst the radio coverage on AM640 and CBC, the nation's newspapers rang in:

• National Post: Blogtown
• Globe & Mail: The TTC Gets Some Online Help

Here's Where We Come In

Figuring that we know a thing or two about building websites, we thought that we could offer some useful feedback to compliment the already excellent thoughts collecting in the comments on the original blog posts. In addition to our Solutions and Portfolio of experience, we know lots of really smart people who could bring a lot of value to the table. And so we did exactly that and gathered a crack team in Radiant Core's boardroom to scratch our heads and stroke our chins and ruminate on how we could help to better the better way. And what a crew it was! In addition to your intrepid scribe and Michael Glenn, our Architecturally Awesome VP of Technology, we invited (in alphabetical order - ranking a team of this calibre would be impossible in anything but):

David CrowDébonair Developer

David is a passionate advocate for Toronto's technology community. An open community has catalyzed around David in the form of BarCamp, DemoCamp, and the Innovation Commons, reinforcing his belief that openness can spark innovation - "the community is the framework". David is an experience designer, consultant and a software developer.

Joey DeVillaAccordion Articulator

Jose Martin "Joey" deVilla is, among other things: The Thrilla from Manila, based in Toronto, Canada, Technical Evangelist for the web services company Tucows, and a guy who often takes his accordion with him, playing AC/DC, Nine Inch Nails and other pop and rock stuff on it.

Madhava EnrosTTC Guru

Madhava is a Toronto interface/interaction designer who spends, perhaps, too much time thinking about public transit. A dedicated TTC-rider, he has been following Toronto transit planning and policy matters for many years.

Mark KuznickiPolicy Wonk

Mark is a strategy consultant, policy wonk and a TorCamper. Mark's recent policy work includes consulting in cultural policy and in the development of an economic strategy for the entertainment and creative industries cluster. Mark's professional background includes work as a tech startup entrepreneur and in business analysis and tech project management in the financial services industry.

Will PateSocial Media Maven

Will is an all-around web geek: blogger, photographer, videogamer, online community and social media consultant. He's a peopleperson who seeks out technologies to enable self expression, connection, or the creating of meaning.

We really couldn't have asked for a more amazing brain trust. Will captured the moment as we settled in for some serious thinking:

And so we were off and running! Stand back folks, because we really rolled up our sleeves and did some serious analizing.

State of the Union

No one would argue that the TTC currently has a good website. If you've somehow been spared the pain of trying to find information on it, take a few minutes and do your own mini-review now: www.ttc.ca.

Sure, it's ugly and all, but just how bad is it? Here's the quick breakdown using a Radiant Core technique called The Five Thumbs - a quick set of five heuristics that you can use to evaluate any software or website. The Five Thumbs are easy to remember if you know your vowels (just think AEIOU and you'll be most of the way there):

1. Adaptive: a good tool adapts to the user rather than the user adapting to the tool. The TTC's site is very inflexible and forces visitors to do things very much in machine-speak like searching for routes by number rather than by name. The site also doesn't bend when it comes to the format of the information: as Henry Ford might have said, you can have it in any colour you'd like as long as it's a huge PDF or badly formatted HTML.
   
2. Expandable: a good website is easily expanded on by encouraging an ecosystem of third parties to build on a solid foundation. There's no way to get access to the wealth of data behind the site including schedules, stop locations, routes, etc. To make matters worse, the HTML is non-standard and schedules aren't presented in tables but rather spaced out using tab characters in a block of <pre> code, making them hard to parse by screen scrapers and readers.
3. Intuitive: the basic functions of a good tool are easy to figure out with minimal assistance. Given that the basic function of this site is to disseminate information, it's a tangled maze of bad Information Architecture which hides important details in deeply buried pages. Navigation is via HTML <select>s, form controls which are usually reserved for selecting options from a list and can cause problems for screen readers and other accessibility devices.
4. Open: how well does it play with others? We usually measure websites on how well they both render across browsers and validate for standards compliance, as well as how deeply they incorporate accessibility features like tabindexes, accesskeys, alt attributes on images and titles on links, etc. The W3's validators can't get passed the lack of a doctype attribute, though the site does fair somewhat better using Watchfire WebXact, which returns few serious accessibility issues.
5. Usable: how useable is it? This can be a fairly subjective measure, but empirical evidence from the comments left in the original blog posts suggests that users of the site have a very difficult time finding content.

The Better Way

It doesn't take a room full of web-savvy thinkers to come up with a great plan for the Commission's site as the way forward is obvious in many respects. We were pleased to see that the commenters on the original blog posts have thought of many of the same avenues (and even a few that we didn't touch on), so I highly recommend a read through them as well. Our thoughts, in no specific order:

Site Features and Functionality

• Trip planner
  • This one is a no-brainer: give us a tool to figure out the easiest way to get there and we'll ride more often. It's not a very original idea either; a quick perusal of Transit Authority sites will provide a dizzying tour of Trip Planners. Some pretty decent examples:
    • Bay Area
    • Hopstop for NYC, Boston, Chicago, San Francisco, and Washington
    • London
    • Mississauga
    • Ottawa
    • San Diego
    • Vancouver
  • Google has built a pretty fantastic Trip Planner for Transit on top of their already swell Google Maps: Google Transit. It's meant to be used by Transit Authorities all over the world to provide planning tools for their riders, and it currently provides coverage for nine US cities including Portland (the first city covered), and Seattle. The TTC and Google have been in talks for some time (see The TTC and Google on Spacing Wire from March 2006), though nothing has come of it yet. According to the Toronto Star article mentioned in that post, the Commission costed out its own route planner at $2 million, which sounds like a pretty expensive wheel re-invention to us! We'd like to see the TTC jump on the GT Bandwagon and publish the data in the Google Transit Feed format (see the API points below).
  • Any Planner they do build/use should make an effort to include other Transit Authorities in the area (e.g.: Go, Markham, etc.) in order to provide a seamless experience for the Great Transit Riders of the GTA.
  • Lots of people come to our fair city to visit and make their way around by transit, so it would be a great idea to include some bookmarked destinations and starting points to help them navigate more easily (e.g.: tourist spots, conference halls, shopping, hotels, etc.).
  • Although not required for the first version, mobile access would mean we could do trip planning on the go. Sure, the data rates from Rogers and Bell suck more than your average vampire, but it would give you one more reason to spring for that new iPhone you're all craving.
• Schedules and Route Maps
  • Easily printed route maps as PDFs (no more monolithic files with every route!). People like to carry schedules with them, so make handy-sized ones which we can print out and staple together to keep in our pockets. Better yet, offer schedules for download, pre-formatted for popular hand-held devices. It would also be great if you could add different schedules to a cart and have them packaged into a customized PDF that you could keep on your laptop or print out whenever it gets too dog-eared and weather worn.
  • Trip planners are great for "Get me from A to B" type foresight, but sometimes you just want to know what time the bus goes there and comes back here. The current site makes it fairly hard to find the first part and an exercise in repetition to get the second, so include a link to the opposite direction of travel on all schedules (e.g.: link to eastbound schedule on westbound page).
  • Consider changing the format of the schedules to something a bit more graphical and easy to follow. Nick Provart suggests a pretty good one (see here), an idea which we quite liked and seemed like an emergent de facto standard, but then again, just say Tufte and we're all ears (see pg. 46-47 of Envisioning Information for more information).
  • Each station in the system should have its own page, which can provide information (e.g.: washrooms, vendors/stores in the station, last/first train, bus connections, etc.) and could even be expanded to act as a hub for the community around the station (e.g.: upcoming neighbourhood events via RSS, etc.).
  • The TTC Timeline system was ahead of its time - a phone number for every stop with recorded schedule information - so far ahead, in fact, that it's one of the only real Y2K bugs that we know about. The system was shut down in late 1999 as it become evident that "...the TimeLine system is not Year 2000 compliant and because of the age of the system hardware and other factors, it cannot be upgraded in a cost-effective and timely fashion to allow for its continued use past December 31, 1999." (see TTC Report F591). We'd like to see a return of the Timeline, but this time as an SMS-based service which works by sending your stop ID to a TTC shortcode and getting a schedule update back. The same stop IDs can be used throughout the Schedules and Route maps to remain consistent across the whole system and to make it easy to get schedule info whenever you see an ID.
  • The City of Chicago is running an experimental, GPS-based bus tracker on their #20 line, which gives a hint of what a system like that could deliver. In addition to providing automated recordings of stop announcements on vehicles, it offers the tantalizing possibility of in-stop signage with updated arrival times (à la York Viva system), accurate web-based schedules and maps, and the promise of not having to stand in freezing rain with no streetcar in sight.
• Schedule Updates
  • Include a blog (with RSS feed!) of closures, schedule changes, etc. Use categories to indicate which type of service is being disrupted (e.g.: Subway, Bus, Streetcar) and/or areas of the city affected.
  • Although frequent transit users might get a chance to travel the length and breadth of the system, most of us just wear a groove into our favourite routes. General information about changes is important, but also build the system to allow users to register those routes and subscribe to updates and changes by email, SMS, and RSS.
• Ecommerce
  • It's 2007 and high time that the TTC boarded the eCommerce train! The Metropass Discount Plan is a great idea, but it would be substantially better if we could complete an online form to apply and provide a credit card number to pay for it. Faxing is so 1843 (no, really). There have been rumblings for a while now that the TTC will consolidate with other GTA Transit Authorities on a Smart Card for fares which would negate this, but that might still be a ways off (personally, we're hoping for something like the Octopus Card).
  • Partner with people who produce merchandise that we'll actually buy and build out a great online store to sell it in. We suggest starting with the Spacing station buttons and Torontoist T-shirts, but this city is jam packed with creatives who are just itching to submit their own designs. Take a cue from Threadless and crowdsource the designs to help support our arts scene. And please (please!) spare us the Legacy Sportswear gear which has been passing as Official TTC Merchandise. No offence to them - we're sure they do great work - but stamping the TTC logo onto a catalogue full of generic items isn't what we're looking for.
• Online trip booking for Wheel-Trans. Danny, in the comments on the Spacing original post, tells a horrible tale of trying to make a booking via the antiquated phone system. Wheel-Trans provides mobility to people who would otherwise not have it, and we'd like to see the service made even easier by a full web-integration.
• Multi-lingual Content beyond a pre-canned page of info. We live in one of the world's most multi-cultural cities, a fact that we love to trumpet, and the information on the TTC's website should reflect that. Here's another opportunity for crowdsourcing: post the info in English and provide a translation UI so the community can work its magic.
• TTC API (Application Programming Interface)
  • Open the walled garden and encourage the development of an ecosystem of user-created applications built on the TTC's data (routes, schedules, etc.). Our city is full of tech people who love whipping up new mashups and projects if you just give them the tools, so open the treasure chest and share the wealth. See this great Google Maps/TTC mashup as an example, built by Ian Stevens.
  • Use the Google Transit Feed format, which will likely become a de facto standard for transit data, but make sure its open and available to everyone. Build a system which requires an API key if control over bandwidth costs is a concern (like Google Maps, WordPress, and Flickr to name a few), or use a service like Amazon's S3 to host the feed.
• Build a Web Standards compliant website with no (or almost no Flash). See our blog post, All Flash = Bad, for an explanation on why building all Flash based websites is just asking for a flashtastrophe.
• Navigation
  • Navigation needs to move away from <select>s and into a more logical structure with more accessible controls.
  • URLs for pages should be logical in order to increase ease of navigation (e.g.: http://www.ttc.ca/metropass instead of http://www.toronto.ca/ttc/metropass_steps.htm). Human readable URLs are a great boon for people emailing links to each other, or for people looking through web traffic reports ("Great! 1,235 people visited the page showContent.php?id=27! Now which page is that?" vs. "Great! 1,235 people visited the page content/ttcwebsiteredesign!"). It's also a really good idea to hide the implementation of the site because it means you can more easily change your backend technology down the road without orphaning millions of bookmarks (e.g.: don't end your URLs in .html or .php, but use a feature like mod_rewrite to rewrite URLs from human readable to machine format, so http://www.ttc.ca/metropass/signup gets rewritten behind the scenes to http://www.ttc.ca/metropass/signup.jsp).
• Visual Design and Navigation
  • The People love the TTC font, so use it!
  • How about using some of those fantastic T.O. photobloggers TTC images?
  • Station pages should use their unique tile patterns as visual elements.

Process

• Despite our knowledge of websites and best practices, we weren't able to answer a central question which needs to be covered: who uses the site and what do they use it for? You can't do a good job of building a huge site which is optimized for everyone, but you can do a fantastic job of building highly optimized micro-sites which share designs and content. The City of Toronto does a pretty good job of splitting their content into four basic groups depending on what you want to do (Living in Toronto, Doing Business, Visiting Toronto, Accessing City Hall), and the colour coding makes it easy to keep track of where you are. Once the TTC has answered the central question, it's easier to break the site down into similar groupings and optimize the Information Architecture around goals (e.g.: Frequent Riders, Visiting Toronto, Selling to the TTC, etc.).
• We also ran into an obstacle establishing what the central goal for the website was, other than to provide information. Madhava has an excellent knowledge of the politics and history of the Commission and provided great insight into the fine balance between funding and ridership, which led us to discern that increasing ridership on suburban routes might be an important goal that the website could help to serve (particularly through schedule update subscriptions, SMS Stop Service, GPS tracking, etc.). That's a good start, but we would need more information to really finish a goals analysis.
• Building the site is only part of the battle; maintaining a site of this size and complexity in a healthy manner requires a team of dedicated personnel. The TTC needs to make sure that they build that cost into their budgets, whether the team be internal or outsourced (or some combination). Can we convince the TTC to try a radically different, non-centralized approach to managing the site? Perhaps we can marry the two halves of the brain and have a Community Ombudsperson oversee the marriage between the central authority of the Commission and a community of volunteer web managers and moderators. This doesn't need to go as far as a wiki (although it would be a very good approach!), but there are many happy mediums between a monologue and a full conversation.
• The Community is here to help! Despite what we perceived as an almost tangible antagonism between the Commission and its dedicated Ridership (see Withdraw anagram map lawsuit threat for an example), we still love the Red Rocket and we want to be part of the solution. Use us for our advice and skills and make sure that the process of building the new site is open and transparent. David likes to say that the "community is the framework", and that applies here just as much as it does there. We're riding a wave of new interest in our city and in the grassroots capabilities celebrated by initiatives like the Centre for Social Innovation, so sow some seeds and (to quote Guy Kawasaki intentionally misquoting Chairman Mao), let a thousand flowers bloom.

What's Next?

If you're still reading, we admire your persistence :) A few final thoughts on where we'd like to see this go from here:

• The TTC should re-open the RFP for the Website Redesign. The original RFP closed on Thursday, November 23, 2006 and received responses from a number of traditional web shops (you can find the RFP info by browsing the somewhat confusing and highly frame-based TTC Materials & Procurements site, or by going straight to the otherwise-framed P01DR06363). The Planned Award date is February 1st, 2007 (which recently changed from January 29th), but we think a strong case can be made for the requirements having changed substantial as a result of the change in Commission Chair and the process kicked off by Robert's post - strong enough that the original RFP should be replaced.
• The TTC should completely embrace the community. Soliciting feedback via blogs is a great start, but we'd like to see Adam Giambrone extend that initiative by keeping the rest of this process open and transparent (keep an eye on this space for a forthcoming announcement on this very topic). Collecting feedback in such a public fashion is an amazing step forward and we salute it wholeheartedly! Let's keep moving in the same direction.
• The TTC should set a goal of building the best Transit Authority website in the world. Our former Mayor, Mel Lastman, was perhaps overly found of calling Toronto a world-class city, but he was often right. Even the best Transit websites out there don't set the bar very high and we feel that this is an opportunity to demonstrate our technology and transit leadership by establishing a new watermark.

As always, we look forward to your comments! Help us help the TTC and everyone wins.