The internal SME review cadence we kept
Weekly 20 minutes beats monthly 90. A year of iterating on our own SME review rhythm, and the cadence that finally stuck.
We started with monthly 90-minute SME syncs because it felt like the respectful way to use engineer time. Ninety minutes is enough to cover ground. Once a month is infrequent enough that it doesn’t cannibalize real engineering work. The meeting invite sat on the calendar for seven months. We kept six of the seven.
It was the wrong cadence. A year in, what we kept is weekly 20-minute SME reviews. Here’s why the tradeoff went the other way than I expected.
The monthly 90 problem
In a monthly cadence, the SME walks into a meeting with four proposals’ worth of context they haven’t seen for 30 days. Ninety minutes sounds like a lot until you try to reconstitute four pursuits, review three evidence attestations that are about to expire, and look at the rejected reviewer feedback from last month’s gold team. The meeting ended with a list of action items that I would carry, the SME would acknowledge, and nothing would happen on.
The Qorus industry benchmark — 48% of teams cite SME collaboration as their top challenge, unchanged for five years — describes exactly this failure mode. It’s not that SMEs don’t want to help. It’s that a monthly meeting asks them to re-enter context they’ve forgotten.
The weekly 20 shift
Twenty minutes forces two things. First, the agenda is literally one or two items — whatever is on the critical path this week. Second, the SME remembers last week, because it was last week.
We protect the 20 minutes as a hard stop. If we don’t finish, we don’t overrun — we pick up next week. This is the discipline that actually made it work: the stop matters more than the start.
The weekly rhythm also changes what gets on the agenda. In the monthly, everything went on the agenda because it was the only slot for 30 days. In the weekly, only this-week-critical items go on it, because there will be another meeting in six days. The agenda self-prunes.
What fills the gap between meetings
Two things we added that made the short meeting sustainable:
A Slack thread per active pursuit. Not a channel — a thread in the proposal channel, one per live bid. Questions go in the thread, the SME answers async when they have a minute, the thread becomes the reviewable record at submission. Quilt’s bottlenecks post makes the case for async-first SME communication; we’ve come to think it’s the only thing that works at scale.
A weekly “questions-for-the-SME” doc. Three to six questions, each with context, shared Friday morning. The SME reads it over coffee before the Monday 20-minute review. When we walk into the meeting, they’ve already decided what their answer is — the meeting is for nuance and the next-step decision, not for thinking out loud. This is the move that made the meeting feel fast instead of rushed.
What we tried and abandoned
Office hours. I set up a standing weekly office hour where any proposal writer could drop in with an SME question. Nobody dropped in. The activation cost — deciding if your question was worth interrupting, joining a call — was too high. Async and the 20-minute review absorbed all of it.
Pairs. Writer and SME sit together for an hour. Tried it twice; once it worked, once it was two people staring at a document. The failure mode was structural: pairing works when both people have already thought about the problem. When the writer hasn’t thought about it yet, they’re asking the SME to carry the cognitive load.
Ticketed asks in a queue. We built a ticketing system where writers would file requests and SMEs would pull from the queue. It worked for mechanical questions (“what’s the current version number of product X”) and failed for anything that required judgment. Ticketing was too impersonal for nuanced asks. The weekly meeting re-absorbed those.
See the part-two post in the SME collab series for the honest retro on the ticketed approach.
What the ritual looks like now
Every Monday, 20 minutes, one SME per meeting. The format:
- 5 minutes — walk through the week’s critical question list (which the SME has pre-read).
- 10 minutes — discussion on the two most consequential items.
- 5 minutes — decide who does what by when, written into the pursuit’s action doc.
We don’t do AOB. We don’t do “what else is on your mind.” The short container is the feature.
Who this doesn’t work for
One-person shops where the SME is the proposal writer. A 20-minute weekly meeting with yourself is a journaling practice, not a review cadence.
Teams with rotating SMEs. If no single SME has ownership of a content area, the weekly 20 fragments into five different 20s and you’re back to the monthly 90 in aggregate. The cadence presumes named ownership. Without it, the ritual collapses.
The one-line takeaway
Short and frequent beats long and rare, in any discipline that depends on remembered context. SME reviews are a discipline that depends on remembered context.