Three weeks later… but my first thought was a bounty pool for external developers to implement some tickets. Some may get interested and stick around the project. However I imagine running that kind of thing brings with it some complications that I’m not aware of
Document management and retention & disposal (particularly regarding sensitive user information and HR) is usually a biggie for non-profits. But I’m not sure how that looks for a ‘nerd heavy’ <3 org like MB, might be okay!
I’ll also >brazenly< plug myself, I do freelance design, comms & marketing. My ideal working relationship is to have a fixed number of hours a month so that things can be done as they come up. Good example, I work for another non-profit (discounted ofc) for 4 hours/week for just under 12k/year. That means they can send me things as they come up without worrying about quotes etc, and if there’s no work that week (hasn’t happened yet!) the hours flows over and is there for bigger projects. Usually gets used on boring corporate stuff like email footers and Word/Gdoc templates, but if that’s what’s needed…
There are singular design projects that I think MB could benefit from - a styleguide (if there isn’t one?) including web elements that can be referenced across all projects, a set of illustrations that can be used to promote or ‘jazz’ up MB elements, illustrations for things like cover types, a uniform icon set/library etc