When working with associations on implementation of their databases, there are points throughout the process where we will have to make a decision, whether it's about how to set up a particular part of the database, whether or not to convert or collect certain data, or deciding which processes to keep and which to change.
When making these decisions, it's important for all staff involved to acknowledge and understand that some decisions made now will turn out to be incorrect later. That is, not every decision made will be the correct one.
What we have to keep in mind is that making the correct decision every time is not what's most important (after all, it's impossible to make the correct decision every time). What's important is how we react and adjust to decisions we made some time ago that ultimately turn out to be the wrong decision.
There is a tendency to become paralyzed when faced with making a decision. My suggestion is that you make a decision and move forward, watching how the decision affects what we need to do, and making adjustments as needed. This is true of databases, new products, and decisions in our personal lives.
Not every decision will be the correct decision, but how you react and adjust to an incorrect decision will be the difference between success and failure.