---
title: "Driving System Adoption"
type: doc
evidence_type: method
category: "GTM Tech Stack"
publisher: "LeanScale"
date_modified: 2023-10-10
word_count: 110
topics: ["revenue-operations"]
canonical_url: https://knowledge.leanscale.team/docs/gtm-tech-stack-driving-system-adoption/
source: "LeanScale Knowledge Hub — https://knowledge.leanscale.team"
license: "Free to quote and cite with attribution to LeanScale."
---

# Driving System Adoption

**Evidence type:** method (what we prescribe)

Adoption follows process, not features. Define and document the process first, evaluate tools on whether they empower that process rather than replace it, then secure stakeholder alignment and invest in enablement and training. Tools bought to fix an undefined process do not get used.

#### Process Before Technology

* **Step 1:** Prioritize process definition and documentation before evaluating technology.
* **Step 2:** Evaluate tools' potential to empower existing processes rather than drive change.
* **Step 3:** Select best-fit technology that aligns with your defined process.

#### Stakeholder Alignment

* **Step 4:** Engage all relevant stakeholders across different teams to gather comprehensive perspectives.
* **Step 5:** Seek insights from unique roles that will interact with the technology.
* **Step 6:** Foster informed decision-making by incorporating diverse viewpoints.

#### Enablement and Training

* **Step 7:** Develop enablement materials and training programs post-decision.
* **Step 8:** Establish forums for users to interact and engage with the technology.
* **Step 9:** Provide continuous training after deployment to ensure sustained proficiency.

## Canonical

https://knowledge.leanscale.team/docs/gtm-tech-stack-driving-system-adoption/