Suggestions for your setup

Teams set kanman up as they go: a connection here, a habit there, a request in the chat. Once a week, and soon after something in the team’s setup changes, kanman looks at the whole picture: the team’s services and connections, its habits, what kanman does on its own, the board and what you have asked for in the chat. When it sees a way to get what you are after more reliably, it suggests it.

Each suggestion follows the same shape. It names what the team does today and what for, then the better way and why:

I see the team asked me for a report story per ticket so that every open ticket gets looked at. Bringing every open ticket into the incident review would get you that even better, because each one gets its analysis on its own card and moves with the incident.

Where you find them

• In the team chat, if you lead the team: one suggestion at a time is pinned over the message box, calmly, after any open questions. The chip reads, for example, “2 questions · 1 suggestion”. Later puts it aside. A new suggestion appears at most once a day, and only after you decided on the last one. There is no notification.
• After you decide, it folds into the chat as one small line: “Applied: … · Undo”, or quietly “Not now: …”.
• Team › Habits: the section Suggestions for your setup keeps every open and recently applied suggestion, with What changes showing each change before and after.
• Your weekly brief mentions in one line how many suggestions wait.

Apply, not now, undo

Nothing changes until a lead of the team decides.

• Apply makes the change. The confirmation offers Undo, and an applied suggestion keeps its Undo button in the Habits tab for two weeks.
• Not now lets you add a short note. kanman won’t bring the same suggestion up again for 30 days.
• Everyone else in the team sees the suggestions too, with “A lead of the team decides”.

What kanman can suggest:

• any of your team’s settings with one value, such as how many stories it works on at once, a budget, or whether a person approves before a merge. Applying changes the setting exactly as its page would, and Undo sets it back;
• a change you make on a setting’s page, such as connecting your wiki or confirming a mapping. The suggestion explains why and Open the setting takes you there;
• bringing every open ticket of a ServiceNow connection into the incident review, not only the most pressing ones;
• starting, pausing or resuming a habit;
• filing cards that are no longer needed;
• ending a routine kanman kept for you by itself once a built-in does the same, or turning it into a habit you can see and change.

kanman draws on a collection of setups that work well for teams like yours (support teams on ServiceNow, code teams with merge requests, platform teams with many repositories and more), and suggests only what fits what it sees in your team.

kanman’s own check-ins

When kanman told you it will look again later (“I’ll check again at 14:00”), the Habits tab shows it under I’m keeping an eye on, with Why one tap away. If you ask kanman to do something regularly, it suggests a habit for it, so the routine stays visible and yours to change.