Training: Quality and Customer Focus

Duration: 30 minutes
Target: All staff (mandatory annual training)
Prerequisites: None

Why This Matters

In 30 seconds: Quality isn't a separate department or a checklist to complete. It's how we work every day. As Swedwise consultants and service providers, you represent our brand directly to customers. When you deliver quality work efficiently, you embody our promise: "Make Time For The Good."

What's in it for you:

• Clearer expectations = less rework and frustration
• Better customer relationships = more enjoyable work
• Process improvements = less time on bureaucracy, more on value
• Shared quality culture = everyone has your back

What's in it for Swedwise:

• Happy customers who renew contracts and refer others
• Competitive advantage in public procurement (ISO 9001 certified)
• Fewer incidents, complaints, and firefighting
• Sustainable growth based on reputation

The Essentials

1. Quality at Swedwise: More Than Compliance

Our Quality Policy (SW-QMS-POL-001) commits us to:

• Customer Focus: Understanding and meeting customer needs
• Continuous Improvement: Learning and getting better every day
• Competence: Having the skills and knowledge to do our jobs well
• Process Approach: Working in defined, measured ways
• Risk-Based Thinking: Preventing problems, not just reacting
• Evidence-Based Decisions: Using data, not guesswork

Connection to "Make Time For The Good":
When we do quality work efficiently the first time, we avoid rework and firefighting. That creates time for what matters: innovation, learning, customer relationships, and work-life balance.

ISO 9001 in plain language:
It's an international standard that proves we have consistent processes for delivering quality. It's not about perfection - it's about having systems that work, measuring them, and improving over time.

2. Understanding Customer Expectations

Who Are Our Customers?

External customers:

• SaaS platform users (Swedwise Communications)
• Organizations we implement solutions for
• Companies we support and maintain systems for
• Anyone who pays for our services

Internal customers:

• Colleagues who depend on your work
• Other departments you support
• Your team members

The golden rule: If someone relies on your output, they're your customer.

What Do Customers Expect?

Explicit requirements (stated clearly):

• Contract terms and deliverables
• Service Level Agreements (SLAs) - response times, uptime targets
• Project scope, budget, and timeline
• Technical specifications

Implicit requirements (assumed but not always stated):

• Professional communication and conduct
• Timely updates on progress or issues
• Solutions that actually solve their problems
• Services that integrate well with their environment
• Consultants who understand their business context

Statutory requirements (legal obligations):

• GDPR and data protection
• Accessibility standards (if applicable)
• Industry regulations (public sector, financial services)

Measuring Customer Satisfaction

We collect feedback through:

1. Surveys (managed by Quality Lead):

   • Annual customer satisfaction survey
   • Post-project surveys
   • Post-support interaction surveys
   • Net Promoter Score (NPS): "How likely are you to recommend Swedwise?"

2. Service Review Meetings (quarterly with key customers):

   • Customer Success Managers discuss performance and gather feedback
   • You may be invited to participate for technical accounts

3. Informal Feedback (daily):

   • Conversations, emails, meetings
   • Your role: Log any significant feedback (positive or negative) with your CSM or Quality Lead

4. Complaints (see Section 5):

   • Formal process for handling dissatisfaction
   • Escalate immediately to CSM or manager

Why it matters to you: Feedback helps identify what's working and where we need support. It's not about blame - it's about making your job easier through better processes.

Feedback Loops

Customer Need → Service Delivery → Customer Feedback → Analysis → Improvement → Better Service

Close the loop: When customers provide feedback and we improve something, we tell them. This builds trust and shows we listen.

3. Process Approach: Working Smarter, Not Harder

What Is a Process?

A process is a repeatable way of doing work that transforms inputs into outputs.

Example - Support Ticket Process:

• Input: Customer reports an issue
• Activities: Log ticket → Classify severity → Assign to specialist → Investigate → Resolve → Verify → Close
• Output: Issue resolved, customer informed, ticket closed
• Controls: SLA response times, escalation rules, resolution documentation

Why Use Processes?

Without processes:

• Everyone reinvents the wheel
• Quality varies depending on who does the work
• Knowledge lives in people's heads (risky when they leave)
• Hard to improve if there's no consistent baseline

With processes:

• Consistent quality regardless of who does the work
• New staff ramp up faster (clear procedures)
• Easier to identify and fix bottlenecks
• Freedom to improve - once the baseline works, optimize it

Key Processes at Swedwise

Process Area	Examples	Your Touchpoint
Service Delivery	Project delivery, SaaS operations, support	You execute these processes
Incident Management	Responding to service disruptions	You report and help resolve incidents
Change Management	Making changes to services without disrupting customers	You request and implement changes
Customer Feedback	Collecting and acting on feedback	You collect informal feedback
Nonconformity & Corrective Action	Fixing problems and preventing recurrence	You report issues and implement fixes

Process Ownership

Each critical process has an owner who is accountable for its performance. Process owners:

• Monitor how the process performs (KPIs)
• Listen to feedback from people doing the work
• Improve the process over time

Your role: If a process isn't working, tell the process owner or your manager. Suggestions for improvement are always welcome.

4. Continuous Improvement: The PDCA Cycle

We use the Plan-Do-Check-Act (PDCA) cycle for improvement:

┌──────────┐
│   PLAN   │ → What are we trying to improve? What actions will we take?
└────┬─────┘
     │
     ▼
┌──────────┐
│    DO    │ → Implement the improvement (small-scale test if possible)
└────┬─────┘
     │
     ▼
┌──────────┐
│  CHECK   │ → Did it work? What did we learn?
└────┬─────┘
     │
     ▼
┌──────────┐
│   ACT    │ → Standardize the improvement; roll it out more widely
└────┬─────┘
     │
     └─────→ (Repeat with next improvement)

Identifying Improvement Opportunities

Where to look:

• Recurring problems or complaints
• Manual work that could be automated
• Waiting time or bottlenecks
• Rework or defects
• Customer suggestions
• Your own frustrations ("There's got to be a better way...")

Examples of improvements:

• Automate repetitive task → Save time
• Clarify confusing procedure → Reduce errors
• Add monitoring alert → Catch issues earlier
• Improve onboarding checklist → New staff productive faster

Suggesting Improvements

You don't need permission to improve your own work (within reason). For small changes in your control, just do it.

For larger changes (affects others, needs resources, changes a procedure):

1. Talk to your manager or process owner - They can help refine the idea
2. Suggest it in team meetings - Collaborate on solutions
3. Log it in the improvement register - Quality Lead tracks improvement initiatives

Culture point: We value learning over perfection. Swedwise operates as a "learning organization" - trying things, reflecting, and adapting is encouraged.

Learning from Mistakes

Fixed mindset: "I failed" → Shame, hide the problem
Growth mindset: "I learned" → Share, prevent recurrence

At Swedwise:

• Mistakes are learning opportunities (if we handle them well)
• Report issues early - it's safer and easier to fix small problems
• No blame culture - we focus on systems, not individuals
• Share lessons learned - help others avoid the same mistake

5. Nonconformity and Corrective Action

What Is a Nonconformity?

A nonconformity is when we fail to meet a requirement.

Examples:

• Missed a project deadline (requirement: deliver on time)
• SaaS service outage exceeded SLA allowance (requirement: 99.9% uptime)
• Customer data accessed without authorization (requirement: access control policy)
• Required training not completed on time (requirement: competence procedure)

Not every mistake is a nonconformity: Typos, minor one-time errors, or isolated slips don't require formal corrective action (though we still fix them).

Reporting Issues and Problems

When to report:

• You notice a nonconformity (anything not meeting requirements)
• A customer complains
• You see a pattern of problems (even if individually minor)
• Something doesn't feel right (trust your instincts)

How to report:

1. Urgent issues (security, safety, critical service failure):
   • Notify your manager and relevant specialist immediately
   • Examples: Data breach, service outage, safety hazard
2. Non-urgent issues:
   • Log in issue tracking system or inform your manager
   • Provide details: What happened, when, where, evidence

What happens next: See SW-IMS-PRO-005 (Nonconformity Procedure):

1. Containment: Fix the immediate problem (correction)
2. Root cause analysis: Why did it happen?
3. Corrective action: Fix the system so it doesn't happen again
4. Verification: Check that it worked

Your role: You may be asked to participate in root cause analysis or implement corrective actions. This is collaborative, not punitive.

Root Cause Analysis Basics

Don't stop at symptoms:

• Symptom: "I forgot to complete the training"
• Root cause: "There's no reminder system for training due dates"

5 Whys technique (ask "why" repeatedly):

• Problem: Customer complained about slow support response
• Why? Ticket wasn't assigned promptly
• Why? Assignment rules unclear for this type of ticket
• Why? New ticket category not added to assignment matrix
• Why? No process to update assignment rules when new services launch
• Root cause: No process linkage between service launches and support procedures

Fix the root cause = prevents recurrence.

Preventing Recurrence

Correction (immediate fix):

• "Complete the overdue training today"
• Fixes the symptom, doesn't prevent it happening again

Corrective action (system fix):

• "Implement automated training reminders 2 weeks before due date"
• Fixes the root cause, prevents recurrence

Both are important. We do correction first (stop the bleeding), then corrective action (prevent future bleeding).

6. Your Role in Quality

Quality is everyone's responsibility, not just management or the Quality Lead.

Following Procedures

Why procedures exist:

• Capture best practices and lessons learned
• Ensure consistent quality
• Meet legal and ISO requirements
• Protect you (and Swedwise) from risks

When procedures feel bureaucratic:

• First, follow the procedure (it's there for a reason)
• Then, suggest improvements if it's inefficient
• Don't skip steps without understanding why they exist (especially security, compliance, or customer-facing steps)

Exceptions: If following a procedure would cause harm or clearly doesn't apply, use your judgment and escalate to your manager.

Documenting Work Appropriately

Why we document:

• Knowledge transfer (others can pick up where you left off)
• Audit trail (prove we did what we said we'd do)
• Troubleshooting (what changed? what was the config?)
• Customer transparency (they can see what we did)

What to document:

• Project deliverables: Designs, configurations, test results, handover notes
• Changes: What changed, why, when, by whom
• Incidents: What happened, how we fixed it, lessons learned
• Customer interactions: Decisions, commitments, important discussions

How to document:

• Use designated systems (project repositories, ticket systems, shared drives)
• Keep it concise and clear (future you will thank you)
• Document as you go, not retroactively (faster and more accurate)

Balance: Document enough to be useful, but don't over-document. If unsure, ask your manager or check the procedure.

Communicating Issues Early

Early warning > Late surprise

Customers (and managers) prefer:

• "We've hit a snag; here's what we're doing about it" (early)
• Over: "The deadline we promised is missed" (late)

When to escalate:

• You're blocked and can't proceed
• A deadline is at risk
• A customer is unhappy or frustrated
• You made a mistake with potential impact
• You don't know how to handle a situation
• Something feels wrong (security, compliance, ethical concern)

How to escalate:

• Urgent: Call or message your manager immediately
• Non-urgent: Email or mention in your next check-in
• Be clear: What's the issue? What's the impact? What do you need?

No penalty for escalating: It's better to raise false alarms than miss real problems.

Taking Pride in Work Quality

Quality work isn't about perfection - it's about:

• Fitness for purpose: Does it meet the customer's need?
• Reliability: Can they depend on it?
• Professionalism: Is it presented well?
• Continuous improvement: Is it better than last time?

Signs of quality work:

• Customer doesn't have to ask for updates (you proactively communicate)
• Handovers are smooth (good documentation)
• Few support tickets after go-live (thorough testing)
• Positive customer feedback
• You'd be proud to put your name on it

Supporting Colleagues

Quality is a team effort:

Knowledge sharing:

• Document solutions to tricky problems
• Share tips in team meetings or internal channels
• Mentor newer colleagues
• Contribute to discipline forums

Collaboration:

• Review colleagues' work (constructive feedback)
• Ask for reviews of your work (catch issues early)
• Help others when they're stuck
• Assume good intent (we're all trying our best)

Giving and receiving feedback:

• Give feedback constructively: Focus on work, not person; suggest solutions
• Receive feedback graciously: It's about improving work, not criticizing you

7. Service Excellence: The Swedwise Standard

Our reputation depends on every customer interaction. Here's what service excellence looks like:

Professional Conduct

Communication:

• Respond promptly (even if just to acknowledge: "Got it, looking into this")
• Write clearly and professionally (proofread customer-facing communication)
• Adapt communication style to audience (technical vs. non-technical)
• Be honest about limitations or delays

Attitude:

• Customer-focused (genuinely interested in solving their problem)
• Solution-oriented (bring options, not just problems)
• Respectful and courteous (even under pressure)
• Represent Swedwise positively (you are the brand when you're on-site)

Boundaries:

• Manage expectations (don't overpromise)
• Say no when necessary (but explain why and offer alternatives)
• Escalate when something is outside your expertise

Timely Delivery

Planning:

• Understand the full scope before committing to timelines
• Build in buffers for unknowns (things always take longer than expected)
• Break big tasks into smaller milestones

Execution:

• Prioritize based on customer impact and deadlines
• Track progress against plan
• Communicate proactively if slipping ("We're 80% done, but need 2 extra days for testing")

Contingency:

• Have backup plans for critical deliverables
• Know when to ask for help (don't wait until the last minute)

Clear Communication

Set expectations:

• When will you deliver? (specific date, not "soon")
• What will be included? (scope)
• What won't be included? (out of scope - manage this early)

Provide updates:

• Regular status updates (weekly for projects, as-needed for support)
• Proactive communication when things change
• Use plain language (avoid jargon, or explain it)

Listen actively:

• Confirm understanding ("So what you need is...")
• Ask clarifying questions
• Read between the lines (what's the real concern?)

Going the Extra Mile

What it means:

• Anticipate needs before the customer asks
• Suggest improvements or optimizations
• Follow up after delivery ("How's it working? Any issues?")
• Share knowledge or best practices
• Fix small issues you notice, even if not in scope

What it doesn't mean:

• Working unsustainable hours
• Doing free work outside the contract (discuss scope changes)
• Sacrificing quality for speed

Balance: Deliver excellence sustainably. "Make Time For The Good" applies to you too.

In Practice: Scenarios

Scenario 1: Customer Complaint

Situation: A customer emails you directly: "The report you delivered is missing data for Q3. This is unacceptable. We needed this for a board meeting tomorrow."

What would you do?

Step 1 - Acknowledge immediately (within 1 business day per SW-QMS-PRO-002):

"Thank you for letting me know. I apologize for the missing data - I understand this is urgent given your board meeting. I'm investigating this now and will get back to you within 2 hours with either the corrected report or a clear plan to resolve this."

Step 2 - Investigate and fix:

• Check: Was Q3 data supposed to be included? (review scope)
• If yes: Fix immediately (correction)
• If data is accessible: Regenerate report with Q3 data
• If not: Escalate to data team or manager

Step 3 - Escalate:

• Notify your manager and Customer Success Manager (this is a complaint)
• Log in complaint register (or ask CSM to log it)

Step 4 - Deliver resolution:

• Provide corrected report ASAP
• Explain what happened and how you've fixed it
• Apologize sincerely

Step 5 - Prevent recurrence (corrective action):

• Root cause: Why was Q3 data missing? (Template error? Data source issue? Misunderstanding of scope?)
• Fix the system: Update report template, clarify data requirements, add validation step

Step 6 - Follow up:

• "The report has been corrected. I've also updated our process to prevent this in the future. Please let me know if you need anything else for your board meeting."

Scenario 2: Process Improvement Idea

Situation: You notice that every time you onboard a new SaaS customer, you have to manually configure 15 settings that are the same for 90% of customers. It takes 2 hours each time. You think: "We should have a default configuration template."

What would you do?

Option A - Just do it (if it's simple and in your control):

• Create the template
• Test it with the next onboarding
• Document it in the procedure
• Tell your team so they can use it too

Option B - Suggest it (if it needs approval or affects others):

1. Document the idea:
   • Current state: 2 hours manual configuration per customer
   • Proposed state: 15-minute template application + 15 minutes customization = 30 minutes
   • Benefit: Save 1.5 hours per customer (×12 customers/year = 18 hours saved annually)
2. Discuss with your manager or process owner:
   • "I have an idea to streamline SaaS onboarding. Can we discuss it?"
3. Implement if approved:
   • Create template
   • Update procedure
   • Train team
4. Measure:
   • Track time savings
   • Share success ("We saved 18 hours last year with the new template")

Result: You've just embodied continuous improvement and "Make Time For The Good."

Scenario 3: Missed Training Deadline

Situation: You receive an automated reminder that your annual Information Security training was due last week. You forgot to complete it because you've been swamped with client work.

What would you do?

Step 1 - Complete it immediately:

• Don't put it off - it's required for a reason (compliance, your safety, customer trust)
• Block 1 hour today to finish it

Step 2 - Inform your manager (optional but recommended):

• "Heads up: I missed the security training deadline due to workload. I'm completing it today. Just wanted you to be aware."

Step 3 - Reflect on root cause:

• Why did this happen? Too busy? Didn't see reminder? Forgot?
• What can you do differently? Set personal reminders? Block time when training is assigned?

Step 4 - Suggest systemic improvement (if it's a common problem):

• If many people miss training deadlines: "Could we get reminders 2 weeks in advance instead of just at due date?"
• Share with Quality Lead or HR

What NOT to do:

• Ignore it (training is tracked; nonconformity will be logged)
• Blame others ("I was too busy with client work so I couldn't do it") - we all have competing priorities
• Fake completion (integrity matters)

Scenario 4: Identifying a Nonconformity

Situation: You're reviewing a colleague's project documentation for handover and notice that security controls required by the customer contract (encryption at rest) were not implemented. The project closed last month.

What would you do?

Step 1 - Verify:

• Double-check the contract requirement
• Confirm with colleague or project manager: Was this intentionally deferred or overlooked?

Step 2 - Report immediately (this is a nonconformity - customer requirement not met):

• Notify your manager and the project manager
• If security-related, notify CISO
• Don't wait - the longer we wait, the bigger the risk

Step 3 - Containment:

• Customer may be at risk right now (unencrypted data)
• Work with team to implement encryption ASAP
• Notify customer (transparency) - they need to know and may need to take action

Step 4 - Log nonconformity:

• Manager or CISO will log as CAR (Corrective Action Request)
• Root cause analysis: Why was this missed? (Checklist incomplete? Review not thorough? Miscommunication?)

Step 5 - Corrective action:

• Update project checklist to include security controls verification
• Add security review gate before project closure
• Retrain team on customer contract requirements

Lessons:

• You did the right thing by reporting - it's uncomfortable but necessary
• No blame - the focus is on fixing the system, not punishing the individual
• Catching it now is better than an audit finding or customer discovering it

Quick Reference

Quality Cheat Sheet

Situation	What To Do	Who To Contact
Customer unhappy	Acknowledge → Investigate → Resolve → Escalate to CSM	Customer Success Manager
Process not working	Follow it (for now) → Suggest improvement	Manager or Process Owner
Made a mistake	Fix it → Report it → Learn from it	Manager
See a nonconformity	Report immediately → Help fix it	Manager, relevant specialist (CISO, Quality Lead)
Deadline at risk	Warn early → Suggest solutions → Escalate if needed	Manager, Customer (via CSM)
Don't know how	Ask → Escalate → Document answer for next time	Manager, Colleague, Process Owner
Customer feedback	Log it → Share with CSM	Customer Success Manager or Quality Lead

PDCA Quick Guide

Plan: What are we trying to improve? What's the goal?
Do: Implement the improvement (test on small scale if possible)
Check: Did it work? What did we learn?
Act: Standardize it (update procedures, train team, roll out widely)

Reporting Channels

Type	Channel	Response Time
Security incident	Manager + CISO (immediately)	Immediate
Service outage	Manager + Service Owner (immediately)	Immediate
Customer complaint	CSM or Manager	Within 1 business day
Nonconformity	Manager or Quality Lead	Within 1 week
Improvement suggestion	Manager or team meeting	Ongoing
General feedback	Quality Lead (email)	Acknowledged within 1 week

Check Your Understanding

Question 1

A customer tells you in passing: "The new feature is great, but the user interface is a bit confusing." What should you do?

A) Ignore it - they said it's great overall
B) Log the feedback and inform the Customer Success Manager
C) Immediately escalate to management as a complaint
D) Fix the UI yourself without telling anyone

Correct Answer: B

Explanation: This is valuable informal feedback (not a complaint, but an improvement opportunity). You should log it and share with the CSM so it can be tracked and considered for future improvements. Option A wastes a learning opportunity. Option C is over-escalation (it's not a complaint). Option D might fix the symptom but doesn't address the root cause or inform the product owner.

---

Question 2

What is the difference between a "correction" and a "corrective action"?

A) They're the same thing
B) Correction fixes the symptom immediately; corrective action fixes the root cause to prevent recurrence
C) Correction is for small issues; corrective action is for big issues
D) Correction is done by staff; corrective action is done by management

Correct Answer: B

Explanation:

• Correction = immediate fix (e.g., "Complete the overdue training today")
• Corrective action = system fix to prevent recurrence (e.g., "Implement automated training reminders")

Both are important. We do correction first (stop the bleeding), then corrective action (prevent future bleeding).

---

Question 3

You're working on a project and realize you'll miss the deadline by 3 days due to unexpected technical issues. What should you do FIRST?

A) Work overtime to try to meet the deadline without telling anyone
B) Inform your manager and the customer (via CSM) immediately with a revised timeline
C) Wait until the deadline passes and then apologize
D) Blame the technical issues and say it wasn't your fault

Correct Answer: B

Explanation: Early warning > Late surprise. Customers and managers prefer to know about delays early so they can adjust their plans. Option A risks burnout and may not work. Option C destroys trust. Option D is unprofessional and doesn't solve the problem. Option B demonstrates professionalism, transparency, and customer focus.

---

Question 4

Which of these is the BEST example of "going the extra mile" for a customer?

A) Working 12-hour days to meet an unrealistic deadline
B) After solving a ticket, proactively sending the customer a tip sheet on avoiding similar issues
C) Doing work outside the contract scope for free without discussing it
D) Responding to emails within 5 minutes even on weekends

Correct Answer: B

Explanation: Going the extra mile means adding value sustainably. Option B helps the customer succeed and prevents future issues (smart service). Options A and D are unsustainable and lead to burnout. Option C creates scope creep and sets bad precedents (discuss scope changes properly).

---

Question 5

What does "Make Time For The Good" mean in the context of quality management?

A) Only work on fun projects, ignore boring compliance work
B) By doing quality work efficiently the first time, we avoid rework and create time for innovation and learning
C) Quality is secondary to speed
D) Customers should accept delays because we're being thorough

Correct Answer: B

Explanation: Quality and efficiency go together. When we do things right the first time (clear processes, good documentation, preventing problems), we avoid firefighting and rework. That creates time for innovation, learning, and better work-life balance. Quality isn't the opposite of speed - poor quality slows us down through rework.

---

Question 6

You notice a colleague repeatedly making the same mistake in their work. What's the BEST approach aligned with our quality culture?

A) Ignore it - it's not your problem
B) Complain about them to your manager
C) Offer to help them and suggest they might benefit from additional training or a procedure update
D) Publicly point out their mistakes in a team meeting

Correct Answer: C

Explanation: We support colleagues and focus on systems, not blame. Option C is constructive, helpful, and may identify a gap in training or procedures (systemic issue). Options A and B don't help anyone. Option D is unprofessional and creates a blame culture.

---

Question 7

According to the PDCA (Plan-Do-Check-Act) cycle, what should you do AFTER implementing an improvement?

A) Move on to the next improvement immediately
B) Check whether it worked and measure the results
C) Tell everyone how great your idea was
D) Document it but don't measure results

Correct Answer: B

Explanation: The "Check" step is critical. We need to verify that improvements actually work and deliver the expected benefits. This is evidence-based decision making. If we skip this step, we don't know if we're improving or just changing. After checking, we "Act" by standardizing successful improvements.

---

Question 8

A customer complaint is logged. What is the PRIMARY goal of the root cause analysis?

A) Find out who is responsible and hold them accountable
B) Write a report for the audit
C) Understand why the problem occurred so we can prevent it from happening again
D) Satisfy the customer by showing we investigated

Correct Answer: C

Explanation: Root cause analysis is about prevention, not blame. We want to fix the system (procedures, training, tools, communication) so the same problem doesn't recur. This benefits customers, staff, and the organization. Option A creates a blame culture (counterproductive). Options B and D miss the point - the goal is improvement, not just documentation.

---

Need Help?

Training and Quality Questions

Quality Lead: [TBD - name and email]

• Questions about this training
• Suggestions for quality improvements
• Feedback on procedures
• Help with customer satisfaction processes

Customer Feedback and Complaints

Customer Success Manager (CSM): [Your assigned CSM]

• Customer complaints or dissatisfaction
• Customer feedback (positive or negative)
• Service review meetings
• Escalations

Nonconformity and Corrective Actions

IMS Owner: [TBD - name and email]

• Reporting nonconformities
• Corrective action requests (CARs)
• Help with root cause analysis
• Process improvement suggestions

Your Manager

• Day-to-day quality questions
• Escalating issues
• Clarifying expectations
• Resource needs for quality work

Resources

• Quality Policy: SW-QMS-POL-001 (what we're committed to)
• Nonconformity Procedure: SW-IMS-PRO-005 (how to report and fix issues)
• Customer Feedback Procedure: SW-QMS-PRO-002 (how we collect and act on feedback)
• Document Portal: [TBD - intranet link to all IMS documents]

---

Final Thoughts

Quality isn't something we do in addition to our work - it's how we do our work.

Remember:

• Customer focus: They're why we're here
• Processes: They're tools, not obstacles (and we can improve them)
• Communication: Early warnings, honesty, transparency
• Improvement: Small steps, continuous learning
• Pride: Take ownership, do work you're proud of
• Support: We're a team - help each other succeed

Thank you for completing this training. Your commitment to quality makes Swedwise a better company and makes everyone's work more rewarding.

Questions or feedback on this training? Contact the Quality Lead at [TBD - email]

---

Document Control

Version	Date	Author	Changes
1.0	[TBD]	Quality Lead	Initial training module creation

Next Review Date: [TBD - annually or when quality policy/procedures updated significantly]