Giving Hard Feedback to Seniors With More Experience Than You
Authority comes from title, obedience doesn't. A conversation structure that preserves relationships and changes behavior.
Topic guide
Technical communication that drives decisions: design docs and ADRs, presentations for boards and stakeholders, and storytelling for technical strategy.
3 topics · 14 articles
Design docs, ADRs, and documents people actually read.
Authority comes from title, obedience doesn't. A conversation structure that preserves relationships and changes behavior.
Your team uses AI with or without approval. Shadow AI is the default state. Eight controls a CTO implements this month.
What an AI-in-code policy must define: banned data, mandatory review, adoption measured, and the consequence of a violation set before it happens.
Three managing-up rituals for staff engineers: a two-line update every two weeks, risk logged before the fire, and a decision ask with a deadline.
A one-page strategy structure: the constraint, a dated decision, rejected alternatives, 90 days of delivery, and a review written in the file itself.
Meetings, boards, and stakeholder presentations.
Boards don't care about Kubernetes. They care about risk, cost, and deadlines. Translating technical roadmaps into business language.
Boards don't buy saved hours. They buy cost per PR, release cadence, and defect rate.
Engineering, product, and business fight for the same week with different numbers. A cross-roadmap review, a shared impact matrix, and a decision record put them in one room.
How to build a technical advisory board: three profiles, a 12-month contract with scope, a 90-minute agenda, and decisions recorded in five lines.
Making technical strategy and roadmaps compelling.
Building internally costs 4x the license price once you count the whole team. A decision tree with numbers on each side.
During a pivot, the technical leader freezes architecture for 90 days, protects paying customers, and picks one metric while the product tests a new bet.
After the build-vs-buy call, five vendor criteria: exit cost, an SLA with teeth, an integration trial, support hours, and a reference of your size.
Eight weeks fit when you cut scope before writing code. A week-by-week plan with architecture decisions that do not turn into debt at launch.
Every sprint without a quality reserve grows debt until a one-week feature takes three. A method to map it, measure it, and decide what to pay first.
Between 5 and 15 pages: complete enough to decide, short enough to be read. Beyond that, split it into smaller documents.
Whoever the decision affects: architects, leads of the teams involved, and product. Too many reviewers slow things down without improving the document.
Start with business impact (cost, risk, timeline) and explain the technology only afterwards, if asked.
Write proposals and decisions, which need careful reading. Present live urgent issues and topics that need a conversation.