Skip to content
Running Product at Brex

icon picker
Running Product at Brex

A fun (and efficient) meeting for running your product organization.
When I first joined Brex, we had three Product Managers (PMs) and no real process for coordinating across the team. We've since grown by several multiples and manage many distinct, but at times overlapping, product areas. It's critical that we (1) spend time together every week to build our organization and it's unique culture, align on top priorities for the week, and ensure we're all working together; and (2) have a clear source of truth for all product documents and decisions. Our product team now meets both objectives—with this Coda doc.

Every Monday, our entire product team meets for one hour, with three goals:
Build team culture. We ask every team member to write a "" and "win from last week." Oftentimes these snapshots are quite creative and humorous; they let us learn a little more about our teammates each week. We devote the next ten minutes to individual updates, ensuring that everyone has a voice early in the meeting.
Track progress toward key objectives. We use to track progress against internal team goals, the to quickly review upcoming launches, and to keep an eye on high-level key goals. Each page is updated before the meeting. Ideally we only discuss open questions or issues.
Discuss and align. The bulk of the meeting is focused on . Everyone writes updates, questions, and topics in this page. We spend roughly five minutes reading during the meeting and 15-20 minutes discussing specific topics.

Product team docs sprawl. They take on a life of their own. Bringing them all together, in one place, is vital to the team’s success.
We keep anything that might be interesting or helpful across the team in our library. The collection ranges from team mandates to product articles. Three specific audiences will find this set of pages useful:
Existing PMs: We have one place to look for any key document.
New team members: After taking a few days to read through our library, teammates should have enough context to participate in most meetings.
Cross-functional partners: Colleagues should know exactly where to go to find product specs or team roadmaps.

The themes and principals details above have evolved naturally over the last 6 months, and they have been increasingly facilitated and memorialized via Coda. Our weekly team meeting works really well for us, but probably isn't perfect for every team. Use this doc as a starting point for creating something uniquely valuable for your team. I hope this helps 🙏

👉 Get started:

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.