#development

I need to write a user story for our development team. The feature is a "password reset" function for our mobile app. Write a clear and concise user story using the standard format: "As a [user type], I want to [goal] so that [benefit]." Then, write a set of specific, testable acceptance criteria for this story.

Debug efficiently with systematic approach. Process: 1. Reproduce the bug consistently. 2. Isolate the problem (binary search through code). 3. Form hypothesis about cause. 4. Test hypothesis (add logging, use debugger). 5. Fix the root cause, not symptoms. 6. Verify fix doesn't break other functionality. 7. Add test to prevent regression. Techniques: rubber duck debugging, print statements, breakpoints, stack traces. Read error messages carefully. Check recent changes (git blame). Search Stack Overflow. Take breaks if stuck. Document solution. Prevention: write tests first, code reviews, static analysis.

Build formal mentorship for skill development. Program structure: Pair senior reps (mentors) with new/struggling reps (mentees). Duration: 6 months. Commitment: 1 hour/week. Mentor selection: top performers, willingness to teach, communication skills. Matching: by skill gap (new rep with veteran), territory (same vertical for relevance), personality (assessment fit). Activities: 1. Call shadowing (mentor observes mentee, provides feedback). 2. Reverse shadowing (mentee watches mentor calls). 3. Role-playing (practice discovery, objection handling). 4. Deal reviews (strategy sessions on active opportunities). 5. Goal setting (monthly targets, skill development areas). 6. Book club (read sales books together). Accountability: shared tracker, manager check-ins, end-of-program presentation. Incentives: mentors get bonus or recognition, priority for promotions. Benefits: faster ramp time (3 months vs 6), higher quota attainment (10-15% lift), retention improvement. Mentee feedback drives mentor improvements.