So you've just been made Quality Manager: your first 90 days

Congratulations — and condolences. The Quality Manager role is one of the most consequential and most misunderstood jobs in any organization. You will be expected to own outcomes you do not fully control, defend a system you did not build, and translate between operations, leadership, and external auditors. The first 90 days set the tone for everything that follows.

This is a playbook for that window. It assumes you've inherited an existing QMS — certified or not — and that you want to be effective, not just busy.

Week 1 — Listen, don't legislate

Resist every urge to change anything in week 1. Your job this week is to map the terrain. Sit down with the people who actually run the processes — operators, team leads, customer-facing staff — and ask three questions: What works well? What gets in your way? What do you wish leadership understood?

You will learn more in five conversations on the shop floor or in the support queue than in five days reading procedures. Take notes. Don't promise anything yet.

Documents to read in week 1

• The current quality manual or QMS scope statement
• The last two management review records
• The last internal audit report and the last external audit report
• The open nonconformity and corrective action log
• The current quality objectives and the latest performance against them

These five documents will tell you, honestly, whether the QMS is alive or on life support.

Weeks 2–4 — Diagnose the system

Now you start mapping. The goal of month 1 is to understand the gap between the documented system and the actual one. Walk the main value-creating process end to end, with the people who do the work, and compare what you see to what the procedure says. Some divergence is normal. Large divergence is a finding waiting to happen.

While you walk, look for the early-warning signals: backlogs of overdue corrective actions, KPIs that haven't been updated in months, calibration stickers expired, training records out of date, customer complaints with no closure. These are the things an external auditor will find on day one.

Build your stakeholder map

Identify who your real allies are — usually a sympathetic operations leader, a meticulous team lead, and someone in IT. Identify who is skeptical or actively hostile. The QMS does not survive without political support; pretending otherwise is the most common failure mode of new Quality Managers.

Month 2 — Pick your battles

By the end of month 1 you will have a long list of things that are wrong. You cannot fix them all. Pick three: one quick win that demonstrates competence, one structural fix that earns credibility with leadership, and one relationship to repair.

• Quick win: close out the oldest 10 corrective actions, or rebuild a broken KPI dashboard, or simplify a hated form. Small, visible, fast.
• Structural fix: usually the document control system, the internal audit programme, or the management review cadence. Pick the one that is most broken.
• Relationship: the function that distrusts quality the most. Often engineering or sales. Earn one win with them.

Do not announce a transformation. Do not propose a new ISO standard, a new software system, or a culture programme in month 2. You have not earned the right yet.

Month 3 — Set the agenda

By month 3 you should be ready to present, to leadership, a short and honest assessment: where the QMS is strong, where it is weak, where the risks are, and what you propose to do about it over the next 6–12 months. Frame it in business terms — risk to revenue, risk to customers, risk to certification — not in clause numbers.

If your organization is preparing for the ISO 9001:2026 transition, this is also when to put a credible roadmap on the table. Leadership will respect a Quality Manager who tells them what is coming and what it will cost; they will not respect one who waits until the certification body sends a reminder letter.

Traps to avoid

• Trying to be the auditor and the improver at the same time. Pick one role per conversation.
• Rewriting procedures in month 1. You don't yet know which ones are actually used.
• Becoming the document-control help desk. Push ownership back to process owners.
• Treating every nonconformity as personal. Some processes are broken by design, not by people.
• Promising leadership a frictionless audit. Audits surface problems — that is the point.

What good looks like at day 90

At the 90-day mark, you should have: a clear picture of the system you've inherited, a short list of credible early wins delivered, a working relationship with at least one operational leader, and a written plan for the next year that leadership has seen and broadly agreed with.

You will not have fixed the QMS. You will have earned the right to start.