"At Apple there’s never confusion 'as to who is responsible for what'."
This is a project I run with almost all of my clients - shifting an organic, but dysfunctional, business arrangement into one where everyone knows their responsibility, and the right person does the right jobs at the right time (and for the right cost point).
This is achieved by shifting focus. Most businesses evolve from the top down: when the business owner/s or managers get too busy, they hire somebody new and hand down some of their tasks (usually those that they don't like). We work with the business to break down everything they do (from setting a vision to cleaning the sink - easier to do than it sounds), and then coach them to assign responsibility based on who is the best person for each task, rather than who was hired first.
I find it fun - although anything that involves defining and changing responsibilities is fraught with danger in a business. People who have been 'hiding' behind vague (or non-existent) job descriptions are suddenly found out. I tell clients to expect up to 10% resignations, but most or all of those who leave will have been holding the business back. It takes strong leadership to hold the business's nerve during that period.
I guess my point is: this element of Apple's success is possible for any business. It's rewarding, but requires good leadership.
That's basically how the small startup I'm working with works. We're a total of 4 people, and at this size, and although we have a founder (or founder and a half), we all basically do what's necessary and everything we can.
The founder is very much against defining roles and job descriptions, despite us sometimes being tempted to go down that road. In the end it makes everything so much more pleasant.
Steve Wozniak was the commencement speaker yesterday at Michigan State. I had the pleasure of attending a meeting he held with engineering students after the commencement.
The biggest surprise I had was that the Woz was on the Macintosh team before Jobs was involved. He said that he, Jef Raskin and a few other engineers wanted to create a low cost version of the Lisa.
It was only after Jobs was banished from the Lisa team/building that he took over the Macintosh team. Also interestingly even though he was a co-founder Woz left the impression that the team leader was initially Raskin. I thought Jobs had founded the Macintosh team.
The Macintosh was a very different computer before Jobs got in there and took the reins. If you can spare six hours, folklore.org has an incredible collection of stories detailing early Apple. You won't be able to stop reading.
Thanks for this! Fell asleep reading this last night and can't put it down this morning. This could be bad as I just tore down my engine last night and kinda need to put it back together today. Oh well.
What's interesting to me is just how early Jobs was booted off the Lisa project, way back in 1980 before Apple's IPO. That's what led to Steve's involvement in Raskin's Macintosh project, and what allowed it to move beyond the stage of research project.
It's been suggested that the Macintosh project was allowed to continue at Apple because it kept Steve Jobs out of everyone's hair.
Fast forward four years to 1984, the Lisa appears to be a failure and the newly-released Mac appears to be a big success (at least initially). The Lisa and Mac teams are reorganized into a single group called "Apple 32", with Steve Jobs at the helm of this new group. During the initial meeting of the new group, Steve's first words to the Lisa people were "You guys really fucked up."
Even more interesting, the guy who took over the Lisa project from Steve in 1980, John Couch, returned to Apple a few years ago as VP of Education Sales. He appears in the top-left corner of the org chart in the linked article.
"Steve Jobs hired dean of Yale School of Management Joel Podolny to run the Apple University, an internal group also featuring business professors and Harvard veterans that are writing a series of case studies to prepare employees for the life at Apple after Jobs."
Podolny was a star at Yale - presiding over a massive change in the MBA curriculum that made it a a lot more useful than the traditional subject by subject based approach.
Interesting. Do you know when that MBA curriculum change happened? Have details on how it is structured now? Have any studies been done on the effectiveness of the program post-restructuring?
Notice how Jonathan Ive does not delegate any work to any Vice Presidents. Compare this to other corporations and you'll see why this works so well (no giant chain of command where every member of staff is trying to put their stamp on things).
The noteworthy stuff is that Jonathan Ive reports directly to Steve Jobs, while Bob Mansfield, SVP of Hardware¹, reports to Tim Cook. That shows what Apple is all about.
¹. The chart says "SVP of Mac Hardware", but on the iPad 2 video he's presented as "SVP of Hardware".
> “Somewhere between the janitor and the CEO, reasons stop mattering.”
Anyone cares to explain that one? It left me confused really... The way I read it, he's a visionary and doesn't care how things are achieved as long as business is good. And to be honest that doesn't sound good for me - more like a dictator who will eliminate failing VPs whether the fault is on their side or somewhere else in the organisation.
If the janitor didn't have reasons to hide behind, then he should have taken initiative to get the new keys or pick the lock or break the door or whatever it'll take to achieve his goal.
The notion is that a VP shouldn't have reasons to hide behind. She must achieve her goal using any approach necessary, especially since her process is not spelled out for her like the janitor's is. A VP should take initiative even if it takes hiring a new team, or doing it herself, or changing the product, or getting the necessary partnership or distribution deal--whatever it takes to surpass Steve Jobs's expectations.
Steve Jobs doesn't have expectations for janitors.
I don't really think it's about expectations or initiative. It's about accountability. He's simply saying that there are times when the guy on the bottom of the ladder has his hands tied and can say there is nothing he could have done(breaking and entering is not a viable option for a janitor). At some point someone has to take responsibility, Jobs says that starts at the VP level.
I also think people get a little carried away with this due to Jobs' persona. I don't think he means it in a, "you must get X done at all costs". I think he's simply saying, "This is your responsibility. You're accountable. Don't blame someone or something else".
Roughly speaking, this is also supposed to be the difference between a professional and an employee, and between an officer and an enlisted man (though a good military will also encourage initiative at all ranks).
"Steve Jobs doesn't have expectations for janitors."
That whole ideology is unsettling to me. The way in which janitors are singled out as not having the same level of expectations to accomplish their tasks as a VP or any other position. I was a janitor for my high school, and I can tell you from my experience we busted our tails making sure the floors were swept and mopped and the all garbage was taken out on time every single day. Management had high expectations of us and refused excuses, which I respected them even more for. If you started slacking, you were out the door, period. Janitors are professionals too and I don't think it's professional to exemplify them as having inferior expectations or purpose compared to any other job. It's still a job and somebody has to do it, and do it well.
If it makes you feel any better, I was a janitor too. My first job with a steady paycheck was being an assistant superintendent at a condo. Effectively I was doing the work of a janitor.
Asses were busted but at the end of the day you go home and there's no lingering stress. I did my rounds, I cleaned my floors, I noted the gauges and rewound the tapes. It's someone else's shift now, they can deal with the leaky pipes or the stuck elevator or the mold in the stairwell. It was a very different type of job from say... founding a startup, or even just being yet another software engineer.
I guess the more you introduce creativity, ownership, and absence of process... the more you depart from the land of janitorial services.
"If it makes you feel any better, I was a janitor too."
It doesn't make me feel any better. I don't need sympathy.
"It was a very different type of job from say... founding a startup, or even just being yet another software engineer."
Agree, but so is every other job. Why single out Janitors? Are they easier to pick on because of their stereotype? Each occupation has expectations which must be fulfilled to a high level of quality. Janitors have a ton of responsibilities of which they're responsible to, including getting creative when need be. Unexpected events do occur, and janitors have to be able to adapt and make personal decisions on the fly.
"Asses were busted but at the end of the day you go home and there's no lingering stress."
I don't know about you, but I know there was a ton of paralyzing stress around my whole body working those shifts. Enough where I couldn't even think about founding a startup, let alone stay awake. Maybe in my dreams though.
It means you can't hide behind excuses. If for example theres a problem with a vendor shipping components for a product line you're a VP for, it means you're responsible. It means the only acceptible answer is that you found a new supplier and we got the product out on time. Not 'we're late because our manufacturer couldn't hold up their end of the deal'. It's a great philosophy, to my mind it's what defines a true manager in any org. If only AT&T implemented it too.
Yeah, I get the idea of more responsibility, but don't really agree with how it was put... There are always things which simply cannot be resolved in a given timeframe and the reasonable decision might be to plan for a delay / propose an alternative plan instead - it looks like the VP gets the blame in that case instead of reconsidering the strategy, since reasons don't exist any more.
More to the point - that sentence paints the world black/white, even though the world never works like that. However, I think it also explains some actions of that company...
Honestly, while I understand what you're saying, I disagree. Changing plans and/or pushing back schedules is independent on who's responsible or to blame. If something happened that can't be worked around and my VP neither made contingencies or raised that risk to me from the start. It's their fault. Period. Might sound harsh, but I can't see how you do it any other way.
Sure, and if that's so, a good VP is ahead of the problem with that new proposal, well in advance, instead of rationalizing the failure after the train goes off the rails.
I think the idea is that the VP is involved in setting the goal, so if they fail to achieve it they take the responsibility for not having planned correctly. If they agree to an impossible goal, it is on them. If conditions change and they see the goal will not be met, they need to manage the expectations and not allow the situation to surprise anyone, especially Steve Jobs, like the example in the article.
Reasons stop mattering proportionally to your power and influence in the organization. From the janitor to the CEO, your ability to change things for the better increases. Therefore if something fails, it's not because you didn't have the authority to make sure it was done right but because you failed to observe and act.
Is this amount of an article being reproduced/summarized really within the bounds of fair use? I'm not complaining, but I felt no need to pay to read the actual article after reading this summary, and I can't imagine Fortune would be happy about that.
This is a project I run with almost all of my clients - shifting an organic, but dysfunctional, business arrangement into one where everyone knows their responsibility, and the right person does the right jobs at the right time (and for the right cost point).
This is achieved by shifting focus. Most businesses evolve from the top down: when the business owner/s or managers get too busy, they hire somebody new and hand down some of their tasks (usually those that they don't like). We work with the business to break down everything they do (from setting a vision to cleaning the sink - easier to do than it sounds), and then coach them to assign responsibility based on who is the best person for each task, rather than who was hired first.
I find it fun - although anything that involves defining and changing responsibilities is fraught with danger in a business. People who have been 'hiding' behind vague (or non-existent) job descriptions are suddenly found out. I tell clients to expect up to 10% resignations, but most or all of those who leave will have been holding the business back. It takes strong leadership to hold the business's nerve during that period.
I guess my point is: this element of Apple's success is possible for any business. It's rewarding, but requires good leadership.