The BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead. Meeting closes the team’s week. It is where the week’s work meets the people who can steer it, and where weekly outcomes become accountable.

Purpose

The team presents the week’s demoable outcomes to the Product Board, and the board responds. This is the moment that turns a week of work into a decision: what was learned, what it means for the initiative, and what should change.

In practice the board does three things here:

  • Gives direct feedback on the work shown.
  • Offers strategic guidance — where the initiative should go next.
  • Makes the unblocking decisions only it can make: budget, priorities, stopping or continuing.

Cadence

60 minutes, weekly, at the end of the team’s week. The week is not tied to Monday–Friday; a team running Wednesday-to-Wednesday holds its Board Meeting on Wednesday.

Attendees

The team and the Product Board. The board functions collectively as a coach — there is no single lead. Each member is available for at least one hour per week of high-quality interaction, and this meeting is where most of it lands.

The Product Board is composed for four distinct contributions:

  • The Specialist — experienced with what the team is building, able to react to the substance of the work.
  • The Critic — challenges the work and keeps it aligned with the company’s values.
  • The Decision Enabler — breaks ties and enables the hard calls: budget, blocking teams, stopping.
  • The Customer Connection — Customer Support, Customer Success, or Sales, bringing the customer’s voice into the room.

Inputs to the meeting are the week’s finished deliverables — design, code, research, data — and the Week Plan they were cut from.

Format

Time-boxed and split roughly in half:

  • ~30 minutes — presentation. The team walks the board through the week’s Product Demo: what was the problem, how it was solved, the data that proves or disproves it.
  • ~30 minutes — discussion and feedback. The board reacts, challenges, and decides.

The equal split is deliberate. It is what keeps the meeting from becoming a top-down review: the team arrives prepared and presents as equals, rather than reacting ad hoc to edicts.

Use a standard format so every week looks the same and nobody re-invents the structure. The session is often recorded and distributed to a wider audience afterwards, so people who could not attend stay in context.

Outputs

  • Feedback on the week’s work.
  • Strategic guidance for the coming weeks.
  • Unblocking decisions — continue, adjust, or stop; budget; priorities.
  • A recording distributed to the wider audience.

Common pitfalls

  • Letting the presentation eat the whole hour, so the board never gets to respond.
  • Showing intentions instead of concluded work — the demo rule still applies here.
  • Treating the board as an audience to perform for rather than a coach to engage.
  • Skipping the discussion half, which is where the accountability actually happens.