Tag Archives: microsoft

Will design save Microsoft?

MS ExpressionWell, I’m down in San Francisco for the Microsoft Expression Launch, and I’m intrigued. Not so much by Expression, which is promising, but not yet a slam-dunk, but mostly by the trend that’s developing in Redmond. Microsoft looks like it might be ready to get design.

Now, don’t get me wrong: We’re not there yet. At this point, there’s a lot of schizophrenia in the air. The speakers sound like Microsofties, geeky and technology-focused, but occasionally they say things that were obviously put in their mouths by designers. It’s tentative, it’s hesitant, it’s uncomfortable. I feel for these poor guys, trying to be loyal to the big Redmond machine and creative at the same time, which sounds like an oxymoron. I know their pain first-hand: I’ve been a UX guy in a geek company for five years, and it’s hard to be true to a user-centered philosophy without spitting in the soup. Same for them: They have to skirt the current reality (which is that Microsoft sucks at design) and it’s nerve-wracking. Kind of like being the Chinese minister for human rights, or an EPA official working for the Bush administration. You mean well, but it’s still doubtful that your boss is really committed.

Nonetheless, this is worlds away from what we’re used to seeing from Microsoft. Clearly, there are people there who go get it, and who are trying hard to get the point across. And the exciting part is that if they succeed, they could change the face of the Redmond Machine. I hope the old Microsoft realizes, soon, that It will take more than words, more than pretty graphics, to really get it. It will take a radical change in thinking, a major transformation. And Microsoft’s developer communities, its business and enterprise customer base, and its very own engineers, will likely all have to be brought into the change kicking and screaming.

But UX is the name of the game today. What tech can do doesn’t get anybody excited anymore, not as much as how it does it. Apple gets it. Adobe gets it. The Web 2.0 community gets it. Microsoft is trying to get it. If they do, they might own the next phase of the computer industry as much as they did the last. I’m certainly not sure that they can pull it off, but if they do, it will be very, very good. At this point, we’re still in the middle of the keynote speech, but I’ll be posting more on Expression itself soon. Stay tuned!

Lovable SharePoint Event

Over the last few months, I’ve been making a big splash around town with my latest crazy invention: Lovable Sharepoint. It’s a new service offering, that proposes to take a behemoth of a gas factory, Microsoft Office SharePoint Server, affectionately known as MOSS, and implement it in full-scale, gas-factory enterprise environments… with UX spearheading the effort. 

 

Title slide for LSP. Image by Peter Alexander.

Title slide for LSP. Image by Peter Alexander.

I’ve put together a presentation, most unlike the typical Microsoft-Gold-Partner Bullet Monster, consisting mostly of one image or word per slide. I’ve worked together a nice 30-minute speech, worked in some blocking and staging, and performed it, first at an INS sponsored event at the Microsoft offices in Denver. We had a full room, while most of these marketing events usually draw about ten people. I had set a single red rose, and my business card, at every seat. Warm breakfast was steaming at some tables in the back. Lights were dimmed a little.

 

It went very well. My friend Cliff Burton was opening for me, with a review of the MOSS feature set, and he was wonderful, turning this dry subject interesting with his deadpan self-deprecating humor. He rammed through the feature set in twenty minutes, connecting everything to what I would say next. He left the audience awake, in a good mood, and expecting more bullet points and clipart.

Then I went up, and I killed, man! I killed! 

I appealed to the grand vision of freedom and joy: enterprise transformation. I showed pictures of a peace march, and described adoption as a very passive-aggressive form of protest. How can we miss the mark so much, with such great intentions? I showed the tower of Pisa. I stressed that an intranet is a process, not a product, I described the user-driven process, the focus on goals, not tasks. Expanded it to a new vision where top-down and bottom-up feed off each other.

User-driven process, Goal-directed approach, Community focus.

I finished with a plea to approach this work with love. The lights came up and everyone was still awake. They were quite alert too. Hands shot up and I took questions, good pointed questions. Handshakes happened with our sales guys. Cards changed hands. I got some personal thanks and good-jobs. I also got the best set of speaker evaluations to date. And my sales guys were drooling at the leads. In the room were IT and Project managers for a large Christian charity, and I think the “love” message struck a chord.

I love it when that happens. When I can be passionate in a business setting, and the reaction I get. People are starved for authentic genuine passion, in the tech world, but it’s as necessary, if not more, as good requirements and functional specs.

MOSS envisioning engagement

The final site map

I’ve been sent to Los Angeles to help a CTO make a case, in one week, for a MOSS implementation. I approached the process with personas & goals, ethnographic interviews, and a usability-oriented review of their current systems. I also established a good rapport with the CTO, by listening to her business goals and inferring her personal goals. She wanted to shake things up, to streamline the bureaucratic machine while empowering the splinter groups, the internal startups that had developed in a vacuum of control. I can respect the wisdom of that approach, especially when dealing with the potential bureaucratic armageddon that can be unleashed with tools like SharePoint.

I applied my goal-directed approach to navigation, yielding a site map that provided a “Cathedral” area for corporate unity, and local, flexible “Bazaars” for the mavericks. We accommodated the security requirements of the compliance division, putting a key ally in our camp. In one week, we put together a solid plan, and the client invited me to help her present it to her boss.

It was a very quiet, subdued moment, after the chaos of trying to piece together a company in a few days. Just the company’s president, my client, and myself. He appreciated the potential for a healthy balance of corporate types and entrepreneurs, as well as the value of our plan. His questions afterwards were related to the logistics of making it happen. The dialog was productive, good decisions were made.

I head back to Denver, with another feather in my cap. The local sales guy is amazed at how calm our client seems to be. It’s not calm, dude. It’s focus!

Clinical Trials and Tribulations

A humanized flow diagramWorked on a whopper of a project, for Microsoft. My company was picked to help develop a “Solution Accelerator” for the Pharmaceuticals industry, providing a SharePoint implementation template for clinical trials, as well as some InfoPath data-gathering tools.

Clinical trials are enormously complex, regulated, and expensive. We focused on the protocol creation and approval process, which contains aspects of collaborative document authoring and workflow, regulatory submission and approval, etc. I had always thought enterprise software projects were big things, but taking a look at clinical trial protocols helped put that in perspective.

The challenge was to learn a lot very fast, in order to be able to add value. In about five weeks, we nailed down the realities of the process of protocol creation and submission, and I insisted we also focus on the context and goals of the different actors and stakeholders. I designed a nifty cast of characters, which we used in process diagrams to make the workflow come to life. They proved unexpectedly useful.

What happened is that the little sketch you see here helped everybody on the team stay on the same page in terms of user functionality. Developers working on a module could see the gal in the white lab coat and glasses using their module, and they made the interface precise and data-rich. UIs were markedly different, more verbose and action-oriented, for the suit-and-tie users.

I created countless flow diagrams, worked closely with developers to ensure all requirements were covered, and designed the SharePoint UI to host and unify it all. On a project of such scale and urgency, the difficulty was to not let user considerations get buried under the colossal weight of enormous and dense requirements. Tensions ran high, but we delivered, and the client was satisfied with the result.