[jhogendorn]

Yes, agree totally because thats me and a few other core people. As a very much self starter it can be hard to build systems that are enough support but not too much for those who aren't as comfortable or 'entitled' as you put it.

We absolutely run into this issue of new people floating ideas and the old hats going 'for the 100th time that will not work because x y z' and the new person going 'jesus, ok then'. Theres a lot of history and learnings thats hard to solidify and pass on and get people into the same book, not even the same page. I still haven't cracked this nut, it feels like i should write a bunch of documentation but i suspect it will not be read.

I've been the polite but chronic reminder/nagger. It does work but its extremely wearing on all participants. I've found the best way to do it is to pair or more people up, in a physical location at the same time to do things. Body doubling is like crack to my audhd brain but it works great for most people as well. Bonus points if you feed them. However, thats a high level of organisation and it can be really tricky to pull it off with the regularity and scale the organisation might require.

I've said in other comments i'd do unseemly things for a volunteer coordinator, but i'd make the devil blush if i could pin down a project manager. Most people just need structure, thats just the long and short of it I've found. You've gotta provide it some way or another, and doing it effectively is a full role and I have enough hats as it is.

How do you combat the old knowledge vs new (naive?) ideas issue? Do you try to reevaluate that 'old knowledge'? Just let the new idea down gently and explain the history? Talk about what you havent tried that might be relevant?