HKSM

A strategic lens for resource planning that identifies which internal capabilities provide the most advantage and deserve priority, protection, or development. It evaluates people, assets, and knowledge for value, scarcity, imitability, and organizational support to guide staffing, sourcing, and training decisions.

Key Points

• Emphasizes internal capabilities and assets as levers for project success.
• Uses criteria such as valuable, rare, hard to imitate, and supported by the organization (VRIO).
• Informs make-or-buy, partnering, training, retention, and knowledge management choices.
• Applied early in planning and revisited at phase gates as availability and priorities change.
• Relies on evidence from skills matrices, calendars, performance data, and lessons learned.
• Directs scarce, high-impact resources to work that most affects outcomes.

Purpose of Analysis

Clarify which capabilities you must leverage internally and which can be sourced externally without eroding value.

• Prioritize limited expert capacity on critical path activities.
• Identify where co-sourcing or outsourcing reduces cost and schedule risk.
• Expose capability gaps and define actions such as hiring, training, or procurement.
• Protect intellectual property and reduce turnover and imitation risks.
• Align resource choices with business strategy and funding constraints.

Method Steps

• Confirm scope, key deliverables, and the capabilities they require.
• Inventory internal resources: people skills, tools, IP, data, facilities, and partner relationships.
• Rate each resource against VRIO to gauge strategic importance and deployability.
• Map high-priority capabilities to WBS work packages, milestones, and decision points.
• Select sourcing strategies per capability: leverage internal, co-source, outsource, or automate.
• Plan enablement for strategic resources: processes, tooling, training, and knowledge capture.
• Quantify gaps and create acquisition or procurement actions with lead times and budgets.
• Update RACI or RAM, resource calendars, and integrate with schedule, cost, and risk plans.
• Review with functional leaders, secure commitments, and set monitoring checkpoints.

Inputs Needed

• Project charter, draft scope baseline, and high-level schedule.
• Skills inventory, resumes, certifications, and performance history.
• Resource calendars, capacity plans, and location or time zone data.
• Asset repositories: codebases, templates, labs, licenses, data sets, and patents.
• Vendor catalogs, rate cards, and labor market intelligence.
• Policies and constraints: HR rules, union or contract terms, legal and regulatory requirements.
• Budget targets, resource cost rates, and funding boundaries.
• Lessons learned and historical make-or-buy outcomes on similar work.
• Preliminary risk log and stakeholder analysis.

Outputs Produced

• Resource management strategy emphasizing deployment of strategic capabilities.
• Role definitions, staffing approach, and a RACI or RAM aligned to capability priorities.
• Make-or-buy decisions and procurement requests for non-differentiating work.
• Training, mentoring, and knowledge transfer plans for critical roles.
• Retention and backfill strategies to mitigate key-person risk.
• Schedule and cost updates reflecting sourcing choices and lead times.
• Assumptions and risk entries covering supplier dependence, IP protection, and capacity limits.
• Supplier selection criteria and handoff plans that safeguard core know-how.
• Monitoring metrics and governance checkpoints for utilization of strategic resources.

Interpretation Tips

• Only a subset of capabilities are truly differentiating; treat the rest as candidates for external sourcing.
• If a capability is valuable but under-supported, plan processes and tools to unlock its impact.
• Validate ratings with functional managers and data to avoid bias and overconfidence.
• Reassess at milestones; talent availability and market options change quickly.
• Pair experts with backups and document workflows to reduce single-point-of-failure risk.
• Use scenario analysis to compare internal, co-sourced, and outsourced options on cost, time, and risk.

Example

A bank plans an API modernization. The team identifies an in-house security architecture group and a proprietary tokenization library as strategic capabilities.

• Assign the security architects to design and review core authentication flows.
• Outsource commodity API test automation to a vetted vendor with clear handoffs.
• Fund training for mid-level engineers to reduce dependence on two senior specialists.
• Capture patterns and threat models in a reusable playbook to preserve know-how.
• Update the schedule to include vendor onboarding lead time and security review gates.

Pitfalls

• Inflating internal strengths without evidence and starving critical work of needed expertise.
• Ignoring enablement, so strategic resources lack processes or tools to scale.
• Creating single points of failure around star performers with no backups.
• Failing to protect IP during outsourcing or not setting clear handoff boundaries.
• Treating all tasks as core and missing cost or schedule benefits from external partners.
• Not revisiting decisions when capacity, budget, or market conditions change.

PMP Example Question

While planning resources for a machine learning project, you find the company’s proprietary data pipelines and two senior MLOps engineers are unique strengths, but test data generation and labeling are standard tasks. What should you do next?

1. Outsource the entire ML pipeline to a vendor to reduce schedule risk.
2. Secure the senior MLOps engineers for critical pipeline work, plan knowledge transfer, and outsource commodity tasks.
3. Delay resource decisions until the WBS is fully decomposed.
4. Assign both senior engineers at 50% across all tasks to maximize coverage.

Correct Answer: B — Secure strategic resources for differentiating work, enable knowledge transfer, and outsource non-core activities.

Explanation: The resource-based view prioritizes scarce internal capabilities on high-impact work while sourcing commodity tasks externally. This protects advantage and reduces single-point-of-failure risk.