I have to go with my first favorite acronym for organizing software and feature requirements: WIBINI (rhymes with epiphany) -- Wouldn't It Be Nice If -- for those features we'd like but aren't currently feasible/realistic/realizable (may never be, but maybe also could be).
I had a colleague at my last library who spent hours on beautiful, absurd acronyms for different committees. We ended up with "Reviewing Evaluation Documents: Auraria Library's Evaluation Rubric Taskforce," also known as RED ALERT.
Comments
🙃
https://dannng.github.io