The document discusses learning customers' language by understanding their problems, asking questions, and listening to their stories. It recommends asking questions like "What problem are we trying to solve?" and "Why are we doing that right now?". It also suggests using personas, task matrices, mockups, and customer stories to understand needs from the customer perspective in a format of "As a [role] I need to [action] so that [happy result]". Behavior driven development and executable specifications are presented as ways to capture stories and test acceptance. Resources on SpecFlow, StoryQ and examples of personas are provided.

1. Learn Your Customers’ LanguageJohn Smith | Orlando, FL @onefloridacoder | onefloridacoder@live.com

2. The Problem

3. AnswersThink AheadAsk More QuestionsTake the Customer to Dinner

4. new Answers();Don’t Think Ahead SoonerAsk Better QuestionsLook for Better Answers

5. Don’t Think Ahead SoonerUnderstand The Problems

6. Don’t Think Ahead SoonerBlack and White

7. Ask Better Questions“What problem are we trying to solve?”- Scott Densmore“Why are we doing that right now?” - Z

8. Look for Better AnswersListen To Your Customers’ StoriesPlay The Ball Where It Lies

9. Customers’ StoriesPersonasTask Matrices

10. Mockups / Wire Frames

11. One Customer StoryAs a <role>I need to <action>So that <some happy result>

12. Another Story VersionGiven <some condition>When I <action>Then <some result happens>

13. Behavior Driven DevelopmentDemos(d => { d.SpecFlow(); d.StoryQ();});

14. Behavior Driven DevelopmentExecutable Specifications

15. Behavior Driven DevelopmentExecutable SpecificationsAcceptance Testing

16. Questions

17. ResourcesSpecFlow https://github.com/techtalk/SpecFlowhttp://www.specflow.org/StoryQhttp://storyq.codeplex.com/Personashttp://www.rimakuprys.com/Personas_iTunes.pdfhttp://www.slideshare.net/lorielue/personas-in-product-design

18. Learn Your Customers’ LanguageJohn Smith | Orlando, FL @onefloridacoder | onefloridacoder@live.com