PKMC Module IV common mistakes
PKMC Module IV · Understand the traps and how to avoid them.
Treating 'knowledge' and 'information' as interchangeable in scenario questions, so the candidate picks the option that describes a document repository when the stem asks how to keep tacit expertise from leaving with a retiring engineer.
The fundamentals domain uses explicit/tacit and data-information-knowledge-wisdom distinctions that sound like vocabulary but drive the correct answer. Candidates skim the stem, recognize a familiar artifact (a lessons-learned register, a wiki), and stop reading.
What to do instead
Before choosing, label the stem's target as tacit or explicit and as person-held or artifact-held. If the asset is person-held expertise, eliminate options that only store documents; if it is codified data, eliminate options that require interviews or mentoring.
Selecting the elicitation technique with the most rigorous-sounding name (Delphi, nominal group technique) regardless of the constraint stated in the scenario, such as dispersed experts, a two-day deadline, or a hostile stakeholder group.
Candidates memorize technique definitions as a list and never attach each technique to its cost, anonymity, and geography profile. Exam stems hide the deciding constraint in a subordinate clause.
What to do instead
Build a one-page matrix of techniques (interviews, focus groups, workshops, Delphi, observation, document analysis, brainstorming) against anonymity, number of participants, time cost, geography, and conflict level. Answer by matching the stem's stated constraint to the matrix column, not by prestige of the method.
Confusing elicitation with requirements gathering and answering that the analyst should simply 'ask the sponsor what they want' when the scenario describes experts who cannot articulate their own process.
Most candidates come from a business-analysis background where elicitation equals stakeholder interviews. The exam tests situations where self-report is unreliable, and the correct answer is observation, shadowing, or artifact analysis.
What to do instead
When the stem signals that the source cannot verbalize the knowledge (habitual work, 'they just know it', process not documented), default to observation, protocol analysis, or document/artifact mining before considering interviews.
Choosing the taxonomy or metadata design that is most complete rather than the one that will actually be maintained, or ignoring the retrieval scenario (search by role, by phase, by project type) stated in the stem.
Candidates equate richer metadata with better organization and pick the option with the most fields. Exam scenarios usually reward fit to the retrieval use case and sustainability over exhaustiveness.
What to do instead
Read the stem for who will search and on what dimension, then select the structure that indexes that dimension. Reject options that add metadata no stated user will query, and reject structures that require rework every time a project closes.
Treating knowledge sharing as a communication or tooling problem, so the candidate picks 'implement a collaboration platform' when the scenario describes hoarding driven by incentives, fear of blame, or lack of trust.
Collaboration tools are visible and easy to name, and candidates conflate sharing behavior with sharing infrastructure. The exam repeatedly tests the social and motivational drivers behind sharing.
What to do instead
Diagnose the barrier named in the stem first: if it is cultural or incentive-based (blame culture, no recognition, competition between teams), eliminate tool-only answers and choose interventions that change incentives, psychological safety, or leadership modeling.
Assuming knowledge created in one project will transfer to another automatically once it is stored, and selecting 'upload to the repository' as the transfer mechanism.
Candidates collapse storage and transfer into one step. The exam distinguishes codification from the active push/pull work of transfer, which requires context, a broker, and absorptive capacity on the receiving side.
What to do instead
For transfer questions, check whether the answer includes the receiving team's context and capacity. Prefer options with active brokering (communities of practice, peer assists, knowledge brokers, joint workshops) over passive repository publication.
Choosing 'reuse the lessons-learned register from the previous project' as the answer for knowledge application, without checking whether the prior context matches the current project's scale, technology, or constraints.
Reuse is intuitively good, so any option containing reuse feels safe. The exam tests the judgment that reuse requires validating applicability and adapting, not copying.
What to do instead
When an option proposes reuse, ask whether the stem establishes comparable context. If not, prefer the option that adapts, validates, or tailors prior knowledge to the current project before applying it.
Answering retention questions with 'archive everything' or 'keep it in the repository indefinitely' when the stem raises storage cost, legal hold, or obsolete information.
Candidates equate retention with preservation and forget that retention policy includes defensible disposal and that obsolete knowledge can mislead future projects.
What to do instead
Separate retention from disposal in your notes. For each scenario, identify whether the risk is loss (needs capture and preservation) or contamination (needs review, versioning, and disposal). Choose the option that matches the stated risk.
Ignoring the timing of lessons-learned activities and selecting 'conduct a lessons-learned session at project closure' even when the stem describes recurring defects mid-execution.
Closure lessons-learned is the most familiar pattern from PM training, so candidates default to it. The exam tests progressive capture and the fact that end-of-project reviews lose detail and cannot influence the current project.
What to do instead
Map lessons-learned timing to the stem's symptom: mid-project recurring issues need progressive capture or after-action reviews at milestones; cross-project learning needs a validation and dissemination step after closure. Never choose closure-only when the stem says the problem is ongoing.
Treating governance, roles, and culture as soft background and picking the option that assigns knowledge management to a single dedicated KM officer or tool owner, rather than distributing accountability across project leadership and roles.
Candidates look for a single owner because that feels like clear accountability. The exam tests that knowledge culture is set by leadership behavior and that knowledge responsibilities are embedded in existing roles, not delegated to one person.
What to do instead
For governance and culture items, prefer answers where the project manager and senior leaders model and enforce knowledge behaviors, where roles have defined knowledge responsibilities in their charters, and where metrics or recognition reinforce them. Reject options that isolate KM in one role with no leadership involvement.