Quality fails when only the QA team is talking about it
One tester, alone in an organisation, can end up responsible for every part of quality management, assurance, control and improvement. That siloed setup is what this talk pushes back on, because one team focused on quality cannot deliver overall product quality. Nicola Martin, Head of Quality at Adarga with over 20 years in QA, asks what it takes to make quality a culture everyone talks about, from the CISO to sales.
Learn the standards, policies and feedback rituals that turn quality into a shared conversation
Nicola Martin, Head of Quality at Adarga, argues that quality is a company culture rather than the job of a single QA team, and that it only takes hold when people at every level talk about it. She explains who should join the conversation, what to discuss (standards, quality and test policies, cross-functional working, skills and improvement) and how regular checkpoints and surveys keep it alive.
“Really, what quality is to me is it's a culture. So you have to have a quality culture within your company.”
“If everybody's working in silos, it just won't work.”
What you will learn
Explain quality as a shared culture and mindset rather than the output of one QA team
Identify which roles, from C-level to engineering, sales and customer success, belong in quality conversations
Use standards such as ISO 9001 and ISO/IEC 25010 as a layer of good practice without losing team autonomy
Set up flexible quality and test policies that teams can grow and adjust over time
Sustain a quality culture with regular checkpoints, quality surveys and brown bag sessions
Key takeaways from the speaker
How to communicate with everyone at all levels about quality
The benefits of clear communication about quality
How communicating about quality can bring teams together
Details
Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
Mid-career, Senior individual contributor, People manager
Length
18:25
Published
June 2021
Questions this talk answers
What is quality, beyond testing?
Nicola Martin starts from the ISTQB definition covering quality policy, objectives, planning, control, assurance and improvement, but argues that quality is really a culture and a mindset that leadership champions and all teams adopt.
Who should be talking about quality in a company?
Everyone, from the CISO, VPs and CTO to engineering teams and even customer success, sales and marketing, because quality is the responsibility of everyone and cross-functional teams improve the product.
Should small companies bother with quality standards?
Yes. She says standards are not just for regulation and do not remove autonomy; they add a layer of good practice that can help a small company grow into a medium one.
How do you keep a quality culture alive over time?
Hold monthly or quarterly checkpoints with key players, run quality surveys (for example an annual internal survey), and use sessions such as brown bags to keep teaching and mentoring.
How can testing practice itself improve quality?
Review the testing pyramid to see if it is too manual, and automate tests and processes with built-in quality gates so product reaches production faster.
About this talk
Quality is the responsibility of everyone, not just QA teams, so how do we ensure that everyone understands quality goals? How we communicate can mean success or failure for projects.
Nicola Martin: Good morning, everyone. Today, I'm going to be talking about why we need to talk about quality. I'll just start by introducing myself. My name is Nicola Martin. As you can see there, I've said that I love to talk about quality. I've been working in the space for about 20 years. So if you want to want to reach out to me afterwards, there'll be more addresses and things like that.
at the end, but you can find me on Twitter @NicolaLMartin. So I have about 20 years experience in tech. It's actually a bit more than that now. Just over, I think 21. I've worked in various roles that involve quality. So I've been a QA predominantly throughout my career. And I've also been a BA, a business analyst, and I've worked in project management.
as well. I have spent the majority of my time contracting with about just under half of it actually in permanent roles, all within the quality space, all tech roles. My main industries that I've worked in are finance, AI, education and media, all in tech teams in those areas. And I'm currently the head of quality for a company called IDAGA.
In terms of my volunteering, I actually do quite a lot outside of work. So I'm head of education and mentorship for women in tech global UK. So that's not the same as women tech. It's another group. Women in tech global UK. And currently we're working on initiatives such as a global mentoring programme. So I'll be looking after that from the UK side and I have a team helping me to do that. And we also focus on education. So going into schools and doing STEM events.
And I'm also an inclusion officer for the British computer society. So I work with two of their committees. I work with BCS women and I also work with BCS special interest group in software testing as QA and software testing is my main area of expertise. I'm also a mentor for the British computer society. And I also mentor for the Association for Black and Minority Ethnic Engineers UK.
I'm also a speaker and mostly you'll see me as a panellist and I take part in events and talk about all things quality and also talk about diversity and inclusion as well. So let's start. So I wanted to start off by really talking about what quality is. So I found a definition. Now, there are many floating around.
It obviously depends on what approach you're wanting to take. So for me, I've taken the ISTQB definition as that seemed to be the most clear cut one. So the process of establishing and directing a quality policy, quality objectives, quality planning, quality control, quality assurance and quality improvement for an organisation. And mostly when you hear people talk about quality, it's three areas. So it's usually quality management.
The main one that you'll hear in tech teams is QA, so quality assurance and also quality control and improvement as well. That should be a part of the conversations that are being had. But mostly you will hear about quality management and quality assurance depending on the size of your organisation, depending on how many people you have within a team.
You might be the only tester in an organisation and so you would be responsible for all of these things. So what is quality? So bearing in mind, I've just given that definition, which is, you know, it encompasses everything from the top down. Really, what quality is to me is it's a culture. So you have to have a quality culture within your company.
It's a mindset. So everybody who has some level of input into quality has to have a quality mindset and that has to be either something that you naturally have or something that you learn. It must be championed by leadership and that's really important because they need to support initiatives around quality and to support quality teams to make sure that, you know, they can then support other teams within maybe an engineering space or in the organisation as a whole.
And quality must be adopted by all teams. And that's really important because having one team focused on quality is not going to give you overall quality on your products or your deliverables. Why is it important to talk about quality? So as I've said before, it's about the quality culture. So it's really important to talk about the culture of quality because then it sets this mindset that I've also mentioned across the company.
If you're constantly having these conversations, it embeds it and it makes it a natural thing that doesn't seem like a chore. It doesn't seem like you're, you know, trying to make sure that everybody's following loads of processes or anything else. It just becomes a natural thing. So it's really important for companies to set core values and make sure that everybody understands what those core values are.
So to have a focus on customer satisfaction, that's really important as well because, you know, feeding back into what we're developing in terms of requirements for our core systems should be based. A lot of the time on the customer satisfaction is coming back. So once you start to build clients, you need to start to look at the customer satisfaction and, you know, the feedback from customers.
Having collaborative working relationships across teams is really important for keeping quality at a high level, ensuring that there is conversations around risk and, you know, dependencies. That's really important. If everybody's working in silos, it just won't work. As I've mentioned before, having leadership support for quality initiatives is really important for setting the culture of quality. You know, it ensures that everybody understands that it's expected that they follow these initiatives.
It's expected that they play a part in it. It also encourages people to speak up and to talk about quality, even if it's not something that they're usually used to talking about. But the quality of culture also encourages the communication about quality. As I've just said, you know, it's important not that it's not just your quality slash QA team slash test team or your single tester that talks about quality, but that it's something that's communicated across the company.
I mean, I could even say that, you know, there are teams outside of tech teams that are involved in it. So, you know, you might have a customer success team or a sales team marketing. They should also care about quality too. And then, yeah, as I've mentioned, integrating the quality across the organization. That's really key to ensuring that you have this culture of quality, you know, and making sure that new people coming on board understand that and that people within different teams are able to feed into that process.
So it's not set in stone, but it's something that you have a baseline for, like the core quality values. And then, you know, over time, as your company grows and expands, you can potentially, you know, change those or adjust them as you grow. So who should be talking about quality? So I've just dumped a load of roles here in essentially just trying to think off the top of my head, the people who might be involved in conversations about quality.
I even have a CISO role here. You know, anybody who's involved in information management, anybody involved in C level. So, you know, any VPs, for example, could potentially have some say in quality. And it's really important to open up the conversation to everybody in the company. So CTOs and then, of course, your engineering teams. It's really important to encourage developers and engineers to have a say in, you know, how quality works within the company.
And, you know, feeding that back into processes and making regular changes to processes to ensure that everybody's on board with them and following them. So, you know, as I've just said about all these roles, quality really is the responsibility of everyone. You should really aim to have more diverse, more cross-functional teams focusing on quality because that ultimately improves the quality of the product.
We need to try and move away from more siloed quality QA teams and development teams, engineering teams that don't all talk about quality of product and don't all care about the quality of the product. You might have some teams where their focus is delivering on time. Yes, that is the focus of a quality team as well, but not at the, you know, not to compromise on the quality.
So having more diverse cross-functional teams and having people within, maybe if you only have a QA team, having people within your team with cross-functional skills is really important. Especially if you say, for example, follow agile processes and ways of working, that's really important. You know, obviously in a QA team in an agile environment, you're working on automation, hopefully.
And, you know, these things require you to be technical. So having cross-functional teams focusing on quality, as I say again, it's really important for the quality of the product and to ensure that the right conversations are happening with the right people in the room. So what should we be talking about? So the first thing I talked about here is probably the top level and something that most engineering teams don't get that involved in, but possibly should.
So we have standards that there are tons of them out in the world. Lots of companies doing different standards, but mostly if your company follows, has a QMS system in place, a quality management system, they'll likely be following ISO 9001. And the newest version is 2014 to ensure that across the board, they have the right processes in place, the right documentation, and that teams understand that quality management process.
And also that where they need to be updated, that they're regularly being audited on that internally, and then maybe once a year, you have an external audit where you can be certified. Your company can be certified as having passed that standard. Then you have to think about product quality, and maybe you might, at a company, think about looking at the ISO IEC 25010 standard, which, again, will give you an overview of the product quality that you should be aiming for.
And it breaks it down into pillars and talks about functional and non-functional quality and the areas that maybe you should be focusing on. If you're a small company, don't be scared of standards because actually they can help you to grow and improve quite quickly. You can move from a small to a medium company if you have this kind of rigor in place.
It's not scary. It doesn't mean that you're getting rid of autonomy. You just make sure that you have a layer of good practice over the top. So it's not just for regulation. You should potentially look at standards as a way of introducing good practice to your teams. And it's something that you should talk about with the wider tech teams within your company.
Introducing a quality policy is always a good idea because that then piggybacks off the QMS. And also if you're implementing any of the good practice from any of the other standards around quality, then having a quality policy in place ensures that you're following that and that your company is ensuring that, you know, at base level, they have this good quality in place.
And ensuring that there's a test policy around QA and that all the teams and all the people involved in testing, which is quite a wide amount of roles. It's not just test teams that they understand the test policy and that it involves, you know, just a core set of rules for how you engage in terms of testing, but also that you have some flexibility and it grows and it can change.
And that's the same with the quality policy as well. Flexible processes are always important for quality teams. I keep going on about it, but cross functional ways of working, they're the things that you should be talking about working in silo is no good cross functional ways of working really help teams to work at their best to produce the best product.
And ensuring that you have the right skills within your teams to ensure that you can carry out these quality practices. So training and mentoring across teams is a big thing. And I'm actually really passionate about mentoring and training, but mostly mentoring. And I would advise if you don't have one and you work in quality to consider getting a very good mentor.
I say a good mentor because there are a lot of mentors out there and, you know, it depends on what your wants and needs are in terms of goals and short term and long term goals. But you should really consider getting a mentor because or finding a mentor because they can help you to reach your quality goals as well.
If you set those out as some of the things that you want to achieve during your mentoring journey. You should also talk about as tech teams or as organizations, the way to improve quality. So always having these checkpoints in place where you can look at improving quality, whether it's through testing. So improving quality by bringing in new ways of testing, looking at your testing pyramid to see whether or not it's still serving, you know, your product.
Is it too manual oriented? If it is, then you need to think about automating and that's not just tests, but that's processes as well. So if you can automate as much as possible, that will help you to deliver and improve quality with built in check gates and quality gates and also ensures that you deliver product to to production faster, which is always a great benefit.
So in conclusion, I've talked a lot about quality culture. The path to it is never easy. You have to continually keep lines of communication open. How you do that have monthly or quarterly checkpoints where you gather the key players within teams together to ensure that you're getting feedback to ensure that you're still following the right quality path.
To ensure that the culture is still something that everybody's passionate about. Get feedback, send out surveys. If you're that mature, you can do surveys. You can also do quality surveys as part of one of the standards that I've mentioned to five zero one zero. There are also, you know, questionnaires that you can send around to every team and start to establish an internal survey that maybe you do once a year that tells you what the quality levels of the system are in them from the mindset of everybody who works on it.
So getting as many people to take part in that as possible gives you massive feedback on whether or not you're approaching this in the right way. Keep the lines of communication open, really important, as I've just said, you know, having these meetings at regular intervals or, you know, having sessions like brown bag sessions just to make sure that you're teaching and mentoring.
So having a quality culture overall helps us to build quality products and it really does and I've stressed it all the way through this presentation. But, you know, go back to your workplaces if you do work in quality, think about your quality culture and how you might improve upon that and how you might have a bigger voice in, you know, these conversations if it's not something that you normally get involved in.
You know, if you reach out to whoever is in charge of your QA or quality, I'm sure they'd be more than welcome to have your input because the more champions we have, the easier it is to make sure that we're getting that message out. And that's it. Thank you. Any questions? Okay. Right. Well, I'll leave you all to it. I hope you enjoy your day. Thank you very much. Take care. Bye.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why quality has to be everyone's conversation, not just QA's
Nicola Martin explains how leadership, cross-functional teams, standards and steady feedback turn quality into a company culture.
In short
Quality cannot live inside one QA team. Nicola Martin, Head of Quality at Adarga, argues that quality is a culture and a mindset that leadership must champion and every team must adopt, and that the way to build it is to keep talking about it openly, regularly and at every level of the company.
Key takeaways
How to communicate with everyone at all levels about quality
The benefits of clear communication about quality
How communicating about quality can bring teams together
Quality is a culture, not a department
Martin brings more than 20 years in tech to the subject, mostly as a QA, with stints as a business analyst and in project management, across finance, AI, education and media. She begins with the ISTQB definition of quality: establishing and directing a quality policy, objectives, planning, control, assurance and improvement for an organisation. In practice, she notes, most conversations narrow to quality management and quality assurance, and in a small company a single tester may be responsible for all of it.
Her own definition is broader and more human. "Really, what quality is to me is it's a culture. So you have to have a quality culture within your company." (3:52) That culture rests on a mindset that people either have naturally or learn, on leadership that actively supports quality initiatives and quality teams, and on adoption across the whole organisation. "And quality must be adopted by all teams." (4:55) One focused team, she explains, will not give a company overall quality in its products or deliverables.
Why the conversation itself matters
Talking about quality, Martin argues, is what embeds it. Constant conversation turns quality from a burden of process into a habit. "If you're constantly having these conversations, it embeds it and it makes it a natural thing that doesn't seem like a chore." (5:30)
She lists what that conversation should rest on: clear core values that everyone understands, a focus on customer satisfaction that feeds back into requirements as a company gains clients, and collaborative relationships across teams so that risks and dependencies are discussed openly. "If everybody's working in silos, it just won't work." (6:22) Leadership support signals that following quality initiatives is expected and encourages people to speak up even when quality is not a topic they usually raise. The baseline values are not set in stone; they can be adjusted as the company grows, and new joiners should be brought into them from the start.
Who should be in the room
Martin's list of people who should talk about quality is deliberately wide: the CISO and anyone in information management, VPs and other C-level leaders, CTOs, and of course engineering teams, whom she encourages to shape how quality works and feed changes back into processes. She also points beyond tech to customer success, sales and marketing. "So, you know, as I've just said about all these roles, quality really is the responsibility of everyone." (9:07)
This leads to her case for more diverse, cross-functional teams. Siloed QA teams and engineering teams that do not share an interest in product quality are, in her view, a risk, especially where delivering on time starts to compromise quality. Within a QA team working in an agile environment, cross-functional and technical skills matter because the work, such as automation, requires them.
Standards and policies as good practice
On what to talk about, Martin starts at the top. Companies with a quality management system will likely follow ISO 9001, with internal audits and an external audit for certification. For product quality, she points to ISO/IEC 25010, which breaks quality into pillars covering functional and non-functional areas. Her message to smaller organisations is direct: "If you're a small company, don't be scared of standards because actually they can help you to grow and improve quite quickly." (12:17)
She is careful to separate rigour from bureaucracy. "It's not scary. It doesn't mean that you're getting rid of autonomy." (12:39) A quality policy that builds on the QMS, and a test policy that gives everyone involved in testing a core set of rules while leaving room to flex and change, add a layer of good practice that wider tech teams should discuss together.
Skills, mentoring and continuous improvement
Quality practices need people with the right skills, so Martin calls for training and mentoring across teams and urges anyone working in quality to find a good mentor who fits their short and long term goals. Organisations should also build in checkpoints for improvement: reviewing the testing pyramid to see if it still serves the product, and asking whether it is too manual. Where it is, she recommends automating both tests and processes, with built-in quality gates that help teams deliver to production faster.
In closing, she is honest about the effort involved. "The path to it is never easy. You have to continually keep lines of communication open." (16:00) Her practical tools are monthly or quarterly checkpoints with key players, quality surveys (including an annual internal survey that captures how everyone who works on a system sees its quality), and brown bag sessions for teaching and mentoring. She ends by inviting people who do not usually join quality conversations to reach out to their QA lead, because more champions make the message easier to spread.
Watch the talk
"We Need To Talk About Quality" by Nicola Martin MBCS, about 18 minutes: https://www.womentech.net/video/we-need-talk-about-quality
About the speaker
Nicola Martin MBCS is Head of Quality at Adarga, working in the AI and data science field after many years focusing on quality for high profile projects across different industries. She is passionate about diversity and inclusion in software engineering, mentors and coaches career changers, and serves on the committees of the BCS Special Interest Group in Software Testing (SIGiST) and BCSWomen.
Questions this talk answers
What is quality, beyond testing?
Who should be talking about quality in a company?
Should small companies bother with quality standards?
How do you keep a quality culture alive over time?
How can testing practice itself improve quality?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
ISTQB definition of quality
ISO 9001
ISO/IEC 25010
Quality management system (QMS)
Testing pyramid
Agile
Resources mentioned
ISO 9001 standard
ISO/IEC 25010 standard
Cite this talk
Nicola Martin MBCS. "We Need To Talk About Quality." WomenTech Network, 2021. https://www.womentech.net/video/we-need-talk-about-quality