Design Principle
Customer loyalty programs should not anticipate all services but instead leave room for customers to shape their own portfolio of desired services and functions, giving customers a real sense of choice and agency.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/ambivalence-trust-loyalty-dp1design-knowledge/ambivalence-trust-loyalty-dp1.mdCustomers are most likely to enjoy a sense of choice and real agency when customer loyalty programs do not anticipate all services but instead leave room for customers to shape their own portfolio of desired services and functions.
This design principle is proposed by From ambivalence to trust: Using blockchain in customer loyalty programs (Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker, 2023).
02
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
2 of 2 concepts · 2 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-principle",
"title": "DP1 - Give customers agency",
"description": "Customer loyalty programs should not anticipate all services but instead leave room for customers to shape their own portfolio of desired services and functions, giving customers a real sense of choice and agency.",
"resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
"source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
"label": "DP1",
"tags": [
"ambivalence-trust-loyalty",
"design-principle",
"energy",
"customer-loyalty",
"trust",
"green-electricity"
]
}