[1] This term is often applied in fields such as enterprise resource planning (ERP),[2] e-government systems,[3] and software development, where simplicity and adherence to vendor standards are more important than expanded functionality.
[4] By opting for vanilla software, organizations benefit from lower costs and straightforward maintenance, though the trade-off may include reduced flexibility and customization options.
For example, IBM's BookMaster system referred to its simplest configuration as "vanilla" and its more complex counterpart as "mocha" to signify additional features.
[7] Eric S. Raymond's Jargon File, an influential glossary of hacker slang, provides a notable definition of "vanilla," associating it with "ordinary" or "standard" states, as distinct from the default setting.
While vanilla implementations align closely with vendor-provided best practices, they may limit organizational flexibility, posing the "common system paradox.