Team Operating System: Rhythms and Rituals for Growth
How to build a team operating system: the six parts of our Team OS, from charter to source-of-truth reports, and how to roll it out so your team starts aligned.
Published 3 min read
Hey All, Happy Friday.
I'm currently operating on no sleep, juggling a new baby at home, and my managers graciously met with me yesterday, to help me get through our 2025 Team OS.
Where does the idea of a team operating system come from?
A couple of years ago, I stumbled on one of the most impactful papers I've ever read: Rituals for Hypergrowth, which takes an inside look at how YouTube scaled.
Shishir Mehrotra described how YouTube, in its early days, obsessed over its operating model: its planning cycles, communication norms, meeting cadence, and decision-making processes. It wasn't just about "having a plan"; it was about creating shared rituals and rhythms that would guide everyone toward the same goal.
Now, my team and I document our operating system every year, and honestly, it's never been more important.
Why is a Team OS the glue that holds a team together?
Planning season means long hours, budget discussions, and making tough calls. Once you have the strategy and goals, how do you ensure your team is aligned and ready to execute?
The answer: Build your Team Operating System (OS).
What goes into a team operating system?
With a fully remote team, it's important to document how they'll operate. Here's a breakdown of our team model:
- Team Charter: What's our mission? What's our business objective? Simply put, why are we here? This is a one-page compass for all of our decision making.
- Audience Insights: Who are we reaching? What do we know about them, and how do they bring value to our business?
- Strategy & Plays: Specific programs we'll invest in, Directly Responsible Individuals (DRIs), and key performance indicators (KPIs) they'll be accountable for.
- Roles & Responsibilities: Define each role clearly with monthly deliverables. Everyone knows what they own and what they need to deliver. The secret? The deliverables provide the role clarity.
- Communications: Set a regular meeting cadence and define Slack norms. Keep meetings small and purposeful: 3-5 people to move things forward, avoid large committees that slow things down.
- Source-of-Truth Reports: Dashboards and reports that serve as our single source of truth. Use these to track progress, adjust if needed, and keep everyone informed.
How do you roll out a Team OS with your team?
Spend a week documenting your operating model. Present it to your team, invite feedback, and refine it together. I promise you, by January 1st, your team will be aligned and motivated.
When you're scaling a team, especially in a remote or hybrid environment, clarity and consistency are everything.
The Team OS allows everyone to be on the same page, even when things get messy. Done right, it turns ambitious goals into a shared mission, and a collection of individuals into a team.
Until next time ✌️
Kyle
P.S. Shoutout to Drea, Rob, and Alanah. Appreciate everything you do for your team.
Questions (FAQ)
What is a team operating system?
A Team OS is how you ensure your team is aligned and ready to execute once you have the strategy and goals. It allows everyone to be on the same page, even when things get messy.
What should a team operating system include?
Here's a breakdown of our team model: Team Charter, Audience Insights, Strategy & Plays, Roles & Responsibilities, Communications, and Source-of-Truth Reports. Strategy & Plays covers the specific programs we'll invest in, the Directly Responsible Individuals (DRIs), and the KPIs they'll be accountable for.
Where did the idea of team rituals and rhythms come from?
It comes from Rituals for Hypergrowth, one of the most impactful papers I've ever read, which takes an inside look at how YouTube scaled. Shishir Mehrotra described creating shared rituals and rhythms that would guide everyone toward the same goal.
Why does a remote team need a documented operating model?
With a fully remote team, it's important to document how they'll operate. When you're scaling a team, especially in a remote or hybrid environment, clarity and consistency are everything.
How long does it take to build a Team OS?
Spend a week documenting your operating model. Present it to your team, invite feedback, and refine it together. I promise you, by January 1st, your team will be aligned and motivated.
Sources
How this was made Originally published in Kyle's newsletter, Brand to Demand (Edition 6, November 22, 2024). Written by Kyle Denhoff from first-hand experience growing the HubSpot Media Network. Edited for the web with AI help: headings, the summary and questions were added, and claims were checked against the sources above.
- Marketing executive on the HubSpot Media Network for nearly five years
- Helped build HubSpot's media brands, including The Hustle and My First Million
- Led content for HubSpot's YouTube channel and State of Marketing report
The newsletter
Get one idea a week.
On content, distribution and demand.
You're in. Watch your inbox for the next issue.
Free. Unsubscribe anytime.
Keep reading