Bring product, engineering, design, and research into one agenda. Huddle summarizes the last seven days of initiative activity, keeps source details one click away, and turns meeting notes into reviewable Initiative Evidence.
Use Huddle when the team needs a shared understanding of what changed across active initiatives without rebuilding the story in slides, chat, Jira, or a separate status document.
Huddle is a meeting surface, not another source of project truth. It reads initiative data and connected evidence, studies, documents, stories, prototypes, and delivery activity. The visible window is always the latest seven days. When nothing new arrived in a lane, Huddle says so and can still show useful prior totals.
The initiative set is yours to curate. Zentrik remembers the selected initiatives for that workspace on the current device until you change them.
The agenda keeps the meeting in order while each initiative explains its latest Discovery, Validation, and Delivery state from connected records.
1. Open Huddle from Initiatives
Open Initiatives → Huddle. The agenda runs across the top, initiative context stays on the left of each item, and three compact lanes explain the latest Discovery, Validation, and Delivery state.
Huddle includes selected initiatives even when they have no recent activity. That makes silence visible instead of silently removing work from the meeting.
2. Build the meeting agenda
Select Add in the Huddle agenda to choose initiatives from the workspace.
Use the selector to:
- search by initiative name, public ID, product, or owner
- apply a saved initiative filter
- narrow by product, lifecycle, owner, priority, or creation date
- show only the initiatives already selected
- select all visible results or clear the selection
Each result includes enough context to distinguish similar initiatives: lifecycle, priority, product, owner, and creation date. Choose Update Huddle when the selection is ready.
To remove an initiative, use its remove control in the agenda and confirm the change. Removing it only changes this Huddle view; it does not delete or modify the initiative.
Search the workspace or use saved and structured filters, then review lifecycle, priority, product, and owner before updating the agenda.
3. Put the initiatives in meeting order
Drag an agenda item by its handle to reorder the meeting. Select an item to move directly to its initiative card. As the team scrolls through the cards, the matching agenda item becomes active and the agenda scrolls when needed to keep it visible.
The short status under each agenda title is a situational summary such as Evidence challenges direction, Negative customer validation, Customer responses unrated, Definition needs decisions, or Delivery is moving. Use it to decide where discussion time belongs; use the initiative card for the supporting context.
4. Read Discovery, Validation, and Delivery
Each initiative uses the same three-lane structure:
- Discovery summarizes evidence and insights linked to the initiative. Its status uses each evidence link’s relationship to the initiative—supporting, qualifying, contradicting, or contextual—rather than treating customer pain as a negative judgment of the initiative. Source reaction remains visible in the details, and the newest evidence appears first.
- Validation summarizes connected Study responses. Direction percentages use collected directional ratings; unanswered or unrated responses are reported separately instead of being assigned a sentiment.
- Delivery explains the current initiative state. During definition it checks the initiative summary, product, owner, planning questions, requirements, user stories, and prototypes. During delivery it can show connected Jira or GitHub state, pull-request activity, and synchronization health.
The lane sentences and counts are deterministic summaries of connected records. Huddle does not invent a next action or turn missing data into a positive or negative result.
5. Inspect the source details before deciding
Use View Discovery details, View Validation details, or View Delivery details to open the supporting sheet.
The detail views preserve links back to the relevant evidence, insight, Study answers, requirements, stories, prototypes, or delivery record. Follow those links when the summary is not enough for a decision. A Study link opens its answers so the team can review the responses behind the validation percentages.
6. Save notes, review decisions, then send them
Select Huddle notes to open the meeting sheet. Capture decisions, follow-ups, risks, and unresolved questions while the team discusses the agenda.
Unsaved writing is kept for the current browser session, so closing and reopening the sheet does not discard the draft. Give the Huddle a recognizable name, then choose Save Huddle. Zentrik first stores the notes and initiative list, then prepares draft decisions as a separate step. The status message tells you whether the Huddle is saving, preparing decisions, ready for review, or sending decisions.
Saving does not create Initiative Evidence. Zentrik routes proposed decisions by initiative and displays every draft in the Huddle sheet. Edit the wording directly in the review queue, or assign the same decision to additional initiatives already in the Huddle. The robot indicator preserves Zentrik's routing rationale; hover it to see why the decision was associated with that initiative. When the list is correct, choose Send decisions. Only that explicit send creates or updates the linked Initiative Evidence for every selected initiative.
The resulting Evidence links back to its source Huddle, and Huddle history links to the Evidence created for each initiative. Sending an updated decision list replaces the Huddle Evidence for that initiative instead of creating duplicate Evidence for the same session.
Huddle names are unique within the workspace history. If you save with a name that already exists, Zentrik asks you to confirm before replacing that Huddle's notes and initiative list. Previously sent Evidence remains linked until you send the newly reviewed decisions.
Name and save the meeting once the discussion is ready. Processed items return as an initiative-grouped review queue, not silent changes.
7. Start a new Huddle or revisit history
Choose New huddle when the next meeting should have its own notes, initiative set, and processed evidence. Unsaved notes must be discarded or saved before the new session starts.
Choose History to review prior Huddles. Each entry keeps the saved name, notes, time, and related initiatives. The current session is marked so the team can distinguish ongoing work from earlier meetings.
Expected result
A useful Huddle has:
- a deliberate initiative agenda in the order the team will discuss it
- clear situational statuses backed by visible source data
- Discovery, Validation, and Delivery summaries for every selected initiative
- direct access to the evidence, answers, artifacts, and delivery records behind the summary
- one named note for the current meeting, with draft persistence during the browser session
- editable draft decisions grouped by initiative before Evidence is created
- two-way links between a saved Huddle and the Initiative Evidence it sent
- a separate saved session only when the team intentionally starts a new Huddle
Troubleshooting
Check these steps against what you see in your workspace. If something differs, note your workspace name and the screen, then contact us.
An initiative is missing from the selector
Clear the search, saved filter, and other selector filters, then confirm the initiative belongs to the current workspace. The main Huddle selection is independent from the filters used in the Initiatives list.
An initiative has no recent changes
Huddle always uses the latest seven days. The initiative remains in the agenda, while each lane distinguishes no recent learning from prior evidence, Study responses, or delivery context.
Validation percentages do not include every response
Direction percentages use responses that contain a directional rating. Open Validation details to review unrated answers and the Study questions separately.
Meeting notes did not create a draft decision
Confirm the note names an initiative and contains a decision, follow-up, risk, or question. Save the Huddle, wait for decision preparation to finish, then review the initiative groups. Evidence is not created until you choose Send decisions.
Continue from here
Related guides
Did this guide answer your question?
Your response helps us prioritize missing or unclear documentation.
Still stuck?
Send your question to Zentrik support. This guide will be included automatically.