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_history_bio.pdf | Doc/PDF | 4/25/2016 | brief adilas history document - 6 page pdf | |
|
Notes:
|
|
On a phone call with Steve. The whole thing was dealing with funds, direction, where things are working, where things are breaking, and where things are potentially fracturing but still working. A lot of our time was spent talking about people and expectations. We talked about the independent model, employee models, hybrid models, etc. We are trying to figure out the balance between what we need and want and what we have. Good conversations. We talked a ton about how some of the custom projects help us fund the future growth of the company. At the same time, they pull us off of the main core projects and prevent maintenance and normal processing. Not enough resources to go around. Everybody gets spread thin. There are pros and cons on both sides of that fence. We'll keep going and see how it works out. We are kinda experimenting right now. We've got a ton of things lightly in place, we just need to let things mature and stabilize (normalizing process). Basically, just keep going and make small correcting strokes as we go. That felt good to feel like we are at least going on the right path. Here are some other small notes that I took from the conversation: - Let the system be the bad guy. - Let it (the system) say yes or no based on rules and expectations. We have done this before and it was a huge area that helped us out (way back to original projects and timelines). This takes defining the playing field, setting rules, figuring out who and what, and then enforcing those rules. See this PDF for some of the original start-up notes. https://data0.adilas.biz/adilas_history_bio.pdf |