9 ms·
The downsides of collaboration between coworkers
- protomok 11y agoMy strategy is basically: -> Politely ask colleagues to send you an IM instead of discussing in person. The context switch hit from a conversation is significantly worse than from an IM. -> Answer questions by making/editing a wiki page then send a link. Although I find this is less helpful for one off questions or during times of super high work load. -> If you've helped person X with a similar problem in the past then simply outsource the question to person X. -> Worst case (especially if someone asks the same question multiple times) play dumb :)
- zepto 11y agoSeems like the problem is that people are being given more responsibility without the necessary power.
- rwmurrayVT 11y agoI don't know if that is exactly how I would describe the problem. It seems as though a majority of my highly skilled coworkers, management or senior engineer, are CONSTANTLY having people come into their office for advice. It's commonly known that if you have a problem or need help understanding something to go ask the resident "expert". These "experts" are bombarded with questions and visits so often it's a wonder they ever get their own work done.
- vonmoltke 11y agoNot to mention the work of the people around them in the near-ubiquitous open offices.
- zepto 11y agoAnd yet they don't have the power to hire assistants to help with organizing disseminating their knowledge. If they are the constraint in the system, the organization should be leveraging them.
- jedberg 11y agoeBay did a great thing in this regard -- they offered a sabbatical every five years. It was a win for the employee because they got a nice long vacation and it was a win for the organization because it forced everyone to figure out how to get along without that employee for an extended amount of time.
- jbob2000 11y agoI really like that! One of the problems I see in my company is the "hero" vs. "process" mentality. We don't setup processes that any employee can handle, we just have a few "heroes" who rush in to save the day any time there is an issue. This leads to huge problems when the heroes want time off because we have no idea how they do what they do. A sabbatical program like this would force a shift towards processes. At least I hope...
- ryandrake 11y agoEvery place I've ever worked relied on heroics to some degree. Some more so than others. Project is way behind schedule? CRUNCH TIME! Only one person knows the code base? Give him all the work! Critical bugs found close to release? All nighters until they're fixed! In all cases, what was needed was more discipline and process. But if you ask people, they'll often tell you "process is bad and project managers should go off and make their spreadsheets and let me write my code in peace!"
- tmail21 11y agoThe other reasons why processes are not adopted is that most employees are not thinking in terms of 'processes'. Secondly typical process/BPM tools are geared towards I.T. rather than regular workers. Both problems can be solved by gearing tools towards end-users rather than I.T. and allowing processes to emerge from lower-level constructs like (say) discussion threads that workers normally participate in. This would gently steer workers towards a process mindset.
- timcederman 11y agoGoogle did the same, until they realised everyone was leaving immediately afterwards.
- rbrogan 11y agoHow does this compare to, say, a Q&A site where one gets positive feedback for answering random questions? Is the reason why people leave because they cannot do the work that they want (time used up in collaboration) or is it because they are not being given credit for the work they are doing?
- morebetterer 11y agoConstantly being interrupted to answer simple questions is a thankless task that has negative consequences to your own productivity. You ultimately have to do their work and have less time for your own, which can be stressful when on projects with tight deadlines (aren't they all?). At some point I realized that being overly helpful makes you an enabler of this rude behavior - why bother spending a few minutes researching something when the guy across from you can answer it immediately? Often it's better to say no and encourage more self reliance.
- rurban 11y agoIt's pretty easy for those overly successful coworkers (I've been such a folk) to setup a knowledge collaboration platform, like a wiki, and share this way the knowledge and let people read it instead of asking per email or phone. That's what I did. It doesn't really make sense to answer each and everyone individually.
- sanderjd 11y agoThis is the right answer, but in my experience, there's still a balance between wanting to be friendly, supportive, and engaged with the team, and wanting to protect your own time. At its worst, the approach you outlined devolves to the "read the manual!" cultures that everyone hates, but if you can strike the right balance between writing documentation and helping people understand it, then you're in really good shape.
- LukeShu 11y agoI've found a pretty good balance to be giving answers that have 3 parts: 1. a short answer (about 1-2 sentences) 2. what section of what manual to read for fuller information 3. other resources; possible "gotcha"s Then, if they come back and still don't understand, don't just take the time to help them, but also update the manual with whatever you tell them!
- sanderjd 11y agoYeah, but this is a classic problem of long-term vs. short-term optimization. In the long term having great, living documentation of everything the experts know is clearly the best, but in the short term it looks very expensive.
- andygcook 11y agoI'm actually working on a wiki built on Slack to solve this exact problem. If this is happening to you, checkout http://tettra.co http://tettra.co. We just launched our beta last week and are looking for companies to work closely with to improve the product. My email is andy@tettra.co if you want to discuss more too.
- slathrop 11y agoThe "War Room" idea promoted by Scrum Masters and Project Managers has a similar downside. War Rooms take your best people and force them to answer questions all day long posed by your least-knowledgeable people. War Rooms are one of the surest ways to reduce the morale and productivity of your best people. However, if you require real-time visibility of project status, you want all of your people to be easily interchangeable and replaceable, and you think that knowledge concentrated in a few good people is risky, then the War Room is for you.
- niels_olson 11y agoThis doesn't seem all that new to me. At the receiving line for a party, back in 2002, the executive officer on the USS Nimitz greeted my wife by saying "Thanks for supporting him, the Navy has a long tradition of riding the good horses until they break."
- colund 11y agoPeople who know a lot and rarely have time to share knowledge will always get questions about things they haven't yet shared with others. Personally, I find it less effective to work in an environment where people don't share their knowledge since less knowledge means frequent questions...
- r2dnb 11y agoI didn't know people were so generous. The experience I have is that all people want to keep their knowledge for themselves. In all the companies I passed by - including Fortune 40 ones - the documentation was non existent. In one of them, a magician who wrote a 20k lines of code Access program doing fancy things like generating stored procedures on the fly, still knew more about the program after 2 years of development than the 10 people team that was in charge of migrating it. More recently - last week - in another company, someone told me very naturally that the requirements were in someone's head and in the database schema and that we should rely on this person's expertise and avoid spending time to lay the requirements down before starting the iteration. The world I live in is much more political than the one that you guys seem to live in. Please give me the address.
- colund 11y agoThat has been exactly my experience as well. There exist job places where "the requirements is in his head" is considered normal and in order and there is too much respect given to such "job security" selfish aes who never share things voluntarily. As contrast, at an earlier work place there were "mentors" introducing newcomers to the domain holding introductory crash courses and doing code reviews. I understand why so many job posts here in Sweden stress the importance of knowledge sharing for common (not individual) success. Sharing knowledge means that more people can share the burden - not the other way around.
- r2dnb 11y agoAmen. I think the reason people are afraid of sharing is that very few people practice continuous learning. They keep using what they learned 5, 10, 20 years ago, therefore - to their mind - if they share it, they are left with nothing. I don't mind sharing as I read like crazy, learn new things all the time, and improve my way of doings things so that I do and understand things much better than I did 5 years ago.
- ArkyBeagle 11y agoMost domain knowledge in one corporation has zero value outside that corporation . There's too much path dependence. And the older the learning, generally the more general it is. There are a million ways to do everything, but a team will have Stockholm Syndrome with how it does things, generally.
- michaelfeathers 11y agoI wonder whether there is a "soft" Dunbar number for collaboration networks?
- orky56 11y agoThat greatest way to ensure job stability is becoming indispensable. Being indispensable entails providing a service or holding information that others cannot fully attain without relying on that individual. Many people, especially from the newer generations are looking for more than stability from their current job. Democratizing information is great as long as the bottleneck is not an individual and their resources.