Laserfiche WebLink
fHE END OF THE JOB As a way oforganizing work, it is a social artifact that has outli_. <br />Page 3 of 5 <br />062 <br />to be done rather than on doing their jobs would wreck most traditional organizations. Just as <br />individuals need to rethink their assumptions and strategies, organizations too will have to rethink <br />O <br />almost everything they do, look at the characlensfics of the post-job organization. The first is that it <br />hires the right people. That sounds obvious, but it means something quite different in an organization <br />that is no longer job-based than it does where one is hiring to fill slots. To begin with, you must find <br />people who can work well without the cue system of job descriptions. At died, America's largest <br />industrial design firm, in Palo Alto, no one has a title or a boss. The head of marketing there, Tom <br />Kelly, leaves no doubt about the importance of hiring:' if you hire the right people if you've got the <br />right fit then everything will take care of itself." Even the right people will produce poor results if <br />organized in the old way. Yes, complex hierarchies are out and the flattened organization is in, but <br />not because that is fashionable. Rather, the postjob employee's necessary vendor- mindedness - <br />thinking of himself or herself as an independent business just doesn't mix with hierarchy. The post- <br />job employee is going to need a much more flexible organization than most can easily find today. <br />How to create this flexibility? Organizations using such workers most successfully are finding a <br />number of approaches effective. Common to many is a reliance on project teams. The project-based <br />organization is not a new idea, 25 years ago Melvin Anshen wrote in the Harvard Business Review <br />that traditionally structured organizations were inherently designed to maintain the status quo rather <br />than to respond to the changing demands of the market. But, he noted, the single organization <br />pattern that is free from this built-in bias ((toward maintaining the status quo)) is the project cluster" <br />Since those words were written, companies like EDS. Intel, and Microsoft have used the project as <br />their essential building block - though "block' is far too fixed and rigid a term to describe the way <br />projects are actually used. <br />STUDY a fast-moving organization like Intel and you'll see a More from Fortune <br />person hired and likely assigned to a project. It changes over The rem- o Ile hco.eoueders <br />time, and the person's responsibilities and tasks change with <br />Toyota has a'.any;,i. c, casr <br />it. Then the person is assigned to another project (well before <br />the first project is finished), and then maybe to still another. GE aim= !o: a rea-my omf„ <br />These additional projects, which also evolve, require working <br />FORTUNE SnC, <br />under several team leaders, keeping different schedules, cr,:,: Issue <br />being in various places, and performing a number of different SuDK`CHC ron,:ne <br />tasks. Hierarchy implodes, not because someone theorizes <br />that it should but because under these conditions it cannot be maintained. Several workers on such <br />teams that Tom Peters interviewed used the same phrase. "We report to each other." In such a <br />® <br />situation people no longer take their cues from a job description or a supervisor's Instructions. Signals <br />come from the changing demands of the project. Workers learn to focus their individual efforts and <br />collective resources on the work that needs doing, changing as that changes. Managers lose their <br />jobs," too, for their value can be defined only by how they facilitate the work of the project teams or <br />how they contribute to it as a member. No good word exists for the place that an Individual fills in this <br />kind of organization: It isn't a "job', "position' sounds too fixed; "role" sounds too unitary . Whatever it <br />is, it is changing and multiple. It is a package of capabilities, drawn upon variously in different project- <br />based situations. Anything that stands in the way of rapid regrouping has to go. Some of what it takes <br />to run the organization moving beyond jobs is part of the environment: the databases and the <br />networking technology, for example, that make it possible for a delocalized operation to function <br />effectively. Such technology, one of the forces transforming organizations and de jobbing the <br />workplace, is part of the emerging organizational infrastructure. It was out there waiting to be utilized. <br />Not so with the social and cultural infrastructure for this kind of work world. Far less developed, not <br />yet widely embraced. and lagging behind the technical, these nascent infrastructures threaten to <br />undermine the new work world. You cannot run a post-job organization the same way you ran the <br />organization when it was job-based. Policies on work hours, for example, won't be the same. <br />Compensation plans will have to change. New training programs will be needed. A different kind of <br />communication is essential. Careers have to be reconceptualized, and career-development has to be <br />reinvented. New redeployment mechanisms become necessary . And the whole idea and practice of <br />"management" need to be re-created from scratch. Many organizations have experimented with flex- <br />time, job sharing, and telecommuting. but the disappearance of jobs puts all these into a new context. <br />Standardized work hours and places, and the equation of one person and one job, were products of <br />mass production and the government bureaucracies occasioned by it. They were wholly irrelevant to <br />the prejob world and would have been burdensome checks on productivity. Take lob sharing. Work <br />was usually shared in arrangements that varied with the demands of the situation. Only when work <br />was divided up into activity packages and distributed one to a person in the form of jobs did anyone <br />imagine that anything but talent, proximity , strength, and availability would determine who did what <br />and when. Of course once you have divided up the common task into jobs, then anyone whose other <br />responsibilities, physical capabilities, or financial needs make a "whole job" unappealing or <br />unworkable will suggest job sharing. But if jobs disappear, there is no longer any reason to treat <br />® <br />these eight- hour chunks of effort as the building blocks from which the organizational structure is <br />assembled. Not that job sharing will be permitted in the post job organization much more than that, <br />The issue disappears. Naturally work will be shared People working on more than one project are <br />http://money.cnn.com/magazines/fortune/fortnne_arciiive/l994/09/1 9/7975 1 /index-htm <br />5/8/2009 <br />