A Confluence template usually gets created with the best intentions. Everyone is fine with it and believes, it would save them a lot of time. And for a while, it does.
Then reality sets in.
A section feels unnecessary, so it gets deleted. Someone isn’t sure what a field means, so they skip it. Another person copies an old page “just this once.” A few months later, you’re looking at five versions of the same page type, all slightly different, all technically “based on the template.”
At that point, the template still exists, but it has quietly lost its power.
One of the most common mistakes teams make is treating templates as something you set up once and never touch again.
Templates aren’t static artifacts. They encode assumptions about how your team works — and those assumptions change. Processes evolve. Roles shift. What was useful six months ago might now feel bloated or irrelevant.
When templates don’t evolve with the team, people stop trusting them.
A good rule of thumb: If people regularly delete the same sections from a template, the template is the problem, not the people.
Templates shine when the structure stays the same and the content changes.
But many teams create templates for pages they only use once or twice. A special initiative. A one-off workshop. A unique project.
The result is a template that feels oddly specific and strangely restrictive. People open it, squint at it, and think, “This doesn’t quite fit.” So they improvise. Or abandon it.
Before creating a template, it’s worth asking:
Will we use this structure again and again?
Or is this just a page we want to get right once?
Templates earn their keep through repetition.
This one is deeply human.
Copying an old page feels fast. Familiar. Safe. You already know it “worked” once. But it quietly introduces long-term problems.
Old pages carry baggage:
Outdated sections
Forgotten labels
Old metadata
Decisions that no longer apply
Every copy introduces a little bit of entropy. Over time, pages that are supposed to represent the same thing start to drift apart. Search becomes less reliable. Reporting gets harder. And no one is quite sure which page is the best example anymore.
Another subtle issue: templates that look good but don’t help.
A page full of headings without instructions assumes everyone already knows what belongs where. In reality, people interpret headings differently, especially across teams or roles.
Good templates don’t just define where content goes, they explain what should go there. Placeholder text, examples, and short prompts make a huge difference.
If someone has to guess how to use a template, they probably will and they’ll all guess differently.
If any of this feels familiar, you’re not alone.
I’ll go first: I used the same outdated SEO briefing page for months. Every time, I deleted the same outdated fields. Removed the same sections. Adjusted the same headings.
Until one day it finally clicked: Wait… I could just update the template. 😄
That tiny realization saved me a surprising amount of time and frustration.
So now I’m curious:
Are you copying old pages instead of using templates?
Deleting the same sections over and over again?
Avoiding templates because they feel “almost right, but not quite”?
What are your "template sins", and more importantly, what finally helped you fix them?
Patricia Modispacher _K15t_
4 comments