With my current colleagues, we actually started with more frequent Zoom calls and standups, but as we built trust, we got rid of these. (Sometimes however I thi

With my current colleagues, we actually started with more frequent Zoom calls and standups, but as we built trust, we got rid of these. (Sometimes however I think it's still necessary, even if we don't rationally understand why, just to see someone else's face periodically). Now we just communicate over Slack, close tickets in Asana and document everything in Nuclino. Generally, if we're feeling anything ("Hmm this process seems inefficient or useless"), we simply express it, and change it. If that meant more bureaucracy, we'd do it. If it meant less, we'd do it too. The most important thing is to communicate how you feel and why. I feel encouraging this culture really comes down to good organizational management and good product management (especially when it comes to feature requirements), not any kind of engineering process. I definitely appreciate this perspective and plan to keep it in the back of my mind - this is probably what some developers are thinking even if they don't say it! So if I keep this handy, people will say: "Oh, it's already been said, and that's okay! Now what? We can figure this out."