If your company is a wheel, the product team is the hub and product managers are the spokes. Most of them operate solo within the context of cross-functional teams, connecting many different disciplines while needing to remain connected to each other, too.

That requires supreme organization, a deep understanding of other teams’ work, and an ability to show everyone company-wide how it’s all coming together.

With everyone working across projects, a wiki anchors PMs to the important information they need — like process guides, user feedback, and who’s working on what. Without a wiki, no one follows consistent steps to solve a problem. No one communicates. Wheels spin, but don’t really go anywhere, and the quality of the end product suffers.

An effective wiki connects your PMs through documented standards and practices everyone on your team can access, streamlining execution and upholding transparency.

Here, we'll walk you through building your own product team wiki using Notion (some of you might call it a knowledge base), and show you how it can save time, lead to healthier collaboration, and result in a much better experience for your users.

In this piece, you'll learn

• How to create a wiki for your product team, step by step
• How to customize it to match your team's needs
• How to use features and integrations that are beneficial specifically for product managers

At the end, you'll be able to build a wiki like this for your product team:

A wiki is an investment in your product

If you’re going to build something people love, you need a wiki that enables your product team to grow and execute to a high standard. Without centralized documentation, your team will become increasingly disorganized with high fluctuation in quality.

Even if you do have guides and principles, they may be scattered and inaccessible. That's basically the same as not having them at all.

Your team deserves a single resource for:

• Teams, roles, squads and their tasks — a directory of who's responsible for what features and products, what teams they’re working with, and how they're solving big problems together.
• A neatly organized table of past learnings from user feedback, customer interviews and projects, each tagged so they’re easy to find and turn into actionable product improvements.
• A reference point for everything your team does, which can be used by new and existing team members — OKRs and goals, onboarding resources, dashboards of data from experiments and your core product-building philosophies.

A clearly organized wiki becomes your product's standard-bearer, holding together PMs fanned out across projects. It gives them a playbook.