Skip to content

Product · Platform overview

One loop turns everyday work into evidence, development and an evaluation

The same record gives the organization an evaluation and gives each person their development. Every step below opens its own page.

How it works: Six steps, and the loop feeds itself

Six steps, and the loop feeds itself: the record of work is built, feedback guides it, AI drafts, a leader decides, and the next cycle starts on that record.
  1. Connect the tools — Chat, tickets, code, documents, meeting notes.
  2. Work becomes evidence — Work items and the discussion around them become dots.
  3. People claim and curate — Each person keeps what's theirs and removes what isn't.
  4. Feedback guides the work — Given in Nextdot or in the tools, while the work happens. Each person sees how they're developing as they go.
  5. AI drafts the evaluation — Pre-filled per dimension of your own framework.
  6. A leader decides — The leader reads the draft and writes their own evaluation. Nothing is final until signed.

The next cycle begins with a year of evidence already on record.

  1. 1

    Connect the tools

    Chat, tickets, code, documents, meeting notes.

    Work-history import 
  2. 2

    Work becomes evidence

    Work items and the discussion around them become dots.

    Dots 
  3. 3

    People claim and curate

    Each person keeps what's theirs and removes what isn't.

    Work-history import 
  4. 4

    Feedback guides the work

    Given in Nextdot or in the tools, while the work happens. Each person sees how they're developing as they go.

    Continuous feedback 
  5. 5

    AI drafts the evaluation

    Pre-filled per dimension of your own framework.

    Performance evaluation 
  6. 6

    A leader decides

    The leader reads the draft and writes their own evaluation. Nothing is final until signed.

    Performance evaluation 

The next cycle begins with a year of evidence already on record.

One record, two outcomes

  • For the organization

    An evaluation built from twelve months of work, in your own framework, that a leader can defend.

  • For the person

    Feedback while the work is live, a view of how colleagues see your skills, and a say in what counts.

  • For leadership

    Sight of how teams develop, and of who develops the people around them.

People decide

Nothing is final without a signature
AI drafts. The leader reads the draft and writes their own evaluation, and nothing is final until they sign it.
People curate their own evidence
What appears in an evaluation is what the person chose to keep. Nothing is attached to them without their say.
Assistant conversations stay private
The Development Assistant belongs to the person. No one else in the organization sees those conversations.

Works with the tools your teams already use

  • Microsoft Teams
  • Slack
  • Jira
  • GitHub
  • Azure DevOps
  • Google Drive
  • Notion
  • Fathom
All 80 tools

The best way to see it is on your own data

Happy to show it running on one team's tools — twelve months of work, your framework, your people.