Lessons Learned That Changed the Game — 8 Kaizens in 60 Days

Why do we monitor kaizens?

• Ensure every relevant decision is documented and easy to consult.
• Prevent errors and rework from repeating — every retrospective becomes insight for the next sprint.
• Give visibility to the team with tracking dashboards and dedicated views for blockers.

The 8 kaizens that made a difference

1. 1Active async communication — decisions in official channels, always recorded in the vault.
2. 2Points System V2.0 — compensation based on deliverables, not hours.
3. 3Bring conclusions, not research — meetings focused on decision; research comes pre-worked.
4. 4Structured weekly meetings — fixed agenda, metrics and action items reviewed live.
5. 5Content before design — complete textual production before approving layout.
6. 6AI-Assisted Methodology — five-phase framework to accelerate planning and execution.
7. 7Philosophy of "Excellence in Everything" — prioritize quality even in MVPs to reinforce branding.
8. 8Constant blocker review — central dashboard with critical blockers, owners and deadlines.

Documentation ritual

• Every meeting generates minutes with decisions, owners and identified lessons learned.
• Each kaizen receives an ID, estimated impact and status (implemented / pending).
• Dashboards display active kaizens to keep the team aware of next steps.

Execution cycle (from trigger to learning)

1. 1Identification — arises in a meeting, client feedback or indicator.
2. 2Recording — noted in the "Lessons Learned" block of the corresponding minutes.
3. 3Planning — we define owner, deadline and concrete action.
4. 4Implementation — action item goes to the Action Items Dashboard.
5. 5Review — we check impact and decide whether to maintain, adjust or escalate.

Tangible impact in numbers

• Async communication → time to formalize decisions dropped by 30%.
• Points System V2.0 → engagement from partners and contractors increased noticeably.
• Conclusions in meetings → we went from 8 to 12 actions per meeting.
• Weekly rituals → critical blockers dropped from 5 to 2.
• Content before design → Site Builder accelerated, without layout redirections.
• AI-Assisted Methodology → projects designed in 1 day (previously: weeks).
• Excellence in Everything → demos generated positive feedback on quality.
• Blocker review → we resolved risks 2x faster.

How to replicate in your company

1. 1Choose a central tool (Obsidian, Notion, Confluence) and keep everything there.
2. 2Create meeting templates with sections for decisions, actions and kaizens.
3. 3Establish a weekly ritual to review kaizens, blockers and metrics.
4. 4Implement dashboards to provide instant visibility of ongoing improvements.
5. 5Assign ownership: each kaizen needs an owner, deadline and checklist.
6. 6Celebrate and reassess: when a kaizen generates impact, document and communicate to the entire team.

Next evolutions of our system

• Create a visual wall of implemented kaizens with an interactive timeline.
• Generate monthly impact reports for leadership and partners.
• Turn recurring kaizens into official playbooks and training programs.
• Integrate culture indicators and NPS into the central dashboard.

Related resources

• Central indicators and active kaizens dashboard.
• Action items panel with priority tasks and owners.
• Site Builder Case — the impact of the "content before design" rule.
• Chatbot Case — documented decisions that became concrete improvements.
• AI-Assisted Methodology — framework that feeds our continuous improvement cycle.