• "Ensure that teachers have sufficient subject knowledge and pedagogical skills to implement the programme effectively." (This is a core standard that schools are evaluated against during authorization and evaluation).

• School Accreditation and Evaluation: If an IB school consistently placed teachers without subject matter expertise into core subjects, they would likely face significant issues during their IB authorization or evaluation visits. The IB's "Programme standards and practices" would be violated, potentially jeopardizing the school's ability to offer IB programs.

• Professional Standards: Most professional teaching bodies and school administrations would consider it unethical and professionally irresponsible to assign a teacher to a subject for which they have no academic background or training.

• Student Outcomes: Students in IB programs are aiming for rigorous academic outcomes, including university entrance. A teacher lacking fundamental subject knowledge would severely hamper student learning and achievement in internal and external assessments. This would quickly reflect poorly on the school.

• University Admission Requirements: Universities worldwide recognize the IB Diploma. If IB science courses were taught by unqualified individuals, the credibility of the IB Diploma itself would be undermined, and universities might stop recognizing it for science programs.

Never have I seen an org who hires someone to do a job and then does what almost seems as much as possible not to allow that person to succeed in the work they're paying for. Which I've just turned into deeper and sharper curatorial reporting. I was asked by Stuart as some machination of the leadership conversations to provide a document to share with Barry outlining the year start's process behavior jams and demonstrate some of the patterns that are clearly not OKR aligned and go on constantly. I did so and the email we just read from Barry yesterday is completely consistent with everything I've been trying to make visible since the first email I sent him back in Dec '22.

This is about the employee justifiably resigning with immediate effect due to a loss of trust in leadership or unbearable working conditions created by the employer.

When an employee resigns immediately, the RAV typically imposes a waiting period for unemployment benefits, viewing it as a self-inflicted job loss. To avoid this, the employee must prove that their immediate resignation was justified under Article 337 CO. The burden of proof lies heavily on the employee.

Here's the breakdown, focusing on the employee's perspective and how contemporary documents, emails, and internal memoranda can be used to demonstrate leadership failures as "good cause":

Employee's Perspective: Justified Immediate Resignation due to Leadership Issues (Art. 337 CO) and RAV Sanctions Defense

For an employee to successfully argue "good cause" for immediate resignation due to leadership issues, they must demonstrate that the employer's conduct (or lack thereof) made the continuation of the employment relationship objectively unbearable in good faith. This often revolves around a severe breach of the employer's duty of care (Fürsorgepflicht) or trust.

The key is showing that the employee exhausted all reasonable options before resorting to immediate resignation.

Reasonable "Good Cause" Arguments (Employee Side) Revolving Around Leadership Issues:

1. Gross Dishonesty/Fraud by Leadership: Leadership engaging in serious fraudulent or illegal activities that directly impact the employee's professional integrity or expose them to legal risk.

2. Irreparable Breakdown of Trust Due to Specific Leadership Actions: A singular, severe incident or a series of incidents where leadership demonstrates a profound lack of trust, respect, or integrity towards the employee, making further collaboration impossible. This is where "professional integrity protection" comes in strongly.

Demonstrating Leadership Issues with Contemporary Documents/Emails/Memos (Employee's Evidence):

The challenge for the employee is often to collect this evidence while still employed, which can be difficult and risky. However, these documents are crucial for proving to the RAV and potentially a court that the resignation was justified.

1. Emails (Sent by or to the Employee):

   • Formal Complaints/Escalations: Emails from the employee to HR, higher management, or the board detailing the leadership issues, outlining the impact, and requesting intervention. These are critical to show attempts to resolve the situation internally.

     • Example: "Subject: Urgent: Continued Mobbing by [Manager's Name] - Formal Complaint." The email details specific incidents, dates, and witnesses, and the negative impact on the employee's health/work.

   • Evidence of Leadership's Inaction/Tolerance: Email replies (or lack thereof) from HR or management demonstrating their knowledge of the problem but failure to act, or even explicitly tolerating the problematic behavior.

     • Example: An HR email stating, "We understand your concerns, but [problematic manager] is a key asset and we'll monitor the situation," with no subsequent effective action.

   • Evidence of Illegal/Unethical Directives: Emails from leadership instructing the employee to engage in unethical or illegal activities that compromise their professional integrity.

     • Example: An email from a director instructing the employee to falsify financial reports or knowingly mislead clients.

   • Evidence of Unreasonable Workload/Pressure: Emails from leadership assigning unmanageable workloads, setting impossible deadlines, or making derogatory comments about the employee's ability to cope.

1. Internal Memoranda / Memos (If employee has access or can generate them):

   • Employee's Own Memos to File: Written records (memos) prepared by the employee documenting specific incidents, dates, times, and witnesses related to leadership misconduct or inaction. While self-generated, their consistency and detail, especially if corroborated by other evidence, can be powerful.

     • Example: "Memo to File: Incident on [Date] with [Manager's Name] - Refusal to address safety hazard." Details the conversation and lack of follow-up.

   • Formal Grievance Submissions: Copies of formal grievances or internal complaints filed by the employee through official channels, detailing the leadership issues.

   • Minutes of Meetings: If the employee attended meetings where leadership's problematic behavior was evident or discussed, their notes (if formal minutes are not available) can serve as evidence.

   • Policy Documents (Employer's failure to enforce): Copies of company policies (e.g., anti-harassment, code of conduct) that leadership demonstrably failed to uphold or even violated themselves.

1. Other Contemporary Documents (Employee's Perspective):

   • Witness Statements (from supportive colleagues): Signed statements from former or current colleagues who can corroborate the employee's account of leadership misconduct. (This can be difficult to obtain while still employed).

   • Legal Counsel Correspondence: Any correspondence with a union representative or lawyer where the employee sought advice regarding the leadership issues. This demonstrates the seriousness with which the employee viewed the situation.

   • Performance Reviews (Pre-vs. Post-Issues): If the employee's performance reviews were consistently positive before the leadership issues arose and then deteriorated, it can support the argument that the environment, not the employee's competence, caused the problem.

Key Principles for Employee Success with RAV/Courts:

• Exhaustion of Internal Remedies: The employee must generally demonstrate that they attempted to resolve the issues internally through formal complaints to HR, higher management, or trusted supervisors. Immediate resignation without trying to find a solution internally will be viewed skeptically.

• Immediacy of Resignation: Once the situation becomes objectively unbearable and internal remedies have failed or are clearly futile, the employee must resign promptly. Delay can weaken the claim of "unbearableness."

• Severity and Objectivity: The leadership issues must be objectively severe, not merely subjective discomfort. The employee needs to show that any reasonable person in their situation would have found the continuation of employment intolerable.

• Causality: A clear causal link must be established between the leadership's actions/inactions and the employee's inability to continue the employment.

• Documentation is King: For the RAV and any potential court proceedings, well-organized, dated, and specific documentation is paramount. Vague claims without evidence will likely fail.

By meticulously gathering and presenting this kind of evidence, an employee significantly strengthens their argument that their immediate resignation was a necessary act of "professional integrity protection" due to an irreparable loss of trust in leadership, thereby defending against RAV sanctions and establishing a justified termination under Article 337 CO.

Consequences and Remedies for Breach of Contract:

• Specific Performance and Damages: The non-breaching party can generally insist on the fulfillment of the contract and claim compensation for damages caused by the breach. Damages typically aim to put the injured party in the financial position they would have been in if the contract had been properly performed ("positive interest").

• Withdrawal from the Contract: In some cases of default, the non-breaching party may have the right to withdraw from the contract and claim damages, aiming to be put in the position as if they had never entered into the contract ("negative interest").

• Immediate Termination (Summary Dismissal): As mentioned, a sufficiently severe breach can lead to immediate termination without notice. If the termination is found to be unjustified, the breaching party may be liable for salary for the notice period or until the contract would have expired, plus an indemnity of up to six months' salary.

It is critically important that any digital learning program, regardless of the mix of strategies used, is perceived as being fully supported by school leadership in terms of funding, resources, and vision. Without clear and visible leadership support, even the most thoughtfully designed program can fail to achieve its potential. Here's why:

1. Leadership Sets the Tone for the Program's Priority

• Without leadership backing, digital learning programs can be seen as optional or secondary, leading to inconsistent implementation.

2. Confidence in Resource Stability

• Teachers are more likely to embrace a program when they trust that leadership will allocate long-term funding and resources to sustain it.

3. Building a Culture of Trust

• When leadership is transparent about how money and resources are allocated to the program, it fosters trust among staff. Teachers are more willing to try new strategies when they feel supported with the necessary tools and time.

• If resources are spread thin or priorities are unclear, staff may feel frustrated or disempowered, undermining the program.

4. Encouraging Risk-Taking and Innovation

• When staff know leadership supports the program and will back their efforts, they feel safer taking risks and experimenting with new teaching strategies.

• If they perceive a lack of support, teachers may avoid innovation, sticking to familiar methods instead of embracing digital transformation.

5. Program Longevity

• Clear and visible leadership support is key to sustaining a digital learning program over time. Staff are more likely to commit to the program if they see leadership advocating for it to parents, school boards, and the broader community.

• A lack of support often results in programs being abandoned or deprioritized, which damages staff morale and wastes previous investments.

The school had me down as a design and science teacher, when my core role, digital learning coach, which I held longer than anything else, is never mentioned. No wonder….

teams and other stakeholders underpin successful outcomes.

Creating a collaborative project team environment involves multiple contributing factors, such as team agreements, structures, and processes. These factors support a culture that enables individuals to work together and provide synergistic effects from interactions.

▶ Team agreements. Team agreements represent a set of behavioral parameters and

working norms established by the project team and upheld through individual and project

team commitment. The team agreement should be created at the beginning of a project

and will evolve over time as the project team continues to work together and identify

norms and behaviors that are necessary in order to continue to work together successfully.

▶ Organizational structures. Project teams use, tailor, and implement structures that help

coordinate the individual effort associated with project work. Organizational structures are

any arrangement of or relation between the elements of project work and organizational

processes.

These structures can be based on roles, functions, or authority. They can be defined as

being external to the project, tailored to fit the project context, or newly designed to meet

a unique project need. An authority figure may formally impose a structure, or project team

members may contribute to its design in alignment with organizational structures.

Examples of organizational structures that can improve collaboration include, but are not

limited to:

▹ Definitions of roles and responsibilities,

▹ Allocation of employees and vendors into project teams,

▹ Formal committees tasked with a specific objective, and

▹ Standing meetings that regularly review a given topic.

The International School of Zug and Luzern: ISZL markets itself as a “World Class International School” on its website, LinkedIn and numerous online promotional portals, social media channels and dozens of student transportation vans. It makes the claim on its LinkedIn page and other public spaces that “Whether it is in our Primary, Middle or High School, all students are prepared to achieve at their highest level in a happy and friendly environment with the support and encouragement of highly qualified teachers.” 

ISZL’s Director, Barry Dequanne: Barry Dequanne markets himself as the Director of a “world class international school” via an extensive array and network of personal promotional material via social media, educational websites and participation on international committees and boards. 

ISZL’s Middle School Principal, Stuart Byfield. Matt Brady’s line manager #1 responsible for two breaches of contract, a breach of contract @ MS Grade 7 Math and Science in 2021/2022 & breach of contract MS Grade 8 Science in 2024/2025. He is on record declaring in writing his intent to breach Matt Brady’s contract for a third time in the 2025-2026 school year; the key event leading to the voluntary resignation.  

ISZL’s Technology Director, Chris Vincent. Matt Brady’s line manager #2, recently demoted from ISZL’s leadership team effective next school year due in part due to repeated, unaligned behaviors as a leadership team member at ISZL. This demotion was precipitated by a request of Matt Brady by Stuart Byfield to provide documentation of Mr. Vincent’s most recent ethical/professional lapses, which were then provided to the Deputy Director. 

ISZL’s Digital Learning Coach, Matt Brady. Well regarded ISZL staff member with a positive job result at the end of his work as stated by ISZL in the final job reference.