LinkedIn·Wednesday, 26 August 2026·4h ago

Every VIM environment develops workarounds over time. 👉 An invoice gets exported to Excel. 👉 Someone follows up approvals by email. 👉…

Sollitics

595 followers

Every VIM environment develops workarounds over time. 👉 An invoice gets exported to Excel. 👉 Someone follows up approvals by email. 👉 Supporting documents are stored outside the workflow. For this month’s VIM: Very Important Message, we asked Anna Bigajska to put one of those everyday VIM observations in the spotlight: workarounds. On the surface, these seem like small operational habits. However, they’re often signs that people have adapted to a process instead of the process supporting them. That’s why we don’t necessarily see workarounds as the problem. They provide valuable input. Every workaround raises an important question: Why did someone feel the need to create this? Sometimes the answer lies in the configuration, sometimes in the process itself. And sometimes standard VIM functionality already provides a better way of working. The best improvements rarely start with building something new. They start with understanding why the current way of working exists in the first place. What’s the most common workaround you’ve seen in an AP process?