Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
Sorry, no photos available for this element of time.
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
Media Name | File Type | Date | Description | |
PG_ReviewAndChangesNotes.docx | Doc/Text | 2/18/2025 | Notes from our session today. Near the latter part of our session today we had a big shift. How we can change Attributes into Desired Outcomes/Results - we can help show what Adilas is, what it does, et.c., etc. Some really great potential we think. Here are some of the notes from our thoughts today - this will be a big, exciting re-work. |
Notes:
|
Quick chat with Wayne about queueing up server-side processing. Talking about a quick need for simple ecommerce. This (simple ecommerce) seems to be a reoccurring theme.
Switched over to working with Shannon. Working on the formatting of presentation gallery. We spent some time talking about the attributes and results - showing some of the cool things that people are doing with adilas. Marketing, showcasing, samples, & mixing different kinds of results. We really want to cover the who, what, when, where, why, how, how many, etc. - all in the presentation gallery. Back to an original thought, about mixing business functions, application players, and core concepts to get some cool results or desired outcomes (leaning this way - changing the attributes section to be called desired outcomes). Design your own systems. Help people... that's what we do. We have a ton to offer, and we keep building and refining it every day. This change, from attributes to desired outcomes, may be a little gift (comment from Shannon). |