3 ms·
I think it depends on the problem. Most organizations where I’ve worked have more of a problem with info being siloed, stuck in people’s heads, or stuck in out
by prepend 6y ago
I think it depends on the problem. Most organizations where I’ve worked have more of a problem with info being siloed, stuck in people’s heads, or stuck in out of date pdfs that people email around.
In that case, I’d rather have the chaos of a wiki as long as there’s version history that shows users. That at least improves the asks to individuals and helps find the mavens of info.
So I’d rather just work on a wiki with search and let the organization happen organically than “burn it down and start over.”
I find it really hard to get the right people to contribute as superficial info from non-SMEs or some contractor whose job is to crank out docs that don’t have usage metrics or quality metrics is worse than nothing.
Currently I’m trying out, not a wiki, but a git repo that takes pull requests and generates a web site that’s hooked into intranet search. It allows easy read and any employee can send a PR or open an issue so all changes are tied back to a specific individual.