BACM11 — Relate Outcome to Performer

The metamodel does not require Outcomes to be Produced by a Capability. Such Outcomes are used to model events that occur outside the capability map of the business, such a customer requesting to purchase an item the business has. The BACM metamodel does not have a way, other than an annotation, to indicate that the source of an Outcome is a Performer(Customer). An alternative approach would allow the customer to have capabilities that would produce such outcomes, but this would add model complexity with little benefit other than providing a connection between a Customer and an Outcome. Note that if BACM11-22 is adopted, outcomes are used to trigger value streams and such a connection between Customer and Outcome becomes critical.
If such a relation is added to the metamodel, it should have a plausible interpretation when used to link an Outcome to a Performer that is in a Role with the Capability that produces the Outcome.

Add triggers_0, triggers_1 and triggers_2 associations to metamodel

Add a triggers_0 shortcut association from Customer to Outcome.
Add a triggers_1 class association from CustomerJourneyStage to Outcome.
Add a PathSpecification tag: "trigger_0.Outcome.^trigger_1.CustomerJourneyStage.^owns_2.CustomerJourney.^takes.Customer.trigger_0" to triggers_0.
Add a triggers_2 association from Touchpoint to Outcome.
The semantics of these triggers_0 and triggers_1 is that the customer and/or customer journey stage creates an Outcome that is used as the entry criteria for a value stream stage.
Note that outcomes produced by capabilities, processes and value stream stages are experienced by the customer indirectly via touchpoints. The triggers_2 association captures the concept of an outcome that is produced by the customer at a touchpoint. This outcome association does not participate in the trigger_0 and trigger_1 semantics, but represents a customer response to an outcome experienced at a touchpoint.
Updates Customer diagram, ValueStream diagram and ValueFit diagram attached to this proposal.
This proposal relates to BACM11-47 resolving BACM11-15.