Synchronous Work > Asynchronous Work

Lately, I’ve been experimenting with a new approach: collaborative build sessions with my clients.

Instead of the traditional asynchronous back-and-forth, we work together in real time for an hour or two each day, building and iterating directly on their project scope.

The best part? Watching clients actively solve their own business challenges. This hands-on strategy bridges the gap between business and technology, fostering ownership and empowering teams to iterate and test new ideas long after our sessions end.

Rather than pouring resources into disconnected development cycles, this approach enables clients to actively shape their software in real-time.

I think the best approach is to combine a mix of both synchronous and asynchronous work to really accelerate development. But so far synchronous work is proving to be valuable.

1 comment