Using Confluence for documenting product strategy - looking for inspiration and advice

Question

Hi everyone,

I am a Head of Product and am reasonably familiar with Jira Software and have been using Jira Product Discovery for about a year and a half. Our dev team is using Confluence for different purposes, but I have no experience with creating anything in Confluence myself.

I am looking for the best way to document our product strategy and Confluence seems to be a good place. Does anyone have experience doing it? And tips, advice, pros and cons that you can point out? I will be grateful for some help!

Laura Campbell · Answer

Great question @Tatiana Torset I agree with everything @Mia Tamm _Simpleasyty_ mentioned. Confluence is a great tool for sharing and collaborating on ideas.

Definitely take a moment to think about how you want to structure & organize the content (use the folder feature, or parent pages).

The overview page for a space is a great place to link to key pages and generally explain what kind of information is included in the space.

And if you ever need to present your product strategy, don't forget there's the Presentor mode in Confluence, which means you don't have to copy everything over to another presentation tool, just start your presentation from Confluence!

Mia Tamm _Simpleasyty_ · Answer

Hi @Tatiana Torset ,

Great question! I’ve worked with Confluence quite a bit for documenting product strategy, and it can definitely be a solid choice if set up well. A few tips and considerations:

Pros:

Centralized knowledge – everyone can access the strategy in one place, and it stays linked to your Jira issues.

Templates – Confluence has built-in templates (e.g. product requirements, OKRs, roadmaps) that you can adapt. They’re a great starting point.

Collaboration – inline comments and @mentions make it easy for stakeholders to contribute or challenge ideas.

Version history – you can track changes and keep older versions if your strategy evolves.

Cons / watch-outs:

Overhead – if you don’t maintain it regularly, pages can get outdated quickly and lose trust.

Navigation – as your space grows, it’s worth putting effort into a good page hierarchy and labels so people don’t get lost.

Not visual enough out of the box – you may want to embed diagrams (Miro, Lucidchart, Figma) for roadmaps and vision statements.

Practical tips:

Create a Product Strategy Hub page that links out to vision, goals, OKRs, roadmap, and discovery insights.

Use child pages for deeper dives (e.g. per product line or initiative).

Agree on a review cycle (e.g. quarterly) so your strategy pages stay fresh.

Don’t hesitate to combine Confluence with Jira Product Discovery – linking ideas directly to strategy gives nice context for the dev team.

If you want inspiration, Atlassian’s own templates library is worth exploring – it saves a lot of time.

Hope this helps you get started!

— Mia Tamm