Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 9/13/2019 3:55 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4957
Template/Type: Brandon Time
Title/Caption: Meeting with Jonathan
Start Date/Time: 9/13/2019 4:00 pm
End Date/Time: 9/13/2019 5:15 pm
Main Status: Active

click to enlarge - photo by: Brandon Moore - Screenshots of some of the mapping of the system. He is starting into elements of time.
click to enlarge - photo by: Brandon Moore - Zoomed out view of some of the mapping. Showing elements of time, financial, and flex grid stuff.
click to enlarge - photo by: Brandon Moore - Some of the mapping done on the financial side of the puzzle.
click to enlarge - photo by: Brandon Moore - Different view of the links and pages on a spreadsheet and/or flat file list. Page inventory per main section.
click to enlarge - photo by: Brandon Moore - Another flat file list of a different section.
click to enlarge - photo by: Brandon Moore - Drawing lines and putting pieces together. Jonathan is trying to figure out what goes where and how best to display all of the pieces without duplicating work and effort.
click to enlarge - photo by: Brandon Moore - Zoomed out view of some of the mappings.
click to enlarge - photo by: Brandon Moore - Small breakthrough for Jonathan. Originally, he was thinking that a certain page had an owner (one of the main player groups). He is now seeing that some of the pages and navigation links go to shared resources and are more of a pointer to that location.
click to enlarge - photo by: Brandon Moore - Future areas to map out within the system.


Uploaded Media/Content & Other Files (3)
Media Name   File Type Date Description
world building help file   Web/HTML 9/16/2019 This is a help file link to introduce the GPS core layout for adilas. This deals with concepts of 3D business world building and what not.
interactive map help file   Web/HTML 9/16/2019 This is a help file explaining what is on the adilas interactive map and why we put things next to certain things (why the layout we chose).
players_object_lesson.pdf   Doc/PDF 9/16/2019 This is a simple comparison between the human world and the adilas world. It talks about how we store data and how we use a concept of a bucket and/or platter to hold all of the peices of data that relate to a single item and/or object inside of adilas.


Notes:

Great meeting with Jonathan. Dustin was on the entire time. We also had Steve for the first half an hour. Here a few notes from the meeting.

- Jonathan is working on mapping things out and getting them organized by colors and by main players.

- Our users can't consume the massive amount of options and functionality.

- The system is somewhat of a labyrinth or giant puzzle. You could literally click and click and virtually connect everything together. That is both good and bad, in some ways.

- Jonathan really wants to help us simplify things.

- Currently, he is somewhat taking inventory - listing out links, sub homepages, navigation, processes, etc.

- Meaning of a location or who owns what - originally, he was thinking about each link and/or navigation as being owed by one player group or another. As he got deeper and deeper, he started to think of some of these pages and sections like locations and multiple ways to get and/or point to that location. Instead of it being owned by a certain party (invoices, depostis, PO's, customers, etc.) it was more of a shared asset and multiple parties used the same resources, just maybe in different ways.

- He is making a spreadsheet or flat storage of page names - resource list - what is available?

- Currently, inside the system, if you click on a certain link, you get all of the rest of the sub luggage that goes along with those sections. He would really like to help limit the amount of extra stuff (even if it belongs) and keeping the navigation on a more digestible level.

- There were a number of comments about the availability to bounce and jump from place to place. That is cool if you know what you are doing. If not, you could get lost really quickly. As a fun side note, I was telling Jonathan that we grew up like this (able to bounce), using navigation that is non linear, non conventional, and allows for jumping from place to place.

- Steve brought up permissions and how that actually affects the navigation both display and show/hiding of different links. Jonathan didn't know that certain greyed out links were tied to permissions and/or that certain navigation options either show/hide themselves based off of permissions.

- Steve was also really excited to keep Jonathan on the project of mapping and/or listing out all of the options that are available. You could almost see Steve sales side coming through as he was talking to Jonathan about the possibilities, if we had everything all mapped out, organized, and listed in an approachable format. Tons of potential there.

- We talked about training wheels, guide rails, and other ways to help new users out inside of the system.

- A quote directly from Jonathan - "Streamlining to me, is removing the complexity."

- We talked about prototypes, direct market tests, and doing other things to figure out more information about what is needed, wanted, and most used features. This also includes where people got lost, what they don't use, and what they don't know. Both side of the fence.

- There were some talks about the currency of data and valuable that is. We talked about the benefit of gaining and organizing that data into smaller chunks, analytics, stats, etc.

- The deeper we get, the more you have to adopt a "system thinking" mentality. It becomes possible, because you are in a system vs standalone mini pieces of the puzzle.

- Jonathan was encouraged to keep looking for reoccurring patterns and helping to expose those pieces. We also talked about if we could show how things fit together, and how those reoccurring patterns play in, it would help with education and getting users oriented faster.

Towards the end of the session, I was showing Jonathan a couple of models dealing with how we organize the system. I showed him the simple plates and cups model and how we tend to track all of the main pieces in a similar format. We had some good training and went into a live system and looked up expense/receipts, invoices, deposits, PO's, etc. We did some training on natural connections, flex grid tie-ins, and how each player group has similar ways of tracking and recording those pieces that make it up. Just for fun, we pulled up a small mini graphic of the plates and cups model, and then drew lines from what we had and/or saw to what that would look like in the plates and cup model. It is hard to write about it, but it works better as a show me exercise where we flip screens, check stats, and then show how that looks in the model. We also briefly talked about how a dresser with drawers type model could do the same thing.

See attached for some screen shots and other pieces.