72: How to Know If a Product Is Ready
b'
Derrick set Jan. 21 as the date to start onboarding some pre-order people for Level. He is trying to keep things in perspective when it comes to both positive and negative feedback. So, he is preparing answers to address questions and concerns about the product\\u2019s features and functions, or lack of.
\\n\\nBen\\u2019s thirsty for more feedback, customers, and interaction. Fortunately, overall feedback for Tuple has been strongly positively. However, any negativity can be brutal. It\\u2019s a mental game. So, he tries to not fear feedback or let it derail progress. Instead, he focuses on celebrating successes.
\\n\\nToday\\u2019s Topics Include:
\\n\\n- \\n
- How to know if a product is ready - present it to people \\n
- Level\\u2019s Onboarding Goals: Introduce them to product via a demo/training, get their account created, and set up game plan for the future \\n
- Overcoming hurdles and getting people to do stuff \\n
- Calendly Calls: Preparing for and performing them is more exhaustive than writing code \\n
- Last-minute list of Level features Derrick wants to include and reconcile \\n
- Tag Team Mouse Mode: Hand-off feature change made for Tuple \\n
- Making assumptions, instead of the simplest solution \\n
- Interesting 4G experience onboarding Tuple team member in India \\n
- Ben asks for Derrick\\u2019s forgiveness and understanding for starting a Slack group to get feedback on Tuple \\n
- Enterprise Sales Process and Pricing: Customer easily spends $5,000, but it takes 5 weeks - keep the ball rolling \\n
- Middle-ground Approach: Make Tuple available to those who want it, can have success \\n
Links and resources:
\\n\\n\\n\\nDerrick Reimer Website
\\n\\nDerrick Reimer on Twitter
\\n\\nBen Orenstein Website
\\n\\nBen Orenstein on Twitter
\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n'