When personas get defined around roles rather than behaviors, they can’t generate the kind of design pressure you’re describing. Blueprint gives teams an early opportunity to pressure-test this — but only if persona variation is being actively used to challenge design decisions, not just document who’s involved.
Couldn’t agree more! Design the persona to fit what they do, not what “roles” they perform. As a former Pega User there was nothing more annoying than trying to figure out which “role” I needed to switch to just to do my job…
Not to mention that Constellation, in Infinity ‘25 does not support the UI Kit “switch portal / switch access group” approach, so you just set yourself up for delivery pain.