How to explain technical debt to a Product Manager
Turn an implementation complaint into a bounded engineering decision. Connect technical debt to delivery, reliability, customer impact, and a concrete next step.
6 min read · framework + examplesMake the next conversation clearer.
Practical frameworks, honest trade-offs, and examples for the conversations engineers actually have.
Technical explanations
READ → TRY → RETRYHow to explain technical concepts to non-engineers
Start with the audience's problem, use a careful analogy, and explain one layer at a time without losing the important trade-off.
6 min read · framework + examplesMeetings
READ → TRY → RETRYHow to give better standup updates as a software engineer
Use progress, blocker, and next step to give a concise engineering update that helps teammates coordinate instead of recounting your whole day.
6 min read · framework + examplesArchitecture
READ → TRY → RETRYHow to present an architecture proposal
Present the problem, constraints, alternatives, trade-offs, rollout, and risks before asking a team to commit to an architecture.
6 min read · framework + examplesLeadership
READ → TRY → RETRYHow to communicate a project delay
Explain what changed, its impact, your response, and the next checkpoint. Communicate a delay without blame or false certainty.
6 min read · framework + examplesIncidents
READ → TRY → RETRYHow to communicate during a production incident
Give an honest incident update: impact, known facts, uncertainty, action, and the next update time. Avoid blame and unsupported recovery promises.
6 min read · framework + examplesYou don’t need to be a natural.
You need a place to practice.
Choose a realistic conversation and give yourself another try.
Try your first communication challenge