Particulars turns the work already happening into a clear, current account of how the company works — what each team is for, who decides what, where responsibilities overlap, and what is changing. People use it to act with confidence. Agents use it to understand their place.
We turn workforce data into decisions about hiring, leveling, and team design. We move slowly on measures, fast on questions.
Every team uses the same compact shape: purpose, focus, measures, decision rights, roles, and working rules. Anyone can understand one team quickly — then read across the company without learning a new language each time.
Start from the channels, documents, and decisions the team already produces. Edit toward what should be true. Particulars keeps watching the gap, so the record does not become another abandoned wiki.
See where work overlaps, where authority is unclear, where roles are missing, and where the organization is changing. The same record gives people clarity, leaders a view of the whole, and agents the context to operate safely.
Forty years of team-effectiveness research says much of a team’s performance can be predicted from how it is designed — before the work begins. Purpose, composition, authority, interfaces, and norms are not administrative details. They are the operating conditions.
Particulars puts those conditions somewhere the team can see them, change them, and keep them close to reality.
Wageman, Hackman & Lehman, “Team Diagnostic Survey” (2005)
Hackman, “Leading Teams” (2002)
Give software a named role, a purpose, explicit authority, relationships, and limits. Particulars compiles the team’s current charter and connections into operating context for the agent — read-only, revocable, and scoped to the work it has actually been asked to do.
The charter shapes the agent. The agent does not quietly invent the organization around itself.
How agents read the organization →“The work already knows how the company works. Particulars makes it visible.”
— The Particulars thesis