- handbook
- Company
- Company
- Operations
- Product
- Development & Design Practices
- Design
- Development
- contributing
- Front End
- How We Work
- Markdown How-To
- packaging
- release
- Releases
- security
- staging
- Using Git
- Website A/B Testing
- Internal Operations
- Legal
- People Ops
- Sales & Marketing
- Marketing
- blog
- Boiler Plate Descriptions
- Content Channels
- Content Types
- HubSpot
- Marketing
- Video
- Webinars
- website
- sales
# Product Demos
Product demos are held internally to rapidly assess the state of a feature set and allow for synchronous validation of feature sets. Each demo is open to the whole company to allow for cross functional learning and development.
A demo consists of a higher level business goal to achieve and is graded against that goal. Once that goal is set, the goal needs to broken down into smaller steps to create a script. For each meeting a participant should be marked as demo leader, going through the steps and try and achieve a successful demo.
The demo itself is a recorded meeting where the demo leader goes through the script. It's anticipated that demos surface friction or fail completely. When problems, challenges, and/or improvement-ideas arise another participant should document these along with the script. When the demo is completed, these tasks are discussed and prioritized.
Afterwards the next demo is scheduled, and the next demo-leader is chosen.