Skip to content
Nerdy beta

Share

Add to Space
 Learning Outcomes

A demo that only shows features turns into feature theater. The Share beat shows what the team delivered, what it discovered, and how it is growing.

Overview

Share is a thirty-minute session at the end of each hyper-sprint in the Dojo Loop. The team gathers its stakeholders: customers, funders, and technical, product, and business leadership. If it sounds like a Scrum demo, that’s partly right.

The team does walk through working software, ideally software that has already shipped. Stop there and you reinforce the output-driven, deadline-driven culture the dojo is trying to change. So the team also tells the story of what it learned in discovery that iteration: research findings, user test results, interview notes, journeys, story maps, and prototypes. Good shares put these artifacts into a clear narrative that lines stakeholders up behind the product direction.

Then the team shares its own growth. What new skills are people building? How did it apply feedback from the last share? Don’t showcase features. Showcase the team’s growth.

Writing the story and presenting it to a room is a skill most engineers never get to practice. Share gives them twelve tries in six weeks.

Run an Effective Share

Prepare the team

What are we presenting, and in what order? Does the sequence flow, or does it jump around? What discovery work belongs next to the delivery work? Who presents each part? Who hasn’t presented in a while, or ever?

Set the etiquette

The team presents everything before anyone gives executive notes. Remind the room of one rule: the team makes no commitments in this meeting. “Thank you for your feedback” is a complete answer. The team asks clarifying questions only, with no debating and no negotiating scope. Planning is coming up, and that’s where the feedback gets weighed and possibly incorporated.

The rule matters because the dojo is building autonomous teams. They need to practice making calls from evidence, not agreeing on the spot to whoever ranks highest in the room.

Take notes, everyone

Don’t appoint one scribe. Have everyone capture the feedback that stands out to them. People will interpret the same comment differently, and those differences often start the most useful conversation in the Reflect beat.

Resources