The model

From idea to work, without a second system

Takt keeps direction and delivery in one graph. Each role opens a different page. The links stay the same.

The chain Takt actually keeps

An idea can become a goal or work. Goals support other goals. Initiatives and deliveries support goals. Teams deliver through deliveries — projects and services. Work items can support a goal and sit on an initiative.

  1. Idea
  2. Goal
  3. Initiative
  4. Delivery
  5. Team
  6. Work
Takt map with goals, initiatives, deliveries and teams, built from real work items.
No lines to draw. The map is generated from the same work items, goals and teams you already use — not a diagram you maintain by hand.

What you can use now

These are first-class parts of the product, not a slide about the future.

Now

Goals, initiatives and ideas

Capture direction, run initiatives, and take ideas in. Link them so the organisation can see what supports what.

Now

The organisation map

See ideas, goals, initiatives, deliveries and teams on one map built from the work items underneath. Work nodes stay off by default so the picture stays readable.

Now

Deliveries, boards and backlogs

A delivery is a project or a service with its own key, board and backlog. Standing teams plan and move work at three altitudes — epics, features, stories. Sprints are optional. A requirement is a work type, with a definition of success on the item.

Now

Planning panel on the backlog

Sprints, initiatives and goals sit in a side panel. Drag a row onto one and the link is saved on the work item — the same link the map draws.

Now

Plans

A team sketches outcome, scope and open questions in one place, then turns the sketch into goals, initiatives and work that stay linked to it.

Now

Labels with colour

Organisation labels for everyone, team labels for the team. Colour them, put them on work, filter the board by them.

Now

The Takt agent

One agent across the product, scoped to the page you are on. Pick a skill or ask in plain words: improve a description, break a feature into stories, turn an idea into a goal. Every change is a proposal a person approves. Admins set a monthly token cap and see usage per team.

Now

Mermaid in the description

Flowcharts and sequence diagrams live in markdown on work items, goals and ideas. Write them yourself, or ask AI to insert one. The same fences render in comments.

Work item TAKT-35 Teams and working context: a Mermaid flowchart of user, membership and team board, and a Kerberos login sequence, rendered in the description.
Diagrams on the item. A Mermaid fence in the description renders as a picture. Ask AI to add one — you review before it stays.

Marked as coming — not sold as done

Coming

Automatic progress from work

Goal progress is set on the goal today. We do not invent a percentage from child work.

Coming

Knowledge base and live trace to code

Decisions and requirements live on the work item now; a wiki is later. A work item can point at its pull request today. Live sync from GitHub, GitLab or Azure DevOps Server is still coming — Takt does not replace git. Sign-in with Microsoft Entra ID and authenticator MFA are in the product; other identity providers are later.

Coming

AI risk detection and voice

The agent drafts and links work. Unlinked-work detection and voice input are not in the product yet.

The same work, three ways

Work view showing requirements with nested epics and stories, each with points, team, status and assignee.
Hierarchy that holds. Requirement → epic → story → task, in one tree, towards delivery.
Backlog and planning view with epics expanded to their stories.
Plan with the team. Rank work and keep it linked to initiatives and goals.
Work item with description, definition of success, children and comments.
One item, everything on it. Description, definition of success, children and relations.