Back reviewing video content from a training video and a presentation done by Kelly Whyman.

- What kind of a setup is it? Coming off of another system, brand new, a recovery type scenario? Fresh setup, new implementation, or a clean-up.

- Corp-wide settings and what you call things? Speak their language and setup an internal glossary.

- Sharing information back and forth. Build the team.

- What are your goals and how are we doing on those goals? Sometime the first quarter is pivotal on if they like the system or not. You have to be there (physically at times).

- Templates and standardizing things. Using bite size flow charts, lots of drawings, etc. Show visual diagrams and then relate it to the system. Start out of the system and then go back in the system.

- No more than 60 to 90 minutes per session. Do a session and then allow for some Q & A.

- Help them learn that mistakes are ok and then how to correct those mistakes.

- When getting a client started, do a once a week follow-up and/or training session. After a few of these, they may not need them as often.

- Recording training sessions and share them - avoid being a broken record.

- On a demo, who am I speaking to (owner or operator)? She usually does a 30 minute consulting meeting and then she gears her demo based on that.

- Talk about the life cycle of different things... there is always a start, one or more steps, and a finish. Sometimes people love seeing that full life cycle.

- 4-square diagram - PO's, Invoices, Expense/Receipts, Deposits - use positive and negatives and explain it really simply. How do these values affect inventory or banks. This is a great simple process of what really works. These are the big 4. So many things play into the mix.

- On tech support - a quick response can help eliminate the escalation of the emotion - sometimes that is where the problems are and/or where their roots are.

- Defining the rules and expectations early on help to set the ground rules

- How much do you want to work? There are tons of options, but it is important that you define those rules and guidelines. If you don't define those goals, it could run you over... literally.

- The language that we speak between developers, consultants, and clients. We all have to play in the same area and define who wants what, who is going to do what, and who is going to fund what? Once we answer those questions, we can move forward.

- When you are onsite with a client, you will get spun in multiple directions... lots of moving pieces. We need both women and men working together to make the team stronger.

- Adilas has and does create a community of independent parties. Working together and sharing values and ethics. Good stuff.