Evaluation of workaround
| Workaround types | Identified workarounds (action taken) | Evaluation parameters for formalizing workaround actions | Recommendation for blockchain work practice | |||
|---|---|---|---|---|---|---|
| Persistence of workaround (collectively developed or individual adjustments) (Davison et al., 2021) | Explicitness of objects (to achieve a crucial object or an inoperative object) (Davison et al., 2021) | Effectiveness of workaround (effective or ineffective) (Davison et al., 2021) | Expert-assessed viability (author’s addition) | |||
| Data adjustments | 1. Copy-pasting vendor data in the blockchain system | Individual organizational adjustment in the blockchain system | Inoperative for achieving traceability object | Temporarily effective to operate the blockchain system, but an impractical workaround for traceability | No, as it can negatively impact inter-organizational trust | Design and define a blockchain solution to channel user behavior and facilitate automated data capturing |
| Procedural adjustment | 2. Changes in existing information sharing policy | Organizations need to change the information-sharing policy to ensure congruence in traceability information sharing | Crucial object - directly supports the traceability achievement | Effective for required information sharing | Yes, the expert suggested the required level of information sharing | Align the inter-organizational information sharing policy to ensure congruence |
| 3. Changes in product labelling and scanning process | Individual adjustment | Crucial for bringing alignment | Effective | Suggested theoretical integration to identify such an inconsistency | Modify product labelling for compatibility with blockchain systems | |
| Parallel system adjustment | 4. Changing the existing system to complement data standards and allowing data input to the blockchain through temporary ID | Individual adjustment | Crucial object | Effective | Recognizing standards globally and then practicing them within organizations. Also organizations without base-level technology should go for an off-the-shelf solution for a simplified onboarding process and required support. | Assess technical maturity, consistency between internal data standards and blockchain requirements |
| 5. Use of complementary technology for an automated scan and support blockchain system | Individual adjustment | Crucial | Effective | Digitization with existing and complementary technology. | Integrate complementary technologies (e.g., automated scanning) to support and enhance blockchain performance | |
| 6. Augmenting existing process for SKU in blockchain system | Collective | Crucial | Effective | Organizations should work on theoretical integration first to understand alignment with organizational process. | Use theoretical integration to identify misalignments | |
| Role adjustments | 7. Mediating roles | Collective | Crucial | Effective | Organizations without base-level technology should go for off-the-shelve solutions for appropriate blockchain support. | Establish continuous support and regular updates for blockchain systems |
| 8. Advocating roles | Individual | Crucial | Effective | Marketing for blockchain and value communication is suggested to address perceived value discrepancy tensions. Experts further added that introducing a reward system for customers, like flybuys, can increase customer interest in blockchain and impact organizational goodwill. | Market blockchain usage to customers, partners, and stakeholders Develop rewards or incentives tied to blockchain adoption to increase engagement- | |
| 9. Agency roles | Collective | Crucial | Effective | Tiered cost model and incentive for the smallest player in the supply chain and for actors with larger responsibility. | Assess technical maturity to select the appropriate blockchain type (e.g. public, private, hybrid or consortium) Implement a tiered-cost model with incentives for blockchain adoption | |
| Strategic design adjustment | 10. Llimited data elements in blockchain | Collective adjustment | Crucial | Effective | Information needs to be shared at the required level, which will help to address resistance and reduce costs with blockchain operations. | Define data elements to ensure consistent data sharing and the objective of using blockchain |
| 11. Enabling data modification in blockchain system. | Collective | Not very crucial for object | Effective | Alert messages before submitting data to the blockchain will help to avoid submitting personal or additional data to the blockchain and avoid the negative impact of blockchain immutability | Implement alert systems to avoid accidental or incomplete data feeding | |
| Workaround types | Identified workarounds (action taken) | Evaluation parameters for formalizing workaround actions | Recommendation for blockchain work practice | |||
|---|---|---|---|---|---|---|
| Persistence of workaround (collectively developed or individual adjustments) ( | Explicitness of objects (to achieve a crucial object or an inoperative object) ( | Effectiveness of workaround (effective or ineffective) ( | Expert-assessed viability (author’s addition) | |||
| Data adjustments | 1. Copy-pasting vendor data in the blockchain system | Individual organizational adjustment in the blockchain system | Inoperative for achieving traceability object | Temporarily effective to operate the blockchain system, but an impractical workaround for traceability | No, as it can negatively impact inter-organizational trust | Design and define a blockchain solution to channel user behavior and facilitate automated data capturing |
| Procedural adjustment | 2. Changes in existing information sharing policy | Organizations need to change the information-sharing policy to ensure congruence in traceability information sharing | Crucial object - directly supports the traceability achievement | Effective for required information sharing | Yes, the expert suggested the required level of information sharing | Align the inter-organizational information sharing policy to ensure congruence |
| 3. Changes in product labelling and scanning process | Individual adjustment | Crucial for bringing alignment | Effective | Suggested theoretical integration to identify such an inconsistency | Modify product labelling for compatibility with blockchain systems | |
| Parallel system adjustment | 4. Changing the existing system to complement data standards and allowing data input to the blockchain through temporary ID | Individual adjustment | Crucial object | Effective | Recognizing standards globally and then practicing them within organizations. Also organizations without base-level technology should go for an off-the-shelf solution for a simplified onboarding process and required support. | Assess technical maturity, consistency between internal data standards and blockchain requirements |
| 5. Use of complementary technology for an automated scan and support blockchain system | Individual adjustment | Crucial | Effective | Digitization with existing and complementary technology. | Integrate complementary technologies (e.g., automated scanning) to support and enhance blockchain performance | |
| 6. Augmenting existing process for SKU in blockchain system | Collective | Crucial | Effective | Organizations should work on theoretical integration first to understand alignment with organizational process. | Use theoretical integration to identify misalignments | |
| Role adjustments | 7. Mediating roles | Collective | Crucial | Effective | Organizations without base-level technology should go for off-the-shelve solutions for appropriate blockchain support. | Establish continuous support and regular updates for blockchain systems |
| 8. Advocating roles | Individual | Crucial | Effective | Marketing for blockchain and value communication is suggested to address perceived value discrepancy tensions. Experts further added that introducing a reward system for customers, like flybuys, can increase customer interest in blockchain and impact organizational goodwill. | Market blockchain usage to customers, partners, and stakeholders | |
| 9. Agency roles | Collective | Crucial | Effective | Tiered cost model and incentive for the smallest player in the supply chain and for actors with larger responsibility. | Assess technical maturity to select the appropriate blockchain type (e.g. public, private, hybrid or consortium) | |
| Strategic design adjustment | 10. Llimited data elements in blockchain | Collective adjustment | Crucial | Effective | Information needs to be shared at the required level, which will help to address resistance and reduce costs with blockchain operations. | Define data elements to ensure consistent data sharing and the objective of using blockchain |
| 11. Enabling data modification in blockchain system. | Collective | Not very crucial for object | Effective | Alert messages before submitting data to the blockchain will help to avoid submitting personal or additional data to the blockchain and avoid the negative impact of blockchain immutability | Implement alert systems to avoid accidental or incomplete data feeding | |
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.