A people partner can help you understand compensation bands, investigation rules, hiring practice, and the correct process for serious performance concerns. They cannot replace the management conversation you owe your engineer. Bring dates, observed behavior, and work impact early, ask what is confidential and what is not, and keep ordinary coaching inside the manager relationship.
When should you contact a people partner?
Contact them when policy, fairness, legal process, compensation structure, or organizational consistency matters. Useful examples include preparing a hiring loop, checking a compensation band, responding to a complaint, considering a formal performance plan, or understanding leave and accommodation procedures. Early advice is easier to use than emergency advice after a manager has already made promises.
Ordinary coaching usually stays with you. A missed estimate, unclear design note, or difficult disagreement belongs in a direct 1 on 1 unless it forms part of a more serious pattern. Asking a people partner to deliver routine feedback weakens trust and implies a formal consequence that may not exist.
According to iSilta's 2026 survey of 146 organizations, 61% train managers only after promotion. A people partner can help you prepare a first management conversation, but they cannot replace the coaching you still owe the engineer.
What facts should you bring?
Bring dates, specific behavior, relevant expectation, work impact, prior conversations, and the support already offered. For example, say that on two release dates the engineer changed a production setting without the required review, that you discussed the rule after the first event, and that the second change caused a rollback. This is more useful than saying the person has poor judgment.
Separate what you observed from what you inferred. You may know that a meeting ended without an owner. You may only suspect that the engineer does not care. A people partner can help choose a process when the evidence is clear, but they cannot turn a vibe into fair documentation.
Include context that could change interpretation. Was the expectation written? Did another manager give conflicting direction? Are peers held to the same standard? Did workload or access make compliance impossible? Facts should support a fair inquiry, not just strengthen the manager's first conclusion.
Which process are you actually in?
| Situation | Manager role | People partner role |
|---|---|---|
| Ordinary coaching | Gives direct feedback | Advises if asked |
| Compensation question | Explains work context | Clarifies band and process |
| Formal performance concern | Documents and coaches | Guides consistent process |
| Investigation | Preserves facts and boundaries | Coordinates required steps |
| Hiring loop | Defines role evidence | Supports fair practice |
Ask the process question directly. Are you seeking advice, starting formal documentation, reporting a concern, or requesting a decision? Each path creates different obligations and expectations. A casual sounding conversation may still become part of a company record, so clarity matters before you share sensitive details.
Also ask who owns the next action and what you may tell the engineer. Never invent secrecy. In some investigations, information must be limited. In ordinary performance coaching, surprise is usually harmful. The people partner should help you understand the boundary; you should communicate honestly inside it.
How do you prepare a difficult conversation?
- Write the observed behavior and work impact.
- Check the relevant expectation and prior guidance.
- Ask which company process applies.
- Clarify confidentiality and documentation rules.
- Draft a direct opening in your own voice.
- Plan questions and realistic support.
- Hold the conversation yourself when appropriate.
- Record facts and agreed follow up.
Preparation should make you more direct, not more scripted. The engineer needs to hear what happened, why it matters, and what must change. They also need room to add context and disagree. A people partner can test whether your language is factual and whether the proposed next step fits policy.
Do not bring the people partner into the meeting merely to make your feedback feel heavier. Their presence can signal formal process and change what the engineer believes is happening. Invite them when the process calls for it or when they have a defined role, and explain that role in advance.
What should remain inside the 1 on 1?
Keep routine expectations, recognition, course correction, growth discussions, and relationship repair between manager and engineer. These conversations are central management work. If you repeatedly outsource them, the people partner receives fragments while the engineer experiences a manager who speaks only when everything is easy.
Ask for preparation help when you are new or uncertain, then return with the conversation yourself. You might practice an opening, check whether examples are specific, or ask how to respond if new information appears. Advice can improve your management without placing a third person in every exchange.
Tell the engineer when a topic has moved beyond ordinary coaching. A formal performance plan should not be disguised as another casual check in. Use the company's terms, explain the process and support, and distinguish facts already discussed from any new concern.
How should confidentiality be understood?
A people partner supports employees and managers, and also has duties to the company and its processes. Do not assume the conversation is private in the same way as a personal confidant. Ask what will be recorded, who may need to know, and what action certain disclosures require.
Share only what is relevant. Speculation about health, family, personality, or motives can create harm and distract from work facts. If sensitive personal information is necessary, follow the advised route and limit distribution. More detail is not automatically better evidence.
If you need personal emotional support, use an appropriate confidential resource rather than turning a case discussion into therapy. You can acknowledge that management is difficult while still protecting the engineer's dignity and the integrity of the process.
When should they join hiring or performance work?
Invite the people partner into hiring design when the role, interview evidence, panel practice, or compensation process needs alignment. They can help identify inconsistent criteria and make sure interviewers know how decisions will be recorded. Engineering managers still own the technical needs and must train interviewers to evaluate them.
For a possible performance plan, contact them before presenting a formal document. Bring the history of direct feedback, expected behavior, observed impact, support, and results. Ask whether a plan is the right tool. A plan should not compensate for months when the manager avoided clear coaching.
During a difficult case, agree on a communication rhythm. You own the ongoing work relationship and factual updates. The people partner owns process guidance and any actions assigned to their role. Frequent alignment prevents the engineer from receiving one message in a meeting and another from company procedure.
How do you keep the partnership healthy?
Build context before a crisis. Explain your team's work, recurring roles, and management concerns during calm periods. This helps advice fit engineering reality and makes it easier to spot patterns across the organization without exposing unnecessary personal detail.
Challenge advice respectfully when it does not match observed facts or team constraints. Ask what policy or risk drives the recommendation and offer alternatives. The goal is not to win against the people partner. It is to combine management context with process expertise and reach a fair, workable action.
Close the loop after advice. Tell them what conversation occurred, what new facts emerged, and what was agreed. Then keep coaching the engineer. A healthy partnership improves your judgment while leaving you visibly accountable for the relationship you manage.
What should happen before a performance plan?
Before proposing a performance plan, review whether the engineer received clear expectations and direct feedback with a reasonable chance to respond. Gather the relevant examples, dates, work impact, and support. If the record consists mostly of private manager concern, the first need may be honest coaching rather than a formal plan.
Bring the evidence to the people partner and ask what process applies. Check whether similar situations have been handled consistently, whether any policy or protected context requires care, and which documents are appropriate. Do not ask them to manufacture certainty. New facts may show that the problem is unclear ownership, conflicting direction, or a role mismatch rather than individual performance.
Prepare to speak in plain language. Explain the expectation, the observed gap, prior conversations, and what must change. Invite the engineer's account before treating your narrative as complete. A people partner may help you test the wording, but the manager should be able to say it without hiding behind company process.
If a formal plan is appropriate, make success observable and connected to actual work. Name support, review dates, decision owners, and possible outcomes according to policy. Avoid goals such as improve attitude or show more leadership. The engineer deserves to know what evidence will be considered.
If a plan is not appropriate, do not leave the concern vague. Return to ordinary management with a specific conversation and follow up. The fact that a formal tool was rejected does not mean the work impact disappears. It means you must use the right level of coaching and accountability.
Throughout the process, preserve dignity. Share information only with people who need it, avoid discussing the case as a management story, and keep routine recognition accurate. Serious concern does not erase every contribution the engineer makes.
What are common questions?
Should a people partner give routine feedback to an engineer?
Usually no. The manager should handle ordinary coaching, while the people partner advises on process, fairness, and difficult preparation.
What evidence should a manager bring?
Bring dates, observed behavior, work impact, relevant expectations, prior conversations, and support already offered.
Is a conversation with a people partner confidential?
Do not assume it is. Ask what is recorded, who may need to know, and which disclosures require company action.
When is a performance plan appropriate?
Use the formal process only after checking policy, evidence, prior direct feedback, available support, and whether the tool fits the concern.
Should a people partner attend a 1 on 1?
Only when a defined process or purpose requires their presence, with that role explained to the engineer in advance.
Related: working with people who are not your reports, working with an embedded consultant, working with an engineer who has manager potential.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.