One of our virtues is to keep going day after day. We also keep trying to solve and take the next logical step. We just keep doing this over and over again. That's what we do.

Steve and I were talking about our guys. Dustin is doing great. We are excited to see where he will end up and what we can do to help that process. Steve is really excited about Eric and getting him going on more internal stuff. He has been a great custom developer and a great team player. We keep trying to make a one stop solution. That becomes a challenge. Steve was talking about directing the energy of the guys and putting them into the right spot and best fit.

Some of our 3rd party solutions end up giving us a big black eye. We want the outside help... but it kinda comes at a cost.

Steve was talking about an analogy between an arrow and a target. If we are the bow (our company), what arrows are we going to use and where do we point it.

We then started talking about some of the byproducts that Adilas can and does create. We are seeing needs in oversight, compliance, training, sales, consulting, custom development, etc. Steve was saying that one of the main goals is making your CPA happy (on the accounting side). Oversight could a reoccurring service. Some of the other services are reoccurring but they tend to cycle through different companies. It is reoccurring and a never ending need but it does cycle more.

Make a small goal, then regroup and huddle up and make the next plan. Kind of a return and report type model.

Steve and I would like to offer more guidance and help with system oversight. To fit Steve's analogy, we need to be aiming the arrow instead of being the arrow. We tend to through the rope across the river and then someone else could come back and help carve out the trail a little bit better. Steve and I are kinda like pioneers in some ways. We keep trying to solve the problems that present themselves. Some of these projects may include scouting, research, ideas, demos, prototypes, mock-ups, and eventual plans.

Inspect what we expect.

We started talking about a trail type analogy. We want to build to certain points, some of it is pretty stable and awesome, some of still needs some loving, and some of it still needs to be pioneered and explored. It just keeps going.

We have tons of projects... we need to turn some of those ideas and projects into ice (water, slush, to ice). We need to follow the same analogy as we did for operations and accounting. We have an ideal (straight parallel lines) but in real life, it needs to flex a bit. Once we allow the flex bubbles or flex pods, we then put in some checkpoints. That helps us make sure that things get brought back together. We could then add in permission levels and eventually allow it flow just like a data assembly line for code vs a data assembly line for data, inventory, and financials.

We are seeing that we, internally, need to provide some small goals and checkpoints and then help with the oversight to help them get to the next checkpoint. We are building SaaS (software as a service). Do we really know where that is going? The answer is no, we truly don't know. But we do have a good idea (an ideal or a goal or a direction). That is great and may be good enough for now. This is a paradigm shift for us.

Taking and bringing things back to the trystorming type methodology. We make a plan and then keep trying and trying, knowing that we will have to circle around again and again.

We need a plan (even if it is dusty and/or a little rough). We then take action to get there (small goals and checkpoints). We then look at the results and make the next decision. We allow the flex but still provide some checkpoints. We do tons of mini project management stuff all the time. Maybe keep going with that and keep it going from step to step vs planning the whole voyage. We still need a vision and master plan, but keep it small and turn it into attainable steps. As a side note, if we don't get enough communication between our developers, we may need to shorten up the checkpoints and make it into smaller attainable goals and steps. Checkpoint, direction, checkpoint, direction. That would be awesome.

Such a fun conversation. We got into resource planning and management (y axis) type stuff. We want to softly start reaching out and helping our guys and gals hit their stride. A fox that chases two rabbits catches neither.

We had some more talks on the adilas community funded projects and helping to tie things into the adilas tick list (see attached for an excel file). We would like to use these two things and actually use those documents as part of the project management tools and tool sets. We also talked about pulling in a ranking (priority) and using some of the code that Bryan was working on for voting on and creating an adilas community and what they would like us to do and work on. This will be a little mini project for Steve and I. Let's use what we have and start down this little path. Yee haw!