one thing to never forget: testing
you can never test too much.
there’s always a certain level of insecurity when putting your beloved project to the test. perhaps it’s the fear that it may not work; or the fear that you have to go back to the drawing board and start over.
getting feedback can be a devastating experience, since there is always a very real chance that it can fail - that it can fall face flat.
but you know what?
if it’s going to fall face flat, better it happen during a “test” rather than the real thing. if you don’t adequately test your product before release, then your release becomes your “test.” and that’s asking for trouble.
testing is a necessary step to releasing a product. make sure you weave it into your team process. schedule a time for testing on a recurring basis, otherwise it’ll just be relegated to the premise of “we’ll do it it when we feel like it,” which, i guarantee, will never be frequent enough.
do it often. do it extensive. just do it.
frequently test for feedback.
