Habit ideas to copy | kanman documentation

Every idea below is a sentence you can paste into the chat as it is. kanman answers with a habit card that says when, what and where; change anything by answering in your own words, then choose Start it. Times follow your team’s week and working hours, and a habit that has nothing to say on a given day stays quiet.

Keep the team informed

Try this in the chatIn your team's chat

Every Friday at 15:00, post what we shipped this week
Every Monday at 9:00, tell us what waits on people
Post a short daily update at 9:00 in our team chat
Every Wednesday at 10:00, tell us which stories have been waiting in review for more than two days
Every second Thursday at 14:00, draft the sprint review: what we planned, what we shipped and what moved

Guard quality

The built-in habit Review merge requests takes your words and follows them in every review.

Try this in the chatIn your team's chat

Review every merge request people open, not only when we ask
When you review, always flag changes to the auth module
When you review, check that every new endpoint has a test and an entry in the changelog
Every Monday at 9:00, tell us which merge requests have waited longest for review

Keep repositories healthy

The built-in habits Watch main and Keep dependencies and security current do most of this already. Tell them how your team likes it:

Try this in the chatIn your team's chat

When main turns red, tell us in the team chat who is looking at it
When a new critical vulnerability is found, fix it across all our repositories and ask me before you merge
Every first Monday of the month, check our repositories for outdated dependencies and group the bumps into one story per library

Handle alerts and tickets

These need the matching connection or a team webhook. kanman never acts in production on its own; what it may do in each system follows the connection’s mode.

Try this in the chatIn your team's chat

When our checkout alert fires, open an incident and keep us posted until it's resolved
When a Jira issue moves to Ready for development, check it has acceptance criteria and ask its author once if not
When a new ServiceNow incident is assigned to our group, look for the cause in our code and add what you find as a work note

Just for you

Habits you make in Personal report only to you and show up on For you. Nobody else sees them.

Try this in the chatIn Personal

Every Monday at 8:00, brief me on my teams
Every Friday at 16:00, tell me which of my merge requests are stuck
Fridays until one I focus. Hold anything that can wait.

Once is enough

Some things you need only once. kanman keeps them under I’m keeping an eye on and lets them go once they happened. Ask for the same thing three times, and kanman offers to make it a habit.

Try this in the chatIn Personal

Tell me when !412 merges
Tell me when main is green again
Remind me on Thursday about the change freeze
Tell me when the next release of the billing service is tagged

Change, pause and look back

Habits are made and changed only in the chat. The Habits tab shows them; the chat changes them.

Try this in the chatIn your team's chat

Which habits do we have, and what did they cost this month?
Post the Friday summary at 16:00 instead
Pause the retro prompt until after the release
Stop the daily update

What makes a good habit

Say when, what and where. “Every Friday at 15:00” is clearer than “regularly”; “in #team-platform” is clearer than “somewhere”.
Start small. One short post that people read beats a long report nobody opens. Add to it once you see it work.
Let it stay quiet. A habit that has nothing worth saying says nothing. You do not need to ask for that.
Keep it within the team’s rules. A habit can be stricter than a connection allows, never looser. Anything that writes outside kanman asks first unless your team chose otherwise.

How habits work in detail, who may change which habit and what the built-in habits do: How habits work and Built-in habits.