Working with me document template for engineers and managers, communication, feedback, and collaboration norms that stick. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. Use this guide to move from generic advice to week by week manager habits on engineering teams.
Why teams adopt working with me documents
Why teams adopt working with me documents is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What to include in the template
What to include in the template is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do you introduce the doc to a new team?
How do you introduce the doc to a new team is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do remote and hybrid teams benefit most?
How do remote and hybrid teams benefit most is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
What pitfalls make these docs performative?
What pitfalls make these docs performative is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do you link personal docs to shared profiles?
How do you link personal docs to shared profiles is a manager practice that turns working with me document into predictable team behavior, not a poster on the wall.
Engineering managers win when working with me document is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 71% report a drop in engagement or listening scores when training is inadequate. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress.
On software teams, working with me document template and working with me document example intersects with delivery pressure, on call load, and review culture. Document what you learn in 1 on 1 notes and team forums so improvements survive reorgs. Prefer small experiments over big bang programs; measure behavior in the next sprint retro, not only in annual surveys.
If you are starting from zero, pick one report and one team ritual to change this week. Ask what would make working with me document easier for them, then close the loop publicly. Teams trust managers who act on listening, not managers who collect more forms.
Pair this work with shared profiles and action points after 1 on 1s so context survives handoffs. When working with me document shows up in skip levels and retros, not only in HR decks, you reduce the weak 1 on 1 patterns that show up when training arrives too late.
How do working with me document practices compare?
| Approach | Strength | Risk |
|---|---|---|
| Ad hoc conversations | Fast to start | Inconsistent across reports; hard to scale |
| Shared written profiles | Reduces guessing; helps hybrid teams | Stale if never revisited in 1 on 1s |
| Pulse and 1 on 1 loop | Connects listening to action | Fails if leaders skip follow through |
Implementation steps
- Clarify why working with me document matters to your team this quarter.
- Co create norms with reports; do not publish mandates without input.
- Pilot for two weeks; gather friction in 1 on 1s.
- Publish what changed because people spoke up.
- Revisit after org or role changes.
Frequently asked questions
What is a working with me document?
A teammate facing guide to your collaboration preferences, popularized by leaders who want less friction and fewer mistaken assumptions.
Is it only for executives?
No. ICs, tech leads, and managers all benefit; psychological safety rises when norms are explicit.
How is it different from a team working agreement?
Personal docs describe individuals; team agreements describe collective rules. Use both.
Should HR store it?
Keep it lightweight in team systems. Avoid making it a compliance form.
Related: personal user manual for work template, team working agreement template, communication styles at work.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.