Sometimes, a process that looks like it could be a pattern isn’t.

If the same thing happens in the same way every time, and it’s performed by the same Role using the same Props, then what you have isn’t processes that are alike.   You have the same process, repeated exactly as part of several larger processes.

As an example, take dealing with a visitor to your office.   Often this is the responsibility of a particular Role.  They greet the visitor, take their coat, show them to a waiting area and offer them a drink.  It makes no difference why the visitor is here, what happens afterwards or who deals with them next, the process is exactly the same whether the visitor is a client, a prospective employee or a tax inspector.

In this case, it’s better to define the process once, and include it in the Customer Experience Score wherever it occurs.  You could call it ‘Receive Guest’, define it the first time you identify it (for example as part of your ‘Enroll Prospect’ process) then refer to it elsewhere (for example, in Handle Tax Inspection, Recruit Team Member, Hold Social Event).

Identical twins, triplets, even quintuplets are a wonderful thing in humans.  We don’t mind that they make more work because they’ll each grow to be unique human beings.

You don’t want them in your Customer Experience Score though.  The extra work they create there is pointless.