In short
Atlassian renamed Jira Projects to Spaces because “project” implied deadlines and endings, while “Spaces” matches how teams actually work, reducing confusion and building trust.
“Project” was never the right word. Not for Jira. Not for how teams actually work.
The word implies deadlines. Deliverables. A tidy little end.
But in Jira? That “project” is your team’s living, evolving workspace. No start-stop. No handoffs. Just constant iteration.
This is why Atlassian is renaming Projects to Spaces. And as a product designer, I get it. This isn’t just a name change. It’s a shift in mental models.
Because when language doesn’t match behavior, confusion creeps in. And confused users don’t trust what they’re using.
Aligned terminology
“Spaces” better captures the fluid, collaborative nature of modern work. It also matches how we use Confluence and other tools in the ecosystem.
Consistency across tools
Design doesn’t live in silos. Neither should the words we use across platforms.
Cognitive clarity
When users expect a fixed project but get an open container, there’s dissonance. Good design clears that up, sometimes just by picking the right word.
This isn’t a redesign. No new flow. No feature unlock. Just a quiet, meaningful change that makes Jira feel more intuitive. And that is design too.
Because when the language fits, the experience clicks. It gets out of the way, and work flows.
Curious to hear: what’s one word in your product that confuses your users but no one’s challenged it yet?
Originally published on LinkedIn
This piece was first shared on LinkedIn. Read it there to see the reactions and join the discussion.
View the original