You don't document ownership by writing it down. You assemble it. Who owns what is already recorded in three places: who answers in the Slack channel, who is listed as the owner in the CRM, and who closes the Jira tickets. Pull those into one page per new hire and have the hiring manager check it.
Where does ownership actually live?
Ask who owns enterprise renewals and you'll get three answers. The org chart names a department. The CRM names whoever was assigned in 2024. Slack shows who actually replies when a renewal goes wrong. Only one of those helps when a renewal is going wrong today.
Ownership lives in four places:
- Slack. Who answers when a question lands in the channel. Who gets tagged when something breaks.
- The CRM. The account owner field, and the activity underneath it that shows who really does the work.
- Jira. Who gets assigned the tickets, and who closes them.
- A person's head. The one who "just knows", and is in meetings until Thursday.
Three of those four are written down already. Nobody reads them in order, and no new hire knows which one to trust. So they ask.
Knowledge workers spend, on average, 1.7 hours a week seeking out the right people to answer questions and provide expertise (APQC, 2022). That is the average for people who already work there. A new hire starts the same hunt from zero.
Why the org chart doesn't answer it
The org chart says who reports to whom. It was built for approvals and headcount, and it's good at both.
It doesn't say who approves a pricing exception, who owns the billing service now that the person who built it has moved teams, or who the customer actually calls. Those are ownership questions, and ownership moves faster than reporting lines. Someone covers an account during a leave and keeps it. A system changes hands in a thread with four replies and a thumbs-up.
A wiki page titled "Who owns what" has the same problem at lower speed. It was accurate the week it was written. Then there was a reorg, and then another. Firstweek vs. your company wiki covers why that page never stays current.
Three signals that show who owns what
You can do this by hand for one team in an afternoon.
- Who answers in the channel. Open the team's main Slack channel and read the recent questions on one topic. The person who answers most is the working owner, whatever their title says.
- Who is the CRM owner, and who is active. The owner field shows who is accountable for an account. The notes and logged activity show who knows it. When those are two different people, write down both.
- Who closes the Jira tickets. Assignment shows who was asked. Closing shows who did it. For systems and internal processes, the closer is the owner.
Where the three signals agree, you have an owner.
Where they disagree, you have found the thing a new hire most needs to be told. A named owner who never answers and an unnamed one who always does is exactly the situation a new hire gets wrong in their second week.
What goes in a one-page ownership map
One page, for one new hire, covering only what their role touches.
- Accounts or customers. The owner, plus the person who knows the history if that's someone else.
- Systems and services. Who to ask before changing anything.
- Processes. Who runs each one, and who approves exceptions.
- Decisions. Who can say yes to a discount, a deadline or a change in scope.
- Open work. What's in flight, and who is carrying it.
- Who to ask about what. Five or six topics, one name each.
Every line should point to where it came from: the thread, the record, the ticket. That lets a manager check the page quickly, and it lets the new hire see whether a line dates from last month or last year.
The page earns its keep during a handover. When someone leaves or changes teams, their accounts and systems are reassigned in a hurry, and the map is whatever the next person can reconstruct. If the signals were already assembled, the reassignment starts from a page instead of from memory.
How to keep it from going stale
Don't maintain it. Regenerate it.
A standing ownership wiki needs someone to update it after every reorg, every reassignment and every quiet handoff in a thread. That someone doesn't exist, which is how the last one died.
A map built from the signals doesn't need maintaining, because the signals update themselves. People keep answering in Slack. The CRM keeps logging activity. Tickets keep closing. Build the page fresh for each new hire, from what the tools show that week, and have the hiring manager confirm it.
By hand, that's an afternoon per hire, per team. It's the right thing to do, and it rarely happens twice.
Firstweek does that assembly for each new hire. It reads Slack, Jira, Confluence and your CRM through read-only connections, summarizes at ingest so raw messages are never stored, and writes a cited onboarding artifact with ownership in it. The hiring manager approves it before day one. The sample artifact shows what the "who owns what" part looks like, and the security page covers how the reading works.
Until someone has the map, the new hire is on payroll asking for directions. The onboarding cost calculator puts your own numbers on that.
FAQ
How do companies document who owns what without writing it all down?
They assemble it from signals that already exist: who answers in Slack, who owns and works each record in the CRM, and who closes the Jira tickets. The result is one page per new hire, checked by the hiring manager.
Why isn't the org chart enough?
It shows reporting lines, not working ownership. It can't say who approves a pricing exception or who to ask before changing a system.
How do we keep ownership documentation current?
Don't keep a standing page. Regenerate the map for each new hire from what the tools show at that point, and have the manager confirm it.
What happens to ownership knowledge when someone leaves?
What they wrote in Slack, the CRM and Jira stays where it is. Assembled into one page with its sources, it gives whoever inherits the work a place to start.
Sources: APQC, KM Makes Knowledge Workers More Productive and Less Stressed Out (2022), listed with its link on the onboarding statistics page.
Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.