5 ms·
It'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
by rurban 11y ago
It'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.
- deleted 11y ago[deleted]
- abalashov 11y agoThis doesn't work in environments where: (1) There's simply too much information, or too much specialised knowledge required for more junior employees to properly utilise and assimilate it, possibly due to widespread hiring of underqualified or inexperiened people; (2) There are too many one-offs, unique or short-term items that are not really economical to formalise -- this is usually a problem of business model, or short-term survival strategies (e.g. consulting); (3) The details are changing too fast for the Wiki to stand a reasonable chance of remaining current and useful, as is often the case in fast-growing, rapidly pivoting and evolving startup companies. In those cases, there's really no getting around the role of "go-to people".
- jasonpeacock 11y ago1) That's what docs/training are for. 2) Writing the answer down in a wiki takes exactly the same amount of time as writing the answer in email. It doesn't need formalizing, just recording. 3) Again, the time it takes to tell someone is the same as the time it takes to write it down. This is a solvable problem, we just have to break the perception that "documentation" is onerous and heavy-weight. That's what wikis were meant to solve. For example - ppl are only allowed to answer questions with wiki links. My team did this, it worked very well. Everything was documented and everyone learned to check wiki first....
- jdbernard 11y agoNo, writing the answer down takes much longer than just vocally expressing it. 1. Few people type as fast as they talk. 2. When talking, you already have all the context of the problem of discussion. This usually doesn't need to be explicitly communicated in detail, both people are currently close enough to the issue to have most of the background. In a wiki you need to establish enough context that the page is useful to someone who comes to it with no other help. There is no point in having a wiki if you still need to talk to one of the guys who wrote it to understand it. 3. With a wiki (or any other secondary doc system) you need to organize the information and make it findable. This is a non-trivial effort as the knowledge base grows. Personally, I'm a big fan of documentation in the code paired with a wiki or other secondary system for longer or higher-level documentation. But it is definitely more work.
- wahsd 11y agoThat is the answer. It is essentially a knowledge management problem if the most knowledgeable are already documenting their work and process and status in a manner that is accessible to everyone else, they not only don't have to repeat themselves, but you're scaling yourself. The challenge, I think, is that each knowledge management technology solution really requires a custom solution to achieve such efficiencies in a final form. Sure, you can throw a wiki together and that works in a one-off manner, but that doesn't scale if everyone is supposed to participate in that process and discovery starts becoming an issue or everyone has their own janky one-ff solution.
- apohn 11y agoIME it is also important for management to officially recognize the need for a Wiki and provide some minimal resources and time to manage it. Otherwise it becomes just another thing for people to add to their ever growing list of things to do. I'm in a team now with a brilliant but highly overambitious manager, and we've got lots of great knowledge locked in people's heads. So three years ago we created a nice wiki and started adding stuff into it. One year later the company reorganized and the group that owned the company wiki master site said they wouldn't pay for it anymore, and that we had to move to a new system. So we did after a lot of work. And guess what happened a year later after another reorg? Putting something in a Wiki also requires you to put in a lot of thought so you properly address the audience that will try to make use of it. And that can range from people who are lazy and need to have their hands held through everything, to people who just needed a nudge in the right direction. With meetings you don't have to be so mindful, apart from knowing which people need to just go away. If there is some recognition from management that a Wiki is required and it officially needs time from people, then there is consistency about what goes in there, the time required, and some escalation process if the Wiki is wrong or outdated. Otherwise it's just another thing you do that gets no recognition that could easily lead to more work.
- QuercusMax 11y agoI did that when I got sick of people bugging me about the same questions over and over. They still kept asking me. The same people. With the same questions. Every. Single. Day. I got yelled at for doing the internal equivalent of LMGTFY in our chat room. Some people just don't want to learn unless they are forced to.
- mercer 11y agoI have a client who calls me every few months to ask for her email password. I've considered adding an item to my next invoice that says 'password manager'. It baffles me that she thinks this is okay, but in her defense it seems to work out pretty well for her...
- hrktb 11y agoI think the company culture will be the determining factor. If you have a number of people trying actively to be as knowledgeable as you are, and documentation is considered critical for everyone, a wiki will be the right approach. If most managers think that people should have strongly separate knowledge domains ("you should be the specialist of XXXX" in our company) and/or strongly value face to face communication, a wiki won't save you from getting drowned into questions and requests. To take the not so good example, in some companies telling your boss you're reading docs related to a library will get you a "why don't you go talk to TheKnowledgeablePerson instead, he worked with a version of it 10 years ago, he might remember things, perhaps"
- cateye 11y agoIn reality, this will only result in even more questions asked: - More specific questions will arise because people will get further but lack the experience to fully understand and solve the exceptions - More people will find you to ask questions - People will not understand or are afraid of not understanding it correctly and will ask for clarification - People are too lazy to read and will just ask anyway - For some stuff, you need a lot of cognitive capability. Not everyone has this. It doesn't matter how much you explain or document, they will not be able to understand it. (This sounds arrogant but it is the same with physical limits: I can't probably be the world champion swimming because of my body characteristics. The same applies for non-physical limitations.)