Thanks for sharing @Tasha Orange!
Hindsight is such a good tool 😉. Having initially built our templates to mirror our pre-Vena Excel templates (which was a major selling point for us at the time), we're now thinking through how to incorporate more industry best practices and streamlining our templates and data models. Our initial build was so focused on replicating what we had, that we didn't spend much time considering how we could simplify things. We've grown our use case organically since we started 5 years ago and after building additional templates and reports each year, we're now pressing pause on further development to reflect on what we really need in hopes that we can align all of our stakeholders on a shared vision of what data and processes are most important and then we'll aim to simplify everything, from back-end data structure and integrations to front end user experience. Vena provides so much flexibility to build whatever you want, but pausing to ask whether you should build something is an important exercise.
I ran our initial implementation solo (with help from a Vena implementation consultant), which proved difficult as there wasn't someone else within the organization who I could bounce ideas around with. After a year or two, we got another member of the team up to speed and he leveraged the Vena Academy training modules as well as plenty of calls between the two of us. After his first year spent building a template, documenting end user training, and troubleshooting any errors, he was able to fully run with things in year 3, preparing for our annual budgeting process with little input from me. I think the lesson here is to get multiple people within your organization trained on the manager/admin side of the platform so that you've got more expertise and capacity to make improvements and guide end users.
Plan To GrowVena Academy