Knowledge transfer
Knowledge transfer is the communication, sharing, or application of information, expertise, or learned capabilities between people, systems, tasks, or contexts.
"Looks Good to Me"
The deliberate process of moving knowledge from one person or group to another.
- How it is used
- Uses code reviews as a deliberate mechanism for distributing team knowledge and reducing dependence on individual developers.
- How deep it goes
- Defines the process, distinguishes it from knowledge sharing, and connects it to reviews, collaboration, recorded rationale, and team risk.
- Examples
- Uses pull requests, review conversations, team meetings, pair programming, commit messages, and explanations of change rationale.
- What you can do after
- Apply it via code reviews and collaborative development practices to distribute codebase understanding and preserve change history.
Think Like a Software Engineering Manager
A structured interaction in which knowledge, skills, or work context are conveyed from one person or group to another.
- How it is used
- Uses knowledge transfer to support delegation, leadership handovers, departures, and continuity of team work.
- How deep it goes
- Provides practical methods such as sessions, shadowing, talks, and documentation, without prescribing a universal handover procedure.
- Examples
- Illustrates a ten-task delegation calculation and a leadership handover built around conversations, responsibilities, and documentation.
- What you can do after
- Practice/perform it through suitable delegation, demonstrations, shadowing, talks, and documentation to reduce dependence on one person.
Read how Think Like a Software Engineering Manager explains knowledge transfer →
Lead Developer Career Guide
A collaborative session in which people deliberately share information, skills, or expertise with others.
- How it is used
- Positions knowledge transfer as a way to support mentees, onboard developers, and keep expertise available when people leave or change roles.
- How deep it goes
- Offers practical sharing habits and reasons for them, but does not specify an agenda or procedure for a knowledge-sharing session.
- Examples
- Uses articles and Stack Overflow answers as reusable records of learning, alongside code reviews and knowledge-sharing sessions.
- What you can do after
- Practice/perform it by sharing learned solutions, remaining approachable to mentees, and helping them mentor others.
Read how Lead Developer Career Guide explains knowledge transfer →
The Creative Programmer
Transfer is the application of learned knowledge or skills to a different task or context.
- How it is used
- Uses programming-language learning to show how prior knowledge can accelerate or obstruct work in a new context.
- How deep it goes
- Explains facilitation and interference with examples, then connects transfer to elaboration, spacing, variation, and retrieval.
- Examples
- Uses Java-to-Kotlin simplification, JavaScript difficulties, Scala and Elixir immutability, and the Spanish embarazada misunderstanding.
- What you can do after
- Apply prior knowledge cautiously while learning languages, testing whether familiar assumptions transfer or interfere.
Read how The Creative Programmer explains knowledge transfer →
Data for All
Data sharing is the provision of data to another person, organization, system, or service for access or use.
- How it is used
- Frames health data sharing as a way to support care and research while raising questions about privacy and public trust.
- How deep it goes
- Explains privacy concerns through policy disclosures and proposed safeguards, but does not provide a step-by-step method for assessing them.
- Examples
- Uses wearable health measurements, NHS data-sharing attitudes, and a healthcare provider’s broad list of potential recipients.
- What you can do after
- Evaluate sharing choices by considering the recipients, purpose, and protections for personal health data.
Also covered in
- .NET MAUI in Action
- Machine Learning System Design
- Think Like a CTO
- Architecting an Apache Iceberg Lakehouse
- Effective Data Analysis
- Privacy-Preserving Machine Learning
- Demand Forecasting Best Practices
- Learn Docker in a Month of Lunches, Second Edition
- Functional Design and Architecture: Examples in Haskell
What to know first
- feedbackFeedback is information or evaluation about an action, system, or outcome that can inform assessment or subsequent decisions and behavior.
- collaborationCollaboration is the coordinated work of multiple participants who contribute toward a shared goal or outcome.
- loopA loop is a programming-language control-flow construct that repeatedly executes a block of instructions according to an iteration rule or continuation condition.
- GDPRThe General Data Protection Regulation (GDPR) is a European Union regulation governing the processing and protection of personal data and establishing related rights for individuals.
Related concepts
- code reviewimplemented by · Code review is the systematic examination of source code or proposed changes to assess correctness, quality, risks, or conformance to requirements or standards.
- container imageuses · A container image is a packaged filesystem and metadata artifact from which a container can be created and run.
- health datauses · Health data is recorded information about health conditions, medical care, treatments, healthcare delivery, or other aspects of individual or population health.
Questions about knowledge transfer
What is knowledge transfer?
Knowledge transfer is the communication, sharing, or application of information, expertise, or learned capabilities between people, systems, tasks, or contexts.
Which Manning books explain knowledge transfer?
"Looks Good to Me", Think Like a Software Engineering Manager, Lead Developer Career Guide, The Creative Programmer and Data for All.
What should I know before learning knowledge transfer?
Manning books that teach knowledge transfer usually introduce feedback, collaboration, loop and GDPR first.
What kinds of knowledge transfer are there?
Kinds of knowledge transfer include far transfer.
What is knowledge transfer a kind of?
Knowledge transfer is a kind of code review goal. An intended outcome that a team selects to guide and evaluate its code review process.
What is knowledge transfer also called?
Knowledge transfer is also called knowledge sharing.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




