Showing posts with label Management. Show all posts
Showing posts with label Management. Show all posts

2006-07-30

Screw up ...

Major screwup at Airbus - BusinessWeek Online - MSNBC.com:
Fear factor: Yet others say the situation is no surprise, because Airbus's corporate culture openly discourages employees from alerting managers to potential problems. 'If you tell them bad news, they simply don't listen,' says Andrew Walker, a former top engineer at the factory in Broughton, Wales, where the A380's wings are built. 'No one dares tell a high executive that something isn't possible, because he risks losing his job,' says a local union leader at the Toulouse factory who asked for anonymity.


*Sigh*. I've been there.

Me: "We have a big problem."

Them: "Shut up and quit being so negative."

*Sigh*.

One great thing about listenig to people's work-related problems all day is that sometimes you notice a pattern that wouldn't otherwise be apparent.

And then you can fix it!

Or sometimes you notice a way to fix about five problems at once!

Efficiency! Cool!

© 2006 Stephen Clarke-Willson - All Rights Reserved.

2006-07-17

Great Hackers

Great Hackers:
When you decide what infrastructure to use for a project, you're not just making a technical decision. You're also making a social decision, and this may be the more important of the two. For example, if your company wants to write some software, it might seem a prudent choice to write it in Java. But when you choose a language, you're also choosing a community. The programmers you'll be able to hire to work on a Java project won't be as smart as the ones you could get to work on a project written in Python. And the quality of your hackers probably matters more than the language you choose. Though, frankly, the fact that good hackers prefer Python to Java should tell you something about the relative merits of those languages.


There are too many great paragraphs in this article for me to quote them all. You really should read it.

I'm not sure I agree with everything 100% but it would be pretty dang close.

2006-06-16

Joel on Software - Bill Gates Reviews Joel's Excel Spec

Joel on Software:
Watching non-programmers trying to run software companies is like watching someone who doesn't know how to surf trying to surf.

"It's ok! I have great advisors standing on the shore telling me what to do!" they say, and then fall off the board, again and again.


Joel on Software ... he says it all for me.

2006-05-18

EALA's Neil Young

GameDaily BIZ: Interview: EALA's Neil Young:
"BIZ: So let's talk a bit about the quality of life issue. Ever since the whole EA Spouse blog post EA has been criticized for quality of life issues. Recently, however, the company settled with its former employees and I hear now that you've really cut back crunch time with something called '5 great days.' Can you talk about how this was enabled and what it means for the workers?

NY: Well the basic underlying idea sort of stems back to that concept of creating intellectual property. Right, so crunch, managed crunch if you like, is built around maximizing execution productivity. And what you really want to do, is you want to maximize creative productivity. You want to create the type of environment where people have the best ideas, you know the first time, instead of a mediocre idea because they're tired and they then have to iterate 9 or 10 times to an OK idea. All of this, '5 great days,' is really just one system with a catchy name. But the whole idea is let's take, in the case of the studio in Los Angeles, which is the studio I run, let's completely rewire the culture. And if you believe that the work is a product of the culture, then the question to ask yourself is, 'What are the things that we need to change in order to deliver a culture that can consistently produce great work?'

And that's about the tone that the management team sets, the talent that you have in your organization and how you work with that talent and how you treat that talent, and you know, the practices that you have in place to be able to move those creative ideas through your organization. And so, really, speaking for Los Angeles, that's really what we've been focused on and I think over the course of the next few years you'll see the results of that and I can tell you that."


Neil Young used to 'work for me' at Virgin. I put 'work for me' in quotes because people like Neil Young and Dave Perry don't really ever 'work for you'. They are genuine self-starters and so the best idea is to create an environment where they can work and then let them go. I also believe in the inverted pyramid view of management - management exists to provide services to the people that do all the work. So in a way it's more accurate to say I worked for Neil and Dave and everyone else in development at Virgin Interactive. In fact, I had the view that Virgin Interactive provided a publishing service to developers. This is definitely in contrast to how most publishers view developers. Most publishers feel that developers are the ones providing the service, which makes sense, since that is the way the cash flows. But I digress.

One thing that Neil did that I really admired was the game Majestic. It was a flop commercially but I was really impressed the way that Neil went out on a limb creatively and technically with that game. I think that modern cell phones have matured to the point where the entire game (which had streaming video and phone numbers you dialed and got clues and things like that) could be played on just the phone. All of the browsing and video and obviously the phone calls could be done by cell phone. The fax portion of Majestic could be converted to text messaging. I think it would be cool if someone resurrected the assets for that game and made it work on modern fancy cell phones.

One thing about Majestic was that it did a pretty good job of making a fake world integrate with the real world, sort of the way Lost (the TV show) is doing with the Hanso Foundation.

On 9/11, 2001, I awoke to find an email in my inbox that one of the World Trade Center towers was on fire. Later I got another email about the second tower being on fire. As I was a beta tester for Majestic I thought these emails were part of the game! Later I received another email about the first tower collapsing and I paid more attention and I realized that these messages were from the alert service I subscribed to from the NY Times. Like everyone else, I instantly ran down and watched the disaster on TV all day.

However, the impact of thinking that the horrible events of 9/11 were fictitious was pretty astounding. (After all, who could have imagined it happening in real life?)

Anyway, I think Neil is really having a positive impact on EALA, which has to be one of the most difficult assignments in the world. Hollywood doesn't 'get' games in general (Spielberg might be an exception) and hiring people who have worked on visual effects to work on games is highly problematic, which is going to be the likely situation if you're located so close to Hollywood. On the other hand if you can integrate with the schizoid Hollywood environment (for instance, by clever use of contracting, which is fairly normal there), you can get a pretty good development engine going.

So good luck to Neil and EALA.


© 2006 Stephen Clarke-Willson - All Rights Reserved.

2006-04-22

Marketing?

It seems to me there are two views of marketing organizations. One view is that they exist to package and market whatever they are given and make it as successful as possible.

The other view is that they are supposed to be in touch with the market and therefore their input and even complete specification of what a product should be is considered paramount.

Either way, someone has to decide which products are made and for whom.

Sometimes, in smaller companies, that person is the founder(s).

Frequently (and certainly during the dot-com bubble) many product ideas were brought forth for which there was no market at all. Or a market existed for a free product but not a product that people would pay for.

Ultimately it is up to the person or organization that chooses which products to make to take credit for the success or failure of an enterprise.

© 2006 Stephen Clarke-Willson - All Rights Reserved.

2006-04-11

The Development Abstraction Layer - Joel on Software

The Development Abstraction Layer - Joel on Software: "Management's primary responsibility to create the illusion that a software company can be run by writing code, because that's what programmers do. And while it would be great to have programmers who are also great at sales, graphic design, system administration, and cooking, it's unrealistic. Like teaching a pig to sing, it wastes your time and it annoys the pig."

This is great. As a person who has created two reasonably large (not huge) software development organizations, I can tell you that what Joel says is true: the vast majority of people believe that organizations are they way they are because that's just the way they are. In fact, every organization is designed, either by default, in which case it is horrible, or by conscious design, where a productive supportive, almost invisible environment of productivity reigns.

Both of my organizations fell into disrepair after I left. That's because those that followed thought things were the way they were just because that's how things should naturally be. In fact, the development organization was something alive that needed to be fed and tuned and supported and gently reorganized as times changed. Without that care and feeding it spirals into a Dilbert comic strip.

I wish I knew how to make a software organization that would survive on its own but I don't. And I know some other successful "software organization architects" whose creations have fallen into disrepair.

As soon as the top-level management support beam that believes in nurturing and tuning and massaging the development organization is gone, the whole thing sinks.

What a bummer.

2005-11-20

Put employees first: Sir Richard Branson

Put employees first: Sir Richard Branson:
"Outlining the Virgin management mantra, Sir Richard said happy employees keep customers happy. A lot of happy customers would create a lot of happiness to shareholders as well. Without good people, corporations are worth nothing. And to motivate people, corporations should create a fun environment to work. Employees should feel that it is a crusade, not just another job. "

Some people think that servicing the needs of shareholders, employees, and customers is a balancing act, but Sir Richard says that's wrong. It's more of a dependency graph: happy shareholders need a company with happy customers which are created by happy employees.

I know a company that puts customers first, and it has had 50% turnover in the last couple of years. Amazing.

2005-09-21

Mini-Microsoft

Mini-Microsoft



This "Mini-Microsoft" blog is a strange blog. If I were younger I would agree with everything he says. But since I am older and wiser I don't.



I agree that the Microsoft review system is bad.



I don't agree that executives at Microsoft shouldn't get paid a million dollars a year. I think they should.



I agree that Microsoft used to have a different culture. It was smaller.



As things get big, the abstractions that managers use to manage change radically. In fact, one might argue, the difference between a successful manager and an unsuccessful manager (besides people skills) is his or her ability to grab on to the right abstract representation of the business. Clearly, in a business like Microsoft, it is impossible for the execs to know all the details. It's just impossible!



What matters is that they understand the control points. And those control points might not be obvious to the underlings.



A really good manager will explain those control points in a way the troops can understand. But the number of managers that can do that is about five. And they aren't going to work at a really big company.



It's funny, because I'm more of a fan of Microsoft now than I was in the old days. I find the software less buggy and easier to use than it used to be. And the compatibility problems Microsoft faces are huge! And yet they create this eco-system for PC development that continues to thrive. That's amazing.





BozoBit

BozoBit:
"BozoBit

When you flip the Bozo Bit on someone, it means that you put them in the Bozo (the clown) category so you never take anything from them seriously again. This is a major step, not easily reversed. "


I had never heard of the Bozo Bit until a manager told me he thought I flipped it on people 'too soon.' (I thought a couple of years of evidence of uselessness was adequate but he basically never wanted me to flip it on this one particular person. Everyone knew this person was a Bozo except the manager.)

So, upon learning of this great concept of the Bozo Bit from the manager, I promptly flipped it on him, since he clearly had no idea who was doing what in the company.

2005-07-18

Harvard Business Review Online | Managing for Creativity

Harvard Business Review Online | Managing for Creativity

Although the press has played up the company’s 35-hour workweek, the truth is, employees often put in extra time to complete a project or fulfill a responsibility. But make no mistake: This is a far cry from some Silicon Valley start-up. The company actively discourages people from working 70-hour weeks. “After eight hours, you’re probably just adding bugs” is a company proverb, repeated often enough by the CEO and others that managers take it seriously. SAS encourages employees to disconnect from work for a time and then come back recharged. Creative people can be trusted to manage their own workloads; their inner drive to achieve, not to mention accountability among colleagues, compels a high level of productivity.

2005-07-13

I've been Terminated!


Stephen's actually a terminator!


The fact is I've terminated people and I've been terminated. It's a natural part of life in a capitalistic economy, especially if you are passionate about what you are doing. (Anyone pissed at me for firing them will be happy to know I've been fired two or three times myself. I think three times.)

I was laid off once, but hired back after a month with back pay. I was very young and that made me really nervous! I was very happy to get hired back.

My favorite firing was when I was fired for quiting. That was hilarious. (Well, the boss was pissed because he'd just given me a bonus a few days before, so I don't blame him too much for getting mad at me.)

Another time I was fired and the company gave me a check for $150,000.00. It turns out they had signed me to a contract a few months before and they had to pay off 100% of my brand new stock options which suddenly fully vested. I still have the check stub hanging on my wall as a reminder of the glories of capitalism.

I had to pay over $50,000.00 in taxes on that check. I wish I hadn't spent the rest of it. I should have given it to my wife to invest.

© 2005 Stephen Clarke-Willson - All Rights Reserved.

2005-05-30

Oblivio > Archives > Opportunities

Oblivio > Archives > Opportunities:
"Related: I once had a boss who refused to say the word problem. This was a technique he learned in a book on management. Whenever he wanted to say problem, he would say opportunity. At staff meetings he would talk at great length about all the opportunities the organization faced. However, since he still used the word opportunity to mean opportunity, you to had to figure out from context what he was talking about, a problem or an opportunity. Later he stopped using the word opportunity to mean problem, and would instead say challenge. Fortunately he wasn't the sort of person to ever talk about challenges, so this was much easier to decipher."

2005-02-11

Google Blogger Fired

It's not such a big deal that one guy was fired because he said too much about internal company stuff on his blog ... but it is a big deal that companies don't generally have blogging standards.

http://redcouch.typepad.com/weblog/2005/02/dinner_with_the.html
http://blog.outer-court.com/archive/2005-02-08-n55.html

An expansive communications policy is pretty important. Game companies, in particular, frequently encourage self-expression by allowing people to decorate their cubes in all kinds of crazy ways. It's easy for an employee to get the idea that such freedom extends in a bi-directional way to the outside world. In some companies that would be fine and in others it would not be fine.

It's all well and good to try to avoid bureacracy by having a minimal set of policies but the fact is people need and want direction and good management supplies it.

Nobody likes to be surprised.

© 2005 Stephen Clarke-Willson - All Rights Reserved.

2004-11-01

Plausible Shipability

Jon Mavor, who co-founded Adrenium Studios with me (actually, he was first, and then I and Jeff Petkau got involved), has come up with a cool term to help people decide when something is “done enough” to move onto the next stage of a project.



The problem with making a game is that there are a thousand things to do, at least, and if you spend too much time on one thing, then the other things never get done!



I have a saying I heard from a Microsoft guy who was working in Multimedia, who said he heard it from an old boss at Apple, which is this: “Shipping is a feature too.” (A Google search turned up a couple of references but nothing definite on who originated this term.)



So, in order to focus a team’s attention, Mavor came up with the idea of “Plausible Shipability,” which means, you can stop working on a feature if you can imagine the game could possibly ship with the feature in the state it is in.



After all, when the whole game is done, you can always go back and improve a few things - that is, if you didn't waste all your time on one single feature.



Louis Castle, founder of Westwood Studios, said once at a Game Developer Conference talk that the best way to improve a title is to find the five worst things about it and cut them! In terms of a “quality percentage”, this will improve the title the most, statistically speaking.



If you spend a long time on a feature that might ultimately get cut, then you’ve really wasted a lot of money.



So take Mavor’s advice and get as much of the game done as possible, so you can find out what works and what doesn’t work, and then cut the things that suck, and polish the things that matter the most.



And then ship the game.

2004-10-20

Vice President

I've been a Vice President of SomeKindOfDevelopment twice - one time I was responsible for about 180 people and the second time about 70 people.



Once the job grew beyond about 50 people I didn't like it as much as when it was small, so both times, instead of moving on to some kind of Better Vice President job I reverted to being an "individual contributer," as big corporations call worker bees.



I like being an "IC". I like making stuff. As a VP I would always be jealous of the ICs that were making all the products. The best thing about being VP was running around and seeing all the cool stuff that the ICs were making.



Sometimes I couldn't resist and I would poke my nose into making something, even though I wasn't an IC, and was supposed to just get ICs to do more work.* I performed the opening ragtime music for the SNES and Genesis versions of "The Jungle Book." For Demolition Man on 3DO, I coded up a thing that ran on SGI machines and read the digital output of a film scanner, which we used to get some cut scenes from the movie into the game.



At Adrenium, the build system was set up so I could check something out and tweak it! On Azurik I fixed a few engine bugs before some key milestones.



I like being an IC.



The hard part is switching back from VP to IC. This is hard for people to understand because it seems like a step back. Maybe it is for some people.



But not for me.





*People love the idea of a hands-on VP until they get one. The fact is, poking your nose into the IC's domain is risky - the ICs have ways of doing things and they don't like it when a potentially ignorant VP touches their stuff. The flip side of messing with people's stuff is that you get a genuine appreciation for how hard or easy their work is; my experience is that people really appreciate it if you know how hard their job is. I actually spent a lot more time messing with people's stuff than I indicated above - I would just screw with something and then never check it in, and the experience of fooling around with stuff helped me sanity check our work processes.



© 2004 Stephen Clarke-Willson - All Rights Reserved.



2004-09-13

Culling

I just read a startling article in IEEE Software (Sept/Oct 2004) called "Why Culling Software Colleagues is Popular", by Peter Middleton, Ho Woo Lee, and Shahruk A. Irani.



The article's main points are:

  • The staff likes it when you get rid of marginal performers; and
  • Managers don't like to do it.

A third interesting point was that

  • Erratic performers annoy their colleagues.

The article explains how Jack Welch as CEO of GE implemented a bell curve for giving out raises and forcing managers to let people go. I think Microsoft does this too. Anyway, Welch found it was hard to get his managers to implement the system, and of course, it got harder as time went on, because the curve moved up as the people at the lower end of the curve were let go.

The astounding thing was that the remaining staff loved it. The reason? Those who remained perceived that those who were let go were holding them back.

One of the main ways the "lesser-performers" annoyed their colleagues was by erratic performance. I've had some people work for me that were pretty erratic, but I always tolerated it. This, in spite of people coming into my office to complain about the erratic people on a fairly regular basis. I never had "erratic" as one of my hot buttons for letting someone go. For me to let someone go, their performance had to be obviously bad, or their skills just plain didn't fit what we wanted to do (those latter kinds of firings are really hard).

Now, after this article, I am seriously rethinking that stance. I'm adding "erratic" to my list of things to be on the lookout for in performance. Now that I think about it, I've never seen an employee evaluation form that asks for an evaluation of how erratic someone's performance is. For instance, you can hit deadlines, which is often mentioned on the form, but still be erratic about intermediate work products, and the like, which can cause other people to miss deadlines.

Food for thought.