Before a new product or feature goes into development, you have to gauge whether it will be a worthwhile investment. You don’t want to spend time and money building a product that no one will use. But what’s the best way to do so - and how can you get honest insights from your end users? Join J.B. Siegel, VP of Client Services at Seamgen, as he explores how to use wireframes and clickable prototypes to validate your product. He’ll discuss how user testing allows you to really understand your users - and how to use the insights to inform your product strategy

1. TO USE YOUR COMPUTER'S AUDIO:
When the webinar begins, you will be connected to audio using
your computer's microphone and speakers (VoIP). A headset is
recommended.
TO USE YOUR TELEPHONE:
If you prefer to use your phone, you must select "Use Telephone" after
joining the webinar and call in using the numbers below.
United States: +1 (415) 655-0052
Access Code: 367-355-793
Audio PIN: Shown after joining the webinar
--OR--
With:
J.B. Siegel
How User Acceptance Testing Can
Save You Time and Money
Moderated by:
Brittany Shear
Webinar will begin
11:00 am, PDT

2. Optimizely is the world’s leading experimentation platform, enabling
businesses to deliver continuous experimentation and personalization
across websites, mobile apps and connected devices. Optimizely
enables businesses to experiment deeply into their technology stack
and broadly across the entire customer experience. To learn more,
visit https://www.optimizely.com/

3. Click on the Questions panel to interact with
the presenters
https://www.productmanagementtoday.com/webinar-series/experiment-your-way-to-product-success/
Old Product, New Tricks
Webinar Series

4. Experiment Your Way to Product Success
Webinar Series
About J.B. Siegel
J.B. Siegel, VP of Client Services, has over 30 years experience in marketing, digital design,
and public relations. J.B. works with clients ranging from technology start-ups to established
leaders in their industry helping them to meet and exceed their business goals and
objectives.
About Brittany Shear
Brittany went to Emmanuel College, where she majored in Writing, Editing, and Publishing
and minored in Marketing, Psychology, and Communications. She now works with
Aggregage as an editor and webinar host on sites including CTO Universe, Product
Management Today, and Connected Health Pulse.

6. POLL
Do you work on an in-house development team or with
an agency providing services to a third party?

7. How user testing can
save you time and
money

8. Outline
➔ Two kinds of product owner testing
➔ Usability Testing
◆ Wireframes
◆ Clickable Prototypes
➔ The middle men: development and testing
➔ User Acceptance Testing (UAT)
◆ Developing test cases and edge cases
◆ Testing with the right tools
➔ User testing with an agile development methodology
➔ Regression testing

9. TEST EARLY AND
OFTEN

10. ➔ User/Usability testing
➔ User Acceptance Testing (UAT)
Two types of testing

11. First and foremost:
Test the product to make sure it
works as intended

12. Then...try to break things!

13. ➔ In-house testing
➔ Crowd testing
Testing
Methodologies

14. ➔ Conducted by stakeholders
➔ Select UAT members internally or
beta testers
➔ Self-diagnose: did you build what
you set out to build?
In-House

15. ➔ Third-party users
➔ Validate the product & collect
feedback/ recommendations
Crowd testing

16. Tips to save you time and money

17. POLL
Are you familiar with user acceptance testing tools?

18. Discovery and
strategy phase
➔ Idea Validation
◆ Paper prototypes
● Quick feedback

19. Paper
Prototype

20. Wireframe phase
➔ Usability should be the primary focus
➔ Low-fidelity clickable prototypes
◆ Simple workflows
➔ Robust interactive prototypes
◆ Interdependent inputs, controls,
etc.

21. Wireframe

22. Testing Approach
Based on the product/application you’re
testing, your approach will vary.
➔ Use inexpensive tool for a simple
product with no data entry or
complex workflows
➔ Use a sophisticated tool for a more
robust platform that requires more
complex tools and controls

23. Clickable
Prototypes

24. Complex
Prototypes

25. POLL
Do you create interactive prototypes to test your user
workflows and validate your product?

26. The Middle Men - Developer
Presumably, once the design of the product is designed and specific requirements
written, developers will implement that vision. While doing so, the developer often
performs component testing. The product may then go through integration and/or
system testing. This may be performed by developers, quality assurance, or
stakeholders depending on the product.

27. The "Acceptance testing" level is not
used explicitly to find defects; rather,
some defects may be found while
testing but the higher objective is to
determine its readiness for the
end-user.
User Acceptance
Testing

28. The UAT Process
➔ Planning
➔ Designing Test Cases
➔ Selection of Testing Team
➔ Executing Test Cases &
Documentation
➔ Bug Fixing
➔ Sign-Off

29. ➔ Business Requirements must be available
➔ Application code should be fully developed
➔ Unit Testing, Integration Testing, and System
Testing should be completed
➔ Only cosmetic errors are acceptable before
UAT
Pre Reqs Before UAT
Can Begin

30. When is UAT
Performed?
➔ Typically the last step
◆ Before the product goes live or
before the delivery of the product is
accepted
➔ Performed after the product itself is
thoroughly tested
◆ (i.e after “system testing”).

31. Moderated Testing
➔ List of functional specifications
➔ UAT members are specifically selected
Unmoderated Testing:
➔ Functions like crowd testing
➔ Non-specific instructions
➔ Functional overview
➔ 3rd
party option
➔ Alpha and Beta Testing
External Testing:
Moderated vs. Unmoderated

32. ➔ Does the application crash?
➔ Do all the functions accept the
correct inputs and give the correct
outputs?
➔ Does the application consume only
the minimum amount of resources?
➔ What’s the load time of the
application? “Load testing”
Process Questions

33. ➔ Prioritize test cases based on risk
➔ Higher risks should be performed first
➔ Edge cases performed last
◆ Things users are unlikely to do
Test Cases - Moderated

34. Test
Cases

35. ➔ If you have one product and test on a
weekly basis, you might organize your
test cycles around features
➔ In other circumstances, cycles might be
organized based on test type
◆ Regression vs Performance testing
➔ In Agile Development, the cycles may be
defined for each sprint
Organizing your test
cases

36. POLL
Do you test the application after every
improvement and modification?

37. UAT in an Agile
workflow
➔ Dynamic & continuous
➔ In-House (all parties involved, ie.
client + developer)
➔ Selection of testing team
➔ Sprint demos
➔ Bug fixing
➔ Sign-off

38. ➔ Contact us :)
Tools for Testing

39. UAT includes both
functional and
non-functional testing
Nonfunctional characteristics:
● Performance efficiency
● Compatibility
● Usability
● Reliability
● Security
● Maintainability
● Portability

40. ➔ Make sure new features didn’t
break old ones
➔ Always necessary before
publishing to production given any
feature implementations or bug
fixes of moderate risk
Regression testing

41. ➔ Test early and often
➔ During design phase:
◆ Paper prototypes
◆ Clickable prototypes
➔ Development
◆ User stories
◆ Test cases with edge cases
➔ Test for functional and non-functional
➔ Regression testing
Summary

42. Thank you!

43. Q & A
With:
J.B. Siegel
Moderated by:
Brittany Shear
VP of Client Services, Seamgen
Linkedin page: /in/jbsiegel108/
Twitter ID: @jbsiegel1
Website: seamgen.com
Assistant Editor, Product Management Today
Linkedin page: /in/brittanyshear
Twitter ID: @prodmgmttoday
Website: productmanagementtoday.com
https://www.productmanagementtoday.com/webinar-series/experiment-your-way-to-product-success/
Old Product, New Tricks
Webinar Series