Using Confluence for Shape Up
Deep native integration with Jira makes it the de facto documentation tool for teams already using Atlassian — Jira issues embed seamlessly in pages. When combined with Shape Up, this makes Confluence a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Shape Up works best in Confluence when you leverage its core workflow features to implement the framework's key practices directly in the tool your team already lives in.
Shape Up (Basecamp's methodology) works in 6-week cycles with fully shaped pitches — no backlogs, no sprints, no estimates. Teams get the full cycle to solve a problem however they see fit.
How to set up Shape Up in Confluence
Set up your shaping workspace
Create a dedicated "Shaping" space in Confluence separate from delivery. Use status labels: Raw Idea, Being Shaped, Ready for Betting, Accepted. Only PMs and shapers have write access to this space during the shaping phase.
Create pitch documents within the tool
Create a naming convention for pitch cards in Confluence: "[Pitch] <Name> — Appetite: 6w/2w/1w". Include the pitch content in the card description or linked document. Keep all pitches in one list for the betting table.
Configure 6-week cycle projects
For each cycle, create a project in Confluence with a hard end date 6 weeks away. Use a list view for tasks. Teams generate their own tasks from the pitch; the PM does not create the task list. No backlog, no sprint planning — only the pitch scope.
Manage the hill chart (progress) and cooldown
Use Confluence's progress tracking to give a weekly "hill chart" update: which tasks are still unknown (uphill) vs being executed (downhill). At week 6, the cycle ends. Create a cooldown project manually at the end of each cycle.
Which Confluence features matter for Shape Up
Confluence has 0 of 2 core Shape Up features natively.