No Process is Invisible Process
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
I was talking to someone the other day about our team process, talking and talking about how our low-process workflow for managing our work and backlog was really great. We don't waste hours and hours in meetings on planning, preparing, estimating, etc, and instead everyone on the team creates tickets, plans out epics, and combs through our backlog also.
However, I realized that this low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.
This works when there's high trust across the team, the team has jelled, and they have all internalized this invisible process.
You're probably better off building a bit of "real" process instead, if only to set the expectation that the work needs to happen.
Tags:
Related Posts
micropost
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.
Published: ....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).