Working well

Your manager cannot read your stack trace

If you only report that you are busy, your manager has no way to help with the actual failure mode.

~5 minCareer
scroll
01 · the shape

Busy is not diagnostic

Managers hear "busy" from everyone. Useful context sounds more like: this decision is blocked, this project has hidden risk, this scope no longer fits, or this work is draining the wrong battery.

1:1 · better signal

The useful signal is usually already there.

career signal visible

Career systems are still systems. Pull out evidence and everything gets harder to debug.

02 · the move

Bring the ask with the problem

Say what is happening, why it matters, what you tried, and what help would change the outcome. That lets your manager use their different tools.

manager-update.md

A clear ask is easier to act on than a weather report.

03 · the check

Escalate early enough to matter

Escalation is not failure. It is routing a problem to the level where it can be solved before it becomes drama.

career signal lab
fuzzy
legible0
fuzzy: good work happened, but the signal is hard to carry forward

Flip the switches and watch the story turn into a tiny operating model.

0parts: risk, cause, tried, ask
0specific manager action
0surprise blockers at launch
04 · the takeaway

Make help easy to give

Your manager does not need every detail. They need the shape of the problem and the lever only they can pull.

source trail