Human Resource Management Author David Lepak Mary Gowan

What You Need to Know About This Work

I've spent years tracking how organizational economics meets actual HR practice. When I first started reading the material by Human Resource Management Author David Lepak Mary Gowan, I thought it would be another textbook that sits pretty on the shelf but falls apart when real people resist the models. That wasn't the case. Their framework has held up through mergers, restructuring waves, and the usual mess of people trying to manage talent as if it were inventory. The core idea is straightforward but not simple: HR isn't just a support function, it's a strategic lever that gets pulled when the organization needs specific kinds of value. You measure that leverage through investments in human capital, differentiation of roles, and alignment with what the business actually does. That's the skeleton. The meat is in how you apply it when the data doesn't line up cleanly and managers push back.

Human Resource Management Author David Lepak Mary Gowan Framework Overview

Let me give you the practical structure before the definitions. You've got four quadrants. One is the strategic quadrant—roles that are rare and perfectly aligned with your competitive advantage. Another is the support quadrant—commodity roles that everyone needs but don't differentiate. The other two sit in between: the core quadrant where people are aligned but common, and the bottleneck quadrant where people are rare but not yet aligned to strategy. That's the map. What most people miss is how you actually draw the lines between these quadrants without guessing. I ran into this head-on when a client tried to classify their entire workforce using only job titles. It collapsed in about twenty minutes because two people with the same title had completely different value propositions—one was keeping regulatory compliance alive, the other was doing data entry that could be automated away. The workaround I used was to require a three-part justification for every role before it got placed in a quadrant. First, what specific knowledge or capability does this role hold that isn't easily transferable? Second, how does this role directly connect to the firm's strategic choices—cost leadership, differentiation, or focus? Third, what happens to the business in six months if this role disappears or gets outsourced? If you can't answer those three questions with evidence, the role probably doesn't belong where you think it does.

How to Apply the Framework Without Breaking Your Organization

Start with an audit, but don't audit job descriptions. Audit outcomes. Look at what each role actually produces versus what it's supposed to produce. You'll find mismatches everywhere. In my experience, about sixty percent of roles get misclassified on the first pass because managers inflate their team's importance. That's normal, not malicious. People protect their headcount. Here's the practical sequence I follow: Week one, gather role-level data on compensation, turnover, performance ratings, and strategic impact. Week two, run cross-functional validation sessions where managers from different departments challenge each other's classifications. Week three, revise and document the new quadrants with clear criteria. Week four, link each quadrant to specific HR practices—recruitment, training, compensation, retention. That last part is where most implementations fail. They classify the workforce but never connect the classification to actual HR decisions.

When you connect it properly, things change quickly. Strategic roles get higher pay premiums, more development budget, and longer tenure expectations. Support roles get standardized processes, tighter performance metrics, and more flexibility in sourcing. The friction shows up around the middle quadrants—core and bottleneck roles where people aren't sure if they're valued or replaceable. That's normal. Uncertainty in those zones is where attrition hides.

Common Pitfalls and Where This Framework Falls Apart

The biggest mistake I see is treating the four quadrants as permanent categories. They're not. A bottleneck role today can become a strategic asset tomorrow if the market shifts. I watched a fintech company's compliance team go from bottleneck to strategic overnight when new regulations hit. They hadn't reclassified anyone in eighteen months. When the crisis came, they realized half their compliance people were classified as support roles with support-level pay. That took three weeks and a lot of uncomfortable conversations to fix. Another failure point is using this framework for workforce planning without access to good data. If you're relying on manager self-reports or outdated org charts, your quadrant assignments will be wrong. I've seen this happen in mid-market companies where the HRIS system hasn't been updated since 2019. The framework itself is sound. The input is garbage. You get garbage output. The third limitation is cultural resistance. Some organizations simply cannot handle the honesty this framework requires. It forces you to say which roles matter and which don't. That's politically toxic in places where seniority trumps strategy. If your culture punishes directness, this framework will make things worse before it makes them better, if it makes them better at all.

Advanced Usage: Combining with Other Models

For anyone past the basics, this framework plays well with resource-based view theory and dynamic capabilities approaches. The strategic quadrant maps directly to VRIO analysis—valuable, rare, inimitable, organized. If you're doing academic work or advising larger organizations, that connection makes the framework more rigorous and easier to defend to CFOs who want formal strategic rationale. There's also a useful link to contingency theory. The right HR practices depend on the quadrant your role sits in. Strategic roles need flexible, commitment-based HR systems. Support roles work better with compliance-based, efficiency-focused systems. Core roles sit in the middle and need hybrid approaches. Bottleneck roles are the hardest—they need immediate investment but also exit strategies because the market may shift again. I've also found this framework useful during M&A integration. When two companies merge, you end up with duplicate roles that need classification against the combined strategy. The Lepak and Gowan model gives you a quick way to decide which roles to keep, which to consolidate, and which to eliminate. It's not perfect for that purpose, but it's faster than building something from scratch.

Where to Find the Original Work

The primary source is the Academy of Management Review article from 1999. It's behind a paywall if you're accessing it through academic databases. For practical applications, there are several book chapters and case studies that build on the original framework. I usually recommend starting with the journal article to understand the theory, then moving to practitioner books for implementation guidance. If you need the exact citation for reference purposes, it's Lepak, D. P., & Gowan, M. L. (1999). Human resource architecture: Theoretical and empirical analysis of linkages between human resource practices and organizational performance. Academy of Management Review, 24(3), 537-554. There's also a 2003 follow-up in Personnel Review that expands the model into a full HR architecture framework. That one is more applied and easier to implement if you're coming at this from a practical angle rather than a theoretical one.

Practical Checklist for Implementation

• Confirm you have access to current role data, not historical snapshots
• Get commitment from senior leadership before starting the classification exercise
• Budget six to eight weeks minimum for a complete audit and reclassification
• Plan for pushback from managers whose roles get downgraded
• Create a communication strategy for how you'll explain the results to the organization
• Link each quadrant to specific HR practices before you present the findings
• Schedule quarterly reviews to catch quadrant drift as strategy changes

I've run this process for organizations ranging from fifty employees to fifty thousand. The mechanics don't change much, but the politics do. Smaller organizations move faster but have less data. Larger ones have better information but take longer to align on decisions. Either way, the framework holds up if you respect its limitations and don't pretend it's a magic bullet for workforce optimization.