Sean and I were talking about online scheduling. We have a good one-to-many solution that just got released to the public. We would like to build out the one-to-one client facing scheduling portion of the system. You can do it inside the system, but that part is not yet exposed to the outside or client portals (ecommerce land).

Steve joined the meeting and we were talking about chipping away at the settings to help with the client facing scheduling. That ended up leading into a discussion about our developers and what size and type of projects are good for each person. We have some of our guys get lost (for months on end) because the projects are so large.

One of our goals going forward, will be to use more of a step-by-step guide or wizard type approach with check lists and crumb trails as to where we are in the process. Basically, breaking our bigger projects into super small baby steps. That way they could have one thing to do and could actually get it done. Once that is done, they could start on the next piece. Basically, a small and limited focus with defined parameters vs an huge open field.