Design Requirement
An intuitive user interface, so users should not have to deal with the technical details of blockchain technology when monitoring generation and consumption data or managing their GET and sustainability bonuses.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/ambivalence-trust-loyalty-dr8design-knowledge/ambivalence-trust-loyalty-dr8.mdAn intuitive user interface, so users should not have to deal with the technical details of blockchain technology when monitoring generation and consumption data or managing their GET and sustainability bonuses.
This design requirement 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.
Derived heading context: Addresses
Derived heading context: Source paper
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
3 of 3 concepts · 5 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "DR8 - Intuitive user interface",
"description": "An intuitive user interface, so users should not have to deal with the technical details of blockchain technology when monitoring generation and consumption data or managing their GET and sustainability bonuses.",
"resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
"source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
"label": "DR8",
"tags": [
"ambivalence-trust-loyalty",
"design-requirement",
"energy",
"customer-loyalty",
"trust",
"green-electricity"
]
}