User Experience / Interface Tiger Team
#MauticUXUI Driving Innovation: Shaping Engaging and Intuitive User Experiences
Change Publish/Unpublish terminology
We would like to introduce a terminology update for statuses to improve user experience.
Published/Unpublished are currently used. However, they may not be ideal for Mautic features as these labels may not clearly convey whether the campaign is active and working or if an email is available for users to use them on campaigns or segments.
The status label “Published” has been revised to “Active” and "Available" according to each scenario. The idea is to have the right terminology for each feature inside Mautic.
Draft/Available:
It's about letting the user to select if their going to make a resource available for use or not.
This change ensures that users have a clear and precise understanding of when a resource becomes usable within the system.
- Custom fields
- Category
- Dynamic content
- Emails
- Marketing messages
- Forms
- Landing pages
- Assets
- Points (Groups)
- Reports
Draft/Active:
This one expresses when something like a campaign is still being created or if it's already running.
- Segments
- Campaigns
- Focus items
- Points (Actions, Triggers)
- Stages
- Users
- Webhooks
The “Draft” label (used on both) clearly indicates that the campaign or email is in development or not available for use; This approach may sound more natural to people, as marketers' everyday tools often use the Draft status (WordPress, Figma, etc.).
This consistency in terminology aids users in better understanding the status of resources, streamlining their workflow. The modification is particularly beneficial for users managing multiple campaigns, webhooks and all the other items mentioned above, ensuring a cohesive and straightforward interface.
Also considered:
Off/On: These labels are clear and straightforward, clearly indicating whether the campaign or email is currently running. However, the “Deactivated” label may not be intuitive for situations where the campaign or email has just been created, is in development, or is not ready to be used. "Why did I create an email and it was immediately deactivated?"
In Preparation/Running: These labels are a little more descriptive, but they can lead the user to think that the email will start to be sent if placed as Running, conditioning them to the error or confusing: "How is this thing running?"
Disabled/Enabled: The “Enabled” label indicates that the campaign is active and working but it can still be a bit weird for resources like emails. These labels are intuitive, straightforward and cover some states that the platform wants to communicate to users but it may not be the best approach for everything.
Community has already given some feedback:
Just an FYI: this comes from feedback from our clients. When asking questions about the UX, the terminology came up and the 'Publish' was given as one of the examples.
It's no specific issue but in a broader context of using terminology that makes more sense/explains its use better
I can confirm this from our clients as well.
Mautic in general is considered as "developer-aligned" in regards of naming and logic. It is logical but lots of marketers have serious problems understanding the naming and logic.
I think the approach is a very good start
"Scheduling an email is called "scheduling" and not "publishing" and it's not the same thing as "keep sending the email to a segment until a certain date"
What do you think about it?
The debate was closed on 09/05/2024 17:37 with these conclusions:
We will use Available/Unavailable and Active/Unactive
List of Endorsements
Report inappropriate content
Is this content inappropriate?
Close debate
What is the summary or conclusion of this debate?
Comment details
You are seeing a single comment
View all comments
Conversation with Andy Towne
I'll propose Active/Inactive rather than Active/Draft.
We have a feature (which will eventually be contributed to the community, I believe) to save emails & landing pages as drafts - so even if they're 'published' a user could make changes to an existing email ID while still allowing for a review process or not needing to make all changes in one session. It doesn't look like I can paste a screenshot here, but using 'draft' instead of 'unpublished' would become confusing for users once the draft feature is available to all.
Here's a recording with a demo of the draft: https://acquia.zoom.us/rec/share/Ngsx14_vG_a0RFuFudadBjmVCqgqrz8tUSN6vDdU8RA0h2PwdB-dvXxSNV2u4AcB.iRWqsZgTzzsEKyEy
That's a really good point @andy_towne thanks for raising it - I hadn't even thought about the wider situation of something you're working on in its entirety being a draft (as in, partially finished)!
Loading comments ...