nexy

Use case

An assistant for a team that remembers everything

Not a wiki that nobody updates. What was decided, what was promised and what the number was stays answerable in plain words months later — and the answer always says who said it and when.

Decisions and promises are captured where they are actually made — in the thread, as they happen — rather than written up somewhere afterwards. Months later anybody on the team asks in plain words and gets the answer with the person and the date attached, so you can tell a settled decision from something somebody once floated.

What it looks like

Captured where decisions are actually made. The answer carries the person and the date, so you can tell a decision from a thought.

How to do it

  1. Decide things in the thread the way you already do. Nothing has to be written up afterwards for it to be remembered.
  2. When something is settled, Nexy says so out loud — the decision, who made it, and anything it depends on.
  3. Promises and conditions are kept as live items. “Revisit if volume passes 4,000” does not quietly expire.
  4. Months later, ask in ordinary words. The answer comes back with the person and the date.
  5. Anything that was raised and never claimed is reported as exactly that, rather than being presented as agreed.

Why it works

Wikis decay, threads do notA document has to be updated by somebody with time. A decision captured where it was made costs nobody anything.
The date is half the answer“We agreed this” means nothing without when. A decision from May under different numbers is a different thing from one from last week.
Unclaimed is a real statusMost team memory failures are not forgetting a decision. They are believing something was agreed when it was only mentioned.
Conditions stay alive“Revisit if X” is the single most commonly lost thing in any team. It is held as a live item rather than a sentence in old minutes.
New people can askSomebody who joined in September can ask why something was decided in May and get a real answer, without interrupting anyone.

Where it stops

It remembers what was said in the threads it is in. It does not watch your company.

It is not in your systemsNo crawling of drives, inboxes or repositories. It knows what was said to it.
It will not present a mention as a decisionIf something was floated and never settled, that is what it tells you — including who floated it.
It will not assign ownersAn unclaimed item stays unclaimed and visible. It does not pick a person.
No performance recordIt is not a log of who did what for review purposes, and it will not be turned into one.

Questions people ask

How is this different from a wiki or a notes document for the team?

A wiki requires somebody to write things up afterwards, and that person is always busy, so within a few months it describes a company that no longer exists. Here the decision is captured where it was actually made — in the thread, as it happens — which costs nobody any extra time. The test is whether it is still accurate in six months, and documents that need maintaining generally are not.

What exactly does it remember?

Decisions, promises, numbers and conditions. “We are not doing the second warehouse” is a decision. “Anne will check the lease” is a promise. “4,000 units a month” is a number. “Revisit if volume passes 4,000” is a condition, and conditions are the thing teams lose most reliably, because they sit in old minutes nobody rereads.

Does the answer tell me who said it?

Always, with the date. Those two things are half of what makes an answer usable: a decision taken in May under a different forecast is a different object from one taken last week, and knowing whether it was the founder or a contractor who said it changes how much weight it carries. An answer without attribution would be worse than no answer.

What happens to things that were discussed but never actually agreed?

They are reported as exactly that. This is the most common failure in team memory — not forgetting a decision, but believing something was decided when it was only mentioned once by somebody in a meeting. Asked about it later, you are told it was raised, by whom, on what date, and that nobody ever picked it up.

Does it read our documents, email or code?

No. It knows what was said in the threads it is part of, and nothing else. Nothing crawls a drive, an inbox or a repository. That is a narrower memory than a search tool over all your systems, and it is also why what comes back is a decision with a person and a date on it rather than a paragraph from a file somebody wrote in 2024.

Will it chase people on unclaimed items?

It makes them visible and says, out loud, that nobody has them. It does not assign them to somebody and it does not pick the person who is easiest to assign to. In practice saying “this was raised in May and nobody ever took it” to a group of four is more effective than a task with a reluctant owner's name on it.

Can somebody who joined recently use it to catch up?

That is one of the strongest uses. A person who started in September can ask why a decision was taken in May and get the reasoning, the people and the date without interrupting anybody or reading six months of threads. It also surfaces the conditions attached to old decisions, which are usually the things nobody thinks to explain to a new person.

Is this a record of who did what, for performance reviews?

No, and it should not be used as one. It attributes decisions so you can weigh them, not so you can audit people. There is no productivity log, no count of who completed what, and no intention to build one — the moment a shared memory becomes a performance instrument, people stop putting real things into it and it stops being a memory at all.

Related use cases

New here? How Nexy works explains the whole thing in a minute, and the index lists every use case.

Stay posted on Nexy

We add a new use case most days and test what actually works. Get the short version by email, or a notification the moment something ships. No account, and one click to stop.

An assistant for a team that remembers what everyone agreed