Design Objective

DO4 - Efficiency

Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.

Design ObjectiveOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/ambivalence-trust-loyalty-do4

Open concept record

Producer label: DO4
Source paper: From ambivalence to trust: Using blockchain in customer loyalty programs
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/ambivalence-trust-loyalty-do4.md

ambivalence-trust-loyaltycustomer-loyaltydesign-objectiveenergygreen-electricitytrust

Design objective DO4: Efficiency

Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.

Source paper

This design objective is proposed by From ambivalence to trust: Using blockchain in customer loyalty programs (Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker, 2023).

Citations

[1] Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker. From ambivalence to trust: Using blockchain in customer loyalty programs. International Journal of Information Management 68 (2023) 102496. https://doi.org/10.1016/j.ijinfomgt.2022.102496 (opens in a new tab) [2] Source document: From ambivalence to trust - Using blockchain in customer loyalty programs.pdf

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Paper

Paper1

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 (authenticity, customizability, transparency, efficiency, usability and affordability) with associated design requirements.

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
DO4 - Efficiency
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
DO4 - Efficiency
Link label
Design objective DO4: Efficiency
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

Design ObjectiveSeed

DO4 - Efficiency

Bundle identity

Concept ID: design-knowledge/ambivalence-trust-loyalty-do4
Markdown path: design-knowledge/ambivalence-trust-loyalty-do4.md
Producer label: DO4
Native type: design-objective

Markdown summary

Design objective DO4: Efficiency Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability. Source paper This design objective is proposed by From ambivalence to trust: Using blockchain in customer loyalty programs (Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker, 2023). Citations [1] Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker. From ambivalence to trust: Using blockchain in customer loyalty programs. International Journal of Information Management 68 (2023) 102496. https://doi.org/10.1016/j.ijinfomgt.2022.102496 [2]…

Raw metadata

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

Show producer frontmatter

{
  "type": "design-objective",
  "title": "DO4 - Efficiency",
  "description": "Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.",
  "resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
  "source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
  "label": "DO4",
  "tags": [
    "ambivalence-trust-loyalty",
    "design-objective",
    "energy",
    "customer-loyalty",
    "trust",
    "green-electricity"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}

Design Objective

DO4 - Efficiency

Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.

Design ObjectiveOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/ambivalence-trust-loyalty-do4

Open concept record

Producer label: DO4
Source paper: From ambivalence to trust: Using blockchain in customer loyalty programs
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/ambivalence-trust-loyalty-do4.md

ambivalence-trust-loyaltycustomer-loyaltydesign-objectiveenergygreen-electricitytrust

Design objective DO4: Efficiency

Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.

Source paper

This design objective is proposed by From ambivalence to trust: Using blockchain in customer loyalty programs (Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker, 2023).

Citations

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Paper

Paper1

Paper

papers/ambivalence-trust-loyalty

From ambivalence to trust: Using blockchain in customer loyalty programs

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
DO4 - Efficiency
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
DO4 - Efficiency
Link label
Design objective DO4: Efficiency
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

Design ObjectiveSeed

DO4 - Efficiency

Bundle identity

Concept ID: design-knowledge/ambivalence-trust-loyalty-do4
Markdown path: design-knowledge/ambivalence-trust-loyalty-do4.md
Producer label: DO4
Native type: design-objective

Markdown summary

Raw metadata

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

Show producer frontmatter

{
  "type": "design-objective",
  "title": "DO4 - Efficiency",
  "description": "Enable seamless, reliable and scalable information exchange between electricity supplier and customer, minimizing blockchain data processing to retain high uptime and availability.",
  "resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
  "source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
  "label": "DO4",
  "tags": [
    "ambivalence-trust-loyalty",
    "design-objective",
    "energy",
    "customer-loyalty",
    "trust",
    "green-electricity"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}