1 min lesson
A discussion guide
Use "A discussion guide" to explain each part and the role it plays.
Step 1 of 2
A discussion guideUse if the format calls for it
- Why this slice
- The user problem, why this narrow change matters and the evidence behind the choice.
- What you cut
- The scope you dropped to ship the slice, named explicitly with the reason.
- With more time
- The next two slices in priority order, ranked by user value not polish.
- How you'd evaluate it
- The concrete metric or eval that proves it works on real usage, not just your demo input.
- How tools helped
- If assistance was permitted, what you kept, changed or rejected and how you verified the result.
Rehearse these points so you can answer clearly if the onsite discussion asks for them.
Watch out
In this rehearsal, do not spend most of the clock on one hidden layer. Protect a thin working vertical and record the gaps. That gives you something concrete to verify and discuss.
Say it like this
“The brief was open, so I bet on inline review of AI edits because that's where I feel the friction daily. I shipped the accept/reject-per-hunk path end-to-end and stubbed the multi-file rollup. With more time that's next and I'd measure it by how many suggestions get reviewed instead of blanket-accepted.”