案例研究
Ask where a project stands and who is actually working on it
它能带来什么Status is written down, but scattered: a ticket here, a meeting note there, an update from three weeks ago. Consilience connects people, projects, and documents into one graph. Ask where something stands and you get the latest written update, who is working on which part, and what has had no movement, each answer linked to the note it came from.
A company of 200 people runs dozens of projects at once, and everything about them is written down somewhere. Tickets, specs, meeting notes, weekly updates, handover documents. What nobody has is one view of where any of it stands.
So "how is the migration going" gets answered by asking around. A manager messages three people, waits, and assembles a picture that is already a few days old. This case covers what happens when the projects, the documents, and the people working on them are in one workspace, and the question is asked there instead.
What the company already writes down
None of this needs new reporting. The material exists. It is spread across tools, and nobody has read all of it.
- Project folders. Specs, plans, and decision records, one folder per project
- Meeting notes from weekly team meetings and project reviews, with who said what
- Ticket exports carrying the assignee, the current state, and the comment history
- Written updates people post at the end of a week or a sprint
- Handover documents from anyone who changed team or left the company
What is missing is not information. It is the connection between a person, the project they work on, and the document where the latest word on it was written.
How a status question gets answered today
Someone asks in chat and waits. The manager messages the three people most likely to know, gets three partial answers at three different times, and stitches them into a summary for the meeting.
The written record does not help much, because it is filed by tool rather than by project. The ticket says what state the work is in but not why it stalled. The meeting note says why it stalled but is filed under a date. The person who could join the two is on holiday.
So status gets collected again every week, and the collecting takes longer than reading the answer.
Connect the projects and the people once
Setup is one pass over material that already exists. After that, new notes land in the same workspace and the graph keeps up on its own.
Getting the company's work into one graph
Load the project folders and the exports
Open "Extract sources" (
Cmd+Shift+I) and drag in the project folders, the meeting notes, and the ticket export. Spreadsheets and CSV exports go in the same way as documents. The originals stay where they are; the app reads a copy.Teach it the words your company uses
Open "Domain vocabulary" in the left rail and register your own terms: project code names, team names, and the words you use for stages, like blocked, in review, or shipped. Extraction reads with those in hand, so a note saying "parked until legal signs off" attaches to the right project and the right state.
Confirm who is who
At "Connecting related items", the app proposes that "J. Park", "Jieun", and the address in a ticket export are the same person. Nothing merges until someone confirms it, and a wrong merge can be undone. This is the step that makes "who is working on this" answerable at all.
Keep it current by doing nothing new
Next week's meeting notes and updates go into the same workspace. Nobody writes a status report for the graph. The graph reads the notes people were already writing.
What you ask
"Where does the billing migration stand?"
→ The latest written update first, with its date and the note it came from.
Under it, the open items and who each one sits with.
"Who is working on the billing migration, and on what part?"
→ The people connected to that project, each with the piece they are named on
and the document that names them.
"What has moved on this project in the last two weeks, and what has not?"
→ Two lists. What changed, with the note that recorded the change.
What carries no written update since a given date.
"What is @Jieun named on right now?"
→ Every project and open item her name is attached to, each linked to the
note it came from, so you can read the original before acting on it.These answer because a person, a project, and a document are three connected things in the graph rather than three separate searches. "Who is working on this" means people pointing at that project, so one question reaches material written in five different places by four different people.
Every line carries the note it came from. Before you take a status into a meeting, you open the note and read the sentence someone actually wrote.
What changes
| Before | Now |
|---|---|
| Message three people, wait, and assemble a picture that is already days old | Ask once and get the latest written update, with its date and the note it came from |
| The ticket says what state the work is in, the meeting note says why, and nobody joins the two | Person, project, and document are connected, so one question reaches all three |
| Status is collected by hand every week for the meeting | The same question can be asked at any time and answers from whatever has been written since |
| When someone changes team, what they knew about the project goes with them | Their updates and handover notes stay attached to the project and still answer |
What goes away is the collecting. Deciding what to do about a stalled project, reordering the week, and talking to the person who is stuck all stay exactly where they were.