The existence of Office on the Mac platform has always been a bit of quandary for Microsoft. On the one hand, they sell a lot of copies and make a good chunk of revenue on it. On the other hand, they sell it to people who don't buy Windows (unless they're going to run it in Parallels or Fusion) and are therefore helping to support the existence of a platform which directly competes with two of their primary money makers (Windows and Office for Windows). There was actually a point in history, back in the dark days of 1997, when Microsoft invested $150m in Apple and pledged to continue to develop versions of Office (and InternetExplorer!) for Mac OS — a move which may well have saved Apple's bacon. Fast forward 10 years and we have a new release of Office, so what's changed?

On the surface, this is a great update. Lots of thought has gone into the UI, which resembles a Mac OS native version of the Ribbon seen in Office 2007 for Windows. It's Intel native, which makes it much faster on modern Macs than Office 2004 was (mostly because it's no longer running in the Rosetta emulation layer). What's not to like? Well, there's one thing. It's a small thing when you read it in a long list of changes, but when you actually stop to think about it, it's not such a little footnote.

Microsoft Office 2008 for Mac OS no longer supports Visual Basic for Applications Macros. VBA has been the standard Macro language for Office releases on both Mac OS and Windows for a long, long time and there are probably millions of Office documents out there that have embedded macros. I regularly use two such documents, an Excel spreadsheet which we built internally and which helps us calculate accurate estimates for clients, and a Word document which was provided to me for a project I'm working on and which I have to use to complete my work. Opening our Costing Workbook in Excel gives the following error dialog:

The first time it came up, I didn't read it properly and thought it was the old security warning that Excel used to give when opening a document with macros in it. It was only on the second pass that I realized what I was seeing: we will never be able to use our Costing Workbook again. This is a little more insidious in the project document I have to use, as it opens without a warning but none of the built-in functions and buttons do anything. Clicking on the "Learn more about macros and Office for Mac" shows a Help window with the following contents:

Cause: Office 2008 for Mac cannot run Visual Basic macros or load add-ins that contain Visual Basic macros.
    Solution: Keep the macro in the file.
    Solution: Remove the macro from the file.
    Solution: Save the macro in another macro-enabled file format.
    Solution: Create a new macro by using AppleScript.

The first three are just solutions which allow you to keep the macros from getting destroyed when the file is saved in Office 2008 format. The last one is the real kicker: the only actual solution is to recreate your macros in AppleScript format. Kudos to Microsoft for beefing up AppleScript support for the suite (and it does look pretty thorough), but what they're basically saying is that you can no longer interop with your Windows colleagues and you have to recreate any macros you had in a completely new language. You may find yourself scratching your head at this point, much as I was when I made this discovery. Why would they do such a seemingly stupid thing? Erik Schwiebert ("Schwieb"), a member of the Mac team, explains in an excellent blog post Saying Goodbye to Visual Basic (have I mentioned how much I love Microsoft's approach to corporate blogging? No? It's awesome. Everyone should learn from them). I completely sympathize with Erik's description of their plight and I agree that a two year delay would have been unacceptable, but I also think this decisions has some very serious consequences for Apple's potential in the corporate market.

We basically run Office only because our clients do. If we had our choice, we'd probably run Pages for word processing, we would definitely run Keynote for presentations (and I use it for any of mine already), and would be stumped to replace Excel (Numbers is a nice start but it's a long way from ready). If we felt that there were other applications out there which would flawlessly handle our clients' documents, we'd probably switch today (we've tried NeoOffice and OpenOffice with mixed results — suggest alternatives in the comments). We're a small shop though, and we get to set our own IT direction. Many of our colleagues work in large organizations who have IT departments which have been actively hostile toward Macs until recently and have only just started to come around (if they have at all). A big reason for that change has been Office, since Mac users can work seamlessly with their Windows colleagues (particularly in an Exchange environment using Entourage). If you work in an organization large enough to have an IT department, there's a pretty good chance that your company has also got some complex documents with macros in them (likely in Excel, which sees a lot more scripting than Word). The very rock and hard place described by Erik is about to crush your chances of getting a Mac on your desk, since any new Mac will be Intel-based and any new license of Office will be 2008 and now you'll be back into no-interop land. I'm not the only one who finds this so disheartening: in an opinion piece published in Macworld way back in December 2006 (when Microsoft first announced that they were removing VBA support), Rob Griffiths said:

Microsoft Office isn'€™t among the apps that will run natively on Intel-based Macs, ”and it won't be until the latter half of 2007, according to media reports. But when it does ship, Office will apparently be missing a feature so vital to cross-platform compatibility that I believe it will be the beginning of the end for the Mac version of the productivity suite.

He also points to a thread on Ars Technica, which includes 3 pages of angry feedback from people who will be seriously affected by this decision. I feel for the Microsoft Mac Business Unit (MacBU) team members who had to make this decision, even though I'm sure that ditching VB's ten year old implementation was a weight off their shoulders. Unfortunately for me, and for many of you, it was really just a transfer of weight onto our shoulders.

So, if you're feeling that weight, MacTech Magazine published their Moving from Microsoft Office VBA to AppleScript: MacTech's Guide to Making the Transition guide in their April 2007 issue (which is now entirely available online), which I recommend as a fantastic starting point. I agree with their introduction in that there is an advantage for Mac users who take the time to learn AppleScript: it's the scripting language for the whole platform so you can easily build scripts which integrate Office into other apps, and you'll know how to script non-Office things as well. I actually do a fair bit of AppleScripting from time to time and have made some great little scripts (particularly Copy Path, which copies the path to the current Finder window onto the Clipboard), and I encourage Mac users with a programming bent to learn it. I'm just not sure you should be forced to do so in order to keep using your own documents.

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!

What a week it's been! Had I known that it was going to take me about 25 pages and 7,000 words to describe our trip, I never would have volunteered for this gig :) I hope you've enjoyed reading through this as much as I've enjoyed putting it together and that this information is of value to some of you out there. Today is the final post in this series and provides a blissfully short summary, so if you're only going to read one of the five posts, make it this one (although you'll miss the Ali G clip).

The New Microsoft (Again)

In Tuesday's post, I talked about how Microsoft is turning a new leaf and repositioning themselves as a design-focused organization. I touched on how there's a lot of new blood breathing life into the beast and how they are making massive investments into UX for high-risk products like Office 2007 and the Ribbon.  I covered the development of the NYT Reader application and how it carefully balances layout and readability issues with brand and content. These are both examples of the positive impact that design can have when factored into your process and a very elementary and basic level and I applauded Microsoft for their efforts. You can find out a little more about their new focus in the Microsoft Design Center website.

Design Matters (Maybe?)

In Wednesday's post, I provide the corollary in which I talked about how we saw an equal number of examples where design (and UX specifically) had not been taken into account. We looked at the Virtual Earth Windows Vista Gadget which violates the User Experience Guidelines for Gadgets, and at Expression Blend which seems to be aimed at the very broad demographic of 'designers' without much consideration as to who that might be specifically. And I managed to sneak in an Ali G clip about ice cream gloves that's still making me laugh a full 24 hours later.

Expression

In Thursday's post, I gave a review of the new Expression Studio suite, which includes the Web, Design, Blend, and Media products. I liked Web but wished for a Mac OS X version, thought Design was an Illustrator knock-off with the sole advantage of being able to handle XAML, felt that Blend would be a useful tool for us if we built Windows applications, and wished that Media provided the ability to easily work from shared catalogues.

Wrapping Up

It's been almost a month since our trip which has given me a fair bit of time to think about what we'd seen and heard. The last five days have really helped me to form some conclusions and I think, in the end, the experience was exactly what I expected it to be. It was an honour to be invited to participate and I hope that I have other opportunities to do the same with Microsoft and with other firms (though I might hold off on the epic blog post series after!). It's not often that you have an opportunity to peek inside the kimono of a big software company and to get a sense of what they're thinking and working on. Like it or not, almost all of us use their software every day of our lives and they have shaped our industry like no other force. I have a lot of respect for the Microsofties and this trip reinforced that they burn their torches with the same passion and strength of belief as our colleagues in the Open Source world.

Martin joked that I should end the series with a surprise announcement that Radiant Core was going to ditch our Macs and switch over to Windows and I really thought about it (the joke announcement, not the reverse-switch), but in the end I was worried that I'd have a revolt on my hands. The truth is that even after two days of learning about their products and plans, I still don't really get it. One of our fellow attendees, Gene Smith, commented that I was under-reporting the general scepticism in the room and I think he was right. Those of us in the industry, especially my fellow UX folk, have grown used to expecting little from Microsoft and being underwhelmed. The video which Microsoft produced as a study of their own bloated box design, entitled Microsoft re-designs the Microsoft iPod 2005 Package, was brilliant not only because it was funny but because it was true. Apple is smaller than Microsoft by several orders of magnitude and has a fraction of their cash reserves and market share, and yet they consistently lead their industry because Apple builds products which people love. We are victims of marketing as much as anything else, but Apple is cool and hip and now and Microsoft is increasingly becoming boring, square, and then. The Mac vs. PC ad campaign is winning people over, not because Macs are necessarily better at photos and video, but because people want to buy into the belief that they are. This is an important point: other than the XBOX 360, people don't tend to have an overwhelmingly positive emotional response to Microsoft's products and they don't inspire the unbridled want lust in the way that only the iPhone can. At the end of the day, we run our business on Mac OS X and Apple hardware because it is easier to use, because it just works when we need it to, and because we have far fewer issues and tech support calls than we ever did running Windows. I started this series off by saying that I was no longer the Jobs worshipping, Apple flag waving fan boy that I used to be and that's definitely true. This conclusion isn't an attempt to sell you on making a switch or on how clever we are for our platform decision, though it would have been in days of yore. Bear with me for a moment while I bring us around to the final thoughts.

We believe in Open in all of its forms. We use an operating system which is built on top of an Open Source kernel (Mac OS X runs on top of the Darwin kernel which Apple released in 2000 under the Apple Public Source License). We run an Open Source web browser which we helped to develop (Mozilla Firefox is released under the Mozilla Public License). We currently build our software on a stack which rests on the most popular web server in the world (Apache is released under the Apache License Version 2.0), includes an Open Source Java Application Server (Tomcat is also part of the Apache project) and an Open Source database (MySQL is released under the GNU General Public License). We write our software in a (mostly) Open Source language (Java was recently released under the GNU GPL Version 2) and develop in an Open Source development environment (Eclipse started life as an IBM project and is released under the Eclipse Public License). We are very active members of the BarCamp community in Toronto and around the world and we dedicate a fair portion of our time to promoting the adoption of Open outside of our industry by organizing events like TransitCamp. We believe so strongly in this movement that we are exploring the possibility of releasing Foundation, our Website Management Platform, under an Open Source License before the end of 2007.

Microsoft is typically held up as the counter-example to the Open Source world in that their business practises in the past have been very closed, proprietary, and predatory. The decision to make Expression Web speak standard XHTML is a very good one and the right thing to do, but it's tempered by the decision to build the Expression Suite on XAML, a proprietary file format published for use by the public. They occupy a strange position in the technology universe, balanced on both sides of a dichotomy in which their Research labs are building some of the most innovative software in the world and yet their product divisions build products which engender little interest from consumers (Zune) or fall short of expectations (Vista). There are rumbles out there that say Microsoft has lost their mojo and are becoming less and less relevant in a world which is focused on the web and which is starting to show a stronger and stronger interest in the value of capital-D Design (led by companies like Apple, Oxo, and Target just to name a few). I think there's some truth to those suspicions and you don't need a richter scale to measure them: just compare the worldwide festivities of the Windows 95 or XP launches to the downright mellow and uninspiring "The Wow is Now" campaign for Vista. Other than the work coming out of the Research labs and XBOX teams, Microsoft is not an innovative company. I had this conversation with a few of my fellow attendees over drinks and the best examples they could come up with to defend innovation at MS were in the data warehousing field. I didn't argue - and I'm sure they're important to Data Warehousers - but that's not much of a defence. Focusing on design is a good move (even if it is playing catch up) but it needs to be a move which starts at the very top of the organization and which inspires everyone to take part. What we were shown during our visit was a great beginning and time will tell where it leads, but given that they are a technology company driven forward by the development of technology, I suspect that it will fall short if the hardcore developers within the company don't buy into it. Bill Gates is worshipped within the organization as the Alpha Geek and his Internet Tidal Wave memo successfully mobilized Microsoft to make an enormous course change in 1995 - where's the Design Tsunami equivalent?

That's it for Day 5 and the Microsoft Trip Report series! Subscribe to our RSS feed to make sure that you don't miss out on future insights from the Radiant Core.

Today we take a look at Expression Studio,  billed as:

Better Designer Tools for Better End-User Experiences

The suite includes tools for visual and web designers (Design and Web respectively), a media cataloguing tool (Media), and a cross-discipline Windows application development environment (Blend - mentioned in yesterday's post). If you haven't heard of it yet, it's only because most of them are still in Beta. Expect the hype machine to kick into action when the full suite is ready for purchase - until then, you can buy Expression Media, buy or try Expression Web, play with the RC1 (Release Candidate 1) release of Expression Blend, or play with the Beta1 release of Expression Design.

Express Yourself

Expression Suite is really interesting in some regards and business as usual in others. The tools share some common DNA with Visual Studio in that they're all part of the .NET 3.0 framework (forgive the occasionally incorrect terminology as we're not a Microsoft development shop - it may be more correct to say that they are built on the .NET 3.0 framework). With the exception of Media, they all communicate using a new XML-based markup language invented by Microsoft, called eXtensible Application Markup Language (XAML) (prounced zammel). The team behind Expression comes from a varied background of well-known players, including Silicon Beach (among many other things, makers of the awesome Dark Castle series of games), Avid, Adobe, Aldus, and Macromedia.

Our Expression day started off with a great intro by Angela Baxley, Product Manager (Expression), who stepped in for Erich Zocher, General Manager Tools (Expression), who couldn't make the morning. Despite her warnings about being new to the material, Angela did a great job presenting an overview of the platform based on one of the better PowerPoint decks we saw. As mentioned back on Day 2, her presentation saw a return of the equation Platform + Tools + Craft = UX, although in this case she was talking about the Platform + Tools piece while Darren was addressing the craft bit. Between Web and Blend (think ASP.NET and .NET Framework respectively) where the actual development work happens, the new platform provides the tools to build everything that a modern dev shop needs to produce.

The Value of Open Standards: XHTML vs. XAML

Most readers of our blog don't need a lecture on why web standards are important (for more information, see Web Standards on Wikipedia), nor do you need to be told that Microsoft has not exactly been known to embrace Open Standards in the past. Given that, you would presumably find yourselves equally as curious as I was to find out what was really meant by:

Expression Web is a professional design tool to create modern, standards-based sites which deliver superior quality on the Web.

Which really makes XAML all that much odder. David and I got in a debate with Arturo about whether XAML was actually an 'open standard', during which he confirmed that it was created at Microsoft and is controlled by them. By my books, that makes XAML a published file format rather than a standard and certainly not an open one by any means. This isn't a particularly new effort, as this handy Comparison of user interface markup languages tells us, and some of the projects go back ten years. We're familiar with a different XML-based approach called XUL (eXtensible User interface Language - pronounced zool as in the ancient Sumerian deity called Zuul, who you know from Ghostbusters). The cynic in me says that having Web do proper XHTML/CSS is an admission of defeat in the sense that Microsoft has been trying for years to  embrace and extend the HTML/CSS standards and maybe they've finally given up. Or maybe they got tired of people bashing the horrible HTML that came out of FrontPage and decided to fix it. Either way, standards support is almost always a good thing so yay! But then why not open up XAML or choose to contribute and work on one of the existing efforts? This is an important issue because anyone who choses to use Expression to build their applcations will be held hostage by the XAML file format and may have to make substantial changes to future versions of their software depending on what Micrsoft chooses to do with the format. Truly Open Standards are controlled by independent third parties who have (or at least appear to have) no particular bias towards any one firm and can therefore (theoretically) make decisions which drive the whole industry forward (e.g.: the W3 'owns' a number of standards including HTML and CSS). Maybe some of the Microsoft folks want to weigh in on this in the comments.

Expression Web

Web replaces FrontPage and is an effort to bring Microsoft's web design technology up to current levels by building a new application and environment rather than trying to fix the old stuff. It's designed to do HTML and XHTML, CSS formatting and code management, and XML/XLSTs, as well as to integrate closely with ASP.NET libraries for things like AJAX (via the AJAX Extensions). The demo was given by Wayne Smith, Senior Product Manager (Expression), who started with a really quick rundown of why standards are important:

1. Speed
2. Search Engine Indexing
3. Efficiency
4. Future Proofing the Web
5. It's professional!

We've spent more time cursing at InternetExplorer's lack of support for standards than most people will ever even spend in front of a browser, so this is a very welcome change in tune from the maker of the most popular browser in the world (though, I suppose, it remains to be seen how much the one hand talks to the other). I agree with all of Wayne's points here - we've been building standard compliant sites since we started the company because they just make more sense. In addition to the standards support, Web has a bunch of other great features:

• CSS Box Model: In 'design mode', the interface goes to great lengths to expose the box model (see BrainJar's CSS Positioning, or a neat-o 3D rendering by Jon Hicks). Wayne showed us how Web uses shaded borders to make the padding and margins more obvious, which you can kinda see at about 17:50 of this training video. Grab the 'crop marks' on the edge of any element to change the margin, or hold down shift and drag to change the padding.
• Style Application Mode: Web's Page Editor options allow you to toggle between having styles applied in either Auto Mode or Manual Mode, with Manual giving choices between inline, as classes in the head of this page, or as classes in an included document. You can also configure the Manual setting on different types of elements to behave differently (e.g.: apply h1...h6 styles inline but divs get styled in the included CSS).
• Multiple Doctype Support: Web supports proper doctype declarations for XHTML1.0 Transitional and Strict, which will affect the doctype output at the top of the page as well as the options in the IntelliSense code completion menus. Web also supports a Secondary Schema, consisting of various versions of InternetExplorer, which will be used to check code compatibility when rendering Quirks Mode pages.
• Style Manager: If you've ever used Word's Styles properly, then you're familiar with the way the Style Manager works. WYSIWYG previews of styles make it easy to pick the right text formatting and apply with a simple click.

Overall, I was really impressed with the product. If they ever released a version for Mac OS there's a good chance we might start using it internally (although it looked good, it didn't look good enough to run Parallels and Vista just to use it). If you're a Windows-based web shop, especially one that does ASP.NET work, you should take a look.

Expression Design

Arturo Toledo took over to show us Expression Design, a vector-based graphic design tool. I actually have no notes from his demo other than "Adobe Illustrator", which will tell you pretty much all you need to know. Challenging Adobe in this space is like trying to take them on in the Photoshop arena, which is ill-advised unless you're even bigger than they are and have mountains of cash. Which Microsoft happens to be and have. They may, in fact, be the only company out there who could reasonably stand a chance of taking any substantial market share away from the 800-pound gorrila. Right now I think you'll have a tough time ahead of you if you need to get your designers to try and switch over, unless the tools, keyboard shortcuts, and menu items mimick Illustrator pretty closely and your designers don't have to give up years of training and muscle memory. The biggest (only?) reason you would do this is to take advantage of the fact that Design can output XAML files to pull straight into Blend. That said, Mike Swanson (a Technical Evangelist with Microsoft) has released an Adobe Illustrator to XAML Export plugin with reasonably good support for the Illustrator feature set and better support coming soon (some of the unsupported features aren't available in Design or XAML), so yeah. Draw your own conclusions (get it? draw? ha!).

Expression Blend

In the same way that you can think of Web replacing FrontPage, Blend basically replaces VisualBasic. The primary intent for the Blend is to build Windows applications on the Windows Presentation Foundation (WPF). Arturo showed us a few demos of the kinds of things which Blend is intended for (the now defunct Microsoft Max project and the Avalon Patient Monitor specifically), which made for really cool looking interfaces with debatable practical value (like the now famous Jeff Han video). I'm always slightly suspicious of totally avant garde interfaces for medical applications which include snazzy animations and effects - when life-threatening decisions need to be made, I sure hope my doctor has to wade through flipping menus and rotating panels! - but it works very well as a proof of concept to show off how flexible Blend's toolset is. I was also slightly put off by Arturo's repeated statements that Blend finally lets you escape the tyranny of the boring gray button (and the Microsoft UX Guidelines) and map full motion video to your spinning control surfaces, which brought to mind thousands of horrendous Flashtastrophes (and one of my favourite Penny Arcade cartoons ever). At any rate, if we built Windows apps (or if WPF/E does become a potential competitor to Flash and gets widespread adoption as a browser plugin), it looks like a great environment for building interfaces. I think we, as a group, were a little confused about who it's being aimed at (see yesterday's post if you haven't already), but once we had sorted out their definition of 'designer', it all made sense. I was particularly impressed when Arturo pulled in an application that only its developer could love, built in Visual Studio, and then reskinned it without affecting the functionality (I grabbed two photos of the finished login and welcome screens). Going on personal experience, I have a suspicion that a lot of shops will end up using Blend by having their Dev team build off a spec and then having their UX/Visual team polish things, so it's great to see that the app works that way too.

Expression Media

Media is actually iView Media Pro, formerly made by iView Multimedia out of London, and acquired by Microsoft on June 27th, 2006, and is the only product in the Expression Suite which is available for Mac OS X. Media is a Digital Asset Management (DAM) Tool (which is fun to say - Dam Tool!), which basically sucks in all of your media in a whole littany of formats and then provides tagging and sorting capabilities. There's an important distinction in the DAM world between browsers (which just read the info available in the media files themselves - like EXIF data in JPEGs) and catalogues (which store their own meta data about the files and can therefore provide much easier and more efficient sorting). If you've used anything like Apple's iPhoto or Aperture, Adobe's Lightroom, or even Google's Picasa, you're familiar with the basics. Media goes further in that you can build up all kinds of ways of looking at photos, including adding custom fields (e.g.: a pro photographer might add price to track how much to charge for her images), and build collections for quick access (e.g.: all potentially good backgrounds in one area). It looked like an excellent media catalogue and something that we might make use of to store assets from different clients for easy retrieval by all of our Professional Services team members. There was some discussion about how much support was included for sharing the library files (could they be checked into a version control system? read of a network mount?) which I think was left open, so if any of the Microsoft folk know the answer, please feel free to leave a comment.

Final Expressions

I really had to work at putting myself in the mindset of a potential purchaser/user of the software since our Mac bias basically rules us out. Someone did ask Erich Zocher if there were plans to do Mac versions and there clearly aren't, which I think is a real shame. We spend a lot of time in the trenches of this industry and we're seeing more and more glowing Apples while we're down there - particularly amongst the digerati whose influence reaches far and wide

That's it for Day 4 - tune in tomorrow for the big wrap up!

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:

Alistair’s Key Awaited Feature List

Hurry Up and Wait

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!

I’ve installed the software on my Toshiba Tecra S1 laptop, and on my HP TC1100 tablet.  Both of these systems are a little underpowered for Vista, which means it runs a little slowly on them.  The Tecra is a 1.4Ghz Centrino system with 1.2 gigs of memory, and the TC1100 is a 1.4Ghz system with 1 gig of memory.