Overview

Your org chart looks normal. Teams are structured the same way they were five years ago. Career paths follow the traditional ladder. Competency models list the same skills they always have.

But everything is different now. Your analyst spends 30% less time on routine analysis and 30% more time on strategic thinking. Your manager is managing people whose work is fundamentally AI-augmented. Your leader is navigating skill changes that happen every year instead of every five years.

The structures designed for pre-AI work don't work for AI-augmented work. Your org chart, career paths, and competency models need to evolve with the work itself.

Executive Summary: AI-era organizations require different team structures, career paths, and competency models than industrial-era organizations. Teams are organized around capabilities and outcomes, not functions. Career paths emphasize multiple progressions (IC, specialist, manager) instead of a single ladder. Competency models include "working effectively with AI" as foundational expectation. These shifts require redesigning not just roles, but how people develop, move, and progress through the organization.

Purpose Statement

By the end of this lesson, you'll know how to redesign teams for AI-augmented work, how to build career paths that aren't limited by position scarcity, and how to create competency models that reflect AI-era expectations. You'll have a concrete framework for making these changes and a roadmap for managing the transition.

Team Redesign: From Functions to Capabilities and Outcomes

The traditional team design (industrial era): - Organize by function (recruiting team, finance team, operations team)
- Stack roles in clear hierarchy
- Clear reporting lines
- Limited cross-functional work

This structure was designed for stability. Work was predictable. Roles were clear. Innovation was planned.

The AI-era team design (capability-based):
- Organize around outcomes and capabilities needed
- Mix skills on teams (cross-functional by default)
- Flexible collaboration patterns
- Continuous learning and evolution

This structure is designed for adaptation. Work changes. Capabilities matter more than titles. Innovation is expected.

Concrete example: Redesigning the Recruiting Function

Let's look at recruiting as a detailed case:

Traditional structure (pre-AI):

VP Talent Acquisition
│
├─ Manager, Sourcing
│ ├─ Sourcer 1
│ ├─ Sourcer 2
│ └─ Sourcer 3
│
├─ Manager, Screening
│ ├─ Recruiter 1
│ ├─ Recruiter 2
│ └─ Recruiter 3
│
└─ Manager, Onboarding
├─ Onboarding Specialist 1
└─ Onboarding Specialist 2

This is clean and simple. Sourcers source. Recruiters screen. Onboarding people onboard. Everyone knows their job.

AI-era structure (outcome-based):

VP Talent Acquisition

├─ HIRING TEAM 1 (Sales) [Cross-functional team]
│ ├─ Recruiter (owns manager relationships, hiring quality)
│ ├─ Data Analyst (hiring metrics, pipeline health, analytics)
│ ├─ AI Trainer (helps managers use hiring AI tools effectively)
│ └─ Sourcer (uses AI tools, manages candidate pipeline)
│
├─ HIRING TEAM 2 (Engineering) [Cross-functional team]
│ ├─ Recruiter
│ ├─ Data Analyst
│ ├─ Technical Sourcers (2 - deep engineering knowledge)
│ └─ Candidate Experience Specialist
│
├─ PLATFORM TEAM (Shared Services)
│ ├─ Data Engineer (builds hiring data pipelines)
│ ├─ Prompt Engineer (optimizes AI prompts and workflows)
│ ├─ Bias Auditor (tests hiring AI for fairness)
│ └─ Tools & Operations Specialist
│
└─ ONBOARDING TEAM
├─ Onboarding Manager
├─ Content Designer
└─ Learning Systems Specialist

What's different:
- Organized around outcomes: Hiring Team 1 owns "fast, quality hiring for Sales", not "sourcing" or "screening"
- Cross-functional: Each team has recruiter, data person, sourcer, trainer, skills mixed
- Shared services: Data engineering and bias auditing are centralized (don't duplicate across teams)
- Flexible collaboration: Teams coordinate through shared goals, not just reporting lines
- Built for AI: Everyone on the team understands how AI affects the work

Why this is better:
- Faster hiring decisions (teams are co-located, not separated by function)
- Better data insights (analyst on team knows the work)
- Better adoption (AI trainer on team helps adoption happen)
- Better fairness (bias auditor reviews what's happening)
- Flexibility (can add people or reorganize based on need)

It's harder to manage (you lose clean reporting lines and clear responsibilities). It also produces better outcomes.

Callout: The Learning Curve - Cross-functional team structures require more communication and coordination. Expect 2-3 months of inefficiency as teams figure out how to work together. This is normal and worth the investment.

Career Paths: From Positions to Progression

The traditional career path (position-based):

Associate → Manager → Senior Manager → Director → VP

Progress by moving up. There's only so many director roles. Competition is scarce positions. Some people plateau. There's nowhere higher to go.

Issues:
- Progress is limited by available positions
- You can only do certain work if you have the right title
- Lateral moves are seen as stepping backward
- "Manager" path is only valued path
- Specialists get stuck (can't advance without moving into management)

The AI-era career path (progression-based):

Multiple progressions. Individual contributors, specialists, managers, all equally valued. Progress through impact and growth, not title hoarding.

INDIVIDUAL CONTRIBUTOR PATH
├─ Analytics Associate (early career, learning)
├─ Data Analyst (independent work, expertise building)
├─ Senior Data Analyst (high impact, scope growing)
├─ Principal Data Analyst (thought leadership, org influence)
└─ Distinguished Analyst (external credibility, strategy)

MANAGEMENT PATH
├─ Analytics Associate
├─ Data Analyst
├─ Analytics Manager (people management begins)
├─ Senior Analytics Manager (larger team, strategy)
└─ Director of Analytics (org-wide strategy)

SPECIALIST/EXPERT PATH
├─ Data Analyst (general)
├─ Senior Data Analyst (building expertise in domain)
├─ Principal Analyst: AI-Integrated Analytics (specializing in AI-assisted analysis)
├─ Distinguished Specialist: AI Strategy (thought leader in how AI changes analytics)

HYBRID PATH
├─ Data Analyst (individual work)
├─ Senior Analyst (some mentoring, staying hands-on)
├─ Principal Analyst (doing work + leading, architecting solutions)
└─ Director (leading + strategy)

Key differences:
- Lateral progression is valued equally to vertical, A principal analyst has same status and compensation as a director
- Roles evolve as technology evolves, Data analyst today includes AI skills
- Multiple ways to progress, You can deepen expertise, build management skills, or do both
- Career is a portfolio, You build capabilities across domains, not just climb one ladder

This requires different mindset:
- Compensation for principal/specialist roles should match director compensation
- Titles need to reflect seniority (not "Senior Data Analyst" for entry-level, "Principal" for thought leadership)
- Career conversations are about impact and growth, not title chase
- Promotion is recognition of capability, not scarcity

Competency Models: What People Actually Need to Know and Do

Traditional competency models (pre-AI) for key functions:

Recruiting competencies:
- Sourcing strategies
- Assessment and selection
- Negotiation
- Candidate relationship building
- Compliance knowledge

Finance competencies:
- Financial analysis
- Process management
- Compliance
- Communication
- Problem-solving

Learning competencies:
- Curriculum design
- Facilitation
- Adult learning theory
- Communication
- Measurement

These are solid, but they're missing something critical: how to work effectively with AI.

Updated competency models (AI-era) for the same functions:

Core competencies (expected for ALL roles):

AI LITERACY (New, foundational)
├─ Understanding what AI can/can't do
├─ Knowing when AI is appropriate vs. when humans should decide
├─ Ability to work with AI tools
├─ Comfort with ambiguity (AI is probabilistic, not deterministic)
└─ Willingness to experiment and learn

WORKING WITH DATA INSIGHTS (New, foundational)
├─ Understanding data quality issues
├─ Ability to interpret statistics and patterns
├─ Challenging data-driven recommendations
├─ Using data to make decisions
└─ Understanding when data is insufficient

CHANGE AND ADAPTABILITY (New, foundational)
├─ Comfort with rapid evolution
├─ Learning agility (can learn quickly from new situations)
├─ Resilience (things change, can handle it)
├─ Feedback orientation (learns from mistakes)
└─ Openness (willing to try new approaches)

Function-specific example: Recruiting competency model (AI era):

Core competencies (all roles):
├─ Relationship building (human-centered, can build trust)
├─ Business acumen (understands what the business needs)
├─ Problem-solving (can figure out how to do things)
├─ AI literacy (understands AI tools used in recruiting)
└─ Data-informed decision making (uses data, doesn't blindly follow it)

Sourcer competencies:
├─ Sourcing strategies (can find candidates)
├─ Search query optimization (writes good search queries)
├─ Prompt engineering for AI sourcing (structures prompts to get good results)
├─ Candidate engagement (can build relationships with candidates)
├─ Pipeline building (builds long-term candidate pipelines)
└─ Persuasion (can convince people to apply)

Recruiter competencies:
├─ Assessment and selection (can evaluate candidates well)
├─ Interview skills (conducts effective interviews)
├─ Negotiation (can close offers)
├─ Candidate experience design (makes hiring experience good)
├─ Understanding AI hiring tools (knows how screening works, when it works, when it fails)
├─ Bias awareness and mitigation (can spot unfair patterns)
└─ Stakeholder management (works effectively with hiring managers)

Manager competencies:
├─ Team leadership (can lead people)
├─ Hiring strategy (can think strategically about talent)
├─ Vendor management (works with tool vendors)
├─ Team optimization using data (uses metrics to improve team)
├─ Leading teams in AI-augmented environment (helps team work with AI)
└─ Ethical decision-making (when something seems unfair, addresses it)

The new competencies (AI literacy, data interpretation, ethical decision-making) are non-negotiable. They're not nice-to-have. They're foundational. Everyone needs them.

Performance Management in an AI Era

Traditional performance management:
- Manager evaluates individual based on role expectations
- Rating given (usually 1-5 scale)
- Tied to compensation
- Annual or biannual
- Relatively static ("you're a 3, keep doing what you're doing")

AI-era evolution:

Performance becomes more dynamic, continuous, and multi-dimensional:

AI-informed but human-decided
- AI provides insights (performance patterns, peer comparisons, data)
- Human manager makes final judgment
- (AI shouldn't decide performance ratings, human judgment must remain)

Skills-based
- Performance measured on capabilities you have and are developing
- Not just "did you hit your goals?" but "are you growing?"
- Recognizes that roles are changing

Contribution over activity
- What impact did you have? (not how busy were you)
- Did you solve problems? (not how many tasks did you complete)
- Did work get better? (not how much work did you do)

Growth trajectory
- Are you developing? Moving to new capabilities?
- Being evaluated on growth as much as current performance

Example conversation (new approach):

Manager: "Let's look at your performance over the past six months. I've been tracking several things. First, your project delivery. You led three major projects, all delivered on time and above quality targets. That's solid. Second, your developing new capability. You completed the prompt engineering course, and I've already seen you applying it, optimized three recruiting workflows, and we're seeing 20% faster screening. That's growth. Third, let's talk about the work style change. AI is changing what we do. You've adapted well, learning tools, changing how you work. I'd like to see you also mentor others on this transition. You're in a good spot: doing current role well, building capability for next role. That's what I want to see."

This is different from:
- "You met all your goals" (activity-based, backward-looking)
- "You scored 8/10" (rating-based, doesn't explain what matters)
- "Here's your rating for this year" (static snapshot)

New approach is outcome + skill + growth based. It's forward-looking.

>
Callout: The Measurement Challenge - In AI era, measurement becomes harder. How do you measure "learning agility"? How do you measure "works well with AI"? You need to define what these look like. "Works well with AI" means: asks good questions, recognizes AI limitations, integrates AI into workflow, teaches others how to use AI effectively. You can measure these behaviors.

Organizational Design Patterns for AI

Different company types benefit from different structures. Here are patterns:

Pattern 1: Centralized AI Capability
- One team owns AI/data strategy and execution
- All AI initiatives go through this team
- Pros: Consistent governance, shared infrastructure, prevents fragmentation
- Cons: Can be bottleneck, slower execution
- Good for: Companies early in AI journey, high-risk industries, regulated environments

Pattern 2: Embedded AI Capability
- AI experts embedded in each business unit
- Federated governance (units coordinate loosely)
- Pros: Fast execution, local ownership, close to problems
- Cons: Inconsistent standards, duplicated work, hard to share learning
- Good for: Large companies, diverse business units, innovation-focused

Pattern 3: Hub-and-Spoke
- Central team sets standards and manages shared platforms
- Teams embed AI capability locally
- Pros: Best of both (speed + consistency)
- Cons: Requires clear governance, more communication
- Good for: Most mature organizations (this is often the target state)

Pattern 4: AI-First Structure
- Most teams are cross-functional (include data/AI as core)
- No separate "data team", AI is part of how all work happens
- Pros: Fast evolution, distributed learning, deeply integrated
- Cons: Requires high capability across organization
- Good for: Companies that are truly transformed by AI, long-term vision

Choose the pattern that fits your company and evolves it as you mature.

Building the Transition: Managing the Change

Moving from traditional to AI-era structures is hard. People have invested in careers. Career paths are understood. Organization feels stable.

Now you're changing it. This requires care.

Principles for managing transition:

1. Be transparent about change
- People need to understand why structure is changing
- What does it mean for them?
- What stays the same? What changes?
- Communication early and often

2. Create optionality
- Let people choose their path (specialist, manager, different role)
- Don't force transitions
- Support people who want to stay in current role and learn new skills
- Support people who want to move

3. Invest in development
- People need help developing new capabilities
- Training, coaching, mentorship
- Time to learn (not on top of full job)
- Don't expect people to figure it out alone

4. Protect people
- Nobody should be demoted because their role is changing
- Base compensation should be protected during transition
- Title changes shouldn't mean pay cuts
- Move people up, not down

5. Create peer models
- Find people who transition well
- Make them visible ("Here's what good transition looks like")
- Have them mentor others
- Peer models are more powerful than management directives

Example transition timeline (12+ months):

MONTHS 1-3: Awareness and Design
├─ Communicate why we're changing (all-hands, small groups, 1:1s)
├─ Involve managers and employees in design (listen to concerns)
├─ Draft new competencies and career paths (get feedback)
├─ Refine based on feedback
└─ Leadership alignment on final design

MONTHS 4-6: Pilot and Early Transition
├─ Pilot new structure with 2-3 teams
├─ Offer voluntary transitions (move to new role/path)
├─ Build support infrastructure (training, coaching, mentorship)
├─ Learn what works and what doesn't
└─ Make adjustments

MONTHS 6-12: Scaled Transition
├─ Expand to all teams
├─ Support people transitioning
├─ Update systems (HRIS, performance management, career path tools)
├─ Measure adoption and impact
└─ Continue coaching and support

MONTHS 12+: Optimization and Culture Shift
├─ Refine based on what you learned
├─ Develop emerging career paths further
├─ Build culture for new ways of working
├─ Celebrate progress
└─ Plan next evolution

The key is speed (do it in 12 months, not 3 years) and support (people need help, not just announcements).

What to Do Monday Morning

• 
  Map your current team structure. Which functions are isolated? Where could AI enable cross-functional collaboration? Where are bottlenecks?
• 
  Pick one team and redesign it. Not your whole organization. One team. Use the principles from this lesson. What changes? What stays same? What's better? What's harder?
• 
  Audit competency models. What AI-related competencies are missing? What needs updating? Start with one function.
• 
  Design one new career path. Pick a role that's changing. What progression options exist? How does someone advance without moving into management?
• 
  Communication with managers. "Organization is evolving. Here's why. Here's how we support people through it. Let's talk about what this means for your team."

Key Takeaways

• Teams are organized around outcomes and capabilities, not functions. AI-era teams are cross-functional by design.
  - Career paths are multiple progressions, not a single ladder. IC, manager, specialist are all valued and rewarded.
  - Competency models must include AI literacy and data skills. These are baseline expectations for all roles.
  - Organizational structure should enable, not constrain, AI capability. Choose structures that support your strategy.
  - Managing the transition is critical. Transparency, optionality, investment, protection, and peer models all matter.

FAQ

Q: Isn't this just a reorganization? Won't people resist?

A: Yes. Change is hard. The key is clarity about why, optionality in how people participate, and genuine support for transition. Do it thoughtfully, not as a shock. When people understand "we're changing to be faster" or "to be better," most come along.

Q: What about people who don't want to develop AI skills?

A: Be honest: working in an AI-augmented organization means developing some AI literacy. That's non-negotiable. But there are many paths forward (specialist role, IC role, different domain, different company). Work with people to find their path.

Q: How do we keep specialist roles valued equally to management roles?

A: Through compensation, title, and visibility. A principal analyst should be compensated similarly to a director. Title should reflect seniority. They should be visible in important decisions. Make it real, not theoretical.

Q: Won't this create chaos?

A: There's a period of adjustment (2-3 months). Teams figure out how to work together. Roles clarify. After that, the structure usually works better than the old one. Temporary chaos is worth the long-term benefit.

What's Next

You've redesigned the organization for AI. Your teams are cross-functional. Career paths offer options. Competencies reflect AI-era expectations. Now you need to think about the future: what's coming in the next 2-5 years? What emerging AI capabilities will reshape HR and organizations again? That's the focus of Chapter 5.