Communication, Trust & Hard Conversations

Technical skill gets you the project. Communication keeps it alive. A forward deployed engineer spends much of the week talking, writing and calming worry. Interviewers know this. They will test how you handle people as closely as how you handle code. This lesson gives you habits and templates for the hard moments.

Know who you are talking to

• Executives want the result, the cost and the risk in a few lines.
• Managers want to know what happens next, and when.
• Daily users want to know if the tool will make their day easier or harder.
• Security and legal want facts about data, access and records.
• Engineers on the customer side want clear technical detail and respect for their systems.

Say the same truth in a different way for each group. Do not change the facts. Change the order and the words.

The weekly update

Send a short update on the same day every week. Predictable updates reduce worry. People stop asking where things stand.

SUBJECT: {{Project}} - week {{n}}: {{one-line headline}}

DONE THIS WEEK
- {{result in plain words, with a number if you have one}}

NEXT WEEK
- {{what you will do, and what you need from them}}

RESULTS SO FAR
- Test set: {{x of y}} passing (target {{z}})

RISKS AND BLOCKERS
- {{what could slow us, who owns the fix, by when}}

DECISIONS NEEDED
- {{decision, owner, date}}

Bad news early

Never hide a problem and hope to fix it first. Customers forgive problems. They do not forgive surprises. Tell them early, with three parts: what happened, what it means, and what you will do.

What happened: {{plain facts, no excuses}}
What it means: {{effect on dates, cost, quality}}
What I am doing: {{the fix and when you will report back}}
What I need from you: {{a decision or a piece of access, if any}}

Saying no

You will often hear requests that are out of scope, too risky or not possible. Do not say no and stop. Say what you can do instead. For example: we cannot promise perfect accuracy. We can reach nine out of ten on your test set, and send the rest to a person. Would that work?

• Point back to the written scope and the success number.
• Offer the next phase for new ideas.
• Explain the risk in the customer's terms, such as cost, delay or danger to their customers.
• Ask what problem sits behind the request. Often a simpler fix exists.

When things get tense

• Listen first. Repeat back what you heard. Do not defend yourself yet.
• Separate feelings from facts. Acknowledge the feeling. Then deal with the facts.
• Move a heated email thread to a call. Follow up with a short written summary.
• Know your escalation path. Tell your own manager early if a customer relationship is at risk.
• Never blame the customer's team in front of others.

Stakeholders who disagree

Different people want different things. Sales wants speed. Security wants safety. Users want ease. Write the trade-offs down. Show the options with their costs. Ask the sponsor to decide. Record the decision and its date.

What interviewers listen for

They listen for calm and clear structure. They listen for ownership: I did, I learned, I changed. They listen for respect toward customers, even in a story about a hard one.