Home › The Garage › Ways of working
Teams & ways of working

Ways of working

How a team actually operates — how decisions get made, how work flows, how people communicate — shapes results more than the org chart ever will. Making those ways explicit is what lets a team improve them on purpose.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What ‘ways of working’ means
  2. The operating model
  3. Making the implicit explicit
  4. Improving them
  5. Common questions
Structure (the visible org chart) How decisions get made How work flows How people communicate
The org chart is the visible layer. Performance lives in the three below it — usually unwritten.

What ‘ways of working’ means

Ways of working are the everyday patterns by which a team actually gets things done: how a decision is made and who makes it, how work moves from one person to the next, how people communicate and coordinate. They are mostly unwritten — which is exactly why they drift and why they are so hard to improve. The org chart tells you who reports to whom; the ways of working tell you what it is actually like to get something done here.

The operating model

An operating model is ways of working made deliberate: an explicit answer to how the team turns inputs into outcomes. It covers who owns which decisions, how work is prioritised and flows, what the cadence of meetings and reviews is, and how teams hand off to each other. A good operating model is boring on purpose — it removes the daily friction of “how do we do this again?” so energy goes into the work, not the coordination.

Making the implicit explicit

The single most useful move is to write down how you actually work — a short, shared team working agreement: how we decide, how we communicate, what “done” means, how we handle disagreement. The act of writing it surfaces the places where people quietly assumed different things, which is where most friction hides. It is the team-level equivalent of a standard operating procedure.

Improving them

You can only improve what you’ve named
Treat ways of working as a process like any other: make them visible, find the friction (the recurring confusion, the slow hand-off, the decision that keeps bouncing), and change one thing at a time. A short regular retrospective is the engine — it turns “this is just how it is” into “here’s one thing we’ll try next.” That is continuous improvement applied to the team itself.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What are ‘ways of working’?

The everyday patterns by which a team gets things done — how decisions are made, how work flows, how people communicate. They are mostly unwritten and shape performance more than the formal org chart does.

What is an operating model?

Ways of working made deliberate and explicit: who owns which decisions, how work is prioritised and flows, the cadence of meetings and reviews, and how teams hand off. A clear operating model removes daily coordination friction.

What is a team working agreement?

A short, shared document of how a team actually works — how it decides, communicates, defines ‘done’ and handles disagreement. Writing it surfaces hidden differences in assumptions, which is where much team friction originates.

How do you improve a team’s ways of working?

Make them visible, find the recurring friction, and change one thing at a time, using a regular retrospective as the engine. It is continuous improvement applied to how the team operates rather than to a production process.

Related guides: High-performing teams · Cross-functional teams · Kaizen