Building Trust and Credibility Questions

Situation: An engineer told me my updates were accurate, but too much of them were status and not enough on blockers. They felt I was reporting progress instead of helping the team move.

Task: I needed to change how I communicated so the team could spend less time listening to updates and more time solving problems.

Action:

• I shortened my updates to three parts: what changed, what is blocked, and what help is needed.
• I started asking engineers at the start of the week, "What could slow you down?"
• I used meetings to remove obstacles, not to narrate every milestone.
• I followed up asynchronously on pure status so live time stayed focused.

Result: The conversations became more useful. Engineers started bringing risks earlier, and I was able to escalate issues sooner instead of hearing about them after the fact. The relationship improved because my role became clearer: help the team execute, not just report.

What I learned is that status is only valuable when it leads to action. If no decision or unblocker comes out of it, it probably belongs in a written update instead of a meeting.

I would evaluate the process by asking one question: does this reduce rework or improve decisions enough to justify the time it takes? A process is just a repeatable way of working. If it creates extra steps without visible benefit, it is too heavy.

How I would test it

• Ask engineers where the friction shows up.
• Compare the time spent on the template or meeting against the value it creates.
• Look for evidence like fewer misunderstandings, faster approvals, or fewer late changes.

If it is too heavy
I would redesign it to capture only what is needed for a decision. For example, instead of a long form, I might use three prompts: what are we deciding, what are the options, and what is the risk if we choose wrong?

Concrete example
If a review template takes 30 minutes to fill out but prevents a 2 hour rework later, it may be worth it. If it adds 30 minutes and nobody uses it to make a decision, I would remove or simplify it.

The goal is to make the process feel like a shortcut for thinking, not a tax on the team's time.

In the first 90 days, I would focus on rebuilding trust by proving that engineer input changes decisions. Trust is belief that your time and expertise matter, so I would design the rhythm around that.

Days 1 to 30

• Meet engineers 1:1 and ask what felt performative, slow, or already decided.
• Sit in planning and retrospectives as a listener first.
• Identify one or two decisions the team can truly influence.

Days 31 to 60

• Change the agenda so meetings start with open questions, not status.
• Share pre-reads early so engineers can react before the meeting.
• Close the loop by showing, "You raised X, so we changed Y."

Days 61 to 90

• Keep only the rituals that produce decisions or unblock work.
• Retire meetings that are just theater.
• Ask the team to rate each meeting on usefulness.

Concrete example
If planning used to be a 60 minute meeting where decisions were already made, I would split it into a 20 minute pre-review and a 30 minute decision session. Engineers would see their input shape scope before commitments are locked.

The signal that trust is improving is not attendance alone. It is when engineers start raising trade-offs earlier and disagreeing in the room instead of after the meeting.

In the moment, I would not bluff. I would acknowledge the constraint, ask one clarifying question, and buy time to make a sound decision. For example: "I want to make sure I understand the technical limit correctly. Can you restate the impact in one sentence?" If needed, I would say, "I do not want to guess here, so let's capture the decision point and I will follow up immediately after this meeting."

Why this works
A technical constraint is a rule or limit that affects what can be built. If I fake understanding, I risk making a bad call and losing trust. If I ask clearly, I show respect for the engineer's expertise.

Follow up

• Summarize what I heard in plain language.
• Confirm the implication with the engineer privately.
• Send the room a short note with the constraint, the impact, and the next step.

Example
If the issue is that a system can only process 100 requests per second, I would repeat it as, "This design may be fine at low traffic, but it will not hold at launch volume unless we change the approach." That turns jargon into a decision the whole room can act on.

The trust-building part is the follow-up: I circle back quickly, own my knowledge gap, and close the loop.

Situation: A commitment had been made to a stakeholder too early, before engineering had fully validated the scope. When I learned the truth, the team needed to hear that the date or feature set had to change.

Task: I had to deliver bad news without eroding trust further.

Action:

• I told the engineers the truth quickly and took responsibility for the premature commitment.
• In the conversation, I focused on the facts, the risk, and the options, not on defending the earlier promise.
• I helped the team pick a realistic path: reduce scope, move the date, or split the release.
• I then went back to the stakeholder with a clear explanation and a revised plan.

Result: The conversation was uncomfortable, but it was respected because I did not hide the issue. Confidence improved when the team saw I would protect them from repeat surprises and would not ask them to commit to impossible work.

To repair confidence, I started involving engineers earlier in any external commitment and made sure no date left the room without an engineering check on feasibility.