Here is our latest pitch, designed to make SpatzAI child’s play to understand. It explains why this problem deserves attention, what we are proposing, how the system works, and what we need now. The aim is simple: make it easy for anyone to quickly grasp the idea and see how teams might start addressing small issues before they turn into bigger conflicts.
When We Confuse Disagreement with Conflict
Disagreements are not conflicts or friction per se. They are differences in perspective that arise from varying interpretations, incomplete information, incentives, or biases. When handled fairly, they can help teams test assumptions and move toward alignment or, where appropriate, consensus or even compromise....
No Surprises: Creating the Catch-All to Team Alignment
I think most team process agreements fail, sparking minor spats, not because people disagree with the goal, but because teams never agree on how breaches of the agreement will be recognised and addressed....
Novelty of SpatzAI and How They Stack Up
The novelty of SpatzAI is not any single distinction, but the integration: precise language, real-time correction, non-punitive accountability, and system-level adjudication tied together in a single workflow.....
Misbehavior Vs Mistakes
I think a large part of why everyday harm persists in organisations is linguistic rather than psychological. We are precise with work outputs, but evasive with conduct. We have no hesitation calling a bad analytical take a mistake. We do not say, “there is a problem with takes, and some poor takes cause issues.” We name the miss because naming enables correction. A mistake is not moral; it simply means the outcome missed the mark.
Psychological Safety: Accountability, Transparency, and the Devil in the Detail
I think far too much is talked around psychological safety—what it is, what it is not—while too few people state, plainly, how they believe it becomes real in someone's day-to-day workplace. These are my tips for how I think it can be achieved:
How to Be More Objective: From Blaming to Accountability in 3 Steps
The original idea was formed in November 2017 and called Object123. The premise was deliberately simple: if someone experiences objectionable behavior, they should be able to object, in three phases, as needed, directly, in real-time and in a structured way. The goal was not to win arguments or assign moral fault, but to interrupt unproductive dynamics while they are still live and correctable.
Psychological Safety and 3 Levels of Accountability: Part II
Psychological safety without accountability is like a soccer referee without a rulebook: the game still “continues,” but nobody knows what counts as a foul, and outcomes drift toward whoever can push hardest without getting called....
SpatzAI Micro-conflict Scenario
At ClearSpan Systems, a routine product review turns into a micro-conflict (spat) when Katya cuts short Keith’s explanation by calling it “basic.” What follows is not a debate about the product, but a live test of how a team handles dismissive communication in real-time, using the Spatz process to move from verbal caution to formal review and resolution....
Psychological Safety and 3 Levels of Accountability
Psychological safety without accountability is like an intersection without traffic lights: everyone can enter, but right-of-way is unclear, and outcomes depend on assertiveness, timing, and luck rather than agreed rules.
Object123 