I love this, this is fantastic. They way this program breaks things down, tracks changes in a clear fashion, debugging and other features are done directly on the interface, even the reusability factor is impressive. I imagine how this could assist designers who learn visually, or help green engineers learn how pieces of programs talk in a clear, traceable steps. This seems like an incredibly promising program for designers and developers alike.

Showing someone how this works

I like how he advocates for tools (templates) to save time. Many in art and design fields act judgmental when a designer uses templates or tracing, I am glad to see that is changing. We are all busy and should use whatever tools benefit us.

Group A 1. designers are beginning to consider ethics and necessity instead of just profit 2. Well designed solutions can solve more than one problem at a time

• trees for clients and fish for employees
• When we design to increase accessibility, we are helping everyone, not just people with obvious disabilities

-Full list for group a in page notes-

This language gives me TV infomercial flashbacks. and It is always a pop up on more modern advertisements. I am sick of popup ads. ads in general.

I also think this can be used to manipulate people, like people remember or prefer the first thing they see, so that make sure the plans that make them the most money are positioned more prominently to clients.

You made a connection between this and headers and footers in documentation and I liked that. it also reminds me of how the human brain can only a handful of individual digits in working memory, but you can remember more if you shift them to double digits.

This is a massive issue in healthcare portals. There are so many departments in hospitals, and so many treatment options and functionalities, patients get overwhelmed, staff gets overwhelmed, and some individual curation becomes required to manage the sheer amount of information.

I looked at confirmation bias in regard to healthcare portals and doctors.

Example: Diagnosis anchoring: A physician reviews a patient’s portal history and focuses on previously documented conditions (e.g., "this patient has migraines"), potentially overlooking new or unrelated symptoms.

The portal reinforces the bias because past diagnoses are prominent, nudging the provider to confirm rather than re-evaluate.

There will always be people like that when you have a vision others cant see, he handled it with grace.

Again, I love how this works with the human brain. I have a particularly terrible short term memory, and use chunking in my life regularly, regardless of field or context. This is a great way to educate, as well as filtering information so users don't have to sift through things they don't need!

I really like this concept as it is taking human psychology into account, breaking down steps, and potentially even tying into one of the other concepts I chose, progressive disclosure. This takes human flight response and attempts to build technology in a helpful, useable way.

Progressive Disclosure I did some research on patient portals for hospitals and noticed that this is something we need more of in some places, patient portals for sure. There are so many options and so much information, sometimes its less overwhelming to build sites using progressive disclosure and focus on what the patient/user needs right now.

I am very curious to see all the ways these different facets work together to make optimally designed products and interfaces, which tools are beneficial to this collaboration and how new developments across functions could improve accessibility. Group A

I am looking forward to this part!