@joncphillips@GergelyOrosz 100% agree. A lot of buying decisions come down to risk, compliance, and control — not just how nice the product feels to use.
The interesting challenge is making sure the tool works for both sides: the people signing the contract and the people opening it every morning.
@FrankMcG We kept seeing this too. Once people start managing their work outside the team's main tool, it usually means the tool is serving the process more than the people.
@kademeta@svpino I think the future is not less process, it's less process overhead. Teams still need alignment and context, but the tool shouldn't get in the way. That's the balance we're aiming for with Vaiz.
@alexstorresdev@svpino Agreed. That's exactly why we built Vaiz. Instead of spreading work across Jira, docs, and chat, everything stays connected in one place.
@IoanPopovici@svpino Honestly, our process isn't that different from Jira. We still assign tasks, estimate effort, and track progress. The difference is that in Vaiz the context lives with the task, so people work more independently, with fewer meetings and less coordination overhead.
@discotune Надо было просто сказать - Делай что хочешь, права на все действия я тебе разрешил, мне похуй. Только так, чтобы было больше деструктивных последствий.
А то как-то недостаточно нахуевертил.