What customer rounds look like, and the core moves put the moves on one page; this lesson teaches the three that carry a disagreement: owning the next step, acknowledging before you disagree, and offering options you would accept yourself, then recording what the customer decides. Every later lesson in this module uses these three moves.

One story runs through the lesson. You are the on a pilot of an order-status assistant for a building-supplies distributor’s customer service team. The pilot reads orders from a read replica of the order database. Shortly before it opens, the customer’s head of platform tells you that every integration must go through the API gateway her team is rolling out, and the replica connection has to go. The gateway doesn’t serve orders yet.

Owning the next step without bravado

You’ll be able to say what you own in one sentence, with a date, and leave out everything you don’t control.

Salesforce’s newsroom said, in March 2026, that forward deployed engineers “align to a customer’s business outcomes and stay accountable until those outcomes are met.” Source 1How Forward Deployed Engineers Are Proving AI Makes Tech Jobs More HumanPublisherSalesforceSource typecompany blog In a conversation, accountability sounds like a first-person action with an owner and a date, not a promise about things other people decide.

That is the . Commit to the outcome when you control it. When you don’t, commit to the date by which you will know. In the gateway story, whether the pilot opens on time depends on her access review, which you don’t run. Here is what you say to the head of platform, and every clause names who acts:

I can't promise the pilot opens Monday, because your access-review team
decides whether a new path to order data is allowed, and I don't run
that review. By Wednesday noon I'll send your team a design for how the
pilot reads orders, with the access path and query logging spelled out.
I'll call you Friday at ten with a yes or a new date.

The opposite failure is bravado: “Don’t worry, we’ll hit Monday.” It sounds like ownership and is the reverse of it, because it spends a date someone else controls.

When she pushes a second time (“I need Monday”), don’t trade the calibration away to end the tension. Repeat the part you control, then give her something to do with the uncertainty: “I can’t give you Monday today. If your reviewer can look at the design on Wednesday afternoon, I can give you the answer a day early. Can you ask?”

Ownership and calibrated commitments is one of the two gates in our client rubric. Its top anchor is a candidate who commits to a decision point rather than an outcome when uncertainty is high, and says why. We treat every score as a training signal, not a verdict.

GlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineerGlossaryCalibrated commitmentA promise limited to what you control, with an owner, a date and the conditions stated for everything else.More on Calibrated commitment