Reading a system before you change it
Three habits that keep tech analysis honest: inventory first, interview second, opinions last.
Blog
Notes for calmer technical decisions
Short pieces for people who analyse systems, compare stacks, and teach those habits inside their teams.
Criteria that survive a stack debate
Agree on evaluation criteria before demos, or demos will choose the criteria for you.
Analysis notes product and engineering can share
A short template: context, evidence, risks, open questions, and a provisional recommendation.
Training analysts inside a growing team
Private cohorts work when leadership protects practice time—not when analysis is squeezed into leftover hours.