AboutEmailResume
Abby G.

Hackathon

Created a product idea that helps families with sick children have better access to health information & resources.
Role:UX/UI Lead
Duration:2 Days
Tools:Figma

Hackathon

Created a product idea that helps families with sick children have better access to health information & resources.
Role:UX/UI Lead
Duration:2 Days
Tools:Figma

Design Process

Brainstorm
‍
As the lead UX team member, I offered to lead our brainstorming by putting together an affinity map of all the ideas we came up with based on our prompt.
Analyze
‍
Following the brainstorm we were able to get a good understanding of what our users needed for a successful product. Using our finding from affinity mapping, we continued to analyze our ideas by creating personas and some user stories.
Design
‍
Next steps involved the visuals. We collaborated on the overall site map of the product as well as the branding for the site. Using a play on our team name we created a simple brand design.

Design Process

Brainstorm
‍
As the lead UX team member, I offered to lead our brainstorming by putting together an affinity map of all the ideas we came up with based on our prompt.
Analyze
‍
Following the brainstorm we were able to get a good understanding of what our users needed for a successful product. Using our finding from affinity mapping, we continued to analyze our ideas by creating personas and some user stories.
Design
‍
Next steps involved the visuals. We collaborated on the overall site map of the product as well as the branding for the site. Using a play on our team name we created a simple brand design.

Brainstorm

Affinity Mapping

To kick off our research, I had the team jot down anything that came to mind related to the ultimate goal of our product.

This encompassed specific individuals and broad concepts reflecting how we could address their needs.

We then organized these ideas, pinpointing common themes to construct a problem statement that outlines the essential elements for a successful product from the user's perspective.
Problem Statement
‍
Users need a log in platform that allows the user to store health information while getting 24/7 access to relevant resources about childhood cancer and family life during/after treatment.

Brainstorm

Affinity Mapping

To kick off our research, I had the team jot down anything that came to mind related to the ultimate goal of our product.

This encompassed specific individuals and broad concepts reflecting how we could address their needs.

We then organized these ideas, pinpointing common themes to construct a problem statement that outlines the essential elements for a successful product from the user's perspective.
Problem Statement
‍
Users need a log in platform that allows the user to store health information while getting 24/7 access to relevant resources about childhood cancer and family life during/after treatment.

Analyze

Personas

The team narrowed our focus to three target users, aiding us in swiftly progressing through the process. This streamlined approach contributed to our overall understanding of what's necessary for a successful product.

Emily
Age: 47
Job: Grocery Clerk‍

Goals:
> Access platform/site from any type of device
> View resources by type to understand difference of what each have to offer
> Talk with other parents ‍

Martha
Age: 33
Job: Bank teller‍

Goals:
> Access to spanish language resources
> Ability to update child’s health information
> View people’s ranking of certain resources‍‍

Michael
Age: 64
Job: Teacher‍

Goals:
> Add multiple patients health information
> Access information on finances
> Ability to access content/resources after hours‍‍

Frustrations:
> Not finding most up to date resources

Frustrations:
> Search results not precise or too many so takes long time to find answers

Frustrations:
> Can’t talk to a real human to ask questions or get more information

Analyze

Personas

The team narrowed our focus to three target users, aiding us in swiftly progressing through the process. This streamlined approach contributed to our overall understanding of what's necessary for a successful product.

Emily
Age: 47
Job: Grocery Clerk‍

Goals:
> Access platform/site from any type of device
> View resources by type to understand difference of what each have to offer
> Talk with other parents ‍

Frustrations:
> Not finding most up to date resources

Martha
Age: 33
Job: Bank teller‍

Goals:
> Access to spanish language resources
> Ability to update child’s health information
> View people’s ranking of certain resources‍‍

Frustrations:
> Search results not precise or too many so takes long time to find answers

Michael
Age: 64
Job: Teacher‍

Goals:
> Add multiple patients health information
> Access information on finances
> Ability to access content/resources after hours‍‍

Frustrations:
> Can’t talk to a real human to ask questions or get more information

User Stories

The team narrowed down our personas to three target users. Keeping these diverse individuals in mind allowed us to progress efficiently, deepening our overall understanding of what's needed to create a successful product.

User Stories

The team narrowed down our personas to three target users. Keeping these diverse individuals in mind allowed us to progress efficiently, deepening our overall understanding of what's needed to create a successful product.

Design

Sitemap & Sketching

Our next move involved synthesizing all the information into a cohesive design. We used a sitemap to guide the structure, determining the number of pages and their placement to ensure a robust product that fulfills all user needs.

Mockups

Solidifying ideas was a crucial step in our process. Drawing from initial sketches and incorporating input from potential users, we mapped out more concrete page ideas for the product. This allowed developers and engineers to gain a clearer understanding of what our team was creating for the users.

Branding

Branding became a collaborative effort inspired by our team name, The Thunderfrogs.

Building on the name, we chose a lilypad as a straightforward icon, complemented by a medical cross. The color palette drew directly from the frog and lilypad theme.

Font choices were simple and clean, suitable for any standard medical site scenario.

Prototype

Right before the big presentation of our product solution, we nailed down the details by creating a basic prototype. This gave us a sneak peek into how we envisioned the product to look and function.

Design

Sitemap & Sketching

Our next move involved synthesizing all the information into a cohesive design. We used a sitemap to guide the structure, determining the number of pages and their placement to ensure a robust product that fulfills all user needs.

Mockups

Solidifying ideas was a crucial step in our process. Drawing from initial sketches and incorporating input from potential users, we mapped out more concrete page ideas for the product. This allowed developers and engineers to gain a clearer understanding of what our team was creating for the users.

Branding

Branding became a collaborative effort inspired by our team name, The Thunderfrogs.

Building on the name, we chose a lilypad as a straightforward icon, complemented by a medical cross. The color palette drew directly from the frog and lilypad theme.

Font choices were simple and clean, suitable for any standard medical site scenario.

Prototype

Right before the big presentation of our product solution, we nailed down the details by creating a basic prototype. This gave us a sneak peek into how we envisioned the product to look and function.

Conclusion

What I Learned
Hackathons are an incredible opportunity for skill development. Collaborating closely with teammates from diverse job specialties gave me valuable insights into their thought processes, allowing me to see my own designs from different perspectives.

Prioritization emerged as a crucial skill during the hackathon, as time constraints pushed me to navigate the balance between perfection and progress. Quickly adapting to moving on to the next task or skipping less critical steps for the sake of project advancement was a significant learning curve.

‍

‍

‍



‍
Challenges I Faced
Embarking on my first-ever hackathon, I was a bit unsure about what I was diving into. The main challenge was wrapping my head around the hackathon process while jumping right into the work.

Another hurdle was the team size. More teammates meant more opinions, and although diverse perspectives are valuable, too many voices can slow down the process.

Conclusion

What I Learned
Hackathons are an incredible opportunity for skill development. Collaborating closely with teammates from diverse job specialties gave me valuable insights into their thought processes, allowing me to see my own designs from different perspectives.

Prioritization emerged as a crucial skill during the hackathon, as time constraints pushed me to navigate the balance between perfection and progress. Quickly adapting to moving on to the next task or skipping less critical steps for the sake of project advancement was a significant learning curve.
Challenges I Faced
Embarking on my first-ever hackathon, I was a bit unsure about what I was diving into. The main challenge was wrapping my head around the hackathon process while jumping right into the work.

Another hurdle was the team size. More teammates meant more opinions, and although diverse perspectives are valuable, too many voices can slow down the process.
AboutResumeEmailHome
Abby G.