A whiteboard session is a collaborative exercise for making thinking visible through sketches, solution walkthroughs, code discussion, or system behavior. In remote settings, preserve the objective—demonstrating reasoning—rather than demanding a fully correct, syntactically complete solution. section 5.1.5
Adapt the session to the role, setting, and evidence you need:
- For technical roles, jointly inspect code or use a shared text editor so the participant can comment on or change an approach while explaining it. section 5.1.5
- For noncoding roles, ask the participant to walk through a solution, draw on paper, and hold the result up to the camera; give advance notice about materials. section 5.1.5
- Allow extra time and communicate clearly because technology can slow the interaction. section 5.1.5
- Use whiteboarding conversationally during due diligence to uncover terminology, customer priorities, product behavior, and follow-up questions. section 14.5.2
Tracing a customer-uploaded file
During a product walkthrough, ask where an uploaded file actually goes, then ask whether and where it is backed up. The sketch or code discussion turns a familiar feature into a concrete probe of system behavior. section 14.5.2
