Emails and recording time. Other small odds and ends. Reviewing and planning the new site for the food pantry. Added some new verbiage to the adilas value add-on core model (master plan).

As part of my review, I was re-reading over some plans that I was working on with ChatGPT for the food pantry - https://chatgpt.com/share/6a5287b4-8b28-83e8-9057-76e9a8d209cb

Here are some of my notes from reviewing the prior chat session:

- Industry adaptation project

- Guided experience for one specific workflow

- Not software... more of a "Volunteer Operations Console"

- At the software level... What do I need to know right now? Try to stay ahead of them.

- Goals: 1. Simple client intake - paper and online - make it simple, 2. Find people instantly (by name, address, barcode, and household), 3. Protect volunteers - alerts and possible workflow disruption feature, meaning, we may need to stop the normal flow until the alert is dealt with or acknowledged, 4. Track visits, and 5. Future client app - this may be a round II or phase II option. Focus on the MVP first.

- Workflow mapping - what do they actually do and in what order?

- This is an MVP bridge type app - keep one platform, create a focused front-end, hide complexity, expose power only when needed, and let organizations grow into the larger ecosystem.

- Mini skin framework - industry specific recipe map - ingredients, workflows, industry adaptation, and generate desired outcomes.

- Serve people over software - focus on the people and serving them

- Look for moments vs screens - aka "Workflow mapping" - Think flow and questions and how can I help vs just interface and software.

- Plan it, meaning this mini project framework, as a case study or industry recipe

- Industry recipe maps and world building - somewhat interchangeable terms - this was a new discover for me. I personally like world building better, but if someone is struggling with what that means, you could always say something like: Another term for world building is "industry specific recipe maps". Instead of selling specific modules or software pieces, you assemble industry specific solutions from a number of proven components. You take business functions and application players (like customers, invoices, inventory items, vendors, etc.), mix them together and these become your ingredients. You then setup specific workflows, industry adaptation, and generate desired outcomes. It becomes an industry specific recipe of sorts.

- Think reusable blueprints - per industry