3 ms·
>When you schedule a meeting, you create a wiki page named like "2023-01-02 Fooproj UX Meeting with Marketing" These are the kinds of wiki pages I come across
by pydry 4y ago
>When you schedule a meeting, you create a wiki page named like "2023-01-02 Fooproj UX Meeting with Marketing"
These are the kinds of wiki pages I come across when I'm searching for docs that are actually useful. I dont think anybody reads them.
- neilv 4y agoWhere does the docs/info you need end up being?
- pydry 4y agoUsually in someone's head.
- neilv 4y agoYeah, ideally all that information would be captured, but it never can be. So there's also a role for a wiki to capture information about who to talk to about a particular topic.
- tremon 4y agoIt's one of the first things that I put up on our wiki: a referral list indicating who to ask for questions about which domain. Actually, there's two columns: the first is the operational lead(s), or "who should I ask questions about X"; the second column is the tactical/architecture lead, or "if we disagree on a solution for X, who has the deciding vote?" The latter has avoided countless hours of bikeshedding, or so I'd like to believe.
- 12345hn6789 4y agoNobody reads them, is it because they aren't useful? Maintaining wikis is a culture thing. If most of your employees don't use the wiki it's basically useless since it'll be falling out of date.
- pydry 4y agoNo, they aren't. IME meeting notes are useful only for people who missed the meeting and wanted to be there. That isn't to say that there aren't other documentation artefacts that should be created as a result of the meeting (JIRA tickets, a wiki page explaining a particular feature), but they shouldn't ever take the form of "2021 June 23 meeting with marketing".