Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Brandon Moore
Created Date/Time: 6/3/2011 12:26 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
Finished/Done: No - (open)
Finished/Done By: ...
Budgeted/Estimated Value: 0.00  
Actual/Real Value: 0.00  
 
Time Id: 22
Template/Type: Coding Ideas & Things To Do
Title/Caption: Training - Adilas theory
Start Date: 6/3/2011
Target/Due Date: N/A
Main Status: Active

Sorry, no photos available for this element of time.


Notes:
There are tons of different adilas theory items... each one needs its own place to be talked about and shown how it plays into the process...

No specific order, just brain dumping...

Centralized data, empower the users, enter once - use many, go to the source (transactions and where the events take place), flexibility comes from settings and permissions that get interconnected, water droplets turned into slush then snow and then ice, business zipper (bring operations and accounting together one cog at a time), teach the why, track every penny in and every penny out, track objects and data over time, roll call accounting, accopps (mix and blend accounting with operations), linear checkpoints and data flow (pull), function over fashion, train and teach people not subjects, life cycle, pioneering the future of business, listen to our clients, under promise and over deliver, give to the people (there will be plenty left for us), education, train the upcoming generation(s), build a relational model, think add-on's and subs, all data is live and searchable, always up to date, no limits, your data... you cache & retrieve it... we secure it, we are one big data portal, community project and community effort, giant tool box - you get to match the tools with the jobs, 3D business model, always open and available, bridge the gap, trystorming vs. brainstorming, peace of mind, super user friendly, digital filing system, ongoing development, go mobile, touchscreen, business data sphere, play the game (rules, players, actions, goals, etc.), everything carries its own weight and luggage, return and report, users are bigger than corporations, one-to-many relationships, new school vs. old school, business platform, be your own style, catching the vision will inspire and guide you, business data mapping, start a revolution, customize your solution, put the horse in front of the cart (as compared with the cart leading the horse), see the whole picture!

Anyways, here are some other words that I needed to record... Lean, just in time, continuous flow, eliminate waste, ease of entry, precision and accuracy, flexibility, pull... all good stuff!

What if you look at things from a user's view... Does that change the "why"? "How"?... I was talking with a physical therapy guy (Sharik Peck) and we were talking about ergonomics and production (workplace safety stuff). What are the human components? If things are multiplied what does that do? Standardization helps flow. Teaching the "why" helps downstream customers and other employees. Distribute the work flow! Easy repetitive steps and processes.

There is a guy by the name of Ammon (in the scriptures)... He was a master at serving and building on common ground and common beliefs (Alma chapter 18). When showing how we are different (old school vs. new school) build on common beliefs and reasons for doing what we are doing. Try to focus on the common threads.

I've got a two page document in my notebook that goes over the progression of accounting and bookkeeping (dated 3/17/11)... Maybe instead of saying... Look what we have... Say something like "if this helps, great! If not, that's ok - we just wanted to share what we've learned." Help others help themselves. Another great quote is "Teach them correct doctrine and let them govern themselves" Joseph Smith.

Sometimes the answer is a change of perspective... the situation may be the same but your view or understanding of it changes.