Shannon and I were working on new content for the adilas university page. We were talking about education, training, and support. They are subjects that are dear to my heart. Here are some of my notes. They are somewhat random but part of what we were talking about and going over.

- Flat line - What if you could kill an application or system (flat line it) by not providing enough support and training? Can that and does that happen? Looking at adilas financials... Where are we at?

- Filling the gap - If we are missing the training, education, and support pieces... then what? What happens if we are missing those pieces? We have them, they are just small ish... who is filling that gap? Talking about how adilas used outside or independent reps for years and years. That really helped fill the gap. Who is doing that now? Internally or internal teams?

- Talking about a 3-way stool or a 3-legged stool (sys, $, edu) - One of the three legs is the system or the features within the system. Another leg is the clients or the money that they bring to the table by using the system (users). The last leg of the 3-legged stool is education and training. Without a robust third leg, your growth may be limited. Ideally, you balance things out, so that all legs or pieces are equally stable.

- Another 3-way relationship is between maintenance, education, and new. We keep chasing the new features, but we may be missing the education and the maintenance. We were talking about levels of satisfaction. These satisfaction levels usually come from things that are well maintained, users have adequate education and/or knowledge, and things are steady. Or sometimes, people find a level of satisfaction through a constant inflow of new (unlimited needs or lust for new features). I was telling Shannon, that for a job I have with a ski school (snow sports), we often get questions about the terrain park, at the local ski resort. People tend to be happiest with well-maintained features and educated skiers and riders who then use the features in the correct way. Some people only like it if there is something new. This demand is super hard to keep up with. However, if you don't maintain it or educate riders (public users), the new features quickly fall into disrepair and can't be used, thus requiring either more new ones or maintenance and education.

- MVP levels... minimal viable product, minimal viable plan, minimal viable person.

- Structural failure (at what point)?

- New features are exciting but they can become tiresome and non-fulfilling - too much chaos. I would rather have more stability over time.

- We know that there is a need for education and support. We had some of our reps that were making more money than we were making (filling that gap). There is value there.

- I have been in demos and meetings, and the question has been brought up, what about education and support? We do have an answer, but it is not super strong. Support is huge (we were talking about two potential bigger clients). That education and support piece is a huge checkbox that is not being filled. Question, could this be a bigger checkbox than all of the features (feeling the security of being able to get help)?

- See a need, fill a need.

- Fear and how much time it takes to do and learn something. What is an ERP system? We did some light research (see below).

Shannon and I looked up ERP software. Here is the definition that they provided:

ERP software, or Enterprise Resource Planning software, is a comprehensive business management solution that integrates and streamlines core business processes across an organization. It helps manage various functions such as finance, HR, manufacturing, supply chain, sales, and procurement, providing a unified view of activities and a single source of truth for decision-making. By automating processes and offering insights, ERP systems enable efficient management and real-time data access, ultimately enhancing organizational performance.