The org chart shows reporting. The network shows work.
A charter is one team’s editable account of its purpose, work, measures, authority, roles, and guidelines. When one charter names another team, Particulars connects them in the company model.
You can start with one team, see its parent and subteams, and follow the working relationships its charter names. Reporting lines stay visible beside the work that crosses them.
Your org chart leaves out the teams people depend on every day.
The org chart answers useful questions quickly. Who reports to whom? Which leaders contain which functions? How many layers sit between a team and the chief executive? Where does management accountability live?
Your work adds other relationships. A payments team depends on identity, risk, finance, customer support, and regional market teams. A transformation team can cross six functions. One person may fill roles in several teams. A decision may require advice from people far outside the reporting chain.
Particulars gives every team the same kind of charter, then connects the charters through nesting and explicit team mentions. You can read the hierarchy, open one team’s neighborhood, or widen out to the whole company without asking one diagram to show every detail at once.
See reporting lines and working relationships in the same company.
A conventional chart starts with people and reporting lines. Particulars starts with team charters, then shows formal structure beside the teams those charters name. Every connection has a source you can read.
Hierarchy
Parent and subteam relationships show formal containment and the broad structural shape of the organization.
Mentions
A charter names another team in a purpose, focus area, measure, decision right, role, or guideline. The line opens back to that sentence.
Neighborhood
One selected team sits with its parent, subteams, named relationships, roles, people, and agents in a locally useful view.
Whole organization
The same records become a zoomable field for finding structural clusters and following relationships across the company.
Start where you work, then widen out when the question gets bigger.
Preserve formal structure
Parent and subteam relationships stay visible because governance and containment matter. A company node provides a stable top. Teams fan outward beneath it, so you always know where the selected team sits.
Open a team and its charter becomes readable while the rest of the company stays in view. You can move to the parent above, a subteam below, or a neighboring team named in the work.
In a nine-team company you can see everything at once. In a 500-team company you start from your team and widen out. The same structure works at both scales because the hierarchy keeps your place while other relationships come forward.
Trace every line back to a sentence
A network becomes a rumor machine when nobody can explain why two teams appear connected. Every Particulars line comes from a sentence a human wrote or a formal parent-and-subteam relationship.
Customer Success may name Product in a focus area. Platform may sit inside Product. An agent may fill a role in Editorial. Select the line and read that source instead of guessing what a decorative connection means.
When no team has declared a dependency, the map stays silent. You can decide whether a visible relationship is current, accidental, or important enough to make clearer.
Search from one question, not the whole company
Most people begin with a local question: which teams depend on us, where does this role live, or who owns this measure? Start from the selected team, its parent, its subteams, and the teams its charter names.
Search brings forward a team, role, measure, or mention and strengthens the paths around it. You can zoom out when the question becomes a company question and zoom back in when you need the sentence that created a connection.
Status and ownership filters help you find an open role, a stale charter, or a team with no editor. The surrounding network stays visible enough to show what the result means in context.
One team’s organizational neighborhood
Select a team to see the parent above, subteams below, roles inside, and neighboring teams named by the charter. The selected team becomes the stable center; the relationship panel explains why each visible edge exists.
The graph helps you read the organization. Hierarchy supplies orientation. Mentions surface working relationships the chart misses. Both remain tied to the team charters.
Build and ship the Particulars platform.
Build and ship the Particulars platform.
Follow a working relationship from the whole company back to the sentence that created it.
A connected model lets someone start with a team, trace a relationship to its source, and zoom outward to see where similar links accumulate. Search can illuminate the teams and connections relevant to a question while the rest of the company recedes without disappearing.
The model tells you which relationships come from formal nesting and which come from explicit mentions. It also shows where the company still needs a conversation because nobody has written down the relationship yet.
A dense cluster may reflect healthy shared work or a team forced to coordinate around a missing boundary. An isolated team may be autonomous or simply absent from the current charters. The graph gives you a place to investigate; people still decide what the shape means.
- See a formal subteam and a cross-team working relationship in one view.
- Move from a 500-team field to one team’s source text without changing systems.
- Give people and agents an organizational neighborhood instead of a directory entry.
“The organization is not a hierarchy or a network. It is several systems of relationship operating at once. The useful model lets each one remain visible.”
— The Particulars thesis