Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Shannon Scoffield
Created Date/Time: 8/13/2013 6:28 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 1184
Template/Type: Daily Ideas
Title/Caption: Daily Ideas
Start Date: 4/9/2013
Main Status: Active

click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
 


Notes:
Recap of meeting with my sister to talk about training and direction: Developer’s notebook
-Protect ourselves by sharing!
-Concepts inside of adilas are 10x (times) greater than the code.
-Visually display the concepts (photos, animations, video, etc.)
- Provide the history and story
o Nested to details
- Brainstorming notes
- Developer’s notebook
- Actual ideas and working pieces
o (Sketch in notebook of brick wall – foundation piece being things like: time, permissions, settings; the next level: data, empower users, etc., etc.)
-Concept based learning
- Each concept needs a story
-Abundance Model – “enough to go around” – sharing
-Tie or connect through feelings or feeling a part of the story.
-“See a need, fill a need” (movie – Robots) – This is a “base”
- As a need is filled it creates a new something or something new
-What about an interactive timeline
-Concept Buffet
-Animated Timeline or story
-The movie “Up” – see entry from 1/5/13 to 1/8/13
-We’d like to show the development of these concepts in two ways. –By Concept –By Timeline
-Teach the “why”
-When recording data (actual pieces) we will need two or more pieces… what concept or subject (players) and what timeframe.
-Figure out the core concepts – we started out with about 20, then decided to go to 10, and then the list kept growing and growing. Kind of started going in circles. I took the assignment to come up with the master list of concepts and sub concepts.
-For the record, here are a few things we scribbled down:
- Centralizing data
- Going to the source
- Empowering the user
- Permissions and settings
- Objects and data over time
- One-to-many relationships
- “See a need, fill a need” – “base” or foundation
- Next logical step – development
- Systems thinking
- Games (rules, players, goals, challenges) game of business
- Data
- adilas – all data is live and searchable
- Dynamics
- Relationships
-Other core concepts that we were listing out:
- Education and sharing
- Types and functions (“why” or building blocks)
- Roll call – what is your story – return and report
- Record the story – the story may be more important than the numbers
- Scalability
- Custom
- Dreaming
- Players
- Culture, vocabulary, change
- Put things to rest “life cycle”
- Mix & blend (we mix concepts and players to create flow, processes, and interface)
- Catch the pieces
- Data mapping
- Peace of mind
- Point the picture – vision of the future
- Open entry, open exit (no contracts, pick & choose, only use certain pieces, etc.)