Do you mean a knowledge system like Confluence or a Wiki? What have you used before? What didn't you like?
It's certainly a challenge to get people to document what they know, maintain it, and then to get people to actually read it. Do you think that a slight change of the 1st idea to automatically pull out people's discussions into the company knowledge system would work? Being an internal system, perhaps GDPR is less of a concern.
weaponizing this information
It's always a company culture issue around estimates becoming deadlines. We've been speaking to a lot of agencies lately where estimates are done early, quickly and, while they have big consequences, are usually semi-fluid (or at least the scope is). Improving estimates here could lead to more profit for the agency as we want to avoid under-estimating (over estimating is far more tolerable).
Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
I've tried setting up wikis, but setting them up can be too much of a hassle for personal knowledge. For some software I am writing with a group of friends, I experimented with setting a wiki up in Documize for us, but it has not been as widely used as I wanted it to. There's a lot of external documentation we need to organize, and it isn't helping us with that. Ideally, we would go through and extract knowledge from all those files, but one only has so much time...
I use Bear on OS X for my PIM system right now. I like its tagging functionality and overall its just a very pleasant editor to use. I'm working on setting up my own website to store/share knowledge as well.
Internal is better, but you'll see different silos/hierarchies of knowledge at different companies. In some companies, communicating openly with another department about certain things amounts to treason. There's some things senior management needs to know that staff don't and depending on your beliefs, some of that knowledge should not be transferred. You would need to be able to tweak the barriers for each company you work with.
You've brought up a lot of interesting things to think about. I think figuring out the value of knowledge would be huge. Are 80% of the devs googling how to rebase every week? It's probably time for some training sessions. What files do people access the most? What are the most common helpdesk tickets? Find deficiencies, and eliminate them. Make the underlying more accessible, and figure out why that knowledge couldn't proliferate on its own. Rinse and repeat.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the detailed & considered response!
Do you mean a knowledge system like Confluence or a Wiki? What have you used before? What didn't you like?
It's certainly a challenge to get people to document what they know, maintain it, and then to get people to actually read it. Do you think that a slight change of the 1st idea to automatically pull out people's discussions into the company knowledge system would work? Being an internal system, perhaps GDPR is less of a concern.
It's always a company culture issue around estimates becoming deadlines. We've been speaking to a lot of agencies lately where estimates are done early, quickly and, while they have big consequences, are usually semi-fluid (or at least the scope is). Improving estimates here could lead to more profit for the agency as we want to avoid under-estimating (over estimating is far more tolerable).
I've tried setting up wikis, but setting them up can be too much of a hassle for personal knowledge. For some software I am writing with a group of friends, I experimented with setting a wiki up in Documize for us, but it has not been as widely used as I wanted it to. There's a lot of external documentation we need to organize, and it isn't helping us with that. Ideally, we would go through and extract knowledge from all those files, but one only has so much time...
I use Bear on OS X for my PIM system right now. I like its tagging functionality and overall its just a very pleasant editor to use. I'm working on setting up my own website to store/share knowledge as well.
Internal is better, but you'll see different silos/hierarchies of knowledge at different companies. In some companies, communicating openly with another department about certain things amounts to treason. There's some things senior management needs to know that staff don't and depending on your beliefs, some of that knowledge should not be transferred. You would need to be able to tweak the barriers for each company you work with.
You've brought up a lot of interesting things to think about. I think figuring out the value of knowledge would be huge. Are 80% of the devs googling how to rebase every week? It's probably time for some training sessions. What files do people access the most? What are the most common helpdesk tickets? Find deficiencies, and eliminate them. Make the underlying more accessible, and figure out why that knowledge couldn't proliferate on its own. Rinse and repeat.