all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
| Media Name | File Type | Date | Description | |
| adilas_stats_features_and_plans_12_6_16_playing_with_steve.xlsx | Doc/Spreadsheet | 12/7/2016 | This was a subject of discussion on 12/6/16 between Brandon and Steve. We were playing around with numbers and concepts of how we want to structure the adilas family and the future of what we are doing. Fun ideas and concepts. See the last two tabs for ideas on what we were talking about. | |
|
Notes:
|
|
On a GoToMeeting session with Steve. We spent the whole time talking about ideas and future strategy stuff. We even bounced around adilas looking at reports, numbers, and small trends of what has been going on. That was fun. We ended up on an Excel spreadsheet playing with numbers and such. Nothing official, just playing with ideas. See attached for the sheet that we were playing with. It is kinda random and has notes all over it. See the tab called projections and the tab called Sheet1 for where we were playing. We kept going back to a quote by Shannon Moore about adilas - "The solution may need to be as creative and flexible as adilas is." We talked about employees, dependables, key players, dream it up as we go, make a plan, map it out, and setup the rules and cause and effects to allow things to play through (Steve related that to a game called marble drop - gravity fed with multiple cause and effect things). We then talked about the adilas family and what that means and is. We talked about the independent helpers, the full time family, and the people who help found and/or build the company. We talked about ownership, compensation, commissions, and percentages of gross revenue. We are looking for people who are good workers and are loyal. We would love to say there are more founders and key players that have help to build the adilas platform. Let's let the people who want to play, come in and play. We talked tons and tons about education, paid and non paid classes, certification levels, schedules, and venues for training. That could be big part of the business all by itself. We talked about getting Shannon some help with tech support and training. We talked about existing players and how we could cater to them and make a flexible plan for keeping them around and happily fed. We want those who want to play to be able to stay and play as long as they like. We talked about some of the pains and knowledge that we have learned along the way. Decisions, good, bad, ugly, etc. We want to push the ball forward. At the same time, it is ok to let it keep going and/or growing slowly (organic growth). Keep dreaming, building, and taking the try storming approach. It is ok to make multiple attempts and circle back again and again. Good stuff. We went over some numbers, ideas, and concepts of revenue sharing. We also talked about virtual adopting into the adilas family, requirements for being part of the family, and ideas on how to make things dynamic and flexible, yet still manageable and able to be evaluated. We even talked price tags and costs of what it would cost to get a really good lead developer/project manager person in place. Kind of a right hand guy for me and what I do. Lots of fun ideas and playing with numbers, percentages, projections, and pay levels. We are looking to make and create a fun and interactive game-type pay structure. It will have a little bit of a loyalty points, active requirements, and compensation for effort put in to help make things better. We are talking a mix between time put in, contribution, efforts, team player, hourly rates, base level salaries, revenue sharing, virtual ownership, etc. At the end of the session, Shawn Curtis, one of our developers popped in. I went over a few of the ideas and concepts with him. He mentioned that the profits are in the margins. Sometimes just tiny tweaks make it sing. Also, while I was talking with him, I was thinking that it might be good to keep building this process out over the next couple of years. Take our time. We ended with the concept of planning and mapping things out. As a funny side note, we started to map things out back in 2010. That process opened up a ton of the things we are working on and building off of right now. I'd love to circle back around and make a master plan for the whole system. If there is a plan in place, than others can follow it and be a part of it going forward. Keep it open and flexible but defined enough (sufficient for your needs) so that it has some structure. Great session. As a note, the Excel file is attached if more info is needed. |