Hey Reader,

​

I'll be honest - this week, I froze.

​

I had every intention of posting an announcement on LinkedIn for this newsletter project. Didn't happen.

​

Why? Perfectionism.

​

Knowing my own network will see it made me spiral. Suddenly, every little flaw felt massive. I wanted the website to be prefect. The positioning airtight. The message polished.

​

But here's the truth I'm learning (again): "Perfect" is just a fancy form of procrastination.

​

So this week, I'm choosing progress. I'm reminding myself that done beats perfect. And if you've ever held back from shipping something because it wasn't flawless- hey you're not alone!

​

Here's to hitting publish even when it's not perfect...
​

Now, onto this week's newsletter! 🎉

​

​

📣Spotlight Story

​

Top 3 Doc Mistakes Teams Make (and How to Fix Them)​
​

We have all been there. You spend weeks assembling a knowledge base. Your team quietly ignores it. The problem usually isn’t laziness. It is that the docs themselves create friction. These are the three most common mistakes I see teams make and some straightforward ways to fix them.

​

​

​

💡Weekly Pro Tip

​

Assume your future self (or teammate) has zero context.

​

This is a huge mindset shift that separates good documentation from confusing chaos.

​

Don't just explain how to do something. Start with:

​

• What is this page/doc about?
• Why does it matter?
• When should someone use it?
• Who owns it or is affected by it?

​

Context builds confidence. It turns a "do this" checklist into something actionable and trustworthy.

​

When a new teammate lands on a page, they should immediately know if they're in the right place - without needing to ping you for clarification.

​

If your doc reads like a Teams message dropped into a wiki... it's not done yet! 😉

​

What your documentation to actually be used? Start by giving readers the backstory they didn't know they needed.

​

​

❓Question of the Week

​

You're right to worry about the balance. But here's the rule of thumb I use:

​

If someone opened the doc/page with zero prior knowledge, could they:

​

1. Understand what the page is for?
2. Decide if it's relevant for them?
3. Take confident action?

​

If the answer is "no" to any of those, you need more context.

​

"Context" doesn't mean writing a novel. It means writing one clear paragraph that sets the stage. Think:

​

• Why this is
• Why it exists
• When to use it
• Who it's for

​

That tiny bit of context saves hours of Teams pings, confusion, and backtracking later. Trust me - your future self will thank you.

​

​

🔜Sneak Peek

​

Coming soon: Setting up Confluence Templates That Scale

​

Confluence makes it easy to create pages. Sometimes it is too easy. A handful of well-designed templates can bring order to the chaos. This post will explain why templates matter, when to use global vs space templates and how to build scalable blueprints using macros like Page Properties. It's going to be a good one! 😄

​

​
Well... that's it for this week. See you next week!

​

Finally aligned,

Josh