9 ms·
"The carpets are so clean, we don't need janitors"
- michaelochurch 14y agoExecutives are day traders. I've known day traders to argue that they make more money trading in the first and last 30 minutes of the day than they do if they're trading all day, because they end up getting involved in "boredom trading" that is break-even at best (and blows out their variance) and quite possibly losing. As for executives, they're disciplined, they can enjoy their easy jobs and high compensation and accept the boredom associated with rarely being needed, because if things are running well, they aren't operationally necessary. Unfortunately, they're rarely content to work 2 hours per day at their cushy jobs. They become forces of nature due to a combination of (a) a need to feel active and important, and (b) a theater in which it's hard for them to have real positive impact (because performance assessment of executives is impossible and most just don't have the talent). "Trading boredom" sets in. The executive's job is to Make Decisions and to gamble with the company culture and operations. In order to feel useful, executives pull this shit. Like "saving money" by gutting the IT organization. What's worst about this is that the executives who do this sort of thing rarely suffer any consequences. They shift blame to subordinates whom they can fire, and if the heat is turned up on them, they move on to other jobs. The employees and the owners get fucked, but executives get to flit about from one cushy job to another on account of building a web of connections that makes them effectively invincible.
- Foy 14y agoI hear nightmarish stories of micro-managers all the time. They feel that in order to do their jobs they have to tweak EVERYTHING that crosses their desk. One memorable anecdote I came across was about an animation artist who was in charge of animating the queen for a 3d chess game. Because he knew his manager's weakness he threw in a duck... Yes, a duck. Fully animated with sound effects and everything. Sure enough, when he showed his work to his manager he said "It's perfect, but get rid of the duck." So maybe the moral of this lesson is that when things are running 100% smoothly, it's wise to toss your micro-manager a bone by doing something intentionally a little wrong to give them something to meddle with. ;-)
- cperciva 14y agoI've heard the same advice applied to PhD theses: Examiners always want to change something, so leave something in which you won't mind having them tell you to change.
- praptak 14y agoI have witnessed this advice applied to contract drafts. Lawyers from the other company were routinely given some bullshit clauses to prove their usefulness in vetting the contract.
- lancewiggs 14y agoThe really entertaining part is when they don't catch them. Every clause is negotiable - don't leave it to your lawyers alone to negotiate.
- Dobbs 14y agoThe duck story is battle chess: http://en.wikipedia.org/wiki?title=Talk:Battle_Chess#The_duck http://en.wikipedia.org/wiki?title=Talk:Battle_Chess#The_duc... I've often had the opposite problem: companies where the CEO is so disconnected from the company (usually by working remotely 80% of the time) that the company doesn't have direction and languishes.
- Foy 14y agoOh thanks! I was wondering where exactly I had heard that.
- Dylan16807 14y agoAww, so there never was a duck.
- rmc 14y agoSpeaking of managers ignoring things, I'm reminded of the last episode of the 90s sci-fi tv show 'Sliders', apparently the producers thought the network exec werent reading the scripts, so they deliberately broke a rule, and wrote a scene where someone was shot in the head and it wasn't picked up on. cf. http://en.m.wikipedia.org/wiki/Sliders#section_2 http://en.m.wikipedia.org/wiki/Sliders#section_2
- praptak 14y ago> they move on to other jobs. ... with their CVs exposing the fuckups as accomplishments: "Successfully managed a cost cutting campaign, sparing the company 2 bazillions in IT costs". The previous company won't admit it was actually a disaster.
- protomyth 14y agoIts even funner at companies that cycle managers through business units to get them experience with the whole company. Leads to a "must make changes that are short-term budget wins but long term negatives" attitude.
- praptak 14y agoIt's called "a bungee boss": http://dilbert.com/strips/comic/1994-09-07/ http://dilbert.com/strips/comic/1994-09-07/
- zcvosdfdgj 14y agoNo need to generalize based on your work experience. There are good AND bad managers. The fact that IT gets cut does not mean the manager is bad. You work in IT, so I'm sorry I have to break this to you, but sometimes the universe does not revolve around IT. Sometimes there are more important divisions, and sometimes IT expenses have to be cut. There's not enough detail in the article to know if the manager was good or bad.
- michaelochurch 14y agoThings were running well. The executive thought that IT was bloated and made cuts. Things were no longer running well. Far more money was lost in the company's dysfunction than saved by the cuts. Sounds like a bad executive to me. I never implied that there aren't good managers and executives, but only that most of them aren't, because most of them get caught up in "boredom trading" that doesn't solve problems, but is just managerial action for action's sake.
- zcvosdfdgj 14y agoFirst, he said the savings almost certainly less than the cost of the waste. This sounds like a guess. He gives no numbers, and doesn't appear to have quantified anything. Second, maybe IT was running so smoothly previously because it was bloated, and was a huge drain on company resources. Maybe it was running smoothly because a bad manager refused to put a limit on anything, leading to a division whos costs were completely out of control. We have no idea, because there are no details in the article about the company, or about the IT spending before OR after the cuts.
- rosstafarian 14y agoThe exact quote is: "Of course, it all went to shit. New employees would go a week before they had machines, phones, passwords, and ACLs. Printers ran out of paper, projectors ran out of lightbulbs, servers ran out of storage, networks got misconfigured, and so forth. The total time lost and wasted across the whole company was most certainly greater than the savings of laying off the expensive and skilled IT staff." The guy might be a bit biased but it's completely clear from his article that even though he might not have exact numbers the company was much better off(not only in terms of total profit) with the old IT department. Are you a manager?
- temphn 14y agoUnfortunately, they're rarely content to work 2 hours per day at their cushy jobs. These are not the characteristics of executives at successful companies. Have you ever started a successful business? If so, did you work two hours per day? I doubt many YC founders would see themselves in this assessment.
- michaelochurch 14y agoI doubt many YC founders would cut IT because things are working well. Startup founders are in a different class because there's actually 8+ (sometimes 14+) hours of work to be done in a day in a company that's fighting its way into existence.
- zobzu 14y agoYC founders and startups have nothing to do with the story IMO. They're generally engineers that make their own companies. Executives as depicted are however the general standard for most companies. They generally have never created any company from scratch.
- ubernostrum 14y agoYes, yes, I see. A person struggling mightily to build a brand-new company from scratch is obviously a perfect analogy for a person who's placed in a high-level position at a strong, established company. I bet that their tasks and workloads are practically identical, even!
- kooshball 14y agoThis kind of generalization is toxic. The engineering community as a whole should not accept this mindset of Engineering vs Executives.
- rayiner 14y agoThe executive community is quite on board with the mindset of "engineers are fungible cost-centers to be reduced as much as possible" so why should engineers not be wary themselves? Engineers being culturally complacent and not willing to make a fuss is precisely why companies like Google, who have revenues per employee twice as high as say Goldman Sachs, get away with paying their engineers a fraction of what financial professionals at Goldman get paid.
- michaelochurch 14y agoIt's not that. Good executives are worth far more than the compensation that they get; but as a class, their net impact is neutral at best and probably negative. As with stock traders (where a lot of them just lose money) most of them aren't very competent. That doesn't invalidate every single one of them or what they're trying to do. It's the CEO-pay debate all over again. No one who actually understands large companies would argue against the notion that it's worth $10 million per year (several times that, actually) for a company to have a good CEO over a bad one. On the other hand, shitty CEOs are paid highly just for belonging to the class of people considered eligible to be CEOs, and increasing executive compensation has paradoxically reduced quality of service: http://michaelochurch.wordpress.com/2010/11/22/pay-more-get-less/ http://michaelochurch.wordpress.com/2010/11/22/pay-more-get-... Also, I think lightweight management is generally better and I don't see why people find my insinuation that most executives should be working 2 hours per day to be an insult to what they do. If I were at a point in my career where I could legitimately justify the kind of compensation that I make now with a 2-hour workday, that would be awesome. I could go back to school, or volunteer, or take another job. I don't know why people in our culture equate working long hours with being productive. I equate it with being so unproductive that people have to make monstrous sacrifices just to reach par (although the reality is that most people are plenty capable of being productive, and the long hours come from social expectations).
- robomartin 14y ago> As for executives, they're disciplined, they can enjoy their easy jobs and high compensation and accept the boredom associated with rarely being needed, because if things are running well, they aren't operationally necessary I'm sorry but you have zero clue as to what running a business is like. Zero. There really isn't much more I can say other than to quote Twain: "He who holds a cat by the tail learns something he can learn in no other way". Go hold a cat by the tail. Then come back and re-read your post.
- deleted 14y ago[deleted]
- rapala 14y agoIn a firm the size depicted in the post business is run by the marketing division. In these firms most of the divisions have executives to sign purchases and attend meetings.
- bgilroy26 14y agoI don't understand the reaction here in the comments. Do the people talking about the uselessness of management think the same of sysadmins whose systems are running smoothly?
- deleted 14y ago[deleted]
- jusben1369 14y agoThere are bad executives like their are bad programmers. You should narrow it down vs being so broad.
- antidoh 14y agoI have put this in my very small file of "things to share when I leave."
- cstross 14y agoAlso: good management is like oxygen -- you only really notice it, much less recognize that you need it, when it goes away.
- emeraldd 14y agoBad management is like mud. It get's on everything and is almost impossible to get rid of.
- Foy 14y agoI've read in multiple places and wholeheartedly agree that it's important to focus on visibility in your work. If your managers can barely describe what you do, or how you do it, then your job is just asking to be cut. When I show my clients an update, I always focus on what "looks" or "feels" different with the user experience. I wouldn't (maybe couldn't even) convey the awesomeness of all my fandangled SQL subqueries.
- zcvosdfdgj 14y agoHe never says what the company is or what it does. After IT was cut, he says it would take a week before a computer was on their desk. That sounds bad. But we have no idea what the company does, so we don't actually know if this is a problem or not. Look, every division is not critical, and sometimes that division is IT. We have no idea how much the inefficiency costs or how much was saved by the cuts. So we have no idea if this was a bad OR good thing for the company.
- emeraldd 14y ago> That sounds bad. But we have no idea what the company does, so we don't actually know if this is a problem or not. That's true. The description of the company does lend itself to the belief that it was sufficiently large enough to make these things a problem. If you have people working in cubicles there is, more than likely, a need for them to have a computer, phone, etc. While it might be possible for them to not those tools, I would expect a different style of working environment if office work were not a significant component of their job. > We have no idea how much the inefficiency costs or how much was saved by the cuts. So we have no idea if this was a bad OR good thing for the company. From the sounds of things, they didn't have a problem with inefficiency prior to the cuts. It sounds very much like they had just the right number of just the right people on hand to keep things running smoothly. At that point, it's like you have an engine and decide, I really don't need all this oil, let's get rid of some of it. You might be spend less on the oil but then you have to deal with the increased wear on the rest of your engine or risk having it seize up completely. Yeah, we don't know the real size of the company or what the company did but, the kinds of things he's describing will lead to a degradation of overall morale and you'll find that "broken window syndrome" starts taking over. You'll find that the IT people hate everyone and that everyone start's hating IT which makes the whole situation worse. So the question is, do you save a little money now to find you have a massive expense in lingering in the future?
- zcvosdfdgj 14y agoFrom the sounds of things, they didn't have a problem with inefficiency prior to the cuts. He includes no details about the IT staffing levels in the company, what the budget was, the size of the company, what the company did, what the employees did, the reason for the cuts (other than speculation), or anything else. For all we know, it was a company with 5 non-IT employees, and a staff of 50 IT people who flipped a coin once a day to decide which of 1 of them was going to work that day. Prove me wrong. How many people were in the IT dept? What was their budget? What did the company do? You have no idea.. because there are no details in the article. So you do not have enough information to say if there was an efficiency problem.
- kevinalexbrown 14y agoIn this case, the downside to saving money by laying off expensive experience is clear. Unfortunately, the downsides are rarely clear before the upsides, and by the time the mistake is obvious, returning to the previous state is difficult, and an incentive has been created for short term savings at the expense of long term ones. By way of example, several years ago I sold tools at Sears. Sears had spent decades building consumer confidence, particularly in their Craftsman brand. If you bought a Craftsman tool, and it broke for any reason, they replaced it, sans receipt. As a result, this warranty was transferable - there were no questions asked. While this policy certainly did not extend to every product sold at Sears, it did exemplify a commitment to service and quality: in the words of one older person I talked to once "if you bought it at Sears, you didn't have to worry." As time went on, Sears was able to increase profit margins by slowly restricting the tool warranty, and using crappier parts. The obvious problem was that once Sears lost its reputation as a "you don't have to worry about it" store, it had to compete with stores like Wal-Mart on price[0]. The interesting problem here is not the Sears strategy, but the fact that it takes years for the effect of reduced quality to become obvious: in the short term, consumer confidence in the brand is still high, so the worse products are bought for the same prices, under the assumption that the quality is still high. By the time consumers on the average figure this out (when your drill wears down in 3 years instead of 10), someone that made the change has been able to demonstrate clear savings to the company and move on. Several people have suggested solutions. The first one I hear thrown around is "get rid of executives." I think this is shortsighted in the same way that getting rid of a good IT department is. Certainly some executives are useless, but "get rid of the bad executives" is vacuous. A more compelling solution is to create incentive structures that encourage "bad executives" to be good ones, such as incentives which outweigh the short-term gains gotten by reducing, say, IT spending. For instance, I've heard it suggested that companies use long-term equity, say 15 years out. I'm not sure how that squares with moving from company to company, but it's interesting. [0]This is not to say that the Sears quality-first business model was sustainable, merely that there was certainly a tradeoff, the effects of which take a long time to see in total.
- martincmartin 14y agoIn this case, the downside to saving money by laying off expensive experience is clear. Things like time developers spend doing traditional IT tasks are clear to developers. But it's amazing how little of that is visible to executives. They certainly don't get an hour-by-hour breakdown of where developers spend their time. And the time to develop software is notoriously difficult to estimate even using the best techniques out there -- and most people just eyeball it. So executives really can't quantify the loss of productivity, they just hear programmers bitching.
- ChuckMcM 14y agoTechstop. That's all I'm going to say.
- deleted 14y ago[deleted]
- bconway 14y agoIt sounds to me (and I know this won't be a popular opinion here) that the original IT department was overstaffed. A printer never out of paper? No projector ever found with a dead bulb? Much like there being a "healthy" amount of unemployment (~3%, I recall?), there's a healthy amount of smaller items not met. It sounds like the company was overpaying for IT.
- emeraldd 14y agoWhat would you say about a building maintenance team that left 3% of the burnt out/bad light bulbs around? Most of the stuff he's talking about can be monitored and caught before they become a real problem or dealt with as soon as they are discovered. (Projector bulbs have expected lifetime, network printers can tell you when they're out of paper, etc.) To me, it just sounds like they have solid monitoring and procedures in place for preventative maintenance.
- darkarmani 14y agoSo, if developers ship on time are they overstaffed? Projects should never ship on time.
- majelix 14y agoGiven the anecdotal basis of the account, there may be a good bit of selection bias on both sides of the cut here. He may be forgiving or forgetting those times when something did slip (either because it was so rare or because it was so easy to get fixed), and might be extremely harsh on the failings in the future, due to it being the 18th time it's happened that week or just "I told you so!"
- gabrielf 14y agoA real life example: In the last ten years Connecticut Light & Power made major cut backs on trimming the trees near its power lines. The state got slammed by a huge snowstorm last Holloween and a huge portion of the state lost power - for as long as 10 days. Not only did CL&P suffer a financial and public relations disaster in the aftermath of the storm, they decided to double their tree-trimming budget for the next year. But this just led to further problems - people who weren't used to the power company coming in with chainsaws created a fuss at town meetings about CL&P removing or damaging their trees, leading to more ongoing PR problems.
- Dn_Ab 14y agoI am brought to mind a quote by a god like galaxy: "When you do things right, people won't be sure you've done anything at all."
- fallenpegasus 14y agoFor a long time, that was my email sig. Then I realized the problem with it. Now I still try to do things right, and then try to make sure that a few key people knew what happened.
- SatvikBeri 14y agoStep 1 is to start bragging. Step 2 is to have other people brag about you.
- blackcoat 14y agoI just started a new job two weeks ago, meaning that I've put in approx 80 hours in. I would guess that I was unable to perform my required functions for about 30 of those, due to setup inefficiencies. This has also delayed the onboard learning curve, because I have to stop and figure out who to talk to to get permissions, or wait for a machine, or an image, or whatnot BEFORE I could start figuring out how to do whatever it was I was trying to do.
- patio11 14y agoAs fun as getting out our tribal aversion to managers who don't respect geeks is, let's focus on the actionable career point: do not work for cost centers.
- tomjen3 14y agoOr better. Turn the perception of being a cost center into being a producer. Most managers wouldn't dare tuch you so long as you say for every dollar put into the department, we save the business x dollars. You could even argue the margins too.
- SatvikBeri 14y agoA similar tack is to get yourself perceived as an incremental value adder, as opposed someone filling a role. For example, IT is generally seen as filling a set of necessary roles where each person is more or less interchangeable. Sales is generally seen as incremental value adds, and sales people get paid accordingly. So how can you get seen as an incremental value adder if you're working in IT? Simple: start projects and clearly explain the impact to the bottom line. If you show the executives that you've saved the company $2MM/year forever, and that project wouldn't have happened if you hadn't dreamed it up, that's going to get recognized. Even at large, highly bureaucratic companies.
- chrisbennet 14y agoA few years ago, my manager at the time explained to me how our company had acted as an incubator for 2-3 of our competitors. It worked like this: Our company would design a product over the course of a few years and once it was in the pipeline (being bought) it would have a life of a few years. More than once, the then current CEO of the company would decide to cut the engineering staff to save money and move on before the next product to fill the pipeline would be needed i.e. the lack of new products wouldn't show up on the bottom line for a few years. In the meantime, the talented engineering team (that they layed off) would go out and start another company to compete with us....
- ricardobeat 14y agoEverytime I see a "for folks from HN" message at the top of a post I feel like I'm part of a school trip. Can we stop littering the web with these?
- greedo 14y agoEfficiency rarely correlates with headcount and budget. 9 years ago, our IT budget was $11 million. Today, it's a hair over $60 million. Adjusting for inflation, we should be around 13 million. Most of the added budget has gone to bloated off the shelf software applications, retaining duplicate/redundant staffing from a pseudo-merger, and mismanaged consultants. The OP has added a lot of facts in replies in this post, indicating that his staff was relatively lean (1 staffer for every 50 users). But be careful in drawing too many conclusions from one instance of anectdata.
- elptacek 14y agoIn a somewhat related adventure, I am scheduled to give a talk soon (hopefully the same talk twice) about managing a security assessment project. I am hearing about this same sort of beheading happening in the infosec departments from various clients. The impact on me, personally, is that my client contacts are stretched so thin that they don't have cycles to prepare and make the best use of my time. I'm planning to have handouts with checklists. So this topic has been very much on my mind, lately. One of the things I've learned from Tom is to keep track of how I spend my time. It is tedious and frustrating, but not unlike dieting: without data, you just have no proof. If I had found myself in the situation that the OP describes, my first reaction would have been to keep a running log of every task I had done, including start/stop time and a description of the work done. I've written scripts to do this in the past that generate PDF timesheets -- you could probably use Trac somehow. I'd keep this stuff on a device I owned, and bring the logs to my reviews. Yes, this adds to the stress. Yes, you'll get criticized for it. But when someone who has no clue why the carpets are always clean starts swinging that axe, you'll be wearing armor.