TL;DR
Measured against the original experience in moderated usability testing.
SiGREEN is Siemens' open, blockchain-secured network for sharing trusted product carbon footprints across the supply chain.

SiGREEN helps companies create and exchange Product Carbon Footprint (PCF) data across their supply chains. The creation form is where that information enters the network: company details, product data, lifecycle emissions, calculation methodology and verification.
That made the form both a usability problem and a data-integrity problem. Making it easier could not mean removing information required by the reporting standards SiGREEN supports.
reduce the effort of creating a PCF without reducing the quality of the data being submitted?
Goals
The existing PCF flow exposed users to a large number of technical fields and nested substages with little support for understanding what was required. Errors were difficult to trace, terminology frequently pushed users outside the product for help, and the structure treated every section with similar visual weight
I combined existing customer evidence with an audit of the live workflow
Reviewed and synthesised interviews conducted by a dedicated research team, focusing on pain points during PCF creation and data entry.
Walked the complete PCF workflow screen by screen, logging friction, inconsistencies, and error-prone steps.
Conducted interviews with eight existing SiGREEN users (five internal, three from supplier companies) to validate audit findings and uncover additional issues.
Sample report findings from one of the user

Users could enter data without understanding its significance
Technical terminology and unclear field requirements meant people could progress while remaining uncertain about what they were submitting.
Errors were detected, but not recoverable
Users knew something was wrong but struggled to identify which field had caused it or how to return to the right place
The information architecture made progress difficult to judge
A large number of visually similar stages made the form feel longer and left users unsure about what remained
Users could enter data without understanding its significance
Technical terminology and unclear field requirements meant people could progress while remaining uncertain about what they were submitting.
Structured, high-stakes forms that already handle staged, standardized input for patterns worth borrowing and pitfalls worth avoiding.
Catena-X and TfS are particularly relevant because Siemens itself supports those PCF standards
Tax workflows: progressive disclosure and clear review before submission
Catena-X / TfS: alignment between form structure and reporting schema
Existing enterprise flows: preserving context while navigating long multi-stage tasks
Iteration 1 - Flatten the workflow
Reduced nested navigation, but still exposed too much information at once.
Iteration 2 - Progressive stages
Improved orientation, but users still struggled to locate incomplete fields.
Iteration 3 - Hierarchical progress + error states
Made the completion state visible at both the stage and substage level.
The original experience reduced data quality to a percentage without explaining what was driving it. I introduced four readable states โ Excellent, Good, Average and Poor โ with a breakdown of the factors contributing to the rating
In moderated testing with 8 users, participants completed the same PCF task using the original and redesigned workflows.




