As someone who's worked in small companies all his career, moving to a larger company produced a whole series of DilbertMoment''''''s.

----
YouKnowYoureInaBigCompanyWhen...

* You say your employer's name, and everybody stares in shock and awe. "Wow, he works for this megacorporation!"

* You sometimes find youself saying "my boss's boss's boss's boss's boss".

* You need a whole group of employees just to help the engineers figure out how to use the code repository.
** Corollary: You use a code repository that requires a whole group of experts on staff just to figure out.
** It's based on ClearCase (which only a BigCompany can afford...)
*** Subcorollary: You work at BigBlue and ClearCase is your company's product.

* You must email the repository department in order to have them label repository sources for you or create a branch.

* The hardest part of completing a task is figuring out how to do a convoluted cross-branch merge of the repository sources.
** Corollary: Your development process is convoluted enough that such merges are necessary.

* Your manager occasionally says something silly enough to remind you that he's not staff.

* It takes 2 weeks to plan for a one-hour task.

* Your manager quashes a plan whereby person B (from another department) helps person C (from a third department) by doing something with your work-product; he quashes it, fearing that ''his'' manager might blame him if person B doesn't come through.

* The email system doesn't use standard protocols and won't work on most platforms, but it books conference rooms automatically... sometimes... until it stops for some unknown reason and forgets your appointments and you start missing meetings...
** ''GroupWise, I presume?'' No, GroupWise runs on most platforms.
** Uh, that would be MicrosoftExchange. (But Exchange ''is'' cross platform; it runs on Windows XP, Windows 2000, Windows Nt...and we have ''both'' kinds of music here. Country ''and'' Western).
*** Uh, "cross platform" refers to being able to run on many different operating systems, i.e.: *nix & MacOS & OS X & AmigaOS. The abomination you refer to as "Windows" is one single platform that promotes enough bugs with each release to make it look like different platforms.
*** I think that was the joke.
** This can also refer to old mainframe-based mail systems.
*** However, old mainframe-based e-mail systems generally tended to ''work.''
** A message you sent was standards-compliant when it was sent, but is not by the time it arrives.

* You get more phone messages from MIS apologizing that email is down than you get from your significant other.

* Your external email address contains a field revealing your department, e.g., joe.blow@engineering.companyname.com rather than joe.blow@companyname.com.
** Or, a field revealing your country, like joe.blow@us.company.com, juan.perez@mx.company.com or ola.nordmann@no.company.com
** Or it reveals your subsidiary. Real example: joe.blow@lotus.com instead of joe.blow@ibm.com

* You dread the day you'll have to hold a phone conference with your colleagues in India and China. 
** ''(This is actually one big reason why American companies will sometimes outsource to Latin America rather than cheaper Asian countries -- the time differences are no more than 7 hours and that's between Alaska and the Easternmost tip of Brazil, which means the managers can spend more time looking after their businesses within working hours)''

* At least one very senior manager is universally acknowledged to be completely incapable of doing his job, but purely political considerations keep him there... for four more years.
** D''id'' you work in the Whitehouse, by chance? ''(-:''
** This happens in small companies too.  E.g. the brother-in-law of the CEO.

* Some administrative procedures require bootstrapping. For example: you need to submit a scanned paper form to request permission to use the company scanner; the bootstrap phase here would be going to Office Depot to have it scanned for you.
** That's their indirect way to say: "Scan your own sh8t!".

* The CEO visits rarely, but when he does, he uses the corporate jet.

* Your boss has more people ''over'' him (i.e. his boss, his boss's boss, etc.) than ''under'' him.

* Terms such as "division," "department," "product line," and "business unit" all have official meanings within your company, and all refer to different levels within the corporate structure.

* Mergers and reorganizations of "divisions," "departments," and "business units" cause yours to change its name and level every couple of months.
** Such changes lead to the introduction with much fanfare of new logos and mission statements for the "divisions," "departments," and "business units" concerned.
** There are contests for employees to come up with the new logos and mission statements.
*** ''Hey, don't knock it. The last mission statement was laminated, and made a nice placemat for keeping my lunchtime sardine oil off pile of papers on my desk.''

* There is more than one employee with the title of "president."

* There are more than two ranks of "vice president," e.g., "VP," "Executive VP," "Senior VP." (And maybe 2 is too many.)

* You are called away from actual work to have a meeting about when you should next have a meeting about "the Schedule." (cue foreboding music) Your company gets the Double Monolith MCP Bonus if this meeting includes a heated discussion about when the meetings should occur.

* You must file paperwork to declare your intent to file paperwork which declares your intent to file paperwork. Double Monolith MCP Bonus awarded if there are more levels of indirection. Remember, you need to fill that out by hand in triplicate without the benefit of carbon paper!
** For this reason, your company plows through ''forests'' worth of paper every month, and is in the process of implementing e-paperwork.
*** Which is so infuriatingly frustrating that people still stick to physical paperwork.

* You have to requisition a form, but it turns out that the form to requisition this form is obtained by requisitioning another form, which in turn requires that you submit the original form in question. (This circular dependence may seem absurd and unrealistic, but I've actually seen one in the wild.)
 
* Your boss's boss's boss's boss's boss works in another city and is someone whom you have never met, but he's still considered to be MiddleManagement.
** At my current job, I've calculated that the maximum boss nesting as a function of employees is about b(e) = log(base 1.4) (e/5). I could end up in this position if our company reaches 50 employees. I guess I should start taking management classes.
*** ''That simplifies to b(e) = log[1.4]e - log[1.4]5 = log[1.4]e - 4.78.  Apparently this means that for 3 or fewer employees you can actually have -1 or fewer bosses!''

* Your company feels the need to organize meetings in which they reassure you that you're more than just one cog in the system.
** Your entire office space counts as just a little cog in the system. ''You, my friend are just a tooth. I think your manager is the little screw that makes sure the cog stays on the shaft.''
** You politely decline an invitation to attend an all-morning "we love you and want to make you feel included" shindig, at which the CEO will be presenting, and your boss's boss has a talk with your boss, who then explains to you that having real work to do is not a good enough reason not to go.

* You miss a meeting to resolve a critical production issue because it conflicts with an appointment you have with HR.
** Corollary: HR is the most important department in the organization.
** The critical production issue is still unresolved, and the aforementioned meeting is still going on an hour after HR is done with you.

* You must attend meetings in order to find out what you are quite capable of reading via email.

* Your company has an internal instant messaging system, like Microsoft Lync or IBM Sametime.
** There's an internal social network which is almost as huge and active as your Facebook.

* In a normal, work-related conversation, you use the word ''yammerhead''.

* You have to ask around to find out the names of the people who are writing the code that will interface with yours.

* "Which building?" is a common question when trying to set up a meeting or find something.

* Due to company growth, the staff is beginning to feel like sardines packed in a can; meanwhile, the company owns the vacant building across the street, which for tax reasons it can't use.
** When the building finally does become available, internal political battles keep anyone from taking advantage of the new space.

* Three months into a project, you find out that another group is working to create a product just like the one you are creating. (They're even using the same specs!)
** You wake up in a cold sweat from a nightmare in which you discover everything you do is a duplication of what someone somewhere else in the organization has already worked on.
** Then, you start poking around, and find out it's real.
** Later you find out this is policy. There are three groups who have been given the same task. After the first or second milestone, upper management will decide which two projects get killed. ''This is in fact how the Samsung Galaxy S3 SmartPhone was developed -- three teams were assigned to develop their own prototype, the one the managers liked best was the one that got released, and the other two projects were killed.''

* The "MIS Department" doesn't include any programmers. The MIS staff works full-time keeping the e-mail server working, tracking down viruses, and auditing desktop computers for unauthorized files.

* The programmers and other technical workers have to maintain their own network separate from the MIS-sanctioned corporate network.
** OMG! We HaveThisPattern - or possibly HaveThisAntiPattern.
** At the company I work, there was once ''three'' separate IT fiefdoms: One that supported basic email and other productivity apps (Word, etc.), one that supported engineers and their tools, and one that supported the finance/accounting department. (This insanity has since been reeled in). ''(In at least one other company, it hasn't)''
*** ... it actually makes sense to have separate fiefdoms, and finance and accounting are themselves separate

* Getting approval to purchase a $3000 laptop is no more difficult than getting approval to buy a $10 stapler.
** Corollary: Getting approval to spend $10 is as difficult as getting approval to spend $3000.
*** Getting approval to spend $10 is more difficult then getting $1.5 Mil for a compute server.
*** The cost of the requisition process is far greater than the cost of the requested items.
**** Entire projects end up getting funded out of the developers' own pockets, because the requisition process is so long it actually becomes more feasible to acquire hardware and resources with personal funds. ''(That one is veering into YouKnowYoureInaBleepedCompanyWhen territory though)''
*** Most servers cost under $5 grand because there is a DiscontinuitySpike in requisition processing complexity if one goes over $5 grand, per company rules.
**** One buys the server with minimum hard-drives and RAM, and then "upgrades" two years later to keep under the $5 grand limit. If one upgrades sooner, then it looks like one is trying to buy an 8-grand server at 5-grand by splitting the order, which is officially a no-no. (True story.)


* The company's web site lists dozens of locations, and yours is not included.

* It's easier to call in to your company's main business line and ask the operator to connect you to a co-worker than it is to look up that co-worker's extension in the internal directory.

* You get sent an email telling you that all logins must be configured to have the company intranet as their home page.
** I'm hoping they don't find out about MozillaFirefox or the OperaBrowser; otherwise, we can convince them that they've won. If they do find Firefox and Opera, they'll probably just ban them.
** Next I'm expecting them to tell me what "My Favorites" must be.
*** Fine, let them tell us what "My Favorites" must be, just as long as they don't start defining my Bookmarks!
** Your company has built its own update and consitency check application. It is mandatory and rewrites your browser hompage and start menu on every boot.
** You have to write your own countermeasure script to automatically restore your configuration after the MIS software overwrites it.

* The MIS staff see all Java applications as a time sink to be avoided, despite the fact that J2EE applications account for most of the company's revenue.
** ... and developers are told to take time out to write Swing applications to hide the command lines, so MIS won't get freaked out... until something goes wrong, and we actually need '''''support''''' from the support staff.

* TpsReports are a real part of your day.

* The MIS department panics because you begin testing the network app you're developing, and they can't figure out where the rogue packets are coming from.
** Corollary: You begin testing your team's new network app. Then, you and two of your managers spend the entire next day fighting a disciplinary report raised by the network's automatic defense systems that were triggered by the rogue traffic.
*** The disciplinary report is sustained by middle management, resulting in all three of you receiving letters in your HR file and one manager is demoted -- all for doing your jobs properly -- because not doing so would contravene company policy about dealing with rogue traffic.
** Our IT department, in an apparent attempt to thwart viruses, worms, and other forms of malware, has blocked ICMP packets from passing through the corporate routers. In other words, "ping" no longer works on the intranet. Perhaps that is a legitimate security practice, but it strikes me as throwing the baby out with the bathwater.
** Your productivity doubles when you secretly get your own non-crippled server outside the network.  You have to pay for it, but it's worth it to avoid having to fill out forms to request meetings to apply for permission to make a ping request. ''(This editor did it by setting up a little Linux VM on his old college netbook, and port forwarding on his Telmex modem and a dynamic DNS in order to have SSH from the internet. It works wonders to get stuff done without having to put up with corporate access controls.)''
*** ''And THAT'S how the developers came to have a separate network from the MIS-sanctioned corporate one''

* While searching for a network switch, you're struck with a odd sense of familiarity... from a Doom map.

* You have an entire bookshelf dedicated to manuals on corporate operations, policies, and procedures.
** And those just cover your department.
** And they are cascading, every layer of hirarchy adds new policies to the one made by the uper layer.

* You have a full-time employee whose only job is to answer questions about the org chart.
** Shell Oil used to have two full time employees whose only job was to answer questions on the organization chart. -- AndrewCates

* You are required to add a "For the recipient's eyes only; please delete if this is not for you" tag to the end of every email, even if the legal benefits of something like that are dubious.
** Such text is added automatically to every email by the mail server.

* You are required to change your password every few weeks even if this has been proved to ''decrease'' security.
** And the password requirements are kept secret! Spend the next hour guessing at passwords that might be acceptable. When one is finally accepted, realize you forgot what you just typed. Proceed to comments on Trouble Tickets.

* All other network access is blocked except for the Web, if you are lucky.

* You are forbidden to use Linux desktops even if practically all the work you do is UNIX development on a remote machine. No rational reason for this is given beyond "company policy."
** The UNIX development server is in a different continent.
*** It takes 2 seconds for a character to appear because of the latency (real story).

* SAP is brought in to make everything more efficient and everything becomes more difficult.

* Hourly employees work slightly staggered shifts (8:10 to 5:10 for one department, 8:20 to 5:20 for another) so everyone doesn't rush to the parking lot at once. Especially true if the office is located in a skyscraper.
** The company parking lot entrance has its own traffic signals.
** The company parking lot entrance has its own rush-hour lanes (different directions in morning and evening) and car pool lanes.
** There is an exit from the freeway whose primary (or sole) purpose is getting traffic to/from the office. Daimler Chrysler's engineering complex in Auburn Hills, MI, USA has one.
** There is a ''freeway'' whose primary (or sole) purpose is getting traffic to/from the office. (Some auto plants in the US have this distinction).
** Or a transit stop (especially for a subway, commuter rail, or LRT station - bus stops don't count).
** The street in front of plant is named after the company.
** The tram stop is named after the company.
** The plant is served by two tram lanes with different routes and tram stops.

* Your company has a skyscraper named after it, or even several, in different cities.
** Your company has a basketball/hockey arena or football/baseball stadium named after it. (AmericanCulturalAssumption: It is common for pro sports teams and even universities to sell the naming rights to athletic facilities to large companies. The Houston Astros baseball team, for example, ''used'' to play in Enron Field, now renamed Minute Maid Park, after the beverage company. ''This practice is by no means limited to the Americas. Nearly all the big rugby stadiums and cricket parks in Australia and New Zealand have sponsors' names.'' Also, the Allianz Arena soccer stadium in München, Germany).

* Generating and closing trouble tickets is more important than solving the problems.
** Generating and closing trouble tickets is more ''difficult'' than solving the problems.
*** Gee, my company finally is more efficient at something! We are able to open and close dozens of trouble tickets before the problem ever gets solved.

* Your manager's primary responsibility is getting time cards filled out and turned in. Accomplishing something is secondary.

* You spend 90% of your time navigating or working around bureaucracy and 10% doing real work.

* Your managers fly into town for a ''release party'', but bring with them someone from human resources to close the office and lay everyone off.
** And your reward for finishing the project early is getting your pink slip early.
** And you're not even invited to the party!

* The district manager comes into town to organize a "morale building meeting" (without pay - on most people's day off), then spends the first twenty minutes chastising everyone for looking grumpy.
** Curious: What would happen if you did not attend? ''You would be "right-sized"''

* Microsoft is willing to negotiate to get your business.
** Your company holds patents that Microsoft wants to trade for some of its patents.

* Company uses a document management system that nobody likes and is slow, but the company keeps because it got a bulk deal on it. People avoid changes simply to avoid having to deal with the evil document manager. It's only purpose is to satisfy "quality certifiers," because nobody internally wants to use it. People use SneakerNet and other means to share documents.
** Much of the infrastructure surrounding the document management system is maintained by some junior IT programmer who couldn't code his way out of a bag.
** To much fanfare, the company announces the retirement of the evil document system - and deploys one which, to the astonishment of all (who didn't think such was possible), is far far worse. Even after the transition bugs are somewhat worked out and people are used to the new tool, employees pine over the "good old days" when the old tool robbed far less productivity. (Where I work, we HaveThisAntiPattern)
** The "official" document management system is so bad that the actual document management system is an ElectronicPickleJar
*** Part of the preparation for an ISO-9000 audit is quickly moving all of the content out of the ElectronicPickleJar into the "official" document management tool so that the auditor will find it in the correct place.
** There are several "official" document management systems that are all so bad (and the instructions about what document goes into which system so bad) that everyone (even some non-programmers) actually put their documents in the code repository.
*** ClearCase licenses are purchased for managers, marketing, other non-programmers so documents can be stored in Clearcase rather than the official repository.

* There are employees whose sole purpose is to type information from one system to another
* There are employees in one department who write scripts to export data from a normalized database into fancy formatted spreadsheets, which then get printed and sent to another department, which scans them in, OCRs them, and writes scripts to parse out the data and insert it into a normalized database.
** Bonus points if this is actually more efficient than it would be to get the necessary permissions, approvals, interdepartmental cooperation, and MIS support to transmit the data directly (or even as emailed CSV dumps).

* You suddenly realize you are posting Dilbert cartoons not because you think they're funny, but because you identify with them.
** You suddenly realize you've begun posting printouts of Wiki pages instead of Dilbert cartoons.
** You begin to wonder just where, exactly, ScottAdams has placed that digital video camera because the latest series in the newspaper is about your project. (This has happened to me on no fewer than three occasions.)
** You get new and useful ideas for dealing with management from Dilbert.

* You stamp everything "DRAFT" to cover your ass.
** Whenever you have a spark of inspiration, your first thought is ''Is this idea really worth fighting for?''
** You decide it isn't.
** And when the project fails, at least it wasn't ''your'' fault.

* Your company has a site or facility (a building on a larger campus doesn't count) whose ''sole'' purpose is administration and/or management (i.e. no sales, R&D, manufacturing, or customer service functions at the facility - internal support functions like the IT department, as well as support roles like secretaries, custodians, cafeteria cooks, and the like don't count). Boeing is a classic example - having built a new corporate headquarters in Chicago - in a location intentionally remote from any of its three divisions (commercial aviation, military aviation, and aerospace).
** There are multiple such facilities in the company

* You have to drop bread crumbs to find your way back to your cubicle after taking a piss.
** You have to eat somebody else's bread crumbs because you've been lost too long, causing them to also get lost.
*** No, I don't think you want to eat those ones. Those ones seem to be damp...

* The building is so large that cell phones don't work inside.
** Or else, the building includes cell phone repeaters.

* You have to use something like MS-Access to manage your CC: list.

* Empowerment means, at each step, you get to choose whether to attack the person on your left or your right as you progress forward.

* You try to locate a machine on your floor and eventually work out that it is in a separate building altogether.

* Two PCs sitting next to each other on the floor are on different subnets and go through so many switches that copying files from one to the other takes hours rather than minutes.
** SneakerNet is used to bypass obstacles (intentionally or otherwise) in the networking architecture
*** Company issues policies against using portable media to share files between devices.

* You're sending a mail in Outlook and your company address book returns 30 matches for your recipient, most of which aren't even on the same continent.
** This results in embarrassing mistakes where someone sends a furious e-mail to John Spencer Bryden from New York when it was supposed to be John Spencer Bryden from Canada.


* Name-based logins: you have an uncommon name but your login still requires a '7' appended to it to disambiguate yours from all the others.
** Bonus points: After you leave and later rejoin the company, there's no procedure for reactivating your old login, so you get a new login with a number appended to disambiguate you ''from yourself''. True story.
*** Because of the double-entry, you get ''two'' pink-slips on Down-size Day.
*** Extra points if HR makes you clean out both your new desk and your old desk.

* You wander around the office for 10 minutes before realizing you got off the lift on the wrong floor, yet everything looks just the same.
**Even the people working there.

* See this nice big mainframe? We can't use it yet, because first we have to sue D*gital for leasing it to us. But we plan to start using it next quarter... (''true''!)

* You attend three different company holiday parties: one for the corporation, one for your department, and one for your group.
** For the annual summer cook-out, the company rents out an entire country club, theme park, or similar facility.
*** The company owns the facility.

* You idly mention to your ProjectManager you intend to write a one-line script to solve some problem, and it gets put on your project schedule, demanding regular status updates and change management reports.
** You present a DesignReview for some (sub)system, and in the design review you describe the components of the system. '''Each component so described''' gets put on your project schedule, demanding regular status updates and change management reports.

* The street you turn into is named the same as your company.
** The street you turn into is '''owned''' by your company.
** Company has its own zipcode (true story)
** It's further from the factory gate to your building than it is from your home to the gate, even though you live in a different town (true story)
*** ''TheSimpsons citation: Homer commutes thru a long traffic jam and parks at the end of the lot - across a chain-link fence from his own back yard...''

* It takes three or four times the effort to go through the ''process'' of shipping a product than went into developing the product in the first place.
** Or takes 2 months to develop and three and a half years '''and counting''' to ship, and is passed off to 3 different project managers in the process.

* There's a little catchphrase that you hear and read very often on everyday situations. 
** IBM, for example, has "business reason", in the sense of "a very important reason that is relevant to the company's business". For example, when you request phone line access, the form says "Please state the '''''business reason''''' for placing external phone calls", as in, "this better be important for us!".

* Your ProjectManager maintains two schedules, one to keep track of what the engineers are working on, and the other to show to management.
** ''And they are both wrong.''

* The QA department files 50 bugs on your product, one for each test that failed, because the component they tested wasn't integrated yet. And this drives everyone into a tizzy because the bug count is too high now.
** corollary: You get in trouble for using TestDrivenDevelopment because the QA department can't meet their bug quota

* The company has a program to save money by reducing the number of network ports per cube/office to one, forcing everybody who has more than one machine (for example, a desktop and a laptop) to get mini-hubs. (Or, in more recent years, to run on the company's wifi).

* The company has an IT department which has a policy to ban minihubs to force user departments to pay money for more network ports.
** Two of your managers have to pressure IT to get them to set you up a network switch, because any change in the network topology requires careful analysis, documentation, justification and an amount of management approvals that would make Soviet bureaucracy look simple and efficient.

* Engineers above a certain rank or pay grade spend more time creating slide presentations than working on code. {Shouldn't this be YouKnowYoureInaBleepedCompanyWhen?}

* Every time you have a meeting with someone from another "department," your manager feels he needs to attend.

* You have a 'Policy on Policies' (true story)

* Matters get escalated to the Escalation Department for further escalation. (Microsoft)

* There's an IT group dedicated to testing new hardware/software for department-wide deployment. By the time their recommendation is approved by senior management, the tested product has been discontinued. (true story, though government, not company)
** I've encountered this also. They were trying to arrange an "equal or greater performance" approval system to better handle it because it became an epidemic.

* Your department pays rent to a department who "owns" the buildings.

* Your department pays for every megabyte storage used on the central file servers to the IT department.
** Storing data on your machine or static storage is forbiden.

* Your deparment pays for every entry in the ClearCase database to the configuration managment and IT department.

* The only thing that gets processed fast is budget cancellations.

* The TRS-80 that your predecessor ordered in 1983 finally arrives at your desk.
** Extra points if you need it because of an old tracking system that hasn't been converted yet.

* Microsoft Word crashes because the quantity of acronyms on your report overwhelmed the spellcheck.

* Your company leases out their parking lot to the city for concert events because it's bigger than the one by the stadium.
** You have lost your car several times on the parking lot.
** You have resorted to always using your smartphone's GPS to find your car.
** You walk one kilometer every day: from your car to your office, and back.

* Your company has a stadium on-campus (Blackbaud Technologies is one of these, but mainly because the founder was a soccer nut [is there any other kind?]. The company also sponsors two soccer teams, including one that plays on a semi-professional level)

* You need to submit a form for whatever requests you are asking for like VPN connection, code repository access, etc, and then a bunch of "managers" will have to approve it, and then you'll need to wait like 3-7 working days for a "staff" to apply for you the access you requested.
** You have absolutely zero idea of what goes where in the forms and need to have your manager walk you through it.

* You need to use a resource reservation application to book the meeting rooms, and there's a high possibility that another person at the same time are clicking the "submit" button, so YOU HAVE TO BE QUICK, or you and your colleagues will have to walk 500 meters just for a meeting.

* If your laptop gets stolen, it's simply a matter of filing a report and having someone grab a new laptop from a huge storeroom. All you get for this is a stern talk about being more careful.
** The gas station closest to your workplace is lurking with burglars who know damn well those who pull there are most likely laptop-carrying megacorp employees.
** Your corporate policy mandates the use of full disk encryption and VPN access.
*** And that was after they stopped earning or lost millions of dollars because a burglar sold compromising information from a stolen laptop to the competition.
** You have to type 5 different passwords before you can start doing any work.
** Your laptop's antivirus likes to kick in right when you're using it the most.

* Nerf guns are verboten citing safety concerns.

* You have a team whose responsibility is to document and improve processes, for documenting and improving processes.

* The department in charge of reducing redundancy was found to be redundant.....12 years after it formed.

* There is an entire manual specifying what is and isn't allowed in your office. Failure to comply will net you a disciplinary or a security report. You can't, for example, have a coffee machine or a heating element on your desktop, or if your office is particularly strict, you cannot have distasteful decorations.

* There are more than two people in your corporate campus who play videogames nobody plays like ''Dwarf Fortress'', ''Dodonpachi'' or ''Touhou Project''.
** The ex-inventor of such a game works there.

* A contract worker died of natural causes in a cubicle and nobody noticed for 3 days. It took another 2 days to find out what project he was on.

*Once your normal toilet was closed so you searched for a new one. You have never found your old cubical ever again and now have a new job, new house new life somewhere in another country.
** ''Isn't there an 80's song about that? "That's not my beautiful wife, and that's not my big new car..."''
** [Talking Heads, "Once in a Lifetime", 1980: "You may find yourself living in a shotgun shack / And you may find yourself in another part of the world / And you may find yourself behind the wheel of a large auto-mobile / You may find yourself in a beautiful house with a beautiful wife / You may ask yourself, 'Well, how did I get here?'" ..."And you may tell yourself 'This is not my beautful house.' / And you may tell yourself 'This is not my beautiful wife!']

* The paper-mail carriers kept filing for disability after a dozen years because of all the miles they walked in the huge building. They thus replace them with a robotic delivery system ( http://www.egeminusa.com/pages/agvs/agvs_mailmobile.html ).
** The robots also get lost.
** Some of the missing bots are discovered in bathroom stalls.
*** Extra points if they ask you to hand them some toilet paper.

----
Contributors: TimKing, numerous AnonymousDonor''''''s
----
Moved discussion to GovernmentVersusPrivateSector
----
See: YouKnowYoureInaWildWestCompanyWhen, YouKnowYoureInaBleepedCompanyWhen, ManagementByObjectives
----
I was gonna c&p this, coz it could be just to push my wiki, but buggar it - here is the link - http://sites.google.com/site/argnosis/corporate-costs-of-it
----
MayZeroSeven

CategoryHumor, CategoryAntiPattern, CategoryOrganizationalAntiPattern