Suzanne’s career shift from QA engineering to technical program management highlights strategic cross-functional collaboration, metrics-driven quality assurance, and the challenges of influencing product outcomes without formal authority. The discussion addresses AI ethics, the risks of automation, the need for human-centric practices, and the importance of embedding care and transparency into technical workflows.

Into The MoTaverse

Rosie Sherry interviews people involved in testing. Video only interviews. Available on youtube or the homepage. Each episode has a full transcript if you find it on the main site.

• https://www.ministryoftesting.com/podcasts/into-the-motaverse
• https://www.youtube.com/playlist?list=PLbdLjg29s9lCY4hspzj3AGdAL7Vr2ys1B

Episode Details

• Show Notes: https://www.youtube.com/watch?v=O4DHbVNdt68
• Published: 2026-04-22T15:48:45Z
• Duration: 01:00:35
• Author: MoTaverse

Overview

The podcast discusses career transitions in tech, focusing on Suzanne Abdelrahmans evolution from engineering management in testing/quality engineering to technical program management, emphasizing strategic coordination across product ideation, execution, and post-launch evaluation. Her work centers on fostering collaboration between engineering, design, and business teams, with a shift from direct technical leadership to aligning cross-functional priorities. Key themes include the importance of metrics like bug rates and documentation quality in QA, the challenges of influencing product quality without formal authority, and the role of organizational culture in shaping outcomes.

The content explores broader industry challenges, such as the ethical implications of AI adoption, its potential to automate tasks while displacing jobs, and the tension between efficiency and human judgment. Discussions highlight the need for leadership to prioritize ethics, transparency, and community-driven values in AI integration, balancing innovation with safeguards against misinformation and societal risks. There is a recurring emphasis on fostering human-centric practicessuch as care, authenticity, and real-world collaborationover algorithmic or AI-driven solutions, with calls to address the “announcement economy” of unverified promises and prioritize tangible, accountable actions in both professional and digital spaces.

Additionally, the conversation critiques the spread of AI-generated misinformation, the erosion of trust in online content, and the need for communities to prioritize genuine human engagement over superficial or automated interactions. Suzanne reflects on adapting to rapid technological shifts, the importance of continuous learning, and the necessity of embedding care and ethical oversight into technical workflows to ensure sustainable improvements in quality, communication, and team alignment.

What If

• What if you implemented a strict AI-assisted feedback loop for product design with non-engineering stakeholders?
  Move: Introduce AI tools to auto-generate summaries of user feedback, then manually curate and prioritize insights with stakeholders.
  Why now: The text highlights the need for continuous feedback loops and aligning business goals with execution, while acknowledging the complexity of communication with non-technical teams.
  Expected upside: Streamlined decision-making by reducing noise in feedback, ensuring cross-functional alignment, and maintaining human oversight of AI outputs to preserve ethical alignment and product quality.

• What if you shifted your role from direct QA leadership to a program management focus, emphasizing boundary management between development and business teams?
  Move: Transition from managing QA teams to facilitating cross-team sprints with developers, product managers, and stakeholders, using metrics like PRD clarity to drive priorities.
  Why now: The text emphasizes moving from technical leadership to strategic coordination, stressing the importance of boundary management to avoid silos and align ideation with execution.
  Expected upside: Improved product outcomes through collaborative alignment, reduced rework due to clearer requirements, and greater influence on the product lifecycle without relying on formal authority.

• What if you designed a community platform that enforces human-curated content and rejects AI-generated spam?
  Move: Build a platform with strict moderation rules prioritizing real human input, using AI only for spam detection (e.g., flagging low-quality posts), not content creation.
  Why now: The text critiques AI-generated misinformation and emphasizes trust in authentic communities, noting the erosion of trust in digital spaces.
  Expected upside: A loyal, engaged user base that values authenticity over algorithmic curation, reducing misinformation risks and fostering deeper trust in your community.

Takeaway

• Adopt cross-functional strategic coordination: Prioritize aligning product ideation, execution, and post-launch evaluation by collaborating with design, engineering, and business teams, even as a solo operatorfocus on boundary management and interdepartmental flow rather than siloed work.

• Track QA metrics proactively: Implement concrete quality indicators like bug rates, PRD clarity, and documentation effectiveness to self-evaluate product quality, enabling iterative improvements without relying on external QA teams or formal processes.

• Balance AI adoption with human-centric skills: Use AI tools for repetitive tasks but deliberately invest in refining your own critical thinking, creativity, and judgment to avoid dependency on automation and maintain competitive edge in areas AI cannot replicate (e.g., ethical decision-making, original problem-solving).

• Build authentic communities prioritizing human input: Foster engagement through direct, transparent communication with users or stakeholders, avoiding AI-generated content or algorithm-driven interactionsemphasize real feedback loops and human accountability to establish trust and long-term value.

• Leverage documentation and feedback for influence without authority: Drive team alignment and quality improvements by creating clear technical documentation, PRDs, and continuous feedback mechanisms, even without formal leadership rolesthis ensures your contributions shape outcomes through collaboration, not hierarchy.