Kelly, Steve, and Wayne were talking about test driven design. There ended up being 7 people on the morning meeting call. The first 45 minutes were mostly Kelly, Wayne, Steve, Cory, and myself. The other guys waited until the end. Here are a few of the topics:

- What is important to the clients in their interfaces? Small disconnect between what is possible, what is available, and how hard/easy is it to use. Also, what if the client doesn't know that a certain function and/or feature is even an option? Education, user interfaces, configuration, training, speed, and tasks at hand.

- Light talked about some of the fracture concepts such as being able to turn everything fully on/off, show/hide interface pieces, mass settings (corp-specific settings and/or industry-specific settings), make sure those on/off toggle switches cascade through the whole system. The iceberg approach vs the mountain approach. Same amount of data, just the approach and perception changes.

- SOP's for adilas developers, adilas reps, adilas consultants, adilas setup people, etc. SOP is short for standard operating procedures. Getting things more standardized and organized. Be able to scale and do it with style.

- On the cart, currently we have some corp-wide settings that help the user determine what they are searching for (items, flex grid tie-ins, recipe/builds, cart favorite buttons, barcodes (mixed sources), and sub barcodes. As we were talking... Steve had the idea of allowing the corporations to check what they search for and in what order to do the search. Currently, they have to chose one of our drop-down cart quick search settings and we then do the search. Steve was thinking that maybe we let them tell us what to search and in what order to do that search. Great idea. Just wanted to record it. Currently, the corp-wide settings is #37, but that may change. Search for it by looking for "mixed sources".

- Along the same lines as above (cart search and scan options)... what if the corporations could set up what they want and then each user could tweak that on a per user basis, if needed. Just another thought. More preferences and helping the system be more effective in the searches.

- Dustin is interested in doing some of the test driven design stuff. He jumped on and was talking to Wayne and Steve about his interest level.

- Two reoccurring themes keep coming up... They are structure and getting more organized. Interesting.