# Team working agreement template for engineering squads Team working agreement template, meetings, Slack norms, review SLAs, and psychological safety rules for software teams. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. Use this guide to move from generic advice to week by week manager habits on engineering teams. ## What belongs in a working agreement? **What belongs in a working agreement is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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 facilitate the first session? **How do you facilitate the first session is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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 engineering specific clauses matter? **What engineering specific clauses matter is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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 measure if the agreement is working? **How do you measure if the agreement is working is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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 agreements support psychological safety? **How do working agreements support psychological safety is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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. ## When should you rewrite vs patch? **When should you rewrite vs patch is a manager practice that turns team working agreement into predictable team behavior, not a poster on the wall.** Engineering managers win when team working agreement is treated as operational data, not a one time workshop. According to iSilta's 2026 survey of 146 organizations, 63% cite regrettable attrition of strong performers linked to underdeveloped managers. That pattern shows up when managers lack shared context about how each person communicates, prioritizes, and recovers from stress. On software teams, working agreement template and team norms 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 team working agreement 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 team working agreement 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 team working agreement 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 * Gather the squad for 90 minutes with a draft template. * Brainstorm pain points from the last sprint (meetings, reviews, on call). * Turn pains into observable behaviors we will / will not do. * Assign an owner to each norm for the next retro check in. * Publish in the repo wiki and link from the team channel topic. ## Frequently asked questions What is a team working agreement? A co authored document of how the squad collaborates: meetings, tools, review times, and how you handle conflict. How often should teams refresh it? After every major team change and at least once per quarter in fast moving product teams. Who facilitates? Tech lead or EM, but ownership is collective, everyone signs on. Does it replace manager readme? No. Agreements are team level; readmes are individual. Related: communication preferences remote team, psychological safety high performance teams, maker manager divide engineering leads. Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo. Canonical: https://isilta.com/blog/team-working-agreement-template/