A Monday-Morning Routine That Actually Catches What Stalled

Twenty-three tickets on the board Monday morning. Twenty of them are exactly where they should be. Three went quiet Friday afternoon and haven’t moved since, and those three are the only ones worth five minutes of anyone’s attention. Finding them by reading all twenty-three costs a lot more time than the problem is actually worth.

A Monday routine that actually catches what stalled starts with a short, specific list, what went quiet since Friday, not a full re-read of every ticket, because most of the week’s work is fine and only a few things actually need attention. That’s a narrower, cheaper habit than a full board review, and it’s worth building deliberately instead of either skipping the check entirely or over-investing in reviewing everything.

What’s a good Monday-morning routine for catching what stalled over the weekend?

A short, targeted look at what’s gone silent since the last real activity, not a comprehensive pass through the whole board. The routine that actually works answers one question, specifically: which tickets had movement before the weekend and none since, out of everything currently open. That’s a small, answerable list on most teams, usually a handful of items out of dozens, and it’s the only part of the board that genuinely benefits from a fresh look on a Monday. Everything that’s progressing normally doesn’t need re-checking just because a new week started.

Why is Monday specifically the right moment for this?

Because two days of no activity is a clean, natural signal that’s easy to see precisely on a Monday and easy to miss any other day. A ticket that’s had no movement since Thursday afternoon looks completely normal on a Friday, since Friday itself is still a working day and a quiet ticket might just mean someone’s focused elsewhere for the moment. The same ticket, still quiet on Monday morning, has now gone dark across an entire weekend plus whatever gap preceded it, and that gap reads much more clearly as a real stall once the weekend has passed. Monday is the cheapest, fastest moment to catch that signal, because the two-day gap that makes a stall visible has already happened by the time anyone’s back at their desk.

What should the routine actually look like, mechanically?

A short list of what went silent, generated automatically, not a manual scroll through the whole board looking for anything that seems off. The mechanical shift that matters is from “review everything and hope something jumps out” to “surface only the specific items that match the criteria: had activity, then didn’t, across the gap.” A person doing this by hand every Monday, scanning twenty or thirty tickets to spot the two or three that stopped moving without anyone flagging it, is spending real time on a task that a specific, narrow filter does faster and more reliably. The routine isn’t “look harder.” It’s “look at less, but the right less.”

One Monday, twenty fine and three flagged

Take a concrete Monday. Twenty-three tickets are open across the team. Twenty of them show exactly the activity pattern you’d expect: comments, commits, or status changes within the last day or two, nothing unusual. Three don’t. One had a PR opened Thursday with no review activity since. One shows “In Progress” with a comment from Friday morning that reads “will pick this back up Monday,” genuinely fine, just correctly quiet over the weekend. One has had zero activity since Wednesday, three full working days before the weekend even started, which is a longer, more concerning gap than the other two.

That’s the entire Monday routine: three flagged items, each worth a specific, different look, out of twenty-three total. The twenty that are fine never needed anyone’s attention this morning at all, and the routine’s whole value is in not spending time confirming that they’re fine, since a full board review would have cost the same attention on all twenty-three regardless of which ones actually needed it.

What does Thor surface automatically for this?

The same stalled-ticket detection covered in “How Do You Find the Ticket Nobody’s Touched in Three Weeks?”, running continuously and delivered specifically as a Monday digest: what went quiet, since when, and what the last real signal was before it stopped. Thor isn’t running a different detection mechanism just for Mondays, it’s the same ongoing check for tickets that had activity and then didn’t, packaged into a digest that lands right when the two-day weekend gap makes that signal cleanest to read. That digest names the specific tickets, when they last moved, and enough context, a linked comment, a PR status, to let a person judge each one in seconds rather than having to go dig up the history themselves.

Without a targeted routine	With a Monday stalled-work digest
Scan the whole board, or skip checking and hope nothing’s actually stuck	A short, specific list of what went quiet, generated automatically
Time spent confirming healthy tickets are healthy	Time spent only on the few that actually need a look
A real stall might sit unnoticed until someone happens to check	The two-day gap surfaces cleanly the first Monday morning after it starts

Why does this beat a generic weekly status meeting?

Because it’s targeted at exactly what needs a look, not a summary of everything regardless of whether it needs attention. A weekly status meeting covering every project, whether or not anything changed, spends time on the parts that are fine at the same rate it spends on the parts that actually stalled, which is the same inefficiency a full board review has. A short, specific list of what went silent skips that cost entirely: nobody’s narrating the twenty tickets that are fine, because there’s nothing to say about them, and the meeting, or in this case the five-minute check, only spends time where a decision actually needs to be made.

What does a person still do with the flagged list?

Decide which of the flagged items are genuinely stuck versus fine for a reason the routine can’t see on its own, a weekend, a timezone gap, a planned pause someone mentioned in passing. The digest surfaces the three tickets that match the pattern; it doesn’t know that one of them is fine because the owner explicitly said they’d pick it back up Monday, or that another is stuck because a reviewer’s out sick and nobody’s covering. That judgment call, sorting a real stall from an explainable quiet period, stays with a person looking at the specific context each flagged item carries. The value of the routine isn’t that it resolves anything on its own. It’s that it puts the right three items in front of someone instead of asking them to find those three items themselves inside a pile of twenty-three.

FAQ

Does this replace checking the board during the week?

No, it’s specifically a start-of-week catch for whatever went quiet over a gap long enough to be worth flagging. Day-to-day work still gets checked and updated as normal; this is the moment that catches what a shorter gap wouldn’t have surfaced yet.

What if nothing actually stalled over the weekend?

Then the digest is short or empty, and that’s the correct, useful outcome. The routine isn’t trying to always find something; it’s trying to find exactly what’s actually there.

How is a two-day gap different from a ticket that’s just naturally slower-moving?

The routine looks at each ticket’s own recent pattern, not a fixed universal threshold. A ticket that normally moves slowly and had activity a few days ago looks different from one that had activity every day and then abruptly stopped.

Does flagging a ticket mean something’s wrong with the person working on it?

No. Plenty of flagged items turn out to be completely fine, waiting on a weekend, a planned pause, someone else’s turn. The flag means “this pattern is worth a quick look,” not “this person dropped something.”

Could a team build this habit manually without a tool doing the detection?

In principle, yes, a scheduled review is a well-established productivity practice on its own. What’s hard to do manually is the actual filtering, reliably spotting the few genuinely quiet items out of a full board every single Monday without it turning into either a skipped step or a full review that costs more time than it’s worth.

See how Thor surfaces the ticket nobody’s touched in weeks. Book a demo.