Complex ESG data made navigable, collaborative and trackable with 100+ questions handled for monthly and annual reporting.
A single CSO-focused workspace that replaces hundreds of spreadsheets with one collaborative screen, cutting the timeline from weeks to days.
Oren Sustainability Hub's reporting screen gives CSOs and Business Units one workspace to collaborate, capture and disclose 100+ ESG fields. It replaces spreadsheets and calls with collaborative features, an audit trail, and support for both monthly and annual reporting.
The Problem
Sustainability reporting is fragmented, postponed and error-prone. It is spread across thousands of spreadsheets with unclear ownership. Companies need a single sustainability platform to report, track, manage and collaborate with business units in one place.
Oren Sustainability Hub's earlier reporting screen was disjointed, failed key user needs and had an inconsistent interface which compromised usability and efficiency.
“Very fragmented data, we do not know who is doing what”
— User Feedback
“We need the ability to track changes and collaborate”
— User Feedback
Solution Overview
From scattered data to a governed, collaborative flow. Simple to navigate, easy to trust.
Oren Sustainability Hub unifies fragmented ESG work into a single platform where teams capture, review and file 100+ disclosures with clear ownership, guided navigation and a built-in audit trail. No one gets lost in the sustainability maze.
Key Features
Collaborative Workspace
Real-time editing and commenting across teams with role-based permissions.
Audit Trail
Full visibility into who changed what and when, ensuring data integrity.
Status Tracking
Clear question-level status indicators so teams always know where things stand.
My Contribution
End to end design
Process and Complete Solution
Target Users
We narrowed down to three main user groups with needs key to the overall experience.
Sustainability Officer
Oversees the entire reporting process. Needs visibility into progress across all ESG categories and the ability to review and approve submissions.
Reviewer
Reviews and validates data submitted by assignees. Needs clear status indicators and the ability to flag issues or request changes.
Assignee
Responsible for filling in specific ESG data fields. Needs to understand what's expected, see deadlines, and know who to escalate to.
Research Insights
High-level findings that guided the design
Teams lacked visibility into who owned which data points, leading to duplication and missed deadlines.
The review process had no structured workflow. It was entirely ad hoc with no accountability.
Users couldn't tell why certain fields were locked or who had edited them last, creating confusion and friction.
Design Challenge
How might we simplify sustainability reporting, tracking, management and audit for CSOs and their teams by unifying it into a single module that enables easy navigation and efficient, accurate reporting?
Design Requirements
Who is responsible for what should be easy to identify
Who has added what data point and when
Question status clarity. Why am I unable to edit this?
User Flow
Brainstorming and Iterations
Focused MVP
Highlighted specific pain points with a minimal feature set to validate the core reporting workflow.
Refined Design & UX
Incorporated user feedback to improve navigation, status clarity, and the review cycle.
Final Implementation
Full feature set with audit trail, EU compliance tracking, and polished interaction patterns.
Incremental UI/UX Changes from Version 2 to 3
Before
After
What Changed
Improved visual hierarchy, clearer status indicators, and streamlined navigation patterns. The review workflow was simplified to reduce the number of steps required to complete an action.
Final Feature List
Reflections
When the first version of this product was created, it was built quickly to ship to clients. We had little to no time to think about user flows, experience design, or how small details might affect usability. At the time, speed felt like the right call.
Gradually, the cracks became impossible to ignore. Users were frustrated, unhappy, and dropping off. Our own team became the primary users of the product, simply because only they could navigate its complexity. We shipped a second round of changes based on feedback, which improved the flow, but there were still significant gaps in the experience.
In the final version, we focused purely on UI/UX refinements and delivered an output that made the reporting module genuinely usable. This project reinforced a lesson I carry into every design decision: design is often deprioritised when shipping under pressure, but thoughtful design choices are what drive user retention and satisfaction. The frustration from poor usability led to a significant drop in engagement. That cost was far greater than the time it would have taken to get the experience right from the start.