Some of the thought leaders in the software testing space don't believe that testers should refer to themselves as QA (aka quality assurance). The reason being because we can't really assure quality, since we don't actually write any of the code, the developers do. What we can do is go looking for risks and problems in the software and raise those to our team, who can, with our input, prioritize and fix them accordingly. I prefer to think QA stands for Question Asker. We are really good at asking questions to obtain more clarity regarding how software should work, what happens if we do this or that, etc. Indeed, whenever we run a test, we are seeking information or at least bringing up topics of discussion among the team. I recently went into one of @Jenna Ostrye 's new communities and just created a Google doc with about 20 questions. The questions don't need to be answered, but can get the wheels turning as some of her prospective members may have those same or similar questions. Also, it may make her consider aspects of her community that she hasn't really considered yet. What I'm trying to do is help her to refine her thinking, by providing an outsiders perspective so that she can anticipate and get ahead of potential questions or issues with her offer, process, etc. I really enjoyed the exercise and didn't even need to use AI to come up with the list. If this is something you'd like for me to do for you, as founding members of Reviews please DM me with a link to your community and email address I can share a Google doc with. This is a great first step for those of you who want to see the insights I can provide you, without committing to a full review at this point! Thanks, Joe

As soon as @Joe DeFilippo opened this group I knew I wanted in! My new communities are not available to the public or even remotely ready yet, but I sent him the invite now anyway for later. Well Joe surprised me today with a very detailed list of questions for my community. See he already had access to my rough draft for the About page and got the basic idea about what I'm doing. So he took the time to go ahead and let me know what he would want to know as a user, which is INCREDIBLY VALUABLE! Like now I can answer those prior to people joining. If you have a Skool community, then send him an invite and your email so that he can do this for you too! It'll spark some creativity too.