Linus Tech Tips

while adding a shitton of process

If you do it right, having processes that are well reasoned and adhered to is a net time saver. I've been on teams with many different levels of processes. I can say from 20+ years of experience that there is nothing worse than a pipeline with too few processes. When every writer has a different way of delivering information to the editors, that's a time waster. When every tester has a different way of putting together a spreadsheet to hand off to the graphics department, that's a time waster.

Also, processes are supposed to serve the needs of the staff. Not the other way around. If a process adds too much effort for little reward, you can always change it or scrap it. Ideally, you'd have someone on staff whose job it is to manage your process flow, facilitate handoffs, and make periodic changes to the processes to close up inefficiencies and pain points for the staff.