Learning 300: Publish Your Progress

Imperative Explained

Publish Your Progress means making your learning public—documenting insights, sharing experiments, and distributing improvements so others can benefit. “Good” looks like clear summaries, simple artifacts, and honest reflections about what worked and what didn’t. Leaders who publish their progress reduce repeated mistakes, accelerate knowledge transfer, and raise the skill level of the entire team.
This imperative drives two outcomes: faster organizational learning and fewer repeated errors that waste time and budget. Visible learning becomes a force multiplier.

Five Behaviors

• Share insights often — Capture and distribute what you learn.
  
  
• Document experiments — Record what worked and what failed.
  
  
• Create simple artifacts — Build templates or guides others can use.
  
  
• Model vulnerability — Share imperfect learning honestly.
  
  
• Invite contribution — Encourage others to add to the knowledge base.
  
  

If You Don’t

Learning stays siloed. Teams repeat avoidable mistakes. Execution slows as leaders recreate work already solved elsewhere. Rework increases, innovation lags, and cross-functional collaboration becomes more fragile. Customers experience inconsistent delivery due to uneven knowledge distribution.

If You Do

Knowledge compounds. Teams execute faster because insights spread quickly. KPIs improve: rework hours drop, time-to-ramp accelerates, and quality stabilizes. Leaders gain credibility as contributors to organizational intelligence, not just performers.

Mini-Case

A technical lead began publishing weekly “micro-lessons” summarizing errors, fixes, and insights from ongoing projects. Within two months, onboarding time for new engineers dropped by 25%, error rates on common tasks decreased significantly, and cross-functional partners reported smoother collaboration due to clearer shared knowledge.

Try It This Week

1. Document one insight from current work.
   
   
2. Share a short summary with your team.
   
   
3. Create a simple artifact someone else can re-use.
   
   
4. Capture one failed experiment and what you learned.
   
   
5. Ask your team to add one insight to a shared space.

Learn More

Learning 300 pairs well with skills focused on visibility and improvement. Explore Accountability 300: Turn Scars into Systems to transform insights into durable processes and Integrity 300: Say It Plain to communicate your learning clearly. Both help scale knowledge across the team.