# For Tech Leads --- title: For Tech Leads author: Bas den Uijl date: 2026-05-23 tags: - owlery - path - tech-leads source-type: path summary: A practical Owlery route for tech leads who lead through technical judgement, translation, coordination, learning, and decision support. confidence: high last-updated: 2026-05-23 --- ## Summary This route is for tech leads who want to use Owlery without reading the whole garden first. Tech leads often lead through technical judgement, translation, coordination, and trust rather than formal authority. ## Common situations ### When the team is busy but not flowing Run [[Readiness to Flow Check (12 min)]]. Then explore [[When Work Looks Busy but Does Not Move]]. ### When coordination depends on a few people Run [[Team Cognitive Load Scan (20 min)]]. Then explore [[When Coordination Work Is Invisible]]. ### When technical debt is really system debt Run [[Debt Classification and Repayment Canvas]]. Then explore [[When Technical Debt Is Really System Debt]] and [[Technical Debt and System Debt Map]]. ### When methods become the argument Run [[Framework Translation Check]]. Then explore [[When Methods Are Becoming the Argument]] and [[Context Before Method Map]]. ### When AI speeds up output but not clarity Run [[AI Work Framing Canvas (20 min)]]. Then explore [[When AI Is Creating More Questions Than Answers]]. ## Useful maps - [[Flow Readiness and Cognitive Load Map]] - [[Team Cognitive Load and Coordination Burden Map]] - [[System Debt Map]] - [[Context Before Method Map]] - [[AI and Judgement Map]] ## Good first rule Make the work easier to understand before trying to make everyone work harder. ## See also - [[Start Here by Role]] - [[For Engineers and Individual Contributors]] - [[What Hurts Today]]