Empathy Bytes logo

Exhibit #1

Empathy Bytes

Note: You can use the i button (bottom right) to navigate the page too!

Overview

My Role

Frontend Web Dev Team Lead

UX Designer and Engineer

My Team

Project Supervisor

Backend Web Dev Co-Lead

Web Dev Team

Tools

Figma, Notion, Discord

Code

GitHub, GatsbyJS, React, GraphQL, Drupal

What is Empathy Bytes?

"Empathy Bytes is a student-run research project working with the GT library to focus on creating immersive technology and media centered around empathy and researching distinct communities connected to Georgia Tech."

Meet the Empathy Bytes Web Team
Part of an Instagram post I created for our Web Team the previous semester when I was also part of the Media Team.
Meet the Web Team
What the Empathy Bytes Web Team Does
We also showcase interviews, research, and each of the teams' progress.
What we do: We create the website showcasing each of the teams' hard work!

Overview

My Key Impacts

There were several things I achieved as a frontend team lead. Here are the numbers:

Improved user experience for

15+

pages and elements

Directed a team of

10+

EB members

Increased team output by

79%

from prior year

I also created an update style sheet and improved the team's programming experience through organizing the code.

Problem Space

Problem Space

What We Were Working With

I had to balance team leading, programming, and designing. This is why I had to organize and map out the problem space with two categories in mind: UX Design/Engineering and Leadership.

  • Only about 5 months to work on our goals with bi-weekly all-teams standups
  • As a GT Vertically Integrated Project, members frequently joined and left each semester, limiting returning experience
  • Many of the new members had little experience with web development
  • Members had other commitments to focus on as they were all GT students
  • I was still learning how to do web dev myself
  • External
    • Georgia Tech Librarians and Archivists
    • Students looking to join Empathy Bytes
    • People interested in EB's work and research
  • Internal
    • The Web Dev Team who are programming and managing the site
    • The other EB Teams (App, VR, Media) looking to showcase their work
Crosland Tower library
  • Improving the Website
    • Refining the site's visual clarity and access
    • Updating the site to reflect EB's current projects
    • Finding shortcomings in the site's functionality
  • Improving Programming Productivity
    • Designing tickets for the team with clear instructions
    • Making it easier for future programmers to do work on the website
  • Basic functionality and formatting of all main pages and navigation
  • Some page redesigns ready for development
  • Design aesthetics and style of website
  • Foundational programming structure and organization

Problem Space

What We Had

The Empathy Bytes website homepage
In the solutions section, you can see other changes to the site.

In the previous semester, we also had updated the home page and navigation system.

Figma design work for the Empathy Bytes website
As much as I wanted to change the Figma system, it was lower on my priorities. Luckily, there was still order to this chaos.

We used Figma for designing and had always made sure to cross reference when redesigning.

Problem Space

What We Wanted to Achieve

We decided to assign members to specific main goals so that all goals made progress and to ensure clear collaboration among those working on the same goal. Each person was given 2-3 goals to work towards.

Frontend

  • Dynamic Sizing
  • Redesign

Backend

  • Dynamic Updates
  • Backend Investigation

Both

  • Implementing Page Features and Redesigns
  • Miscellaneous
  • Onboarding

Problem Space

Key Design Issues

As much as I would have liked to build new features, there were a couple of issues that were long overdue...

Also, hover the pictures to learn more!Also, click on the pictures to learn more!

Unfriendly Mobile Interface

Problem:

Previous members did not use dynamic sizing units that resize elements based on screen size while programming. This was esepcially problematic for visual clarity and navigatability for different screen sizes.
Picture of improper sizing
Unfriendly Mobile Interface

Unfriendly Mobile Interface

Problem:

Previous members did not use dynamic sizing units that resize elements based on screen size while programming. This was esepcially problematic for visual clarity and navigatability for different screen sizes.

Unused Components and Redesigns

Problem:

There were redesigns and unused components not currently implemented or polished. This was especially problematic for users accessing features and for the team to move on.
Screenshot of VSCode editor. It is not an actual screenshot of the website's code.
Unused Components and Redesigns

Unused Components and Redesigns

Problem:

There were redesigns and unused components not currently implemented or polished. This was especially problematic for users accessing features and for the team to move on.

Redesigning Old and Outdated Pages

Problem:

Since there was a lot of focus on the main pages, many of the sub-pages were severely outdated and still followed the first iteration of the site's style. This was especially problematic for both consistency and legibility since this old style was meant to be placeholders for a more established design.
A broad screenshot of the Empathy Bytes Figma
Redesigning Old and Outdated Pages

Redesigning Old and Outdated Pages

Problem:

Since there was a lot of focus on the main pages, many of the sub-pages were severely outdated and still followed the first iteration of the site's style. This was especially problematic for both consistency and legibility since this old style was meant to be placeholders for a more established design.

Problem Space

Key Team Issues

The previous team structure was good enough for a group of 3-4 people. However, as the team and workload continued to grow past that, several things needed to change...

Also, hover the pictures to learn more!Also, click on the pictures to learn more!

Undefined Style Guide

Problem:

Although the site’s style was present, the lack of an updated and defined style guide led to guesswork for exact component sizing, colors, and styling. This was especially problematic for consistency.
Screenshot of the style guide document.
Undefined Style Guide

Undefined Style Guide

Problem:

Although the site’s style was present, the lack of an updated and defined style guide led to guesswork for exact component sizing, colors, and styling. This was especially problematic for consistency.

Historically Unclear Ticket Instructions

Problem:

Tickets didn't define goals/constraints and developers had to often interpret requirements on their own or constantly ask leads for clarity. This was especially problematic for members that were new and/or inexperienced in web dev.
Example of a ticket I made.
Historically Unclear Ticket Instructions

Historically Unclear Ticket Instructions

Problem:

Tickets didn't define goals/constraints and developers had to often interpret requirements on their own or constantly ask leads for clarity. This was especially problematic for members that were new and/or inexperienced in web dev.

Poor Communication

Problem:

Previously, members were largely left to their own devices, leading to little team interactions and participation. This was especially problematic for team dynamics and reports on accomplishments or problems.
Communication corporate illustration
Poor Communication

Poor Communication

Problem:

Previously, members were largely left to their own devices, leading to little team interactions and participation. This was especially problematic for team dynamics and reports on accomplishments or problems.

Solutions

Solutions

Solving Design Problems

For improving website user experience, we focused on feel and functionality. For each of these problems, I detail what I did personally within the "Learn More" button.

Picture of improper sizing
Overflow and overlap were common across all pages. I tried to fix as much as I could within the time we had.

Dynamic Sizing

Creating Dynamic Responsiveness...

Our biggest “feel” issue is the lack of mobile support since users are likely to check out EB through their phones. This problem would only worsen as the site continues to build if not addressed promptly.
A broad screenshot of the Empathy Bytes Figma
For designs, we used Figma to plan and create low to high fidelity prototypes.

Redesigning

Collaborating on and Reviewing Redesigns...

We created, reviewed, and then finalized designs in Figma before it moved to the implementation stage. We wanted to make sure we were also still updating the outdated portions of our website.
Screenshot of VSCode editor. It is not an actual screenshot of the website's code.
We used VSCode as our code editor. (Not actually a screenshot of the site code)

Implementing

Developing the Website Code...

In order to launch the website to production, we have to first program it. Implementation of our designs and ideas through code is the more technical part of our process but I won't go into that much here.

Solutions

Building Team Structure

To make as many of our design goals a reality, it was really important to improve our team structure.

Screenshot of the style guide document.
We used Google Docs to write up our style guide (as well as other documents).

Style Guide

Updating the Outdated...

One of the main goals for the team was to create an updated and detailed version of our style sheet. We questioned what stylings needed to be centralized and consistent across all pages.
Example of a ticket I made.
Example of a ticket I made

Tickets

Creating Clarity in Tasks...

We used Notion for ticket making and delegation. At first, I wanted to use a simpler application but we found it best to stick to Notion for documentation and accessibility purposes since we already had been using it previously.
Communication corporate illustration

Communication

Increasing Team Participation...

Previously, all our forms of communication went really quiet and discouraged members from talking. As a lead, I had to find ways to enforce communication and encourage newcomers to ask questions.

Dynamic Sizing

Largest GoalImprove AccessibilityEnforce Good Coding Practices

Picture of improper sizing
Creating Dynamic Responsiveness...

Our biggest "feel" issue is the lack of mobile support since users are likely to check out EB through their phones. This problem would only worsen as the site is built if not addressed promptly.

We got pretty far into this goal in the end but couldn't implement it all into the production site. This is why one of our team goals was to create a style guide and knowledge board for the next semester's team.

What I Did
As the team co-lead that mainly oversaw frontend, I had to address the misuse of sizing units that were scattered across all of the programming files. This included fixed pixel dimensions for layouts and size estimation among other responsive problems.
Deciding the Pages

With the time we had, we couldn't do all the pages. I collaborated with my fellow co-lead to decide which pages to make responsive (or at least rework designs).


The Questions...

Our choices:

  1. Home
  2. About
  3. Projects
  4. Contact
  5. Individual Team Pages

**plus navigation bar and footer

The navigation side bar for mobile showing all the pages.

Common Problems (and Proposed Solutions)

  1. Components didn't stretch/shrink based on screen size due to the code not using the appropriate sizing unitsSolution: Rewrite parts of the code with dynamic sizing units while still maintaining its original format and design

  2. Formats that felt good on desktop look crowded on mobileSolution: Redesign the mobile version of the pages and reduce length of descriptions and text

  3. Interactions were unfriendly to mobile usersSolution: Research good mobile UI/UX practices and implement them alongside the redesign
A screenshot of a previous code review where the reviewee did not use dynamic sizing. They said, "I might be testing your work wrong, but this what I see when I shrink to a smaller screen. I was expecting the footer shrink in terms of the screen width, but some of the footer gets cut off."A screenshot of a previous code review where the reviewee did not use dynamic sizing.

They said, "I might be testing your work wrong, but this what I see when I shrink to a smaller screen. I was expecting the footer shrink in terms of the screen width, but some of the footer gets cut off."
Steps Taken
Here are the steps I took as the frontend lead to make dynamic sizing happen:
Example of a ticket I made.

Step 1. Make Defined Tickets

For each page, I noted what the problems were and the types of changes that could improve mobile accessibility.

I also checked the code behind them to see if it followed proper programming practices and used dynamic sizing units (rem, vh, etc.) This way, I had enough information to create tasks to give to the rest of the team.

Step 2. Redesign for Mobile

Some pages only required code updates to their sizing units to improve readability whiles others required us to fully design its mobile version.

Example (right)

I decided to switch the Projects page to a 1-column layout to prevent each card from become too skinny. Several similar layouts also got this treatment for readability in addition to consistency.

Additionally, I had the old navigation bar replaced with a classic mobile pulldown navigation bar for a cleaner, mobile-friendly look.

A broad screenshot of the Empathy Bytes Figma
Screenshot of VSCode editor. It is not an actual screenshot of the website's code.

Step 3. Implement via Code

This last step was actually programming the component into the production site. Since we mostly focused on the redesign and cleaning the code, there were several items that didn't get fully developed but were noted.

Most of my work in implementation was cleaning and replacing code related to responsiveness.

I also did various edits to the code to make sure pages were accessible such as the 404 error and experiences pages.

The Impact

Following these changes, we noticed a huge improvement to site accessibility and approval from both users and members.

Users can view the website on their phones or from various screen sizes

Users can easily navigate through new mobile user interfaces

Members have less confusion about layout bugs when reviewing code

Since we only had a semester to work on this, there was still a bit left to do for dynamic sizing. I made sure there was proper documentation and notes for future fixes to layouts.

Redesigning

Update the OldUse New Style GuideImprove User Experience

A broad screenshot of the Empathy Bytes Figma
Collaborating on and Reviewing Redesigns...

We created, reviewed, and then finalized designs in Figma before it moved to the implementation stage. We wanted to make sure we were also still updating the outdated portions of our website.

Redesigns allowed us to improve the aesthetics and user experience for our website. These were done in our Figma design space for both mobile and desktop sizes. Members created, reviewed, and then finalized designs before it moved to the implementation stage.

Example of My Work
I collaborated with another member to redesign and update the about pages for each of the Empathy Bytes teams (Media, Web, VR, and App).
A screenshot of the real ticket.

Click outside the picture to exit.

Our Ticket

We were tasked with updating the information and redesign the individual team pages.

Goal: Increase the readability and structure to better align with the style guide.

Previously...

  1. There was lot of negative space and not much separation from the background nor contrast within the content.
  2. It didn't support dynamic content and required developers to always change the code rather than our content management system (Drupal).
  3. It was inconsistent with current style/branding of the site.
Previous Web Team page design with the listed problems.

Click outside the picture to exit.

Previous App Team page design.

Click outside the picture to exit.

Screenshot of the style guide document.

Keeping Consistency

We decided to make a template first to ensure all the info needed was there and that the pages were consistent amongst themselves and the rest of the site.
Our Changes
For the template, we wanted to establish a better visual hierarchy and provide more contrast to improve readability. We decided to keep the original key sections but also make room to add team-specific sections and examples of their work.

The redesigned team page template with annotations describing each change
The redesigned team page template with annotations describing each change

Click outside the picture to exit.

We got a template...

But what was next?

We had to design each team page following our design, of course!

While we were creating the template, I had contacted each of the four EB team leads for the following:

An updated "About" description and tools used

Pictures, videos, and assets of their projects

Any extra sections needed to best show their work

We also proof-read to ensure that the descriptions weren't too long and if any assets needed to be changed or of higher quality.

Our Final Results
We went back and forth with our team leads about our design for feedback and approval. This iterative process allowed us to create what we now see below. Then, it was sent off to be implemented to the production site.

Click on the images to see them more closely.
The redesigned Web Team page

Click outside the picture to exit.

The redesigned Media Team page

Click outside the picture to exit.

The redesigned App Team page

Click outside the picture to exit.

The redesigned VR Team page

Click outside the picture to exit.

Implementing

ProgrammingFor ProductionPublicly Seeing Improvements

Developing the Website Code...

In order to launch the website to production, we have to first program it. Implementation of our designs and ideas through code is the more technical part of our process but I won't go into that much here.

Screenshot of VSCode editor. It is not an actual screenshot of the website's code.Not a real screenshot of the website's code

Programming Tech Stack

  1. GatsbyJS
  2. GraphQL
  3. Drupal

Gathering Ticket Topics

I would write up programming tickets that EB members would assign themselves to. These were written as website bugs were discovered and as redesigns were completed.
Example of a ticket I made.
VSCode Logo

Implementing

Members would follow EB's programming practices and find a way to make the ideas/redesigns come to life.
VSCode Logo

Review

Members would put their code up for review by others. Once approved, the updates join the main project and go live for everyone to see.

Style Guide

DocumentationImprove ConsistencyStart Centralizing Styles

Screenshot of the style guide document.
Updating the Outdated...

One of the main goals for the team was to create an updated and detailed version of our style guide. We questioned what stylings needed to be centralized and consistent across all pages. This targetted the inconsistency problem on a more foundational level especially when the team continues the work in the future.

Setting the Foundation

We collaborated with the media team lead for a consensus of how the website and its content should be styled / sized. We decided to keep the general style of the website but define any sizing/styling requirements for each page.


Style Guide
We focused on the basics so that future team leads didn't need to worry about it and so that they can easily add clarifications or updates.

We covered:

  1. Colors
  2. Font
  3. Components
  4. General CSS Styling
  5. How to Word Things
  6. Pictures/Assets
Screenshot of hte color palette.

The Impact

This document was key to future updates to design and layouts.

Faster onboarding process for the next project cycle

A clearer design standard with no guessing

Better visual consistency and clarity of information

Following these changes, members had a better idea of EB's branding and coding practices.

Tickets

Help New MembersInstructional ClarityInform Developers

Notion's logo
Creating Clarity in Tasks...

We used Notion for ticket making and delegation. At first, I wanted to use a simpler application but we found it best to stick to Notion for documentation and accessibility purposes since we already had been using it previously. Tickets were picked on a first-come-first-serve basis and we made sure all current tickets had somebody working on them.

Problems
Although there was documentation of accomplishments, the Notion and AGILE methodology weren’t properly used as intended:
  1. Tickets weren’t being consistently made by team leads
  2. Tickets didn’t properly outline a defined goal nor the constraints that the programmer needed to follow
  3. Members were encouraged to find and fix problems individually
  4. Sprints weren’t being updated to the next on Notion
Example of a ticket I made.
Ticket Design
We wanted to ensure members understood their tasks without having to do guesswork or asking for clarifications.

Ticket Goals

  • Smooth onboarding for newer members who may be doing web dev for the first time
  • Tackle unfamiliarity with working in bigger projects and AGILE methodologies
  • Increase efficiency and learnability
  • Decrease ticket confusion and guesswork
  • Better organization of project goals and tasks

Ticket Contents

  • Have a clear description and/or instructions
  • Connect ticket task to a main goal
  • Organization of content and clear prioritization
  • Include any necessary links or pictures that show the task problem
  • Constraints and files to change
Screenshot of the Web Team Plan document

Ticket Timeline

We had 2-week long sprints with the first sprint spent onboarding and figuring out team logistics.

Me and my co-lead decided to include more instructions in the earlier tickets to act more like a tutorial for those onboarding (and eventually phase it out). This gave more clarity and direction for how to complete the tasks.

Web Team Plan

Balancing Tasks

However, we did need to be careful that us team leads weren’t spending too much time making tickets. As time went on, included less hand-holding instructions on the assumption that members were now used to the codebase, expectations, and work flow.

I also had created a basic template to work off of for each ticket and some parts were copy/pasted if they were relevant.

Example of an earlier ticket

The Impact

Following these changes, we noticed an improvement to participation and task completion.

79% more tasks and goals completed than previous semester

Better task delegation, management, and documentation

Tangible and significant progress to the main goals

Members also gave positive feedback on the ticket system and instructions. They also used Notion more for task management which is good for documenting for future references.

Communication

Increase Team ParticipationPromote DocumentationEncourage Questioning

Increasing Team Participation...

Previously, all our forms of communication went really quiet and discouraged members from talking. As a lead, I had to find ways to enforce communication and encourage newcomers to ask questions.

The Changes
There were several basic changes that me and my co-lead implemented to improve communication:
Screenshot of the Empathy Bytes Discord server

Discord

For meetings and communication, we mainly used discord. We emphasized using discord each meeting to ask any questions or have people review tickets to push into production.

Weekly Meetings

Previously, participating in the weekly stand up was optional, leading to limited engagement. We implemented a system where everyone shares their accomplishments to promote accountability and project awareness.

This way, everyone knows what everyone else is doing and the meeting isn't just run by the same subset of people. It also got rid of the awkward quiet moments when no one is answering a team lead.
Screenshot of discord voice channels.
Screenshot of example entry for the knowledge board.

Knowledge Board

We had recently added a knowledge board the previous semester to document issues and to help create tickets for the obstacles encountered.

Me and my co-lead further pushed our team to document any outstanding problems members had that are out of the scope of their ticket.

The Impact

We noticed tickets were getting faster progress with these changes in place. Also, more team interaction and participation were more welcomed.

50% more team participation from the previous semester

Increased accountability and project awareness

Members were more knowledgeable on progress

There was also more communication to the future EB web team on what to fix and problem points.

Results

Results

UI/UX and Team Improvements

Even though we didn't 100% completed our goals, we did make it pretty far:

Accessibility amongst various screen sizes increased

More information about each Empathy Bytes team is now available

Consistent with the new style guide

Cleaner and more organized code

Positive feedback on new ticket system

Better documentation of completed tasks for future references

As A Lead, Developer and Designer:

  • How to be an essential spokesperson between the stakeholders and developers
  • Making better site usability, maintainability and mobile responsiveness
  • How to consider the developers in my goal of improving the site and code
  • The tradeoffs between the “ideal” and the “feasible”

Areas of Improvement:

  • Balancing time, team management, and web development better
  • Gathering user feedback for the most updated version of the site instead of relying on old user data
  • Using a more defined and structured user-centered design process rather than intuition
  • Even more detailed documentation in my code for future developers

Results

What I Learned

Although I did this project from the perspective of a developer and leader (rather than just a designer), I realized the importance of proper team and product design early on in my role.

Reflection

I learned that when designing an effective site, it is really crucial to understand not only the audience but also the actors that make the site a reality. This awareness is what would allow me to create meaningful impacts to user interaction and experience.

I'd like to note that my biggest mistake was that I initially didn’t consider developers as part of my user group. I didn’t fully consider the skill variation in my team, leading to an overestimation of what we could accomplish even if we knew that we would never 100% complete the goal. Nonetheless, me and my co-lead decided to recalibrate our goals, focusing on achievable outcomes and clearer structure to better support the team.

Overall, I learned a lot about project planning and designing despite not specifically following a traditional design process. Moving forward, I feel more confident applying these insights to future projects as both a designer and a project manager.

Web Team Picture