It's an interesting thread. Historically organizations faced these same challenges getting people to consult a website and use E-mail, both of which are now viewed as the default. The problems you are facing do not come from the fact that non-techies are stupid. And learning how to solve them is good practice for working with normal prospects (vs. early adopters).
One specific suggestion: pick one thing that will reliably be in the wiki and get people used to checking it just for that. Then branch out. Two good places to start: meeting agenda page becomes meeting minutes that any attendee can modify; internal or product specifications that would benefit from a wiki's ability to branch to background and related pages.
I don't think it's a technology barrier at all (unless you are forcing them to use Wiki markup instead of a WYSIWYG editor) it's force of habit.
One specific suggestion: pick one thing that will reliably be in the wiki and get people used to checking it just for that. Then branch out. Two good places to start: meeting agenda page becomes meeting minutes that any attendee can modify; internal or product specifications that would benefit from a wiki's ability to branch to background and related pages.
I don't think it's a technology barrier at all (unless you are forcing them to use Wiki markup instead of a WYSIWYG editor) it's force of habit.