Home Insights

The questions that need two datasets

Standups tell you who is blocked. Kudos tell you who was thanked. Together they tell you something neither can on its own.

Add to Slack installs Morgenruf on the free hosted instance CloudDrove runs. Self-hosting is the same MIT code.

Member cards showing which features each person runs

Who runs what, at a glance.

Morgenruf Insights reads standup answers and kudos together, to show blockers nobody has cleared in days and people who contribute every morning without being thanked. It is part of Morgenruf, a free, open-source (MIT) Slack app for standups, coffee chats and kudos, hosted free or self-hosted.

Last reviewed September 26, 2026

09:30 The bot DMs each person 09:31 They answer in their own time 10:30 One summary posts to the channel 10:10 A private nudge to whoever has not
Where the data comes from: the answers each morning, which Insights then reads across days.

Two questions worth asking

Most dashboards count things you already knew. These two need two datasets at once, which is the only reason to have standups and kudos in one app rather than two subscriptions.

Who has been blocked on the same thing for days?

A blocker in today's standup is normal. The same blocker in five consecutive answers is a different thing, and it is invisible in a channel where each day scrolls away. Insights groups repeated blockers by person and by how long they have persisted.

Who answers every standup and is thanked by nobody?

Recognition data is skewed towards visible work. Somebody who files every morning, unblocks other people, and never gets a kudo is a retention risk that neither dataset shows on its own.

What that looks like in practice

An illustration rather than a screenshot. Say someone has written "waiting on the staging database" in five standups running. Each morning on its own reads as normal, and each one scrolls away. Across the week it is one blocker nobody has cleared, which is the pattern Insights groups by person and by how long it has lasted. The same goes for somebody who has filed every morning for a month, unblocked two colleagues in their answers, and appears nowhere in the kudos leaderboard.

What it deliberately does not do

  • No productivity score, and no ranking of people by output.
  • No reading of messages it was not sent.
  • No exporting your team's answers anywhere. It reads your database and stops there.

It can be switched off per workspace like any other module. Paying two vendors per seat to get one answer of this kind is most of why this was built in the first place.

Questions

About insights

What does Insights actually look at?

Two datasets at once. Standup answers on their own tell you who is blocked today; kudos on their own tell you who was thanked. Together they answer questions neither can: who is contributing and going unrecognised, and which blocker has been in someone's answers for days.

Is this surveillance?

It is the same information already in your channel, counted. It does not read messages it was not sent, does not score people, and does not produce a ranking of who is 'productive'. If you want a tool that tells you who to performance-manage, this is not it.

Can I turn it off?

Yes. Insights is a module like the others and can be switched off per workspace, at which point it stops running and leaves the sidebar.

Free for every seat, and that is the whole pricing page

Add to Slack puts Morgenruf on the free hosted instance CloudDrove runs, in about two minutes. Or self-host the same MIT code with Docker Compose or Helm and pay only for the server.