Cross-functionality (in GTM30)
One shared narrative, one shared data model, one shared view of the customer, and one shared operating cadence across Product, Growth, Sales, and Support.
Last updated: December 12, 2025
Definition
One shared narrative, one shared data model, one shared view of the customer, and one shared operating cadence across Product, Growth, Sales, and Support.
In practice
- Use the schema as a contract: shared fields (problem, ICP, lifecycle stage, intent) must mean the same thing across teams.
- Run a shared rhythm (weekly signal review, bi-weekly alignment, monthly narrative review) so drift gets corrected quickly.
Common mistakes
- Parallel tagging systems (“sales terms” vs “SEO terms”) that create conflicting narratives and routing logic.
- Quarterly surprises: schema changes that aren’t reflected everywhere the same week.
Related terms
- Shared schema — The cross-functional contract: a shared set of fields and definitions that represent reality consistently across GTM30, without team-specific terminology or parallel tagging systems.
- Entity model — A small, stable set of entities (problems, use cases, roles/personas, industries, etc.) and their fields/relationships that power content, analytics, automation, and LLM retrieval.
- Canonical page / canonical link — The single page you want threads, content, ambassadors, and internal tools to link to for a topic — so knowledge compacts instead of fragmenting across repeated answers.
- Signal — A meaningful observation from community, ambassadors, support, or content performance (friction, requests, language patterns, objections) that can be tagged, routed, and acted on.
- Signal schema — A minimal, consistent set of fields for capturing signals so Product, Sales, and Support can act without losing context (source, ICP segment, lifecycle stage, tags, severity, status, and link).
- Traits — Machine-readable tags derived from page views and behavior (tied to entities) that feed analytics, automation, and CRM without manual interpretation.