The artefact two teams write together is the artefact they trust.
Design teams and dev teams inside the same company drift for predictable reasons. Two languages. Two cadences. Two filing systems. One product. The standup is supposed to fix this. Most of the time it does not. People report into a meeting, the meeting ends, the doc gets forgotten, and the drift returns by Thursday.
The fix I have shipped on two teams is to make the standup carry a shared written artefact, not a shared spoken update. One Google Doc, two columns, both sides write into the same file. Design Updates on the left. Dev Updates on the right. Every person reports into one column, every day. Nobody talks over the doc. The talking is in service of the writing.
On a recent product, the doc was permanent. We could go back to last month and read what we had said about a button on a Tuesday. By the end of the first month, designers were referencing component prop names. Developers were correcting Figma layer hierarchies. A senior person walking in mid-sprint could read the last week and be useful by the afternoon.
What this taught me is that the standup is the wrong unit of focus. The real unit is the artefact the standup produces. A meeting that ends without a written line that both teams sign off on is a meeting that built no trust. A meeting that produces a permanent two-column document, even if it is fifteen lines, has built a shared memory both sides can return to.
The honest limitation is that this only works when both teams treat the doc as load-bearing. The first week a designer skips her column, the doc is dead. The same is true of dev. The discipline is enforced by the lead writing into the doc visibly, every day, including the days they have nothing new to say.
The trick is not standing up. The trick is writing down.