Two questions, four styles
The four-style model comes out of assertiveness training in the 1970s — Robert Alberti and Michael Emmons' work is the usual reference — and it survives because it needs so little to work. Every time you want something from another person, two things are at stake: whether your need actually gets stated, and whether their standing survives the statement.
Say the need and leave them intact, and you are being assertive. Leave the need out to protect them, and you are being passive. Say it at their expense, and it is aggressive. Send it sideways — deniably, so it can be withdrawn if challenged — and it is passive-aggressive. Everything else is detail.
How this differs from your conflict style
These are two different questions and it is worth keeping them apart. Our conflict style quiz asks what you do once a disagreement is already open: whether you push, trade, fold, or leave. This one asks something earlier — how a need gets out of your mouth in the first place, before anyone has disagreed with anything.
Plenty of people are collaborative in an open conflict and passive about ever starting one. That combination is extremely common and it produces a specific pattern: excellent at resolving the arguments that happen, and quietly accumulating everything that never got raised.
Passive-aggressive is not a character defect
It is the result that reads worst, so it deserves a plain explanation. Sideways communication is what happens when a real need meets no route that feels safe to state it. The signal is genuine — you noticed the thing, you registered it accurately, you did not simply absorb it. Only the delivery is broken.
That is why it responds so well to a small change. Sideways signals are deniable, which means the other person either misses them entirely or feels handled; either way you get the friction anyway, without the benefit of having said anything. Taking one thing that is currently going out sideways and saying it plainly, close to when it happened, usually lands far better than expected — because the other person had already noticed something was off and was mostly relieved to learn what.
Assertive is not read the same way from everyone
One honest complication. The same sentence, delivered identically, is heard as clear from some speakers and demanding from others, and the difference tracks gender, seniority, accent and race more than it tracks the words. That is a fact about listeners, not about the speaker — but it is real, and pretending otherwise does not help anyone navigate it.
Two practical consequences. If you get read as aggressive more often than the content warrants, the fix is usually specificity rather than softening: a concrete request about a concrete thing is harder to hear as an attack than a general statement of dissatisfaction. And if you are the listener, it is worth occasionally asking whether the discomfort is about what was said or about who said it.
Where each style gets better
- Passive: practise on something trivial. The boundary script builder writes the first sentence; the trick is to use it somewhere the stakes are low enough that failure costs nothing.
- Aggressive: drop the absolutes and repair the how afterwards, separately from who was right. The apology message helper does the second part.
- Passive-aggressive: pick one sideways signal a week and convert it into a plain sentence, close to the event.
- Assertive: check whether it holds with the two or three people you most fear disappointing. That is usually where the exception lives.
Every one of those improves under the same condition — raising things while they are still small. That is mostly a matter of noticing the gap in time, which is what Endearist is built to do: a local-first personal CRM, on your device, with no account and no feed.