
Scope: Didn't ship yet. This project focused on discovery, concept exploration, and early validation to identify a clear product differentiator for migrating Confluence customers.
There was no guided step or prominent next step after creating a site.
Migration problem
There was no guided step or prominent next step after creating a site.
Users found it difficult to find where to add Atlassian source.
Themes and styles are for each page and also global, making it challenging for users to know how to change them.
I conducted 1 hour task based on think-aloud usability test with 8 participants, and each participant were asked to build ‘Intranet’.
If we could let customers create a proof of concept quickly, more customers would stay engaged with our product.
We realized customers weren’t ready to “build a site” yet.
They first needed to experience what having a site would feel like—with their own content—before committing to configuration, customization, or rollout.This reframed the challenge from:“How do we help users set up a site?”
to
“How do we help users understand the product’s value early enough to want to continue?”


Even when it's skippable options, too many options for 'browser' customers granular separate templates like palette or site structure templates. Best way to reduce the time to show what's achievable with Refined is using full-fledged templates ONLY in connection with using customer's content. In this way, customers can understand the product concept which is a CMS on top of Atlassian content layer.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote