In the mid-80’s I took my second tech job, at a company called Silicon Graphics, Inc.
SGI, before it officially contracted its name to “SGI”, was a fantastic place to grow and learn. It was intense and focused, and my modest technical know-how in Unix, TCP/IP Networking, and Computer Hardware matched well as the company grew its Unix workstation business and more customers connected computers to Internet Protocol networks. I was soon a main contact point for the most intractable problems from customers, and the Customer Support representative to new product introductions.
The focus and intensity made for arguments, some that probably would seem to outsiders as knock-down, drag-out fights. But a friend from those days put it well when he said, “We fight with each other, but we fight to make a great product.”
If I came to engineering with a problem and hadn’t done my homework, didn’t have a good handle on what was happening and why, and hadn’t collected useful information from the customer, the criticism was withering. One networking engineer, who I consider an important early mentor, was especially tough. But once I learned to do my research and bring him useful information on real problems, he was very responsive and engaged, helping me pull in other engineers on really complex cases.
My team worked with real customers every day. We had an understanding of how real customers used these computers, and the real environments they were in — the networks, the labs, and the variety of configurations, and why a problem that some might consider a minor annoyance was actually a major disruption for another customer. But often it was difficult to produce clear data supporting our insights. By the time the data was clear, the problem was too big, or at least much more expensive to fix.
This was especially the case in new product introductions. Even down to the question, “Is this ready to ship?”, we were there, contributing to the decision and wielding a rarely used veto. These arguments were often heated, but the Product Managers and Marketing and Sales Execs came to know that our concerns should be considered, even on apparently light evidence. And we knew that a big part of our job in new product intro’s was to ensure that we never needed to use that veto.
It was an environment where you were expected to know your stuff, whether on technical topics or in business. And even if you had a reputation for knowing your stuff, you would get challenged, and you had to fight it out.
As Silicon Graphics grew, it became known as the place the best people all wanted to work. Not because of that original espresso machine that Jim Clark bought for the engineering team, but because of our reputation for excellence in every part of the company.
But as the growth started to accelerate in the early 90’s, things changed. Instead of arguments about making our products and services better, about serving customers, fixing problems and getting things done, the fights became political. Which VP was supporting that position? Who are you? Whose budget is this going to come out of? In-fighting between divisions and groups and backstabbing and office politics grew. SGI had become a “big company.”
Many great people left, but many stuck around. Even if you were unhappy, the growth made it easy to find something new and interesting to do.
But the necrosis had set in.
We were no longer focused on building great products and changing the world. We were fighting the wrong fights.
Building a great product (or service) is never easy. Tough decisions must be made, and among smart, motivated people, coming from differing experience and perspectives, that’s going to cause arguments. And even in the best teams, sometimes the argument will go too far, or stray into personal attacks, or involve some back-channel politicking. And learning to develop an idea and gather support for it is critical to getting anything done in a large organization.
You have to keep bringing everyone back to the point: To make a great product.
(IIW)[http://www.internetidentityworkshop.com] uses the (Open Space Technology)[https://en.wikipedia.org/wiki/Open_Space_Technology] process for self-organizing the conference. The importance of all of this is often unclear to the newcomer, but people come around, as they come to understand that there rules generate a conference that works much like the hallways and bars in traditional conferences. The whole thing becomes a great swirling stew of fascinating interlocking conversations, and real work comes out of it.
This starts with four principles:
1. Whoever comes are the right people. These people came to this session because they wanted to be here. The mix of opinions, ideas, and questions that result are exactly what we are hoping for.
2. Whatever happens is the only thing that could have. These sessions are generative. What happens is not always what you thought might happen, but that’s ok! Let go of your expectations and enjoy the flow of ideas.
3. Whenever it starts is the right time. Start on time, even if you are expecting more people. Someone may join mid-way through, and that’s ok.
4. Whenever it’s over it’s over. We give over the space to the next sessions on time. If you are still in the middle of a great conversation, move somewhere, or schedule a follow-up. If the conversation is over, or the part that interests you is done, then you may leave.
Plus, the important Law of Two Feet:
You have both Mobility and Responsibility! Move around if you like. if a conversation isn’t interesting, just move. It’s common that there is several interesting sessions at the same time slot — move around, sample and enjoy.
Book of Proceedings:
Every IIW generates a Book of Proceedings, containing the notes from every session. it’s important that someone at each session takes notes. There is a simple, standard format for the notes, to include the sessions number, location, convener, title and note-taker.
See also: (IIW Wiki)[http://iiw.idcommons.net/Main_Page] and (IIW Session Notes Format)[http://iiw.idcommons.net/Note_Form]
Internet Identity Workshop is my favorite conference. The topics covered, which span across Identity, Privacy, Community, and Security and more, continue to be relevant even after more than a decade. The “Open Spaces” format generates lively discussions across a range of topics, all created on the spot by the participants.
It’s also a conference full of friends who I’ve come to know over the years. I’ve already had a couple quick “catch-up” conversations and looking forward to more.
I had an interesting discussion this weekend about computers and devices and Internet of Things. I’m still sorting out how exactly to articulate this, and then this morning this great example from Marco Arment came to my news feed:
It’s unwise and futile to try to shove iPhone interfaces and paradigms into the Apple Watch. Instead, design for what the Watch really is.
All these devices are testing the creativity and interaction concepts of designers and developers. Whether it’s the Apple Watch, some new “Internet of Things” device, or even something as straightforward, but polarizing, as the new Apple MacBook, Thinking about what the thing is for, and understanding the subtle ways that people will use the new thing — that’s where the magic happens.
Read Marco’s post about his app. The specific are interesting, and the more general lessons essential.
My old turntable may be back in action soon.
I roped my friend Cliff into giving me a hand figuring out how to repair the cracked and wobbling plastic drive belt pulley. It doubles as a strobe indicator, so repairing it is best. This turntable is a somewhat rare thing from the 70’s. Some parts are still available, but not this strobe pulley.
I think Cliff’s repair job is going to work. Here are a couple photos…
You can see the cracked plastic in the close-up picture above. Cliff cut a copper tube for the inner post sleeve, glued in the shards of the original part, and then packed it all in a special epoxy modeling clay. the larger outercopper tube then adds structure and also cut away a bit of excess clay.
Here is what it will look like in position, shown here with the drive belt pulled aside, since the strobe pulley repair is not yet set. it spins freely with no discernible wobble. I think this is going to work!
I took a break this afternoon while my old friend Cliff was here with his kids. Cliff and I fiddled with the repair project on my old turntable (more about that later) while the kids played my piano and guitar and took some photos of the horses.
Yesterday was the day that John Gruber, one of my favorite tech writers, calls “Internet Jackass Day”. But among all the stupidity and annoyance are some gems. My favorite? This one, by the scientists at CERN:
You really have to read it. Love the coffee photo!
I’m looking forward to the new book about Steve Jobs, coming in a few weeks. The Isaacson book was a disappointment, and this one seems (by reports) to do a much better job of capturing the man and the complexity of his story. As Tim Cook says in an interview with Fast Company:
II thought the [Walter] Isaacson book did him a tremendous disservice. It was just a rehash of a bunch of stuff that had already been written, and focused on small parts of his personality. You get the feeling that [Steve’s] a greedy, selfish egomaniac. It didn’t capture the person.
Read the whole article. Just this short piece gives a deeper view of the man.