Shall we ship the new page on Tuesday?
The proposal is ready. Before fixing the date, I would like to know whether anything is still blocking the team.
Choose a signal to see how it works
How it works
How to gather team feedback without a meeting
A short proposal, a shareable link and three signals. MinuteVibe makes views clear during the consultation; you remain responsible for the final decision.
Create a Vibe Recipient previewFictional example · local
Lifetime6 hours
Your signalThis demo creates nothing and sends no signal to the server
Try the format with a colleague, on a decision of your choice
Try with a colleagueAn editable example, nothing sent automatically
From proposal to decision
To consult a remote team, share one understandable proposal and set the period during which each person can respond.
Provide the useful context
The prompt is limited to 60 words. An optional 12-word question clarifies the choice. Share the participant link and keep the control link private.
Read the views received
A blocker requires an objection of up to 20 words. The alignment meter covers the replies received, not the entire team. Silence does not mean agreement.
Conclude without keeping everything
Examine objections, then make the decision. Close the Vibe or let access expire. Record any lasting conclusion and its reasons in your reference tool.
MinuteVibe editorial notesUpdated:
Simple, brief, useful
One decision, five steps
Write less
An impulse of no more than 60 words and, if needed, a 12-word decision question.
Seal locally
The browser encrypts the Vibe before it is sent to the server.
Collect a signal
Recipients answer Aligned, Blocked or Neutral. A short reason is required for Blocked.
Read the team signals
Open your control link to read responses and objections. Refresh to see new signals.
Destroy or let it expire
From the control view, the sender can destroy the Vibe or let it become inaccessible when its lifetime ends.
What the server receives
An encrypted envelope, opaque identifier, lifecycle dates, a reply public key and metadata strictly required for operation.
What the server does not normally receive
The reading key kept in the URL # fragment, decrypted message, decrypted question or objections in clear text.