Goal settings
Everything a goal carries lives in one Edit goal window. This page follows its categories the way you see them in the window's left column; the quick summary table is in the map overview.
Where to find it
The window opens with a double-click on a node in the map, or with the pencil on the card (the only way on a touch screen). In a shared map where you are only a collaborator, this opens your own steps; other people's you can look at. On the Tasks page the pencil on a row opens the same window.
Three buttons are always at the bottom: Move to stash (the goal leaves the map for your idea stash; sub-goals stay and get detached), Cancel and Save.
Basics
Title, description, status, icon and color.
- Status — To do → In progress → Done. It changes by clicking right in the map, here and in the task table; it is the same value everywhere. The status colors are deliberately the same in every skin: red overdue, amber in progress, green done.
- Node icon (optional) — the smiley button opens the icon picker: a search field on top (Czech and English, accents ignored — “goal” finds 🎯), a Recently used row, categories with about two hundred icons and a Custom character field for any emoji from your keyboard. The recently-used row is remembered by the browser. The icon shows in the map and in the task table.
- Background color — preset colors or a Custom color. Color and icon are purely visual: they have no effect on statuses, progress or notifications.
Formatting the description
Above the description there is a bar: Bold, Italic, Strikethrough, Heading and Subheading, Bulleted list, Numbered list and Insert link. Ctrl+B and Ctrl+I work. A filled-in description opens Locked (read-only, so you don't overwrite it by accident); the Edit button unlocks it.
The link button offers From this goal's attachments — a click inserts a link named after the attachment — or a Custom address with your own label (What the link should be called). The description then reads “records” instead of an address across the whole line. On the card in the map the description shows without formatting marks — one or two lines fit there.
Assignment
Deadline, assignee, a due-date request, a reminder and recurrence.
- Deadline — optional. Past the deadline the goal lights up red in the map. A plan is not a deadline: in My day you can plan a task for today without committing the goal to a date — see Tasks and My day.
- Assignee — who is responsible for the step and who gets the notifications (such as Goal is ready when the goal gets unblocked). If you assign someone without access to the map, the app offers to share it right away. Below the field you see who assigned the task (Assigned by: …).
- A due-date request — only the assigner changes the deadline (Only the assigner can change the due date). Everyone else has a Propose a different due date button: pick a date, write a reason and Send request. The assigner then sees a panel “… proposes …” in the window with Approve (saves the goal with the proposed date) and Decline; the card shows the Due date request badge. The requester can Withdraw their request.
- Remind me of the deadline — below the Deadline field: on the deadline day, the day before the deadline (the default, at 16:00), 2 days or a week before the deadline, plus the hour. The reminder is yours only, does not change the deadline and moves along with it. Details in Calendar.
- Recurrence — daily, weekly or monthly, on chosen weekdays or every N-th; see below.
A task is a goal with an assignee or a deadline
In killBottleneck a task is no special record: a task is a goal that has an assignee or a deadline. As soon as you set them here, the goal appears in the assignee's My day and the deadline notifications watch it. Whatever belongs to no map is an idea in the stash.
Recurrence
A goal can repeat: the switch Does not repeat / Daily / Weekly / Monthly, for weekly the weekdays (e.g. Tue and Thu), for monthly the day of the month, and every N-th (every 2 weeks, every 3 days…, 1–4). When marked Done it returns to To do by itself and the deadline advances in the rhythm of the original deadline: every Monday stays a Monday, the 31st stays the 31st (the last day in shorter months), an even week stays even. Past occurrences are skipped to the nearest future one. A goal without a deadline gets the first occurrence when you switch the rhythm on. The note below the switch says what will happen.
On the next occurrence the “when I'll work on it” plan is cleared and the reminder stays and moves with the deadline. In a process the goal also puts its sub-steps (and their tasks) back to To do — a checklist starts over. The card shows the rhythm in words (🔁 every Monday) to everyone who can see the map.
Under the hood it is an ordinary automation rule (“when Done → set back to To do and advance the deadline”), which you can also see in the map's Rules. If you edit it by hand there, the switch notices (This goal's recurrence is driven by a manually edited rule) and leaves the rule alone. A recurring goal carries the 🔁 badge with its rhythm — and a map with such a goal never reports “All done”. For maps that keep running rather than finish, see Project and process.
Attachments
Files and links pinned to the goal: Add attachment (a file), Add link (Drive, OneDrive, SharePoint, e-mail…) and, where Google sign-in is on, Pick from Drive. A Gmail link gets an envelope icon, Google Drive or Docs a triangle — and without your own label a readable name instead of a truncated address. Each attachment has Copy link, Open (or Download) and Delete.
On instances that don't store files (KB Cloud Start) there is only Add link and the note This instance does not store uploaded files — attachments are added as links. When a rule with the “a file is uploaded to a node” trigger targets the node, the window says so in advance: Uploading a file starts the automation “…” right away.
Tasks & comments
The goal's sub-tasks and the discussion under it. This category and Attachments show a count in the left column, so you don't have to click through to find the comment you saw on the card.
History — who did what and when
One row = one event, with date and time, newest first. It answers the question nobody else can — “why did this goal slip by a week and who decided that?”
Recorded are the goal's creation and deletion, a change of status (Status: To do → In progress), deadline, owner, title, a move under another goal, a change of the brief, icon, colour, executor and waiting for sub-goals, added comments, attachments and links — and rule interventions (Rule “…” ran / failed / skipped). Every entry says who did it: a person, rule, agent, AI assistant or system.
A few things worth saying up front:
- Content is not copied here. For briefs and comments you see that they changed, not the full text.
- Moving a card around the canvas is not recorded. Tidying the map would flood the log.
- A deleted comment or attachment disappears from the history too. A deleted goal keeps the Goal deleted row.
- The history reaches 400 days back. Older entries are cleaned up automatically.
- The history is not part of a publicly shared map.
Automation
- Who performs this — Person or Automation. Even when a machine performs the step, the assignee stays human: The assignee stays human — even for an automation it is the assignee who gets notified. Plus the Which automation does it field (if the name matches an agent in the registry, killBottleneck can start it itself) and the I would like this automated switch, which lets the AI agent managers know. See Automations and agents.
- Wait for children — Until every goal under this node is done, the node waits (⏳). See waiting and blocking.
- Rules for this node — which automation rules target the node, with the run log and a button for a new rule. See Rules.
The org-structure map
In the org-structure map the window has a different set: the Position category with the Position / function name, Kind (Position / Function), Holder and Deputy of this position fields. See Org structure.
Limits
- Only the assigner changes the deadline; others only propose. A goal with an assigned task can be removed from the map only by the assigner or the project owner.
- A filled-in description is locked after opening — the Edit button unlocks it; it's not a bug.
- The recently-used icon row is remembered by the browser, not the account.
- The history reaches 400 days back and does not show the content of changes.
Related
- The map and goals — the whole map at a glance
- Tasks and My day — breaking goals down into concrete work
- Calendar — deadlines, reminders and events
- The canvas — the bars, the controls and multi-select
- Automation rules — recurrence and node rules

