Designing the meeting as a product
Shishir Mehrotra, co-founder and CEO of Coda, argues that strong product teams invest as much in how work gets done as in what ships. 
Meeting rituals recur in three forms, and a healthy team maintains a mix of all of them. Shishir Mehrotra and Elise Keith, founder of Lucid Meetings, developed this taxonomy to slot every meeting type into one of three buckets.
- Cadence meetings — staff meetings, stand-ups, project syncs. Recurring with the same group, they follow a set cycle of setting goals, executing and reflecting. The question they answer: "Are we on track for the goals we set?"
- Catalyst meetings — decision-making forums, product reviews, design crits. Direction-changing by nature, they can burn out a team if there are too many. The question they answer: "Did we get an answer to our question?"
- Context meetings — All Hands, off-sites, new-hire orientations, one-on-ones. Focused on sharing information and building connections, they have the broadest outcomes: "Did we come away better enabled to do our job?"
If you ask people to name this ‘employee product,’ they would most likely call it ‘culture.’ But if you ask them to really describe it, describe how it works in practice, they will immediately start describing the company’s rituals.“If you ask people to name this ‘employee product,’ they would most likely call it ‘culture.’ But if you ask them to really describe it, describe how it works in practice, they will immediately start describing the company’s rituals.”
Templates exist for getting started with each: Dory/Pulse, Bullpen, The Eigenquestion and Braintrust.
Cadence meetings need rituals of their own
When JFK committed in 1961 to putting a man on the Moon by the end of the decade, he scheduled a weekly meeting with the head of NASA to keep the goal on track—a classic cadence meeting. Such meetings move work forward but are rarely inspiring. Asked to describe how their cadence meetings feel, 50 people from 50 companies produced answers like "boring," "a chore," "inhuman," and worst of all, "something I have to attend instead of want to attend." The best teams counter this with distinctive rituals that drive engagement.
One example is YouTube's Bullpen: a 90-minute block with the leadership team and intentionally no agenda. Small groups form quickly and multi-threaded conversations emerge at once, absorbing the ad-hoc five-minute exchanges that would otherwise become dull single-threaded agenda items or 30-minute meetings that are impossible to schedule. At Coda, Bullpen is used for smaller groups, sometimes impromptu one-on-ones, typically no larger than seven or eight people.
The format proved popular enough to run multiple days per week in place of other meetings, and it spread across Google and to other companies. Coda, as a distributed team, could not simply put everyone in one room and let them self-organize, so it built a workflow in which people list topics, indicate who they need and estimate the time required; groups stay at seven or eight people, and the system flags conflicts so discussions can be ordered. Because it lives in a table, its impact is measurable: at a recent Bullpen, the team covered 30 topics in a single hour—the value of being multi-threaded.
Coda's favorite cadence ritual is Dory/Pulse. Rather than raising hands or trying to get a word in, participants add discussion topics to a "Dory" and upvote or downvote them; the name comes from the fish in "Finding Nemo" who asks all the questions. Pulse handles feedback and alignment: everyone writes a numerical score reflecting their alignment on a decision—ship this feature, hire this person, buy this company—plus a written rationale, with all responses hidden until everyone has answered, which combats groupthink.
For an entirely different register, there is the "Reset," which Ariana Huffington adapted from Stripe's "spin the wheel" process. Research into neuroscience behind her company Thrive holds that a 60- to 90-second Reset can change the brain's orientation. Her version is a breathing exercise paired with a video montage of family, her hometown in Greece and favorite quotes, playable at the start or end of a day or in stressful moments. Every team member creates a personal Reset montage of images, sounds and words; at the start of a meeting, someone is picked at random to play theirs. It works both as a team meditation that sets the right mindset—a key cultural value—and as an icebreaker that builds human connection.
Decision forums and the people in them
Catalyst meetings center on a topic that needs a decision or a question that needs deeper exploration. Making decisions inside a stand-up or staff meeting fails because such meetings contain the wrong people: the full exec team may not be needed for a product call, while those who understand the nuances may be absent. The best teams keep a separate decision-making forum, and these forums have no standing attendees. Reviews named "Product review" or "Launch review" tend to bloat, and sheer attendee count adds friction instead of unblocking work. Inviting only those strictly necessary for each decision lets meeting owners assemble the right room, and the result at Coda has been a 10x increase in decision-making volume.
We've found that the best teams actually have a separate forum for decision making, and here's the catch: These decision making forums have no standing attendees.“We've found that the best teams actually have a separate forum for decision making, and here's the catch: These decision making forums have no standing attendees.”
Effectiveness in such a forum depends above all on framing the problem. Amazon's press release and FAQ is the most famous standardizing ritual: before a line of code is written or Figma opened, the team writes a press release validating intent and answering likely customer questions, forcing consideration of whether customers would be compelled to try the product and allowing adjustments before it is too late. Square's Spade template and Zoom's root cause reasoning write-up follow a similar pattern of a distinct catalyst forum.
The Eigenquestion is another tactic for expediting decisions. The name is invented, borrowed from the mathematical eigenvector—the "most discriminating vector in a multi-dimensional space"—though the math isn't required. When questions are ranked by urgency or impact, the framework re-ranks them to surface the one likely to answer most of the others first, so effort goes into asking the right question rather than hunting for the right answer.
Braintrust: feedback without approval
Since 1979, Pixar has produced 24 feature-length films and earned 23 Academy Awards, and when anyone there is asked the secret, they name a ritual: the Pixar Braintrust. Filmmakers regularly schedule screenings with the group, which watches together and listens for reactions—noting when the audience laughs, when they cry, and how much—followed by a frank discussion. A film averages eight Braintrust screenings before release.
The role definition is the striking part. Role taxonomies like RAPID, DACI and RACI all begin with an explicit "approver," which easily disempowers the truly responsible driver. At Pixar, the Braintrust approves nothing, and bringing a film to it is not even required—yet every filmmaker does. Coda renamed its Approver role to Braintrust and wrote down principles such as "Add Lift not Drag," so that reviews and reviewers are not dreaded: feedback is a gift, and should be seen that way.
Rethinking the one-on-one
One-on-ones are usually treated as places to unblock decisions or check progress, missing their more important purpose: coaching employees on how to grow. Jenny Emick, a design lead at Square, kept hearing designers complain that meaningful career feedback arrived only during the performance review cycle—objectively a terrible moment for a career conversation, and far too infrequent. Auditing the design team's one-on-ones, she found they all looked alike: a standing meeting with the manager, usually accompanied by what she called "a forever scroll" Google doc of date-and-notes entries running to about 60 pages.
Her replacement was a new agenda template in Coda, with separate pages for meeting notes, goals and career development, forcing a more regular discussion of where each team member is headed. At the front of the doc sits a "partnership agreement" in which employee and manager write down their expectations for each other. It functions as a meta ritual: by having every pair craft their own partnership, it signals that each pairing is unique, that there is no perfect one-on-one, and that the pair must develop its own way of working together.
Packaging the rules into practices
Mehrotra's ten rules are meant to be usable rather than admired. Several of them translate directly into artifacts a team can maintain: a shared doc of standing decisions, a template that assigns the driver, a default of one decision per meeting, and a regular 10/10 review in the calendar rather than in intention.
- Write it down. A decision that never leaves the room cannot bind anything.
- Name the driver. Ambiguity about ownership is the most common reason meetings repeat themselves.
- One decision per room. Bundling decisions dilutes accountability for each.
- Review the meeting, not just the work. A periodic 10/10 review surfaces what to drop.



