Reading uptime gaps across a family of internal apps
Isolated outage tickets rarely show whether one shared service is quietly dragging several business apps down at once.
Field notes
Notes from assessment rooms
Short pieces on how we read platform stack health for internal business apps — techniques, interview habits, and sequencing decisions.
Draw ownership maps before you chase another dashboard
Stack health analytics stall when nobody can say who decides for a shared middleware component.
How change calendars quietly stress the stack
Release friction often shows up as health noise even when individual deployments look clean.
What a 90-day remediation sequence actually looks like
After a stack health assessment, the value sits in the order of work — not in a long list of equal-priority fixes.
Interviewing application owners without turning the room defensive
Stack health findings depend on candid interviews. Tone and question order matter as much as technical depth.