Tool Note And Vote

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2abfbb961d31 · 19 Oct 2026Report an issue or request a re-scan

• Publisherproduct-on-purpose GitHub organizationOwner of the repository this skill is read from
• Source folderproduct-on-purpose/pm-skills/skills/tool-note-and-voteThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict2abfbb961d31A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when…

---
name: tool-note-and-vote
description: Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable to Foundation Sprint, Design Sprint, and any participatory decision context.
license: Apache-2.0
metadata:
  classification: tool
  version: "1.0.0"
  updated: 2026-07-04
  category: coordination
  frameworks:
    - character-note-and-vote
  timebox_minutes: 25
  roles:
    - facilitator
    - decider
    - whole-team
  inputs:
    - decision question
    - time allocation
    - voting method
    - optional silent-write prompt
  outputs:
    - silent ideation board
    - vote summary
    - discussion notes
    - decision record
  author: product-on-purpose
---

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

# Note-and-Vote

Run a structured group decision in 20-30 minutes. Silent contribution surfaces independent thinking before group dynamics narrow the option space; explicit Decider supervote closes the choice. Produces a written audit trail of the decision and the alternatives considered.

## When to Use

- A small team (3-10 people) needs to make a fast decision with diverse input.
- Groupthink, status bias, or loudest-voice dominance is a real risk.
- A workshop or meeting moment demands silent ideation before open discussion.
- The decision needs an audit trail (what was considered, why the chosen option won).
- Decision authority is clear (a Decider exists and is in the room or available).
- Used heavily across Foundation Sprint and Design Sprint at decision moments.

## When NOT to Use

- A single person owns the decision and just needs to make it. Use direct judgment.
- Consensus has already emerged organically. The voting overhead adds friction without value.
- The decision is high-stakes enough to warrant longer deliberation (multi-day investigation, written proposals, formal review). Note-and-Vote is a 25-minute tool, not a governance process.
- No Decider is available and the team has no authority to close the decision themselves. Defer until a Decider can attend.

## The Five-Step Protocol

```text
1. Frame the question (1-2 min)
2. Silent ideation (3-7 min, depending on complexity)
3. Silent voting (2-5 min, multi-vote or single-vote)
4. Brief discussion of the vote distribution (5-10 min)
5. Decider supervote (1 min)
```

Total: 12-25 minutes depending on time allocations. Default is 25 minutes for a non-trivial decision.

```mermaid
flowchart TB
    Start([Decision needed])
    Start --> S1[Step 1: Frame the question<br/>1-2 min, spoken]
    S1 --> S2[Step 2: Silent ideation<br/>3-7 min, silent]
    S2 --> S3[Step 3: Silent voting<br/>2-5 min, silent]
    S3 --> S4[Step 4: Brief discussion<br/>5-10 min, spoken]
    S4 --> S5{Step 5: Decider supervote<br/>1 min}
    S5 -->|Most common| TopVote[Pick top vote-getter]
    S5 -->|Sometimes| Override[Pick different option<br/>with stated rationale]
    S5 -->|Rare| Revote[Call re-vote after re-framing]
    TopVote --> Record[Decision recorded in artifact]
    Override --> Record
    Revote --> S2

    style S2 fill:#e1f5ff
    style S3 fill:#e1f5ff
    style S5 fill:#fff4e1
    style Record fill:#e1ffe1
```

Silent steps (blue) protect against anchoring. The Decider supervote (amber) has three legal outcomes; the loop back to silent ideation is the recovery path when the framing was wrong.

### Step 1: Frame the question

Write the decision question on the board, one sentence, unambiguous. Examples:

- "Which target customer segment should our Foundation Sprint commit to for Day 1?"
- "Which solution sketch goes forward into Wednesday's storyboard?"
- "Which sprint question should be the primary scorecard row on Friday?"

Bad framings to avoid:

- Compound questions ("which customer AND problem")
- Yes/no questions (use a different tool)
- Open exploration ("what should we do?")

### Step 2: Silent ideation

Every participant contributes options silently and independently. Sticky notes on a wall, cells in a Miro board, or rows in a shared doc. No talking. No reading others' contributions until the timer ends.

The facilitator MUST enforce silence. Verbal contribution defeats the purpose.

### Step 3: Silent voting

Display all contributions anonymously (or with attribution if the team has agreed). Each participant gets N votes (often 2-3 for a multi-vote round, 1 for a single-vote tiebreaker). Vote silently using dots, stickers, reactions, or numbers. No discussion during voting.

### Step 4: Brief discussion

Surface the top 2-3 vote-getters. Each person who voted for the top options briefly explains why. The facilitator times this (5-10 minutes max). If discussion expands beyond the top options, the facilitator pulls it back.

This is the place where the team can detect surprises ("I didn't realize we were aligned on X") or unsurprises ("we're split between A and B for known reasons"). It is not the place to relitigate the framing.

### Step 5: Decider supervote

The Decider names the chosen option. The Decider may pick the top vote-getter (most common), pick a different option with stated rationale (sometimes), or call for a re-vote after the discussion (rare).

The supervote is the decision. Record it explicitly in the artifact. Do not let the supervote blur into continued discussion; the team needs to see the close.

## Output Structure

The skill produces a single bundled artifact containing:

1. The decision question (verbatim)
2. The silent ideation board (all contributions, timestamped, attribution per team agreement)
3. The vote summary (counts per option, voters per option if attribution agreed)
4. Discussion notes (brief, the rationale that surfaced)
5. The decision record (chosen option + Decider name + Decider rationale if n

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/product-on-purpose/pm-skills
git -C pm-skills checkout 2abfbb961d31

Works in

1. 2026-10-19
   ✓SAFE B 89 / 100

   first audit · source 2abfbb961d31

Questions about Tool Note And Vote

• github.com/product-on-purpose/pm-skills/tree/main/skills/tool-no — the audited source at commit 2abfbb961d31 and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology