4 ms·
If you make big changes, just do it. Don’t explain it at length. If you explain it, you give people room to argue and hem and haw and ends up being counterpro
by mc32 7y ago
If you make big changes, just do it. Don’t explain it at length. If you explain it, you give people room to argue and hem and haw and ends up being counterproductive. It’s an invitation to bikeshedding.
- ethbro 7y agoWell said, comrade!
- mc32 7y agoTrue! But these are places of work not town hall. Get on with your work. All I’m saying is it’s like getting into an argument with a kid and you try to explain every ensuing “why”? At some point it’s “because!”
- JoeAltmaier 7y agoHey I would counteract my kids' 'Why?' with "Why is not a question. Why what?" They'd have to form a clear question. Made them digest the issue enough to say what they were curious about. And incidentally made it more work for them to keep asking "Why".
- ethbro 7y agoI would much more like to employ your children than ones which were taught to accept "Because."
- JoeAltmaier 7y agoGreat! One was a soldier in Iraq and Korea, got his masters in MechE and is a process engineer in a factory now. Looking to move on. The middle son is already employed in Silicon Valley, in some startup I can't pronounce. Getting bored, might want to move on. The third is a trained pianist and cellist. Now is in IT in Target's national deployment center in St Paul. Definitely interested in broadening his experience, and would welcome a call to talk about other opportunities.
- ethbro 7y agoCould you drop me an email at username.co a t gmail with a way to get in touch? (With you or them) Can't guarantee it would be a fit -- the stuff I do is either incredibly interesting or incredibly boring to people, depending on their interests.
- JoeAltmaier 7y agoDone
- chipgap98 7y agoThat seems like it be worse. Making unilateral changes without any rational would likely anger people more.
- mc32 7y agoSometimes a straight directive is more efficient than nuanced measures. Nuance is for intellectual pursuits, not for management.
- AlexandrB 7y agoTrue, unless you want to retain employees doing intellectual pursuits. I think Google is past that point.
- JoeAltmaier 7y agoMost folks don't really care what you are doing. Because they don't understand your issues at all. Just say "It was the solution to a problem we were facing. If you want to find another solution, be my guest" and watch their 'anger' disappear quickly.
- montjoy 7y agoThat’s not that terrible of advice. You are empowering others to take action rather than feel disaffected. If they can come up with a better way with the same constraints then why not? Otherwise everyone gets to move on.
- keiferski 7y ago“Therefore any cruelty has to be executed at once, so that the less it is tasted, the less it offends; while benefits must be dispensed little by little, so that they will be savored all the more.” - Machiavelli, The Prince
- wesammikhail 7y agoThat quote gave me some serious creeping chills down my spine.
- nyolfen 7y agowhat is creepy about it? it’s downright humanitarian. ‘mitigate negative experiences and protract pleasant ones.’
- grawprog 7y agoHmmm >Therefore any cruelty has to be executed at once, so that the less it is tasted, the less it offends; That doesn't say to mitigate negative experiences, it says to do them quickly to get them over with >while benefits must be dispensed little by little, so that they will be savored all the more.” This says to dole out benefits slowly little by little so the masses can savour each little good thing given. That's not humanitarian that's Pavlovian.
- deleted 7y ago[deleted]
- noirbot 7y agoHumanitarian isn't really the right word, but it's good advice even if you're not being evil about it. If you have to give out bad news, it's better to be quick and complete about it than have rumors swirling for weeks, or have to keep giving out a new bit of bad news every week for months. That's true even if you're not intentionally being cruel, and can help people process it all at the same time, instead of just living in a deluge of bad feelings.
- pixelrevision 7y agoMuch of google’s success is built on trust. People had to trust them a whole lot to sign up for most of their services at one point or another. Most employees I have met felt the company was very open, their ideas mattered and that they were working on something positive. Maybe that much trust is naive but when your decisions can amount to things like censoring the internet for half the world it’s maybe not the best plan to just pull the trigger and tell everyone who works for you to just deal with it.
- dunkelheit 7y agoHaving recently spent some time in a leadership position, I must admit I became disillusioned with "consensus emerging from democratic debate" - everyone tends to argue from their myopic view of the issue and to avoid thinking through the consequences fully (because ultimately they won't be responsible for them). That said, as a subordinate, I hate it when no rationale is given. And it can be counterproductive too because people will start to speculate about "true reasons" behind the decision. Instead a reasonable thing to do seems to be to publish a rationale but make it clear that the debate is over and everyone has to commit to the decision even if they disagree with it.
- mc32 7y agoI agree with your experience. However I disagree with one aspect, in my experience. Giving a rationale hasn’t engendered trust, and instead has contributed to conspiratorial discussions (they say it’s about x, but it’s really about y!) and often times the conspiratorialists were kind of right. There is no good answer but a straight directive with little food to chew on leads to less counterproductive speculation. And often it is less “dishonest”.
- montjoy 7y ago> and often times the conspiratorialists were kind of right I think people are fairly good at noticing when they are just getting “spin” or an incomplete answer. The conspiracy theories pop up to fill the void. The only way to avoid this is to give enough information. Once you are caught withholding key information you will never be fully trusted again. Giving no information is probably better than giving misleading information but it certainly doesn’t engender trust. If you want your employees to be honest with you then you must give them a reason to trust you. Personally I believe part of that is being as transparent as is rationally/legally possible.
- wayoutthere 7y agoI think Google has finally embraced the fact that they're an advertising company and they're not going to change the world for the better. This means they need to drive off the idealistic hackers that built the company and replace them with corporate drones who aren't focused so much on building an empire as much as protecting it. This has been happening at both Google and Facebook over the last 5 years. I think the fact that they're driving off their most talented (and expensive!) employees is part of the plan for transitioning from explosive growth to maintenance. The growth mindset has become a liability for them.
- tarsinge 7y agoTangentially related I hope developers will realize that the current stack inherited from them is basically enterprise software made for large teams of interchangeable developers, just with better marketing than J2EE 15 years ago. For reference: https://martin.kleppmann.com/2008/05/11/ruby-on-rails-vs-java-enterprise.html https://martin.kleppmann.com/2008/05/11/ruby-on-rails-vs-jav... > I believe that if there was a full standard distribution for Java EE (e.g. Icefaces+JSF+Seam+EJB3+JPA+Hibernate+Glassfish, to name just one possible API stack out of thousands of different combinations), people would write a lot more good documentation for that particular stack, and it would become a lot easier for more developers to start using it effectively. With the right tools and good documentation, productivity could potentially be about the same for Rails and Java, but at the moment Java is shooting itself in the foot in this regard.
- wayoutthere 7y agoI would have to agree with this -- I work with a lot of large telecoms and nearly all of them use Java for any back-end services that need scale. Sure, Java is insanely verbose syntactically; but that has the side-effect of forcing you to formally model your application architecture in order to generate stub code. The unfriendliness of Java is just managed through tooling that presents a simplified interface to developers. It's easy enough to wrap a JVM in a container to work with Kubernetes or arbitrary cloud services, so many of the operational aspects of working with the JVM are greatly simplified. Moreover, Java on the web (first in the form of JSPs, later Spring-based frameworks) was largely a reaction the shortcomings of LAMP, which was largely a reaction to the shortcomings of Perl5 CGI-BIN (what I consider to be the first widely-used web framework). The great irony is that Perl had an advanced dependency management system in CPAN in the mid-1990s and PHP had nothing for years. Ruby on Rails succeeded largely by combining a CPAN-like dependency management system with a web-native development framework.
- devit 7y agoNot explaining is a bad idea, since it means that people who disagree have no chance to be convinced or even understand the motives if not convinced, so they are much less likely to effectively cooperate with the new course. Instead, explain at length and let people discuss, but at some point explain that the decision is final unless some major new elements come up.
- mc32 7y agoPeople who disagree are not going to be convinced by corporate comms. It’s not going to happen. It’s a bigger distraction than what you’d otherwise get.
- devit 7y agoThe idea is not to release "corporate comms", but in full transparency, honesty and with complete willingness to be proven wrong release all the data (email messages, meeting transcripts, web sources, documents, spreadsheets, simulations, etc.) the decision was based on and your thought process.