Communication

Declare your status. Asking questions is the work.

Why Communication Matters

Most project failures aren't technical. They're communication failures.

Someone didn't know they were blocked. Someone assumed understanding that didn't exist. Someone waited too long to say "I don't know." Someone didn't write it down.

Technical skills get you hired. Communication skills determine what you can accomplish.

Declaring Your Status

Your manager, your team, your stakeholders, they can't see inside your head. They don't know if you're stuck, making progress, blocked, or confused. Silence looks the same whether you're crushing it or drowning.

Declare your status proactively.

The Phrases That Work

In discovery: "I'm in discovery on this. I'll have questions. Once I understand it, I'll come back with a plan."

This reframes not-knowing as process, not failure. It sets expectations. It buys you time to learn.

In validation: "I'm spiking the riskiest assumption. I'll know by end of day if our approach holds."

This shows progress while acknowledging uncertainty. You're not guessing; you're testing.

When blocked: "I'm blocked on X. I need Y to proceed. Can you help me get Y?"

Clear. Specific. Actionable. Not "I'm stuck" but "here's what would unstick me."

When behind: "This is taking longer than expected because of Z. Current estimate is now W."

Bad news early is better than bad news late. Surprises are worse than delays.

The Rhythm

Daily: Quick status to your team. What you did, what you're doing, what's in the way.

When things change: Immediately. Don't wait for the standup. If you're blocked, say so now.

When you don't know: Say that. "I don't know yet, but I'm working on finding out" is a valid status.

Asking Questions Is the Work

Questions during discovery aren't admitting weakness. They're doing the work.

The Permission to Not Know

You're allowed to not know. That's expected at the start of any significant work. The questions are how you get to knowing.

Bad: Pretending you understand when you don't. Building on shaky foundations. Wasting time because you were afraid to ask.

Good: "I don't understand X. Can you explain it?" "What did you mean when you said Y?" "I'm confused about Z; is it A or B?"

Questions asked early are cheap. Questions asked after you've built the wrong thing are expensive.

The Two Contexts

The old rule (adversarial contexts): Never ask a question you don't already know the answer to.

This applies in courtrooms, negotiations, some meetings. The question is a move in a game. Showing uncertainty is weakness.

The new rule (collaborative contexts): Ask because you don't know. That's the point.

This applies to most engineering work. You're trying to understand, not win. Questions reveal unknowns. Unknowns addressed early save time.

Know which context you're in. Most of your work is collaborative. Ask freely.

Asking Good Questions

Be specific. Not "I'm confused" but "I don't understand how X connects to Y."

Show your work. "I've looked at A and B and I think the answer is C, but I'm not sure because of D."

Ask the real question. If you're worried about something, ask about that thing. Don't dance around it.

Ask the right person. Who actually knows? Don't waste everyone's time.

Writing Things Down

If it's not written down, it doesn't exist. Verbal agreements, whiteboard discussions, hallway conversations, they evaporate. People remember differently. Details shift. Writing clarifies thinking, and your future self is a stranger who will not remember why you decided.

What to write: decisions (what was chosen, what alternatives were alive, why — the ADR template works), status, how things work, and what went wrong. Put it somewhere findable and close to the code; chat is ephemeral. Summary first, structured for scanning. And update or delete: outdated docs are worse than no docs.

Communication Anti-Patterns

The Disappearance. Going silent when things get hard. This creates anxiety and removes your ability to get help.

The Info Dump. Sending walls of text with no structure. No one will read it.

The Assumption. Assuming people know what you know. They don't.

The Hedge. Saying "I think maybe possibly this might be an issue" when you mean "This is a problem."

The Surprise. Revealing a major issue at the last minute. Deliver bad news early.

The Blame Shift. "I didn't know" when you should have asked. "They didn't tell me" when you should have confirmed.

The Core Practice

Declare your status. Proactively. Regularly. Especially when things change.

Ask questions. Early. Specifically. Without shame.

Write things down. Decisions, status, how things work. Somewhere findable.

Communication isn't a soft skill. It's how work gets done.

Declare your status. Ask the questions. Write it down. The communication is the work, not a distraction from it.