, we build intelligent systems that transform people’s lives through fitness, health, and wellness. Our smart home gym machine bundleshardware, software, and content that trains millions of members to become their strongest. The mounted equipment, the clean interface, the world-class coaches—the individual components of the system are each top-notch. But those components alone don’t lead to the transformations we see in our members. The magic happens when you combine everything into one seamlessly-connected and convenient system.
As a Product Manager leading Tonal’s Content Experience, I’ve learned that my team deserves a parallel intention—that it’s important for our internal operations to tap into that same systems-mindset to power our product. At the heart of our internal system is a team hub that bundles all the pieces of shipping a great product into a single Coda doc, including:
Like Tonal’s product, our team hub makes work feel seamlessly connected. By centralizing our work in one place—key docs, meetings, tools, and slide decks—we eliminate much of the “work beneath our work”.
But it wasn’t always that way.
Before: Scattered artifacts → Confusion and wasted time.
Previously, our product system was fractured. PRDs lived in dozens of scattered Google Docs, roadmaps and goals were duplicated across stale spreadsheets, and decisions were made with slide decks that became outdated the moment they were shared.
This led to confusion from everyone on the team. “Where’s that link again? What’s the latest progress on our OKRs?” And worse, product managers wasted time copying, pasting, and re-telling the same story again and again.
After: Team Hub → Organized and effective collaboration.
Now, our product Team Hub is the single link where our work gets done. It allows us to connect our data in a way we never could with docs and sheets. And it’s even become the glue between teams like product, engineering, design, UXR, and marketing. Our team hub has fundamentally reshaped the way we communicate and collaborate—I can't imagine working without it anymore. That’s why I’m excited to share a few reasons why we built this centralized hub.
1. Organization simplifies wayfinding.
The fun part of building product is that things constantly change. As our ideas and processes evolve, our team hub easily flexes to meet our needs. When we need more space, we just create a new page in the doc. This allows us to have just one link for our entire product planning and execution process:
and keep working on it with the team, right inside the Coda team hub.
Because our key documents and apps are integrated in a central hub, we have a true single source of truth.
2. Connected data automates reporting to executives.
One of a PM’s primary jobs is hopping between altitudes: going down into the weeds with an engineer at 10:00 am, then convincing an executive of a high-level product vision at 11:00 am.
Typically, a PM bridges this gap by manually summarizing the executional details into concise summaries for executives. The problem? This requires a tremendous amount of manual copying and pasting. What a waste of time.
After using Coda for a bit, I’ve started thinking in pages and tables. It’s such a better way to organize and communicate ideas. I don’t think I could live without it. Now, traveling between altitudes is so much easier because of two key features in our team hub:
, but each person on the team can have their own view of the goals relevant to them. I look at my view of the table every day. Meanwhile, executives can look at their own personal views of the same table. When the data is updated in one view, it simultaneously updates in all the other views.
This ultimately leads to trust. The executives visit the same link each week. They have confidence that the data is current and up-to-date because it’s connected to the actual work. And because the dashboard self updates, I can spend more time on more impactful work.
3. A network of hubs connects teams.
A funny thing started happening when we rolled out our Product Team Hub. When an engineer had a question about our OKRs, we sent them our team hub link. When marketing wanted to see the progress of a Jira issue, we sent them our team hub link.
Soon, other teams realized they could answer many of their questions just by looking in our team hub. Then, those teams created their own hubs.
Within Tonal, there is now a network of inter-connected team hubs. We recently learned that some teams spend just as much, or even more time in our team hub than our own team does. The hub has naturally become a nexus point for cross-functional collaboration:
Within the team: by organizing work into pages and connecting all our specialist apps into one place.
Between teams: by giving space for engineering, design, UXR, and marketing teams to work together.
Between altitudes: by facilitating both top-down and bottom-up communication between executives and teams.
Between team hubs: by syncing important pages between and data between docs.
In short, our team hubs replace siloed documents and spreadsheets with an all-in-one platform for our work. While each team customizes their own hub to fit their unique rituals, they all serve as a single source of truth, keeping everyone in lockstep.
Ready to build your own team hub?
Feel free to explore Tonal’s team hub using the page list on the left. When you’re ready to build your own team hub, you can copy this simple template and follow the guided onboarding.