> ## Documentation Index > Fetch the complete documentation index at: https://plantis.ai/llms.txt > Use this file to discover all available pages before exploring further. # Leadership: Focus on Growth > Leading human-first adoption with champions, not mandates **The Reality**: The biggest challenge in AI transition is **human, not technological**. ## Human-First Adoption Leaders must **respect the craft and expertise** developers have built over years. ### Why This Matters Engineers have invested **years** building skills: * Mastery of languages and frameworks * Deep debugging expertise * Architectural pattern recognition * Code review instincts * Problem-solving intuition **Don't dismiss this expertise**. Frame AI as amplifying it, not replacing it. ### The Wrong Approach ❌ "AI can do your job now, learn it or fall behind" ❌ "Everyone must use AI by next quarter" ❌ "We're measuring AI-generated lines of code" ❌ "Seniors should be 10x faster with AI" **What this creates**: * Resistance and resentment * Fear and anxiety * Performative adoption * Quality degradation ### The Right Approach ✅ "AI is a tool to multiply your expertise" ✅ "Experiment and share what works for you" ✅ "We're investing in your growth and skill expansion" ✅ "Quality and judgment matter more than speed" **What this creates**: * Genuine curiosity * Safe experimentation * Quality-focused adoption * Organic knowledge sharing ## Psychological Safety: Frame as Multiplication **The message**: This is about **individual impact multiplication** and **career growth**, not replacement. ### Framing the Opportunity **For Individual Contributors**: ``` "You've built deep expertise over years. AI lets you apply that expertise to bigger problems. Instead of implementing one feature per sprint, imagine driving three features—with the same quality bar you're known for." ``` **For Senior Engineers**: ``` "Your architectural judgment is more valuable than ever. AI handles the mechanical implementation, freeing you to focus on system design, mentoring, and solving the truly complex problems that need human insight." ``` **For Team Leads**: ``` "Your team's output multiplies, but the bottleneck shifts to review and coordination. Let's evolve your role to focus on architecture, quality gates, and strategic direction." ``` ### Career Growth Narrative Position AI adoption as **skill expansion**: | Traditional Role | AI-Enhanced Role | New Skills | | ---------------- | ---------------------- | ----------------------------------------------------------------- | | Senior Engineer | AI Conductor | Prompt engineering, context management, agentic workflows | | Code Reviewer | Review Architect | Rule codification, automation design, strategic review | | Tech Lead | System Orchestrator | Parallel workflow management, quality system design | | Architect | AI-Augmented Architect | AI-friendly architecture, documentation design, scalable patterns | **The pitch**: "You're not learning to be replaced—you're learning to operate at a higher level." ## Space for Deliberate Practice Engineers need **time to build new foundational "muscles"** without the immediate pressure of a deadline. ### The Learning Curve Mastering the AI workflow requires: * **Phase 1 (Weeks 1-2)**: Slower than manual coding, learning basics * **Phase 2 (Weeks 3-4)**: Matching manual speed, building confidence * **Phase 3 (Weeks 5-8)**: 2x-3x manual speed, finding rhythm * **Phase 4 (Weeks 9-12)**: 5x-10x manual speed, mastery achieved **Critical**: Don't judge performance during Phase 1-2. ### Creating Practice Space **Dedicated Learning Time**: * 20% time for AI workflow experimentation * Non-critical features for initial practice * Pair programming with AI-experienced engineers * Internal "show and tell" sessions **Safe-to-Fail Projects**: * Internal tools (low stakes) * Technical debt cleanup * Documentation generation * Test coverage improvements **Explicit Permission to be Slow**: ``` "For the next month, prioritize learning over speed. We expect you to be slower as you build new skills. That's not just okay—it's required for mastery." ``` ## The Adoption Curve Identify and empower **"champions"** to experiment and share wins rather than forcing a top-down mandate. ### The Innovation Adoption Curve **Innovators (2.5%)**: Already experimenting with AI **Early Adopters (13.5%)**: Willing to try if shown value **Early Majority (34%)**: Need to see proven results **Late Majority (34%)**: Adopt when it's the new normal **Laggards (16%)**: Resist change, adopt last ### Champion-Led Strategy **Step 1: Identify Champions** Find your **Innovators** and **Early Adopters**: * Who's already using AI tools? * Who's excited about new workflows? * Who has influence on the team? **Step 2: Empower Champions** Give them resources and support: * Dedicated learning time * Access to premium AI tools * Permission to experiment * Platform to share findings **Step 3: Amplify Wins** Make success visible: * "Show and tell" demos * Internal blog posts * Slack channel for sharing tips * Metrics showing impact (quality, not just speed) **Step 4: Build Momentum** As wins accumulate: * Early Majority sees value and adopts * Late Majority follows the new norm * Laggards adopt or self-select out ### What NOT to Do ❌ **Top-Down Mandate**: "Everyone must use AI by Q2" * Creates resistance * Leads to performative adoption * Quality suffers ✅ **Bottom-Up Momentum**: "Our champions achieved 3x productivity—want to learn how?" * Creates curiosity * Leads to genuine adoption * Quality improves ## Toxic Metrics to Avoid **Don't judge performance** based on "AI-generated lines of code." ### Metrics That Backfire ❌ **Lines of AI-Generated Code** * Incentivizes quantity over quality * Encourages bloat and over-engineering * Misses the point entirely ❌ **Percentage of Code Written by AI** * Penalizes thoughtful human coding * Ignores context and quality * Creates perverse incentives ❌ **Speed Alone** * Ignores correctness and maintainability * Pressures engineers to skip quality gates * Leads to technical debt accumulation ### Metrics That Matter ✅ **Qualitative Shifts** * Are engineers tackling bigger problems? * Is code quality maintained or improved? * Are engineers reporting more creative freedom? * Do engineers prefer the new workflow? ✅ **Outcome Metrics** * Features delivered per sprint (same quality bar) * Time from idea to production * Developer satisfaction scores * Code review cycle time ✅ **Adoption Indicators** * Do engineers use AI voluntarily? * Are engineers sharing tips organically? * Do engineers feel AI adds value? * Would engineers go back to manual coding? ### The "One-Way Door" Test The best indicator of success: **Question**: "Would you go back to writing all code manually?" **If mastered**: "No, the old way feels cumbersome now." **If not working**: "Yes, this AI thing is more hassle than help." **Key insight**: Once an engineer truly masters this workflow, they rarely go back. It becomes a **one-way door**. ## Leadership Principles ### 1. Invest in Growth, Not Just Output * Provide learning resources * Create safe practice spaces * Celebrate learning, not just shipping ### 2. Trust Professional Judgment * Engineers know what works for them * Different workflows for different people * Quality over speed mandates ### 3. Lead by Example * Leaders should learn the workflow too * Share your own learning journey * Demonstrate vulnerability in learning ### 4. Measure What Matters * Focus on outcomes and satisfaction * Avoid vanity metrics * Track qualitative improvements ### 5. Build Institutional Knowledge * Document what works * Share team learnings * Create feedback loops *** **Key Principle**: The transition is human, not technical. Lead with empathy, empower champions, measure what matters, and create space for genuine skill development. The "one-way door" comes from mastery, not mandates.