Should companies use a formal weekly business review with named directly-responsible individuals to stay aligned as they scale?

Matteo Franceschetti · Nov 20, 2023

Requiring written agendas increases rather than reduces velocity, and the objection that they slow things down comes from people who have never written them

He needs to digest data and sleep on a topic to reach a good answer; pre-reading and commenting turns a three-hour discussion into twelve minutes with a better conclusion

62:19 20VC: The Ultimate Hiring Playbook: Five Questions to Ask Every New Hire | What Makes Truly Great Leaders and How They Give Feedback | Do VCs Really Add Value; Lessons from Hard Fundraises with Matteo Franceschetti, Co-Founder @ Eight Sleep

Antoine Le Nel · Oct 18, 2024

Weekly problem-solving cycles beat less frequent reviews because teams stop wasting days preparing presentations and course-correct far faster

With monthly meetings teams spend the last two or three days building a deck for the exec, which is waste; with weekly cadence you just open the Jira board and dashboard and solve the problem, and you never work a month in the wrong direction before getting feedback

Scope: works within a highly standardized, matrixed team structure

32:33 20Growth: Revolut's Chief Growth Officer on The Growth Playbook Revolut Used to Scale to $2.2BN in Revenue | How Revolut Launch and Grow Products | Why the Best PMs Don't Need A/B Tests & Why CAC is a BS Metric with Antoine Le Nel

Matteo Franceschetti · Nov 20, 2023

The best meeting memos are shorter, straight to the point, data-driven and very clear — and it typically takes at least six months to develop someone who can write one

56:08 Best memos are short data driven and take months to learn to write

Matteo Franceschetti · Nov 20, 2023

A good meeting agenda follows a fixed framework: executive summary with key data, then a section per OKR/goal covering what's working and what's not working, all supported by data, ending with action items each assigned a DRI and a deadline

The structure forces clarity and data-driven thinking, and action items with owners and deadlines make outcomes enforceable

57:02 Agenda follows fixed framework of summary per goal sections and dri owned action items

Matteo Franceschetti · Nov 20, 2023

Meetings should not walk through the agenda at all — everyone reads it in advance and the meeting only works through the comments left on the doc

Anything not commented on is assumed understood, so a four-page agenda can produce a twelve-minute meeting

58:48 Meetings should run through async comments on a pre read not a live walkthrough

Matteo Franceschetti · Nov 20, 2023

Showing up without an agenda is acceptable only if a P0 emergency consumed the time; if it was a failure of planning, the meeting gets cancelled and that is not okay

A genuine P0 has real value and deserves focus, while lack of thoughtfulness in scheduling is just poor planning

60:12 Missing agenda is excusable only for a genuine emergency not planning failure

Matteo Franceschetti · Nov 20, 2023

Training people to write good agendas is mostly trial and error inside recurring meetings, with executives correcting drafts over time

Beginners write long, unclear, non-data-driven documents and improve only through iterated feedback from executives

61:38 Agenda writing skill develops through iterated executive feedback over time

Noah Desai Weiss · Jun 16, 2023

The biggest unsolved process problem in product building is knowing the actual latest state of every major area of the company — Slack itself doesn't solve it, and organizations fall back on manual spreadsheets because software is too rigid to.

Opening a random team channel is too noisy to tell what the latest is or whether something needs review; the workaround is a weekly meeting reviewing quarterly priorities in a spreadsheet.

18:26 No software solves real time cross team visibility so teams fall back to weekly spreadsheet reviews

Fernando Fanton · Jul 27, 2025

The weekly business review — a fixed list of ~10-20 objectives, each with a named directly responsible individual who writes what's happening, why, and what they're doing about it — is the right operating rhythm for a scaling company

Startups can rally around one thing the founder names, but at scale there is more than one thing, and companies compensate with proxies instead of learning to communicate the actual objectives; transparency, data and weekly rhythm solve this

34:35 Weekly business review with a dri per objective is the right operating rhythm at scale

TJ Parker · Jun 5, 2023

Founders should be selfish about who attends the weekly business review, because the meeting's attendee mix determines what the whole company focuses on.

Divide the meeting's hours by the number of people in the room and each attendee effectively gets that much airtime, so including HR, legal and finance leaders means spending large fractions of your most critical meeting on promotions and leveling.

26:26 Limit meeting attendees to those whose presence should set company focus

Matt Lerner · May 31, 2024

A weekly growth meeting reviewing experiments, learnings and numbers is critical because it functions both as an information-sharing pump and as a forcing device on the pace of experimentation

Sharing everything learned makes the whole team smarter and generates ideas nobody had walking in, while the fixed cadence makes people finish experiments by the deadline

38:43 Weekly growth experiment review meeting serves as information pump and pacing forcing device