Design Principle

DP2 - Provide customers with sufficient and verifiable information

Customer loyalty programs should proactively ensure that customers can access all required information in an easily verifiable manner, since simple consumption management and reliability control are enormously attractive to customers.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/ambivalence-trust-loyalty-dp2

Open concept record

Producer label: DP2
Source paper: From ambivalence to trust: Using blockchain in customer loyalty programs
Timestamp: 2026-08-05T00:00:00+00:00
Bundle path: design-knowledge/ambivalence-trust-loyalty-dp2.md

ambivalence-trust-loyaltycustomer-loyaltydesign-principleenergygreen-electricitytrust

Design principle DP2: Provide customers with sufficient and verifiable information

Since simple consumption management and reliability control of GETs are enormously attractive, customer loyalty programs should proactively ensure that customers can access all required information in an easily verifiable manner.

Source paper

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).

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Paper

papers/ambivalence-trust-loyalty

From ambivalence to trust: Using blockchain in customer loyalty programs

To reduce customer ambivalence toward green electricity tariffs, the paper develops a blockchain-based loyalty program refined over four iterations, structured around six design objectives (accountability, customizability, simplicity, efficiency, maintainability and affordability) with fourteen underlying design requirements, and derives four generalized design principles (customer agency, verifiable information, appropriate usability, and data access).

ambivalence-trust-loyaltyblockchaincustomer-loyaltydesign-science-research+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

From ambivalence to trust: Using blockchain in customer loyalty programs
Paper
Source
DP2 - Provide customers with sufficient and verifiable information
Target
From ambivalence to trust: Using blockchain in customer loyalty programs
Link label
From ambivalence to trust: Using blockchain in customer loyalty programs
Status
Resolved
Derived heading context: Source paper

Incoming backlinks

From ambivalence to trust: Using blockchain in customer loyalty programs
Paper
Source
From ambivalence to trust: Using blockchain in customer loyalty programs
Target
DP2 - Provide customers with sufficient and verifiable information
Link label
Design principle DP2: Provide customers with sufficient and verifiable information
Status
Resolved
Derived heading context: Design knowledge

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

2 of 2 concepts · 2 directed relationships

Concept types

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP2 - Provide customers with sufficient and verifiable information",
  "description": "Customer loyalty programs should proactively ensure that customers can access all required information in an easily verifiable manner, since simple consumption management and reliability control are enormously attractive to customers.",
  "resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
  "source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
  "label": "DP2",
  "tags": [
    "ambivalence-trust-loyalty",
    "design-principle",
    "energy",
    "customer-loyalty",
    "trust",
    "green-electricity"
  ]
}