The most useful product feedback describes a real moment. You don’t need technical language or a proposed solution to explain something that got in your way.
Tell us what you were trying to do
Start with the task: publish a schedule, assign work, find a document, or pass a message to the crew. Explain what a successful outcome would have looked like.
Describe what happened instead
Include the steps that led to the problem and whether it happens consistently. If relevant, mention the device and browser you used. Never include passwords, private access links, financial information, or other people’s personal details in a report.
Explain the impact
Did the issue stop your work, create confusion, or simply take more clicks than expected? That context helps the team understand the problem. A clear explanation is more useful than a severity label on its own.
Share what worked, too
Knowing which parts of a workflow were clear helps us avoid changing something useful. If a feature saved you a handoff or made information easier to find, describe the moment.
Interested in contributing? The beta application lets you tell us about your operation, the products you want to explore, and how you’d prefer to share feedback. Applying does not guarantee an invitation.