Marcus, in action.

A rough idea of what it looks like when Marcus is working.

Three real screenshots from our Google Chat. No fancy dashboard, no editing, just the actual thread the team works in with Marcus most days.

Google Chat thread showing Marcus posting a weekly summary listing 17 deploys, 9 issues closed, what shipped, what is pending, and a regression-watch note.
The weekly summary, posted unprompted. 17 deploys, 9 issues closed, what shipped, what is pending, and a sober note about regressions worth watching. Nobody asked for this. He just runs it.
Google Chat thread: Raquel reports a bug after renaming an option. Marcus diagnoses the cause as orphaned popover values, proposes a two-part fix, ships the immediate one with a commit hash, then Raquel replies 'I fixed it' and 'Thank you' with a smile.
Raquel hits a real bug after renaming a dropdown option. Marcus diagnoses the cause, sketches a two-part fix, ships the immediate version with a commit hash, links to a GitHub issue for the bigger change. Raquel replies "I fixed it" and "Thank you." That whole loop, start to finish, is roughly half an hour.
Google Chat thread: Marcus apologises for being offline overnight because the Mac mini ran an auto-update restart, then posts two PR ships with commit hashes and what changed, and a careful explanation of how Status columns differ from Dropdown columns in the project.
Two PRs shipped with commit hashes, plus the small detail I like most: Marcus owning that his Mac mini auto-updated overnight and took him offline. He explains it, picks back up where he left off, and gets on with it.