Judy Mosley
Judy Mosley
QA Engineer
She/her
QA Engineer curious about systems and how they work. My experience includes participating in Agile processes, automated testing, and sharing insights. More human than bot. Interests: ☕, 🎧, and 🧶
🎂 MoTaBirthday | July 8, 2023
Open To
Podcasting
Write
Inspired by a wonderful conversation with Judy Mosley during TWiQ, we landed on a disclaimer that we should display on ourselves at all times:
Humans are human and can make mistakes. Please double-...
14 Aug
On this week's Episode 147 of This Week in Quality, the topic of Impostor Syndrome came up, and I said I'd share something I read recently from the "War of Art" by Steven Pressfield. The quote itse...
14 Aug
Being on the job hunt is frustrating. With the role of AI now part of the process, it can feel scary wondering if your resume will be seen at all! Spending months applying and being unsure if anyth...
24 Jul
On the 15th of January 2026 myself and Ujjwal Kumar Singh joined a call and pressed record. We were curious to see what would happen. A few weeks later I’d done the same with Neil Taylor and Clare ...
6 Jul
What if showing up was enough, because the rest is already built for you?
30 Jun
A great conversation on friction, influence and showing up authentically
11 May
A reflective episode on joining new teams, respecting existing quality processes, asking better questions, naming the work we already do, and using community to turn uncertainty into learning.
14 Aug
A 'good problems' episode about production-testing drama, MoTaverse growth, new voices, lifelong learning, and how community conversations help people keep going.
24 Jul
No Shame, No Blame
An approach to raising issues that focuses on surfacing the problem and moving forward, without assigning fault to whoever caused it. So what? Removing blame from the process of reporting issues makes people more willing to speak up quickly and honestly, rather than covering things up out of fear of consequences. Example: A team lead frames bug reports as "here's where we are, what do you want me to do with it," rather than pointing fingers at who introduced the problem. Editorial note: This definition has been inferred from how the term was used in the source material.
MoTivation
A resource available to any person, built up and curated by the people of the MoTaverse. It thrives and expands through actions like writing articles, creating and continuing discussions on The Club, creating moments and memes that share insights, and thanking each other. Its action makes it possible to either give or earn stars.
Riffing
A member of the MoT community writes an article, meme, or memory. Or, maybe they contribute to a talk or take part in This Week in Quality. What they say is absorbed by other members of the community and sparks an idea in someone else. The community member who receives the spark then contributes their own article, talk, or meme. The community member "riffs" on the original idea, expanding the original idea that creates sparks in other members. The conversation not only continues. It expands in new ways and meanings, sparking more conversations. The known boundaries goes as far as the riffs continue, making the stopping point, unknowable. Riffs spark riffs. The ripple effect can only be experienced
Good Question
A spark that ignites in the mind of any person who finds themselves in any situation. The spark tends to lead with curiosity, causing someone to ask for more information, clarification, or meaning. At times, a person can feel a good question coming up before they have words to voice it. Creating space for thoughts and feedback is a great way to allow good questions to bubble up to the surface.I also like Tammy Palazzo’s definition:
“A good question stimulates thought, encourages discussion, and inspires an insightful response. It's a catalyst for learning and a beacon that guides us to the unexplored territories of knowledge.”
Feedback loop
What is a feedback loop?
A feedback loop is the part of a system in which some portion (or all) of the system's output is used as input for future operations. Each feedback loop has a minimum of four stages. During the first stage, input is created. During the second stage, input is captured and stored. During the third stage, input is analyzed and during the fourth stage, the insight gained from analysis is used to make decisions.
Comments
(49)
Thank you to the MoTaverse Community
Congratulations Gary! So well deserved. We're rooting for you, and we are proud of you.
What the duck?
They're wonderful.
Here's why I recommend Judy Mosley
Thank you, Simon!
Ady asks the MoTaverse #1
What about something like Testing Thinking? Many times, I think that the way I'm thinking about something is correct. When I have some tools/frameworks to test my thinking, I'm better able to see what I'm missing. It's a fun loop. I test my thinking so that I think more clearly about ways of testing.
Testing meets fun: How we accidentally created the best testing icebreaker using sticky notes and a whiteboard
I would be one of the shy ones, and I appreciate that you suggested giving them a job vs trying to push them into it right away. This sounds like a lot of fun!
Not registered for any upcoming events
Thanks for your contribution
Reality bytes. Meet the teams and terms where they are
Community Star
about 21 hours ago
Learner finished your session
Reality bytes. Meet the teams and terms where they are
Community Star
about 22 hours ago
Thanks for your contribution
Reality bytes. Meet the teams and terms where they are
Community Star
about 22 hours ago
