Why We Consult in Parallel
In the previous chapter, we introduced the "parallel consultation" format, where all seven roles submit their assessments at the same time.
If you do not yet have a clear sense of why we consult in parallel, the format loses much of its meaning. You might reasonably wonder: if we ask all seven roles anyway, does it matter whether we ask them one after another or all at once?
In this chapter, we compare parallel and sequential consultation side by side and explain what goes wrong when you consult sequentially.
What Happens When You Consult Sequentially
Sequential consultation means asking for input one role at a time, in a fixed order. The flow looks like this.
Tech Lead reviews the draft and reports back: "No technical issues." COO then sees that comment before reviewing the operational side. COO says "No issues." QA runs its quality check already knowing that two roles have passed the draft. Brand Voice checks the tone and style after seeing QA's verdict.
What happens in this flow? Each role's assessment influences the one that follows.
After Tech Lead says "No issues," COO tends to approach its review with the assumption that the technical side is already clear — so COO focuses only on operational concerns. A role that has already passed something is implicitly trusted. That is a natural human (and AI) response, but it is also exactly where blind spots grow.
Why Seeing the Previous Assessment Is a Problem
Whether the reviewer is a person or an AI, seeing the context of a prior assessment pulls the current reviewer in that direction. This is called conformity bias (the tendency to unconsciously align with what others have already said).
In group settings, later speakers tend to cluster their opinions around the first speaker's position. Sequential consultation has the same structure. Once an early "looks good" verdict appears, the assessments that follow tend to converge in the same positive direction.
A problem that QA should normally catch becomes harder to surface in a context where two roles have already passed the draft. The implicit message — "the previous two cleared it, so it must be fine" — works against independent judgment.
What Changes When You Consult in Parallel
In parallel consultation, every role sees the same draft at the same time, before anyone else has weighed in.
The draft that Tech Lead reviews and the draft that Brand Voice reviews are identical: the original, with no prior assessment attached.
That is why Tech Lead can say "No technical issues" while Brand Voice, seeing the same draft from an entirely different angle, can independently say "This phrasing does not match the tone of our series." Brand Voice is not pulled by Tech Lead's verdict because Brand Voice never saw it.
A problem that QA missed can also be caught by Researcher approaching the same material from a different direction. Because the seven viewpoints are not contaminated by each other, each role's specialist sensitivity operates at full strength.
Parallel Consultation as a "Blind Spot Detection System"
The strength of parallel consultation is that the reassurance of "someone already approved this" never kicks in.
In sequential consultation, each successive approval makes the next reviewer a little more lenient. By the time a fifth role is evaluating the draft, the fact that four roles have already passed it is a strong bias working in the background.
In parallel consultation, all seven roles evaluate the draft as if seeing it for the first time. That false reassurance never forms. Every role starts from zero, which makes blind spots easier to surface.
The Golden Rule 7+1 we run in this series connects to the idea we laid out in The Audit Is a "Problem-Surfacing Device". The purpose of an audit is to surface problems — not to confirm the absence of them. Parallel consultation is the structural design that maximizes that problem-surfacing capability.
Summary
Sequential consultation passes the draft through roles one at a time, so each earlier assessment influences the ones that follow. The system tends toward conformity, and blind spots form in the gaps.
Parallel consultation has every role assess the draft at the same time, without seeing any prior verdict. Each role's perspective operates without contamination from the others, so we end up with seven genuinely independent viewpoints.
The answer to "why consult in parallel?" is this: so that no role is pulled along by what came before. By keeping the seven perspectives separate, the structure avoids conformity bias (the tendency to drift toward consensus) — which is the built-in weakness of any deliberative body (a group that makes decisions by pooling opinions).