Help Ensure Knowledge Transfer

PMI draws a sharp line between explicit knowledge (things you can write down — specs, procedures, code comments) and tacit knowledge (things experienced people just know — judgment calls, "why we didn't do it that way last time"). Documentation alone captures explicit knowledge; tacit knowledge needs mentoring, pairing, and structured conversation.

This task is tested heavily around team turnover and project closure: a key team member is leaving mid-project, or the project is closing and handing off to operations. The best-answer pattern is almost always a deliberate knowledge-transfer plan (shadowing, paired work, retrospectives feeding a lessons-learned register) rather than "ask them to write a handover document" alone.

Study focus: the lessons-learned register is built continuously throughout the project, not assembled from memory at closure — a commonly tested distinction.