Overview
Worked on internship project to create an informative experience for message-makers to stay updated on their message statuses
Context
Engagement Plaftorm is an internal Atlassian tool where message-makers can create in-product messages and test new features that appear on Atlassian products like Confluence, Jira, and Trello.
Message-makers include:
- Marketing Team
- Project Managers
- Crossflow Experience Designers
- Anyone at Atlassian who needs to create a message
The Problem.
Message-makers are not kept up to date on the status of the messages they create. They must proactively check the progress themselves, which results in:
1. Forgotten messages (left in Drafts)
2. Delays in when messages reach end users
3. Lower performing messages running for long periods of time
This ultimately creates wasted time during the message shipping process.
The steps that message-makers currently experience:
.png)
My Hypothesis.
We believe that providing message makers with helpful notification updates on their message statuses
Will result in a decrease in the time it takes for a message to reach the end user
Because message makers will be guided through each critical action along the journey and no longer have to manually keep track of message progress
We will succeed if message makers can monitor and maintain messages with lower effort and time
Success Metrics 🏆
1. The average number of days that a message is in draft decreases by 25%, from 22 days to 16.5 days
2. The average CTR of Slack notification messages is 25%
My Solution.
Informative In-product Updates
Section Banner
Initial Design
Revised Design
The elements of the revised design
- Yellow color banner
- "Active voice" header
- No option to dismiss
Combine to form a clear Call to Action that message-makers cannot miss or ignore
Slack Message Updates
Initial Design
.png)
Revised Design
.png)
Impact
➡ Reduce the number of stale messages (left in Drafts > 30 days) on Engagement Platform
➡ Reduced the effort and time needed for the E2E journey of producing a message
Some Final Thoughts
This was my first big industry-level project experience! 🎉 During the onboarding process, I was pretty overwhelmed with all the new terminology, information about the Engagement Platform tool, and the different nuances within the message-making experience. Through asking questions, synthesizing user research, and engaging in critique sessions with different stakeholders, I developed a much more solid grasp on the problem. Moving forward, I've gained confidence in tackling challenges that initially feel intimidating.
Throughout the process, I was challenged to think about:
1. Balancing what the business is currently prioritizing with what the users want
2. The feasibility of each new design component
3. How to synthesize varying feedback from different stakeholders (designers, engineers, content designers, PMs) and figure out next steps
Additional work at Atlassian
During my internship at Atlassian, I also took the opportunity experiment with illustrations and create some "Better Together" narrative graphics for Atlassian products Jira and JSM.
Feel free to check out my other projects and works!
.png)
%204.png)
.png)
%201.png)
.png)
.png)
.png)
