Atlassian
5 min read
Crafting a unified calendar experience.
Outcome: Delivered an 8.8% increase in customer acquisition rate for 40,000+ enterprise teams and their employees.
Note: Details on this project have been limited because it is NDA-protected. Please reach out if you would like to learn more.
Role:
Product design intern
Duration:
12 weeks, May 2025 - August 2025
Tools:
Figma, User Interviews, Dovetail, ProtoPie
Team:
1 product design intern, 1 product manager, 1 content designer, 2 engineers
Within Confluence Company Hub, employees struggle to discover and engage with company events.
Confluence Company Hub is Atlassian's intranet solution that brings together company announcements, news, and tools for employees. It serves both employees to stay informed with company updates and admins to share trustworthy and relevant information. However, there was a critical gap within the platform: there was no unified way to share and manage company-wide events.
Confluence Company Hub
The ChalLeNGE
Companies were using fragmented tools to share events.
Since no event management feature existed in the current experience of Company Hub, employees were using tools like Confluence pages, Slack announcements, and separate Google Calendars to keep up with company events. The various platforms led to:
01
Admins duplicating events across tools
02
Invites to hundreds of irrelevant events
03
Employees missing important company updates
How can I create a unified calendar experience that helps company admins efficiently share relevant events while enabling employees to easily discover and engage with them?
Research and Discovery
How do teams share events today?
I conducted a comprehensive competitive analysis and internal audit to understand current pain points and industry patterns.
How events are shared inside Atlassian:
Confluence calendar
Multiple layouts and labeled events, but feels visually outdated and lacks additional features.
Slack
Quick notifications and updates, but no calendar view causes events to get lost, and text formatting lacks hierarchy.
Confluence pages
Supports collaboration but hard to discover without direct links and difficult to visualize multiple events simultaneously.
Competitor features:
Through this research, I found that no competitor offered target audience controls, or the ability to invite different employee groups to events relevant to them. This became a key differentiator for my solution, while I also kept in mind important features that were done well across these tools.
What do our users think?
I also interviewed current users of Company Hub, where I discovered that 83% of our users already use an external calendar.
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
While stakeholders initially requested a new manual event management interface, I realized that I needed to prioritize a third-party calendar integration feature, since creating manual events would duplicate work that employees had already done.
So, I challenged the initial brief.
I knew that users preferred 3P sources rather than a new tool. But my product manager had initially proposed a manual, entirely new event experience for employees due to development efforts. How could I reach a compromise?
I advocated for 3P calendar integration as the MVP, with manual event creation as future scope, working with my product manager to refine the product roadmap. I also lead multiple discussions with my engineering team to ensure the design direction was feasible within the given timeframe. We successfully balanced both user and business value, aligning user needs with a faster time-to-market.
P0 (Must-haves MVP)
3P calendar integrations
Two-way sync for event updates
Target audience controls
Event labeling and categorization
P0 (Must-haves MVP)
P1 (Nice-to-haves future scope)
Manual calendar creation
Custom event type labels
Additional admin customizations
AI summaries and analytics
P1 (Nice-to-haves future scope)
Design Explorations
Step 1: Third-party calendar integration flow
I started with the foundation of importing any existing calendars from 3P sources. I designed the flow to show all available calendars at once rather than requiring users to add them one by one. This matched how users mentioned they work and wanting to see their calendars together.
I also made sure my designs followed the design system and fit cleanly and accessibly within the Company Hub layout.
Step 2: Multiple calendar layouts
Once calendars were connected, users needed the flexibility to choose their preferred layout for showcasing events. I designed multiple views to accommodate different use cases identified in my research and industry findings.
Month view: Traditional calendar layout for seeing the full month at a glance and to plan ahead. This layout also gives users the opportunity to spotlight certain events.
List view: Chronological list showing more event details for users who want to quickly scan upcoming events.
Card view: Visual event cards with images and additional details for users that want an engaging and lively feel.
Step 3: Event management and targeted invites
Finally, admins needed a way to manage which events appear to employees and showcase important ones. Within the side panel, users can configure full event metadata, including title, type, date/time, location, and description. They can also enable invitees to limit events to be shown only the relevant employees, which was the biggest gap I noticed in competitive analysis.
This configuration panel for showcasing events unified the experience for admins to control all calendar settings and preview updates in real-time as they make changes.
User testing
Over the next two weeks, I validated my designs with users to identify successes, problems, and areas for improvement.
I conducted moderated SEQ (single-ease question) usability testing with 8 user groups, including intranet admins from internal teams and external companies. Using prototypes, I asked each participant to guide me through a series of tasks related to the calendar feature in Company Hub, centered around 3P integration, event management, calendar layout, and metadata. After each task, participants answered follow-up questions and rated its ease of use using the SEQ scale from 1-7.
I also recorded qualitative user responses over this 60-minute interview session into Dovetail, grouped them into patterns and insights, and delivered a report to my team's UX researcher for future considerations.
Does this feature meet our users' needs?
The SEQ testing and qualitative responses helped me identify what worked and what improvements were needed. Overall, users found the calendar feature useful for simplifying workflows and easy to use. However, the lower score for the event management task indicated an improvement opportunity.
What worked
Third-party integration
“Alright, I’m linking my account… and I can see everything updating here instantly. This is really smooth.”
6.3/7
What worked
What worked
Calendar layout customizations
“I’m trying the card layout now... this one’s much clearer for our team events. I like that I can choose what works for me.”
6.6/7
What worked
Improvements needed
Event management
“I don’t like having to scroll through all of my events. There’s too many and it takes too much time.”
4.2/7
Improvements needed
Improvements needed
I also found multiple use cases of users not knowing what certain features or terminology meant, which made them unable to complete tasks.
Continued Design Iterations
So, I worked on improving the terminology first, replacing confusing labels based on user feedback.
I then addressed event confusion.
Before, the side panel for showcasing events presented issues with scrolling through potentially hundreds of events, cognitive overload, and left minimal room for event details. This led to users failing the event management task. I adjusted my designs to have a clear hierarchy for each calendar, prioritized target audience controls, and moved event detail management into a wider modal.
The new modal provides a larger viewing experience with more room for event details supporting hundreds of events over multiple years. I also designed additional filtering functionality suggested from user interviews, and there is now a clearer distinction between featured and non-featured events.
FINAL DESIGNS
Welcome to a unified calendar feature that integrates with existing tools, supports targeted audiences, and provides flexible viewing options.
A smooth onboarding process.
Relevant event visibility.
Easy event management.
Customizable calendar layouts.
And an effortless event viewing experience.
Future Considerations
Throughout this process, I also wanted to make sure my designs were fully accessible to users. For handoff, I provided fully accessible guidelines to my engineering team.
Examples of a11y annotations of my designs, including headings, buttons, landmarks, images, form fields, tab order, and reading order.
I also made sure to design for P1, our future scope ideas.
Following my discussions with my product manager and feedback from users, I designed for additional user filtering, featuring multiple events, showing past and future events, customizing event types, and editing and adding events directly on Company Hub, to be implemented in future product rollouts.
Impact
The calendar experience created easier event management and stronger team collaboration for over 40,000 users…
…and an 8.8% increase in product visits after a month of implementation.
With my feature, employees are able to more easily discover events on Company Hub, leading to more engagement within their company. Additionally, we found an increase in visits and adoption of the platform.
Reflection
Be flexible and advocate.
Throughout my design process, I learned how important it is to be confident in my own design choices, while also learning how to compromise with other perspectives. I frequently had discussions with my engineering team, modifying my designs to be feasible with their efforts. Every weekly meeting with my team, we collaborated on ideas that best fit visual appeal and the user experience. Multiple times during research and design, I presented design choices backed with user feedback to my product manager that conflicted with the initial brief, and we worked together to refine the product vision. I learned how important it is to challenge the starting point while working toward a solution that values both users and the business, and overall, to trust myself.
Understanding your customers is essential.
Without the feedback I gathered through user interviews and usability testing, I would have designed a completely different feature that may have aligned with business requirements, but it would have not directly helped our users. With their input, I was able to deliver a solution that our customers want, love, and need.
Explore the unknown.
Recruiting and sourcing the right participants for usability testing was one of the most challenging parts of my internship. I also had to familiarize myself with SEQ testing with help from my UX researcher, which I had never conducted before. Then I had to be sure to follow consent guidelines, lead the users through objective tasks, and afterwards, spend hours reviewing transcripts to identify recurring patterns and meaningful insights. Yet, spending the time to do this helped me learn so much about the importance of real user input. Seeing the impact and how the findings informed my design decisions made the entire experience incredibly rewarding.
I also thoroughly enjoyed learning and applying accessibility standards. I got to understand Atlassian's accessibility handoff process, implement a11y annotations directly into my designs, and participate in weekly meetings focused on accessibility initiatives across the design team. This experience taught me how to create inclusive experiences even within complex and standardized company processes.
Atlassian
5 min read
Crafting a unified calendar experience.
Outcome: Delivered an 8.8% increase in customer acquisition rate for 40,000+ enterprise teams and their employees.
Note: Details on this project have been limited because it is NDA-protected. Please reach out if you would like to learn more.
Role:
Product design intern
Duration:
12 weeks, May 2025 - August 2025
Tools:
Figma, User Interviews, Dovetail, ProtoPie
Team:
1 product design intern, 1 product manager, 1 content designer, 2 engineers
Within Confluence Company Hub, employees struggle to discover and engage with company events.
Confluence Company Hub is Atlassian's intranet solution that brings together company announcements, news, and tools for employees. It serves both employees to stay informed with company updates and admins to share trustworthy and relevant information. However, there was a critical gap within the platform: there was no unified way to share and manage company-wide events.
Confluence Company Hub
The ChalLeNGE
Companies were using fragmented tools to share events.
Since no event management feature existed in the current experience of Company Hub, employees were using tools like Confluence pages, Slack announcements, and separate Google Calendars to keep up with company events. The various platforms led to:
01
Admins duplicating events across tools
02
Invites to hundreds of irrelevant events
03
Employees missing important company updates
How can I create a unified calendar experience that helps company admins efficiently share relevant events while enabling employees to easily discover and engage with them?
Research and Discovery
How do teams share events today?
I conducted a comprehensive competitive analysis and internal audit to understand current pain points and industry patterns.
How events are shared inside Atlassian:
Confluence calendar
Multiple layouts and labeled events, but feels visually outdated and lacks additional features.
Slack
Quick notifications and updates, but no calendar view causes events to get lost, and text formatting lacks hierarchy.
Confluence pages
Supports collaboration but hard to discover without direct links and difficult to visualize multiple events simultaneously.
Competitor features:
Through this research, I found that no competitor offered target audience controls, or the ability to invite different employee groups to events relevant to them. This became a key differentiator for my solution, while I also kept in mind important features that were done well across these tools.
What do our users think?
I also interviewed current users of Company Hub, where I discovered that 83% of our users already use an external calendar.
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
While stakeholders initially requested a new manual event management interface, I realized that I needed to prioritize a third-party calendar integration feature, since creating manual events would duplicate work that employees had already done.
So, I challenged the initial brief.
I knew that users preferred 3P sources rather than a new tool. But my product manager had initially proposed a manual, entirely new event experience for employees due to development efforts. How could I reach a compromise?
I advocated for 3P calendar integration as the MVP, with manual event creation as future scope, working with my product manager to refine the product roadmap. I also lead multiple discussions with my engineering team to ensure the design direction was feasible within the given timeframe. We successfully balanced both user and business value, aligning user needs with a faster time-to-market.
P0 (Must-haves MVP)
3P calendar integrations
Two-way sync for event updates
Target audience controls
Event labeling and categorization
P0 (Must-haves MVP)
P1 (Nice-to-haves future scope)
Manual calendar creation
Custom event type labels
Additional admin customizations
AI summaries and analytics
P1 (Nice-to-haves future scope)
Design Explorations
Step 1: Third-party calendar integration flow
I started with the foundation of importing any existing calendars from 3P sources. I designed the flow to show all available calendars at once rather than requiring users to add them one by one. This matched how users mentioned they work and wanting to see their calendars together.
I also made sure my designs followed the design system and fit cleanly and accessibly within the Company Hub layout.
Step 2: Multiple calendar layouts
Once calendars were connected, users needed the flexibility to choose their preferred layout for showcasing events. I designed multiple views to accommodate different use cases identified in my research and industry findings.
Month view: Traditional calendar layout for seeing the full month at a glance and to plan ahead. This layout also gives users the opportunity to spotlight certain events.
List view: Chronological list showing more event details for users who want to quickly scan upcoming events.
Card view: Visual event cards with images and additional details for users that want an engaging and lively feel.
Step 3: Event management and targeted invites
Finally, admins needed a way to manage which events appear to employees and showcase important ones. Within the side panel, users can configure full event metadata, including title, type, date/time, location, and description. They can also enable invitees to limit events to be shown only the relevant employees, which was the biggest gap I noticed in competitive analysis.
This configuration panel for showcasing events unified the experience for admins to control all calendar settings and preview updates in real-time as they make changes.
User testing
Over the next two weeks, I validated my designs with users to identify successes, problems, and areas for improvement.
I conducted moderated SEQ (single-ease question) usability testing with 8 user groups, including intranet admins from internal teams and external companies. Using prototypes, I asked each participant to guide me through a series of tasks related to the calendar feature in Company Hub, centered around 3P integration, event management, calendar layout, and metadata. After each task, participants answered follow-up questions and rated its ease of use using the SEQ scale from 1-7.
I also recorded qualitative user responses over this 60-minute interview session into Dovetail, grouped them into patterns and insights, and delivered a report to my team's UX researcher for future considerations.
Does this feature meet our users' needs?
The SEQ testing and qualitative responses helped me identify what worked and what improvements were needed. Overall, users found the calendar feature useful for simplifying workflows and easy to use. However, the lower score for the event management task indicated an improvement opportunity.
What worked
Third-party integration
“Alright, I’m linking my account… and I can see everything updating here instantly. This is really smooth.”
6.3/7
What worked
What worked
Calendar layout customizations
“I’m trying the card layout now... this one’s much clearer for our team events. I like that I can choose what works for me.”
6.6/7
What worked
Improvements needed
Event management
“I don’t like having to scroll through all of my events. There’s too many and it takes too much time.”
4.2/7
Improvements needed
Improvements needed
I also found multiple use cases of users not knowing what certain features or terminology meant, which made them unable to complete tasks.
Continued Design Iterations
So, I worked on improving the terminology first, replacing confusing labels based on user feedback.
I then addressed event confusion.
Before, the side panel for showcasing events presented issues with scrolling through potentially hundreds of events, cognitive overload, and left minimal room for event details. This led to users failing the event management task. I adjusted my designs to have a clear hierarchy for each calendar, prioritized target audience controls, and moved event detail management into a wider modal.
The new modal provides a larger viewing experience with more room for event details supporting hundreds of events over multiple years. I also designed additional filtering functionality suggested from user interviews, and there is now a clearer distinction between featured and non-featured events.
FINAL DESIGNS
Welcome to a unified calendar feature that integrates with existing tools, supports targeted audiences, and provides flexible viewing options.
A smooth onboarding process.
Relevant event visibility.
Easy event management.
Customizable calendar layouts.
And an effortless event viewing experience.
Future Considerations
Throughout this process, I also wanted to make sure my designs were fully accessible to users. For handoff, I provided fully accessible guidelines to my engineering team.
Examples of a11y annotations of my designs, including headings, buttons, landmarks, images, form fields, tab order, and reading order.
I also made sure to design for P1, our future scope ideas.
Following my discussions with my product manager and feedback from users, I designed for additional user filtering, featuring multiple events, showing past and future events, customizing event types, and editing and adding events directly on Company Hub, to be implemented in future product rollouts.
Impact
The calendar experience created easier event management and stronger team collaboration for over 40,000 users…
…and an 8.8% increase in product visits after a month of implementation.
With my feature, employees are able to more easily discover events on Company Hub, leading to more engagement within their company. Additionally, we found an increase in visits and adoption of the platform.
Reflection
Be flexible and advocate.
Throughout my design process, I learned how important it is to be confident in my own design choices, while also learning how to compromise with other perspectives. I frequently had discussions with my engineering team, modifying my designs to be feasible with their efforts. Every weekly meeting with my team, we collaborated on ideas that best fit visual appeal and the user experience. Multiple times during research and design, I presented design choices backed with user feedback to my product manager that conflicted with the initial brief, and we worked together to refine the product vision. I learned how important it is to challenge the starting point while working toward a solution that values both users and the business, and overall, to trust myself.
Understanding your customers is essential.
Without the feedback I gathered through user interviews and usability testing, I would have designed a completely different feature that may have aligned with business requirements, but it would have not directly helped our users. With their input, I was able to deliver a solution that our customers want, love, and need.
Explore the unknown.
Recruiting and sourcing the right participants for usability testing was one of the most challenging parts of my internship. I also had to familiarize myself with SEQ testing with help from my UX researcher, which I had never conducted before. Then I had to be sure to follow consent guidelines, lead the users through objective tasks, and afterwards, spend hours reviewing transcripts to identify recurring patterns and meaningful insights. Yet, spending the time to do this helped me learn so much about the importance of real user input. Seeing the impact and how the findings informed my design decisions made the entire experience incredibly rewarding.
I also thoroughly enjoyed learning and applying accessibility standards. I got to understand Atlassian's accessibility handoff process, implement a11y annotations directly into my designs, and participate in weekly meetings focused on accessibility initiatives across the design team. This experience taught me how to create inclusive experiences even within complex and standardized company processes.
Atlassian
5 min read
Crafting a unified calendar experience.
Outcome: Delivered an 8.8% increase in customer acquisition rate for 40,000+ enterprise teams and their employees.
Note: Details on this project have been limited because it is NDA-protected. Please reach out if you would like to learn more.
Role:
Product design intern
Duration:
12 weeks, May 2025 - August 2025
Tools:
Figma, User Interviews, Dovetail, ProtoPie
Team:
1 product design intern, 1 product manager, 1 content designer, 2 engineers
Within Confluence Company Hub, employees struggle to discover and engage with company events.
Confluence Company Hub is Atlassian's intranet solution that brings together company announcements, news, and tools for employees. It serves both employees to stay informed with company updates and admins to share trustworthy and relevant information. However, there was a critical gap within the platform: there was no unified way to share and manage company-wide events.
Confluence Company Hub
The ChalLeNGE
Companies were using fragmented tools to share events.
Since no event management feature existed in the current experience of Company Hub, employees were using tools like Confluence pages, Slack announcements, and separate Google Calendars to keep up with company events. The various platforms led to:
01
Admins duplicating events across tools
02
Invites to hundreds of irrelevant events
03
Employees missing important company updates
How can I create a unified calendar experience that helps company admins efficiently share relevant events while enabling employees to easily discover and engage with them?
Research and Discovery
How do teams share events today?
I conducted a comprehensive competitive analysis and internal audit to understand current pain points and industry patterns.
How events are shared inside Atlassian:
Confluence calendar
Multiple layouts and labeled events, but feels visually outdated and lacks additional features.
Slack
Quick notifications and updates, but no calendar view causes events to get lost, and text formatting lacks hierarchy.
Confluence pages
Supports collaboration but hard to discover without direct links and difficult to visualize multiple events simultaneously.
Competitor features:
Through this research, I found that no competitor offered target audience controls, or the ability to invite different employee groups to events relevant to them. This became a key differentiator for my solution, while I also kept in mind important features that were done well across these tools.
What do our users think?
I also interviewed current users of Company Hub, where I discovered that 83% of our users already use an external calendar.
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
"“We already rely on Google Calendar for everything. Recreating all of our events here doesn’t make sense for us.”
While stakeholders initially requested a new manual event management interface, I realized that I needed to prioritize a third-party calendar integration feature, since creating manual events would duplicate work that employees had already done.
So, I challenged the initial brief.
I knew that users preferred 3P sources rather than a new tool. But my product manager had initially proposed a manual, entirely new event experience for employees due to development efforts. How could I reach a compromise?
I advocated for 3P calendar integration as the MVP, with manual event creation as future scope, working with my product manager to refine the product roadmap. I also lead multiple discussions with my engineering team to ensure the design direction was feasible within the given timeframe. We successfully balanced both user and business value, aligning user needs with a faster time-to-market.
P0 (Must-haves MVP)
3P calendar integrations
Two-way sync for event updates
Target audience controls
Event labeling and categorization
P0 (Must-haves MVP)
P1 (Nice-to-haves future scope)
Manual calendar creation
Custom event type labels
Additional admin customizations
AI summaries and analytics
P1 (Nice-to-haves future scope)
Design Explorations
Step 1: Third-party calendar integration flow
I started with the foundation of importing any existing calendars from 3P sources. I designed the flow to show all available calendars at once rather than requiring users to add them one by one. This matched how users mentioned they work and wanting to see their calendars together.
I also made sure my designs followed the design system and fit cleanly and accessibly within the Company Hub layout.
Step 2: Multiple calendar layouts
Once calendars were connected, users needed the flexibility to choose their preferred layout for showcasing events. I designed multiple views to accommodate different use cases identified in my research and industry findings.
Month view: Traditional calendar layout for seeing the full month at a glance and to plan ahead. This layout also gives users the opportunity to spotlight certain events.
List view: Chronological list showing more event details for users who want to quickly scan upcoming events.
Card view: Visual event cards with images and additional details for users that want an engaging and lively feel.
Step 3: Event management and targeted invites
Finally, admins needed a way to manage which events appear to employees and showcase important ones. Within the side panel, users can configure full event metadata, including title, type, date/time, location, and description. They can also enable invitees to limit events to be shown only the relevant employees, which was the biggest gap I noticed in competitive analysis.
This configuration panel for showcasing events unified the experience for admins to control all calendar settings and preview updates in real-time as they make changes.
User testing
Over the next two weeks, I validated my designs with users to identify successes, problems, and areas for improvement.
I conducted moderated SEQ (single-ease question) usability testing with 8 user groups, including intranet admins from internal teams and external companies. Using prototypes, I asked each participant to guide me through a series of tasks related to the calendar feature in Company Hub, centered around 3P integration, event management, calendar layout, and metadata. After each task, participants answered follow-up questions and rated its ease of use using the SEQ scale from 1-7.
I also recorded qualitative user responses over this 60-minute interview session into Dovetail, grouped them into patterns and insights, and delivered a report to my team's UX researcher for future considerations.
Does this feature meet our users' needs?
The SEQ testing and qualitative responses helped me identify what worked and what improvements were needed. Overall, users found the calendar feature useful for simplifying workflows and easy to use. However, the lower score for the event management task indicated an improvement opportunity.
What worked
Third-party integration
“Alright, I’m linking my account… and I can see everything updating here instantly. This is really smooth.”
6.3/7
What worked
What worked
Calendar layout customizations
“I’m trying the card layout now... this one’s much clearer for our team events. I like that I can choose what works for me.”
6.6/7
What worked
Improvements needed
Event management
“I don’t like having to scroll through all of my events. There’s too many and it takes too much time.”
4.2/7
Improvements needed
Improvements needed
I also found multiple use cases of users not knowing what certain features or terminology meant, which made them unable to complete tasks.
Continued Design Iterations
So, I worked on improving the terminology first, replacing confusing labels based on user feedback.
I then addressed event confusion.
Before, the side panel for showcasing events presented issues with scrolling through potentially hundreds of events, cognitive overload, and left minimal room for event details. This led to users failing the event management task. I adjusted my designs to have a clear hierarchy for each calendar, prioritized target audience controls, and moved event detail management into a wider modal.
The new modal provides a larger viewing experience with more room for event details supporting hundreds of events over multiple years. I also designed additional filtering functionality suggested from user interviews, and there is now a clearer distinction between featured and non-featured events.
FINAL DESIGNS
Welcome to a unified calendar feature that integrates with existing tools, supports targeted audiences, and provides flexible viewing options.
A smooth onboarding process.
Relevant event visibility.
Easy event management.
Customizable calendar layouts.
And an effortless event viewing experience.
Future Considerations
Throughout this process, I also wanted to make sure my designs were fully accessible to users. For handoff, I provided fully accessible guidelines to my engineering team.
Examples of a11y annotations of my designs, including headings, buttons, landmarks, images, form fields, tab order, and reading order.
I also made sure to design for P1, our future scope ideas.
Following my discussions with my product manager and feedback from users, I designed for additional user filtering, featuring multiple events, showing past and future events, customizing event types, and editing and adding events directly on Company Hub, to be implemented in future product rollouts.
Impact
The calendar experience created easier event management and stronger team collaboration for over 40,000 users…
…and an 8.8% increase in product visits after a month of implementation.
With my feature, employees are able to more easily discover events on Company Hub, leading to more engagement within their company. Additionally, we found an increase in visits and adoption of the platform.
Reflection
Be flexible and advocate.
Throughout my design process, I learned how important it is to be confident in my own design choices, while also learning how to compromise with other perspectives. I frequently had discussions with my engineering team, modifying my designs to be feasible with their efforts. Every weekly meeting with my team, we collaborated on ideas that best fit visual appeal and the user experience. Multiple times during research and design, I presented design choices backed with user feedback to my product manager that conflicted with the initial brief, and we worked together to refine the product vision. I learned how important it is to challenge the starting point while working toward a solution that values both users and the business, and overall, to trust myself.
Understanding your customers is essential.
Without the feedback I gathered through user interviews and usability testing, I would have designed a completely different feature that may have aligned with business requirements, but it would have not directly helped our users. With their input, I was able to deliver a solution that our customers want, love, and need.
Explore the unknown.
Recruiting and sourcing the right participants for usability testing was one of the most challenging parts of my internship. I also had to familiarize myself with SEQ testing with help from my UX researcher, which I had never conducted before. Then I had to be sure to follow consent guidelines, lead the users through objective tasks, and afterwards, spend hours reviewing transcripts to identify recurring patterns and meaningful insights. Yet, spending the time to do this helped me learn so much about the importance of real user input. Seeing the impact and how the findings informed my design decisions made the entire experience incredibly rewarding.
I also thoroughly enjoyed learning and applying accessibility standards. I got to understand Atlassian's accessibility handoff process, implement a11y annotations directly into my designs, and participate in weekly meetings focused on accessibility initiatives across the design team. This experience taught me how to create inclusive experiences even within complex and standardized company processes.