Amandine Revol

Redesigning Levuro's main failure path: The connection of an Instagram profile and the definition of a publishing method.

My role: UX Lead, the sole designer at this early-stage startup. I identified and prioritized the problem, then owned the end-to-end design, working closely with a cross-functional team of 4 developers and the CEO.
When: 2022.
Scope: Instagram profile connection and publishing setup, across Levuro's web and mobile apps.

Impact

Introduction

About the company

Levuro is a Swiss startup building a social media and live stream management tool for Instagram, Twitter, Facebook, LinkedIn, and YouTube. Users can publish via web or mobile apps.

Problem statement

More than half of Levuro’s users have Instagram accounts and expect automatic publishing, but many struggle to connect profiles and set up the correct publishing method. The complex flow leads to frustration and high churn, with users abandoning or deleting their accounts.

Solution

I redesigned the user flow to make automatic publishing an option for all users, guiding them to convert their profiles to business accounts when needed. I simplified the setup process, rewrote the guidance text to be clear and jargon-free, and removed barriers so users could draft posts before selecting a publishing method. This allowed users more flexibility and control over how they publish their content.


Context

The data: what analytics showed

I surfaced this during monthly product discussions using data analytics, beta user feedback, and customer support reports. Key finding: half of Levuro’s users had a connected Instagram account, but 70% of those accounts had no publishing method set up, meaning they couldn’t publish through Levuro at all. Users stuck this way were deleting their accounts.

Analytics dashboard showing the share of Levuro users with a connected Instagram account and the percentage still missing a publishing method

The why: what user testing revealed

The data told me what was broken, but not why. With competition for social media tools intense, fixing this was critical to reducing churn and converting more users to paid accounts, so I ran usability testing with users stuck at this step to find out why they were failing to set up a publishing method.


What success looks like

Defining success metrics and product goals

Success metrics and product goals defined for the Instagram publishing project

User test findings

Through beta user feedback, usability testing, analytics, and customer support data, we identified multiple pain points and high user frustration. While we uncovered more than 10 bugs, the primary issue was confusion around the user flow for defining a publishing method for Instagram.

Finding 1: Users don’t understand why they need to define a publishing method for their Instagram profile, and those who attempt it struggle with the unclear instructions.

On figure 1, you can see the user's pain points when they try to define a publishing method for their Instagram profiles.

Diagram of pain points users hit when trying to define a publishing method for their Instagram profile

Figure 1: Pain points when trying to define a publishing method for Instagram profiles.

Finding 2: Our current flow restricts automatic publishing to business profiles, which frustrated many users (fig 2). They expected this feature to be available for all Instagram accounts, as advertised, and it was a key reason they were willing to pay for the tool.

Current flow showing automatic publishing restricted to Instagram business profiles only

Figure 2: The current flow don't allow all users to use auto publishing.

Finding 3: Users were blocked from creating posts if they hadn’t defined a publishing method.

Composer screen blocked from creating a post because no publishing method is defined

Figure 3: Without a publishing method, users are stuck.

Finding 4: Some users who opted for mobile notifications didn’t receive them and had no easy way to resend the notification.

Mobile app screen showing the failed attempt to publish when the push notification wasn't received

Figure 4: Using the mobile app to publish if they don't receive the notification didn't work.

Web app interface with no option to resend the mobile publishing notification

Figure 5: No easy way to trigger a new notification from the web app.

These findings revealed critical issues in the user flow for Instagram publishing, particularly around setting up and understanding the auto-publishing feature. Users were confused by unclear instructions, limited by restrictive publishing options, and blocked from creating posts without properly setting up a publishing method. This led to significant frustration and abandonment of the platform.

Next Steps: Based on these insights, we took the following actions:

1. Redesign the user flow to make auto-publishing available to all users and guide them through converting to a business profile if needed.
2. Clarify modal dialogues by simplifying the language and offering clearer instructions on connecting profiles and setting up publishing methods.
3. Allow post creation even if the publishing method isn’t defined, so users can create drafts and set up publishing later.
4. Add a feature for resending mobile notifications easily from both the mobile app and web app, ensuring users can complete the publishing process.

Design solutions

1. Redesign the user flow to make auto-publishing available to all users and guide them in converting to a business profile, if needed.

I introduced a new user flow that enables Business, Personal, and Creator profiles to publish posts automatically on Levuro (Figure 6). This update empowers users to choose how they want to publish their Instagram posts, with guidance provided for converting to a business profile if they wish to enable automatic publishing (Figure 7).

New user flow enabling Business, Personal, and Creator Instagram profiles to publish automatically on Levuro

Figure 6: New user flow for Instagram auto-publishing.

Updated flow for connecting an Instagram account and defining a publishing method

Figure 7: Updated flow for connecting an Instagram account and defining a publishing method.

2. Allow post creation even if a publishing method isn’t defined, so users can create drafts and set up publishing later.

By enabling users to draft posts without immediately defining a publishing method, we made the process more intuitive and motivational. Users can invest time in creating the perfect social media post and then define their publishing method when scheduling the post (fig 8).


Updated composer interface allowing users to create post drafts without defining a publishing method first

Figure 8: Updated interface for creating drafts and defining publishing methods later.

3. Allow users to resend the mobile notification directly from the web app.

Updated web app flow for resending the mobile publishing notification

Figure 9: Updated flow for resending notifications and publishing from the web app.

Mobile app screen letting users publish directly if they don't receive the push notification

Figure 10: An easy way to publish from the mobile app if users don’t receive the push notification.


Conclusion

After one month of implementation, we saw the first improvements, which kept building over the following months:

What’s next?

We will continue monitoring the success rate for Instagram publishing setup. With the Instagram API evolving, including new features like automatic publishing for reels, we’ll need to assess potential updates to the user flow. This may involve revising help articles, creating new ones, and adjusting the UX to ensure clarity and relevance.


Extra: UX Writing

I focused on giving users clear choices on how to publish their posts and guiding them to automatic publishing.

Underneath are the new modal dialogs allowing users to choose how they want to publish. With the text, we explained the difference between the 2 methods and indicated what they needed to do to use Auto-publishing.

Modal dialog letting users choose between automatic and manual Instagram publishing

Rewriting confusing modal dialog.

Most users could not understand what was written, as a result the setting up of a publishing method often failed. My objective in rewriting the modal dialogs was to:

You can see below the modal before and after.

Modal dialog copy before the rewrite, using unclear technical language
Modal dialog copy after the rewrite, in plain, jargon-free language
Additional modal dialog example showing the rewritten step-by-step guidance
Error state modal dialog with clear, actionable guidance after the rewrite