Tuesday 18th March, 2014
11:25am to 12:10pm
Once a testing tool is implemented and velocity picks up, the test ideas come quickly. This is great, but the brainstorming process can easily get sidetracked, hijacked, or mired in tactical testing that doesn’t provide much in the way of insights. When test ideas are too complex, too costly or only serve individual or department needs, you have to just say “no”. But saying no is hard. Brooks presents justifications that make it possible to reject an idea while at the same time encouraging focused, testing creativity in the future.
I'm into persuasion, psychology, visual design, data interpretation, and building the perfect company. bio from Twitter
Sign in to add slides, notes or videos to this session