A tailored course, built for your situation
Mid-Market Moving from IC to Head-of-Practice for High-Growth Organizations
A structured path to leading technical practices in scaling mid-market firms
The situation this course is for
Transitioning from IC to Head-of-Practice means shifting from output ownership to capability building. Most technical leaders are left to figure out team design, stakeholder alignment, and budget advocacy on their own, leading to slow ramp-up, misaligned expectations, and missed impact in critical growth phases.
Who this is for
Senior engineers, architects, product leads, or consultants in mid-market companies (50, 500 employees) preparing to lead a practice area, such as engineering, data, security, or product, in a high-growth environment.
Who this is not for
C-suite executives, startup founders, or professionals outside mid-market tech-adjacent organizations. This is not for those seeking certification, crash courses, or theoretical overviews.
What you walk away with
- Design and propose a practice structure aligned with company growth stage
- Build influence across engineering, product, and GTM leadership
- Develop operating budgets and resource plans for technical practices
- Create scalable playbooks for hiring, onboarding, and performance in technical teams
- Lead change initiatives without direct authority using stakeholder mapping and alignment frameworks
The 12 modules (with all 144 chapters)
- Defining the Head-of-Practice role
- Growth stages and leadership needs
- From contributor to capability builder
- Organizational maturity models
- Case study: Engineering practice evolution
- Case study: Data function scaling
- Case study: Security practice formation
- Signals that your org needs a practice lead
- Mapping stakeholder expectations
- Common transition pitfalls
- Assessing your readiness
- Setting your leadership foundation
- Practice vs. team: structural differences
- Centralized, federated, hybrid models
- Span of control and reporting lines
- Aligning with engineering or product orgs
- Defining roles and career ladders
- Designing for knowledge sharing
- Creating centers of excellence
- Integrating with delivery teams
- Balancing autonomy and standards
- Onboarding new practice members
- Measuring practice health
- Iterating on structure
- Influence frameworks for technical leaders
- Building credibility through delivery
- Leading cross-functional initiatives
- Running effective practice councils
- Facilitating technical alignment
- Driving adoption of standards
- Navigating power dynamics
- Communicating value to executives
- Creating feedback loops
- Handling resistance to change
- Using data to support decisions
- Sustaining momentum without mandates
- Understanding cost centers and budgets
- Building a practice funding case
- Estimating headcount and tools
- Aligning with annual planning cycles
- Tracking practice ROI
- Managing vendor relationships
- Allocating shared resources
- Justifying investment in quality
- Balancing innovation and delivery
- Forecasting future needs
- Negotiating with finance stakeholders
- Optimizing spend across teams
- Designing technical career paths
- Defining competency frameworks
- Running skill gap analyses
- Creating internal upskilling programs
- Mentorship and coaching models
- Rotations and stretch assignments
- Evaluating technical impact
- Conducting technical reviews
- Rewarding non-managerial excellence
- Retaining top contributors
- Onboarding new specialists
- Scaling development at pace
- Identifying high-leverage practices
- Documenting standards and playbooks
- Versioning and change control
- Driving adoption through enablement
- Measuring compliance and impact
- Running practice-wide initiatives
- Integrating with CI/CD pipelines
- Automating governance checks
- Scaling code reviews and audits
- Managing technical debt portfolios
- Running architecture review boards
- Balancing agility and control
- Translating business goals to tech priorities
- Participating in strategic planning
- Building roadmaps that reflect practice needs
- Prioritizing technical investments
- Communicating strategy across levels
- Influencing product and engineering roadmaps
- Managing technical dependencies
- Responding to market shifts
- Scenario planning for tech capacity
- Linking innovation to business outcomes
- Using metrics to guide decisions
- Reporting progress to executives
- Designing practice newsletters
- Running all-hands and syncs
- Creating knowledge repositories
- Facilitating peer learning sessions
- Sharing wins and learnings
- Documenting decisions and rationale
- Managing communication overload
- Engaging remote and distributed members
- Using async effectively
- Building psychological safety
- Soliciting feedback and input
- Celebrating technical excellence
- Choosing leading vs lagging indicators
- Defining practice KPIs
- Tracking quality, velocity, reliability
- Measuring adoption of standards
- Assessing team health and morale
- Benchmarking against peers
- Reporting to leadership
- Using data to drive improvement
- Balancing quantitative and qualitative
- Avoiding vanity metrics
- Conducting practice retrospectives
- Iterating based on feedback
- Understanding resistance in technical teams
- Applying ADKAR in tech contexts
- Building coalitions of advocates
- Piloting new practices effectively
- Scaling successful experiments
- Managing change fatigue
- Communicating the 'why'
- Aligning incentives with change
- Tracking adoption metrics
- Handling edge cases and exceptions
- Sustaining changes over time
- Evaluating change success
- Understanding executive priorities
- Tailoring communication to leaders
- Preparing for executive reviews
- Translating tech risks to business risks
- Building trust with CTO/CPO/CEO
- Managing upward expectations
- Handling scrutiny and pressure
- Presenting data and insights
- Influencing without overpromising
- Balancing transparency and diplomacy
- Escalating when necessary
- Maintaining credibility over time
- Recognizing signs of leadership burnout
- Setting boundaries and delegating
- Building a support network
- Managing workload and priorities
- Practicing self-reflection
- Seeking feedback and coaching
- Maintaining technical credibility
- Balancing depth and breadth
- Planning for succession
- Staying energized by impact
- Creating space for innovation
- Leading with sustainability
How this maps to your situation
- You're a senior IC preparing to lead a practice
- You've been promoted but lack formal frameworks
- You're influencing without authority across teams
- You're building a case for practice investment
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 45, 60 minutes per module, designed for completion over 8, 12 weeks with real-world application between sections.
How this compares to the alternatives
Unlike generic leadership courses or academic programs, this course is implementation-focused, tailored to mid-market constraints, and built specifically for technical professionals transitioning from IC to practice leadership, offering actionable tools, not just theory.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.