Part III: The practiceChapter summary

Every team already touches how agents see an organization. Marketing writes the facts agents repeat. Engineering decides whether agents can get in and what they can call. Commerce sets the offers and checkout. Service answers the questions. Legal and security set the rules. Nobody owns the whole, which is why the whole is usually neglected.

The Framework’s answer is a small central practice that enables everyone else rather than doing everything itself. It sets the shared language, runs the assessment, keeps the list of failed tasks, chooses the standards and reports progress. Each domain has a team that leads it and others that contribute; the chapter sets out a typical split and how to adapt it to an organization’s size.

TeamDiscoverDescribeConverseTransactTrustMeasure
Marketing and brandLeadsLeads···
Engineering and product·LeadsLeadsLeads··
Commerce and sales··Leads·
Service and operations·Leads···
Legal, risk and security···Leads
Agent Relations practitioners·····Leads
Figure 11. Who leads what. A central practice enables the teams that already own each part of the relationship.

In a large company the practice may be a team of three to five, sitting near digital or marketing, with a senior sponsor. In a small one it is a single person with a part-time brief and help from an agency. In both, the first ninety days look similar: assess, fix the obvious blocks, publish accurate facts, stand up one way for agents to ask and one way to act, and start counting.

Funding follows measurement. Early work is cheap, often a matter of configuration and writing. Later work, such as endpoints, actions and verification, needs engineering time, and the case for it is made with the outcomes the practice has already counted.

Read the whole chapter

This is a summary. The full chapter is in the book, which is coming soon. One email when it is published.