Using Primitive Learning Scenarios to Enhance Team Capability Development

Human learning historically occurred in four primitive scenarios—fire, water source, cave, and daily life—and these same contexts can be mapped to modern organizational learning. When learning fails, it is often not due to the instructor or effort, but because the learning scenario and method are mismatched.

Fire represents a storytelling setting where a knowledgeable authority shares insights to a group. In organizations this can be an internal trainer delivering lectures to a team, department, or the whole company, or a specialist sharing expertise across the industry. One‑to‑many knowledge transfer has high leverage, but only when the content is targeted and accurate.

To ensure targeted capability building, the team establishes a quantifiable assessment system:

Define a technical skill matrix covering tool technologies (programming languages, cloud platforms, testing frameworks), practical skills (agile engineering, TDD, XP, DDD, trunk‑based development, CD, logging/monitoring), business knowledge, and system knowledge.

Periodically (e.g., every three months) evaluate each member against the matrix using a Level 1‑5 scale.

Discuss target scores with stakeholders (architects, development managers, team members) and compare individual scores with team averages to identify gaps.

Create improvement plans based on identified gaps and regularly track progress.

Improvement actions can include sharing sessions, workshops, and peer‑teaching. Rather than passive reception, the key is mutual teaching: those who need improvement pair with experts, then teach the material back to the group, reinforcing learning.

Water Source is the place where early humans sought water, a frequent site of dialogue. In modern teams it corresponds to informal spaces such as office tea rooms, cafeterias, or scheduled “fruit time” where spontaneous technical conversations happen without formal meetings, often yielding unexpected insights.

Cave symbolizes reflective learning. Individuals process insights gained from fire and water source scenarios, using external resources (books, websites) and internal reflection (e.g., iteration retrospectives) to consolidate knowledge and generate new understanding.

Life brings learning into practice. The ideas and knowledge gathered from the previous three scenarios are applied within the software development workflow, repeatedly validated, and eventually become part of the team’s collective knowledge base.

Case 1: “Open the Volume” – By encouraging team members to publish articles, blog posts, and insights on internal and external platforms, individuals leveraged all four learning scenarios, accelerating personal and team capability growth. The author recounts how sharing an Authentication Sidecar practice progressed from water‑source discussions to cave‑style research, culminating in fire‑style presentations that reached the project, client, and broader industry.

Case 2: Training a Non‑Computer‑Science Graduate – A new team member with an economics background was guided through a staged plan using water‑source one‑to‑many and one‑to‑one conversations, cave‑style self‑study, and fire‑style knowledge sharing. Within two months, the individual transitioned from passive learning to active participation, applying agile, DDD, and micro‑service concepts and sharing insights with the team.

These examples demonstrate that aligning learning activities with the appropriate primitive scenario—fire for high‑leverage sharing, water source for informal dialogue, cave for reflection, and life for practical application—significantly enhances both individual and organizational capability development.

真正的能力提升是一次冒险，就像人生一样，只有行动才能改变。每当个人和组织迈出一步的时候，他们就会不断释放自己的潜力，能力就会发生重建。