What is Quench’s current process for keeping teams aligned when operational changes occur?
I’m particularly interested in understanding:
- How changes are initiated and categorized (e.g., standard vs emergency changes)
- The documentation and approval workflow
- Tools and systems used for coordination (e.g., GitLab, Notion, Slack)
- How cross-functional alignment is ensured (e.g., between Sales, Tech, Product, and Ops)
- Any rituals like syncs, reviews, or retros that reinforce operational clarity
- How teams track and follow up on action items or rollout impact
I’d like a breakdown of both formal change management procedures and day-to-day practices that help ensure transparency, reduce silos, and keep everyone in sync across departments.
