ThemeWellbeing & Balance
CardCard 58 of 61
Questions5 to explore

Work processes

The standardized processes we repeat

The way work actually gets done, the recurring processes and routines, shapes the daily experience of culture more than most formal initiatives.

Work processes are the accumulated habits of an organization: how projects get started, how decisions get reviewed, how meetings are run, how information is handed off, and how exceptions get handled. Some of these are deliberate and documented; many more have evolved without anyone consciously designing them. Both types shape culture.

Processes that work well tend to become invisible; people follow them without thinking. Processes that are broken, redundant, or unclear generate friction, frustration, and workarounds. The presence of many informal workarounds is usually a signal that the formal processes have failed to keep pace with how work actually happens.

There is also a cultural signal in how the organization treats process itself. Organizations that invest in clear, documented, and regularly reviewed processes tend to respect people's time and cognitive load. Those that leave processes undefined or expect people to simply figure it out on their own often create unnecessary stress and inequity between those who know the informal system and those who do not.

How it shows up

How this facet of culture actually appears in everyday working life, and what a healthy version tends to look like compared to one that is strained or ignored.

Clear and shared

Core processes are documented, accessible, and understood by the people who need to follow them; there is not a hidden knowledge layer for insiders only.

Regularly reviewed

Processes are updated when they stop working, rather than being maintained out of habit long after they have become obstacles.

Bureaucracy for its own sake

People navigate layers of approvals, forms, and sign-offs that add friction without adding value, which breeds quiet resentment.

Everyone doing it their own way

The absence of shared process means outcomes depend heavily on who is involved, creating inconsistency and a steep learning curve for new people.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

What are the most important recurring processes here, and how well do people understand and trust them?
Where does process feel like it helps people do good work, and where does it feel like it gets in the way?
Are there informal ways of getting things done that exist alongside or instead of official processes?
How does the organization decide when to change a process versus when to maintain it as it is?
What would a new person need to learn about how things actually get done here that is not written down anywhere?

Things to notice

Process debt, accumulated outdated or redundant steps, can slow teams down significantly before anyone has explicitly named it as a problem.
Processes that made sense at one organizational size often break under growth; the inflection points where processes need reinvention are worth watching for.
The people who know the informal system are often the most critical knowledge holders; their departure can expose how thin the documented process actually is.