This weblog started to log the making and release of a book. Well, the book is out and doing well - But what to do here now?

Here’s the plan:

Weekly short pieces on:

• Management, teams and leadership.
• The making of good things.
• Design, technology and creativity.
• Highlights from the pmclinic and uxclinic discussion lists.

Monthly pieces on:

• As new book projects come together I’ll be writing about them here, bringing you into the process.
• Longer essays once a month will be posted here along with other book news, meetups or tour dates.

And as always, if if you’re willing to post it, I’ll write about anything people ask for .

Cheers.

Posted in Plans and goals | 5 Comments »

I do a ton of public speaking and it never fails that wherever i go, regardless of the size of the venue, most of the front row will be empty. Even when the lecture hall is standing room only (should I be so lucky), many of the seats up front will be peopleless. In this photo you can see people standing, literally with their backs against the wall, instead of taking a seat in the front.

Now at a rock concert, or sporting event, people would sell their children to get a front row seat. The only time I had front row seats at a basketball game it cost me $300 and I had to watch two sucky teams: for good teams there were no front row seats available. The front row is usually the bees knees: what’s going on?

My theory is the following:

• We like the freedom to be bored. In the front, there’s nowhere to hide. If we want to nap, pick our nose, read e-mail, we can’t without feeling embarassed. If the speaker is bad, we’re stuck, for an hour or more, in living hell.
• We’re taught in school to go for the back. People in the front get called on by teachers. Most of us hated that, so we hide ourselves in the middle rows.
• We have low confidence in public speakers. We’re pretty sure it’s not going to be all that good, and we want the option to leave quickly without embarassing ourselves.

I suppose it’s a sign of a speaker with a good reputation when people confidently sit in the risky front row.

Posted in Teaching/Training | 10 Comments »

The author page in the back of The art of project management has this photo.

This represents a life goal: to write enough good books to fill the shelf. I’ve measured its width and according to my calculations I need to write 20-25 books to fill it. Since the artofpm took a year to write, working nearly full time at it, I expect to be working towards this goal for the rest of my life. I won’t publish anything I’m not proud of so I’m after quality too, not just volume. If I die with a half full shelf of good books, I’ll still be a happy man (as happy as a dead man can be).

I think this goal is as insane as you probably do - but when I quit Microsoft in 2003 I made a long list of possibilites: this was the least insane. Just like everything else, insanity is relative.

Writing forces many good things to happen for me: most interesting perhaps is that I have to confront my own bullshit. I can’t just complain about things I don’t like or handwave about how I’d make something better: instead I have to sit down and try to do it myself. And if I do it right, other people benefit from the effort.

I’ll be writing more on this blog about the goal and my approach. If this interests you let me know: if not I’ll keep most of it to myself :) Any encouragement is encouraged and thanks for reading so far.

Posted in On writing, Plans and goals | 5 Comments »

This week in the pm-clinic discussion forum: Topic #47 - Figuring out lessons to learn.

Here’s this week’s situation:

We just finished a 6 month project: or more precisely, the project finished us. We had many of the major things that can go wrong, go wrong: big schedule slips, low quality code, and upset customers. We did finally deliver work to the customer but no one was very happy about it. Since we use agile we’ll be continuing to do iterations on the same codebase after a short break.

At last Friday’s status meeting we talked for 20 minutes about what we can learn from last time. Nobody spoke up. Our well intentioned, but somewhat confused, group manager talked the whole time and made vague suggestions without commitments. I don’t expect to hear anything about it again. I’m afraid that the next project is going to be much like the previous one.

Does anyone ever take time to learn from the past? Who should lead the process? How long does should it take? Has anyone experienced a good post-project review?

Comment here or join the clinic.

Posted in Management, Software/Web development | No Comments »

Here’s a crazy idea: instead of trying to teach people by drowning them in books and materials, lets put them in the situations they’ll experience after college, while they’re in college. Crazy you say? Well Business schools have been doing this for a long time: it’s called the case method. Harvard Business school claims to be the originators of the idea, although I’ve come across the concept in various books on learning theory and teaching.

The challenge is that case or situational based learning requires different skills from professors and teachers. The teacher dominant model (think of your favorite grade school horror story), where there is one path of learning that the teacher defines, is easier to manage. But it’s controlled to the point where students contribute little to their own learning. And since it’s all tightly scripted, teachers are quickly bored by their own lesson plans.

CASE based teaching demands an interactive style, where discussion, interpretation and improvisation are primary to the experience. The teacher has to be able to intense classroom discussion of opinions and ideas, a skill many teachers don’t have (or are afraid to try and learn). It also demands a sense of incision and a point of view: something everyone has but many teachers are afraid to express.

Programming, design and management all benefit greatly from CASE based teaching, but it’s rare to see, even from professional trainers and consultants. And as far as colleges, many curriculums disapoint: even the senior projects rarely expose students to the challenges they’ll face after they leave school, and even fewer do it in a format worthy of their time.

Anyone have examples of CASE or situation based courses for managers, designers and programmers? Undegraduate or graduate?

Posted in Teaching/Training | 7 Comments »

I read about a book a week and most don’t stay in the front of my mind long. I finished this one a month ago and still find myself thinking about it.

The book Deep Survival: who lives, who dies and why, by Laurence Gonzales, asks the question: why do some people survive dangerous situations and other people don’t? The author spends most of his time telling riveting survival stories: plane crashes, mountain climbing accidents, people lost in the woods - they’re all page turners, but Gonzales also pulls out details to offer theories and hypotheses, most of which are relevant to daily life.

I finished the book in two sittings, enjoying the stories and his thoughts on psychology, training, intelligence and stoicism.

The nugget that I can’t get out of my head is this: people that survive abandon their mental models of the world and open their eyes. They don’t try to force the world to be a certain way: instead they respond to the world like a child, taking it to be what it is, and working within the real world to try and survive (or thrive).

Every day since i’ve read the book I’ve caught myself trying to force something and stopped myself, asking: am I seeing how I want the world to be, or I am I working within the world trying to make it how I want to be?

If you enjoyed Into thin air, or the film Touching the void, this book will add another level to your appreciation of those stories.

Posted in Book reviews, Management | 6 Comments »

The planning for part 2 of the book is winding down. There are still a few slots open, so if you have a venue or a suggestion for one, let me know. If anyone wants to meet up for a meal I can try to make that happen, just let me know.

10/11 - Boston (open)
10/12 - MIT Sloan school
10/12 - MIT CS department
10/13 - Open (Boston or NYC)
10 /14 - Razorfish, NYC
10/17 - Cooper Union, NYC
10/18 - Carnegie Mellon University, Pittsburgh

Updated dates and time are now here and will be updated here.

-Scott

Posted in On Tour | 7 Comments »

Ever wonder why so much of what’s made is so bad? Here’s some answers and advice on what to do about it. Includes two laws on suckage, the learning curve myth, the expectation gap and lots more.

Why software sucks

Posted in Design, Essays, Software/Web development | No Comments »

Someone kindly submitted my post to slashdot this morning, and it took the site down for awhile - apologies. The first two times I was slashdotted it didn’t generate anywhere near the traffic this one earned.

I wanted to clarify a few things:

• I left Microsoft in 2003 . I did work on IE for a long time (1.0 to 5.0), but the way the slashdot post was worded many assumed I’m still employed there: not true - I work on my own as a writer and consultant.
• There is a good parallel discusson on Asa’s blog. Asa works on Firefox and is one of the folks that deserves the praise for making an excellent piece of software. I responded to a few comments over there.
• Thanks for all the feedback and commentary. I doubt I’ll ever see this many comments for a single post again. It’s been fun - thanks for writing your opinions.
• On ui design. The mistake we’re all making, myself included, is focusing on designing for ourselves. Designing for ourselves isn’t a sin, but if the game you want to win is market share, you have to work very hard to make sure your needs and wants jive with people who’s needs are less sophisticated than ours (Which is most of the planet’s web browsing poulation). Lots of folks said “my mom can do X” or “my friends can do Y” as justifications of how their experience matches everyone elses, but I think we’d all agree how fragile and anecdotal those claims are. Your mom might be a rocket scientist, and your friend might have watched you do whatever it is before they tried to do it themselves. I’m not saying I’m right, you’re wrong, or that your pants are on fire. Instead I’m saying that design arguments, ui design arguments in particular, can and should stand on firmer ground. There should be an essay somewhere called “how to have a meaningful UI design argument” (finger on nose).
• On history trails, tabs and new windows. Folks pointed out at least a half dozen different ways both new windows and tabs are used. My stated opinion was narrow: apologies. But the concerns still strike me as valid (tabs make back/forward more complex, since there are now N history trails per browser window). I’ll need some time to read through all this, do some sketching, and rethink my stance.
• On open source and design decisions. In digesting all of this, my primary thought is “how does each of these opinions/complaints/usage patterns, as diverse and sometime contradictory as they are, fold together into shaping a single design that’s of the greatest value to the most people.” I’m familiar with the extensions and how the community encourages people to modify, create and involve themselves, which rocks. It’s an innovation pool for ideas that can be considered for the core (Some might recall the Win95 and IE powertoys, it wasn’t community based, but the idea was similiar). But I flinch at using extensions as the copout to challenges to the basic design. It’s a great plan B, but as a designer, for core parts of the experience, the obligation is to dig deep enough that plan A stands tall on its own. I’m not suggesting anyone said otherwise: I just wanted to make sure we’re on the same page. It’s surprising how few mainstream users, of anything, customize. All the data I’ve ever in my career (web,software, etc.) is on the order of 10-30%, and that 10-30% correlates with advanced, savvy, early adopter, industry types: e.g. most of you reading this. I posit that most people, for most things in life, live with the defaults (I mean this about software and life in general).

I’m still reading through all the comments, so keep them coming. I can’t promise to respond to all of it (150 comments and counting, plus e-mail) but I do promise to read them all.

Cheers.

Posted in Design, web browsers | 52 Comments »

Spoke this evening at the Seattle PMI chapter - Great crowd of around 200 people. If you were there, thanks for coming.

As promised here are the slides: What to do when things go wrong.

And if you missed it, here’s the audio from a similiar presentation (73MB, ~90 minutes) of this talk at baychi from May ‘05.

Posted in On Tour | 1 Comment »

It’s a sad day and a good day. For years I’ve held onto my IE install out of love. I worked on IE 1.0 thru 5.0, and was one of the people that designed much of its UI. But my love for the past has faded. Last week I switched to Firefox: and I’ve been happy.

Why I switched:

1. IE is a ghetto. There are specs I wrote for UI features in 1998 that are unchanged today, 7 years later, in a world where browser usage has changed dramatically. I’ve watched bugs that I fought to have fixed in 5.0 become regressions, appearing in 5.01 and surviving in 6.0. Even though it’s the product I was proudest of, using it now makes me sad - it’s been left behind. I do read the IE blog now and again - smart folks are working - but there’s nothing for me to install.
2. Bookmarks work. The Favorites UI model in IE is the same one we built in 1997, when we knew most of our users had 20-40 favorites. It was made to be super simple and consumer friendly as most of the population was still new to the net. This UI is effectively broken today, designed for people that don’t exist. The Favorites menu and Favorites bar show links in different orders, the organize favorites dialog is just weird, multiselect doesn’t work: favorites is a sad forgotten place. This was by far my greatest frustration with IE, even though I’m responsible for much of the original design.
3. Firefox has quality & polish. IE 5.0, for its time (1999), was a high quality release. Really, it was. Joe Peterson, Hadi Partovi and Chris Jones fought hard to give the team time to do lots of fit and finish work. We did fewer features and focused hard on quality and refinement. Firefox feels to me like what IE 6.0 should have been (or what i expected it to be after I left the team in ‘99). It picked a few spots to build new features (tabs), focused on quality and refinement, and paid attention to making the things used most, work best. The core UI design is very similiar to IE5: History/Favorites bars, progress UI, toolbars, but its all smooth, reliable and clean.
4. They made a mainstream product. One of the big challenges in designing software is balancing the requests of earlier adopters in the community, with the needs of the majority of more mainstream users. After playing with mozilla on and off I was afraid firefox would be a built for programmers by programmers type experience. It’s not. I don’t know who in the firefox org was the gatekeeper on features and UI, but I’d like to meet him/her/them (seriously). They did a great job of keeping the user experience focused on the core tasks. If you’re reading please say hi.
5. Security isn’t annoying. . The press makes security into such a huge deal, but I’ll be honest. I don’t want to think about security at all. I’ll do what I need to, but mostly I want the system to take care of it and stay out my face. Nothing in FF makes me feel safer explicitly, I just don’t deal with as many warnings, settings and other details. I know from the PR that security in FF is better (even if only because it’s less targeted by spyware, etc.) but I’m pleased that the product doesn’t remind me of how safe I am all the time.

Problems with Firefox:

I’m a UI design guy, so many of these are UI related. (Added note: I’d used FF on and off, but since I’m now 100% some of these are complaints might fade in a month of usage. Stay tuned).

1. Find UI. Why does the find dialog appear at the bottom of the screen? I agree that a dialog box (semi-modal) can be a mistake if you’re doing multiple searches, but flipping a coin for placement (top vs. bottom), the top is a better choice for any UI, especially if it’s going to look and act like a toolbar. I can’t move it so it earns a spot on this list. However, the overall implementation isn’t circa 1992 like the IE one. It highlights, it searches on type, & it warns on unfound items - nice..
2. Download UI. Here’s a case where modeless makes sense (it’s never my primary user task), but here we get a dialog box. My first crack at this would be a one line toolbar, much like the find bar, at the bottom of the screen telling me about downloads. That’s where all the other dl status info goes. Again, despite my nits, it’s an improvement on the ancient IE implementation (which we all hated forever too).
3. Tabs and new windows. Firefox goes against IE behavior and starts each browser instance from scratch. IE intentionally brings the browser history into the new window: the bet being that users who want to continue from where they left off can, and those that want to go their home page can do that with one click. Everytime I hit Cntr-T and see a blank screen I think I’m in Word. I use tabs less often than I expected: opening new windows is often more comfortable - easier to track which window lives where. With multiple tabs (I find) the back/forward behavior becomes complex and hard to predict. Strict UI logic would put the tab UI above the toolbars, not below, but that creates other problems.
   
4. Tabs and modality. The desired illusion of tabs should be to make each tab a virtual browser. Well this breaks when you bring up a modal dialog within a tab: you can’t switch to another tab. It’s an annoyance, not a sin, but when it happens it reinforces my new window habit, and slaps my wrist on my growing New tab habit.
5. The return of the go menu. It was with great pride that we killed the go menu in IE 5.0. It was the stupidest menu I’d ever seen, since it was never used and no one knew what it did. For accessibility it was necessary, but had no rights to be a top level menu (IE has View.Go). The Go menu was probably inherited from NSCP/mozilla, but it really should be put out to pasture. And if it stays, someone needs to explain why it shows a different history list than the one in the back button drop down.

For reference: I wrote about principles of browser design here: How to build a better browser.

(Update: I’ve responded to many of the comments in a second post.)

Posted in Design, web browsers | 307 Comments »

This week in the pm-clinic discussion forum: Topic #45 - Managing up to executives. This week’s situation comes from a web development veteran in a new organization.

I am an experienced web development manager: I’ve shipped a few things and have managed people for years. I’m in a new organization now and I’m having a hard time with my VP and the folks that work directly for him (I don’t).

I’m used to having significant authority over my team and my areas. I’m used to being in the room as big decisions that will impact my team are made: I’m at least a party to the discussion, if not at the center of it. I realize my place but I expect my VP or his subordinates to recognize mine.

Now, in this organization, I’m not even in the game. I am dictated to, or given decisions to respond to well beyond the point I can possibly offer alternatives or make a stand. My direct manager is ok, but ineffective. He doesn’t see a problem with how our organization works.

Should I:

1) Suck it up. The results are ok/good even if the means aren’t. Maybe it’s my ego that’s the problem.
2) Go direct to the VP (skip manager) and state my case.
3) Get political. Should I become more aggressive in obtaining power, getting a little rougher in how I play ball, and work around my boss if necessary.
4) Leave. Find a place where my role is more like what I want.
5) ?

Posted in Management, Software/Web development | 1 Comment »