Home About
Dealer Permissions AI Assistant Analytics and Reporting Restructuring Data Model Finance Calculator Marketplace Checkout
HOME ABOUT

Restructuring Data Model

Evora Global

Role
Product Designer
Year
2022 to 2023
Team
2 UX researchers, 1 product manager, 4 engineers, 2 data architects
Tags
Data architecture, Onboarding, Information architecture, B2B SaaS
An office building with solar panels on the roof.

Context

The platform got portfolios wrong. Funds, properties, buildings, spaces and meters sat in one flat list with implicit relationships, and onboarding captured them in the wrong order. Every screen inherited the same blind spots, and customers kept parallel spreadsheets because they did not trust the product. No interface patch could fix it: the model itself had to change.

Approach

I led the design work with two UX researchers, a product manager, four engineers and two data architects. We rebuilt the entity hierarchy first, then the onboarding that fills it, then the interface on top.

Research with consultants, asset managers and customers showed the same symptom across three roles: the model did not match how they thought about their portfolio. Card sorting and prototype tests on real portfolio shapes took us from three levels to five, adding Space between Building and Meter, with totals rolling up instead of being typed in.

Key decisions

Tables handle the data and a canvas handles the relationships: two views of the same data, with the selection kept between them. Drafts are a first-class state, so partial entities show everywhere, with prompts tied to what a report actually needs. A self-serve Actions panel lets customers retry and diagnose failed meters without raising a ticket. One thing we cut was the six-step setup wizard, which no tester finished; per-entity creation, with drafts by default, replaced it.

Outcome

Customers could see how their portfolio was structured, level by level. Gaps in the data showed up where they sat, by meter and month. Onboarding no longer waited for a complete data set before anything appeared.

Customers stopped relying on a parallel spreadsheet, and the entity tree became the version of the portfolio they trusted. That is what made the analytics layer possible.

Full process

Problem

The data model didn't reflect how real portfolios are organised, and every screen built on top of it inherited the cracks.

Where it hurt

The platform held entities as a flat list joined by name. A single misspelt building name would silently break a fund's reporting roll-up.

Who felt it

ESG managers spent days reconciling the same property across spreadsheets, the platform and their own portfolio records, and asset owners stopped trusting the totals.

The end goal

A data model the platform enforces, an onboarding flow that captures the right thing in the right order, and an interface that shows gaps before they become reporting incidents.

The old entity list: one flat list with no hierarchy.
The inherited model: one flat list, no hierarchy, no roll-up.
The old onboarding steps, stalled part way.
Onboarding as it was: it stalled at the same point every time.

Research

I ran onboarding interviews with ESG managers, asset owners and the consultants who picked up the slack, and walked through the live data of two existing accounts with their teams. Three questions framed the work: what a portfolio looks like in a customer's head, which onboarding steps cause the most rework after go-live, and what proof customers need that the numbers they see are the numbers they own.

What testers told us, sorted by theme

Feedback from the onboarding review sessions went onto a board, grouped by the part of the model it touched. Lifecycle, ownership, utilities and audits came up again and again, and the audits column asked for the one thing the old platform couldn't give: who changed what, and when.

A board of sticky notes grouped under Lifecycle, Utility, Ownership, Contracts, Location, Financials, Audits, Tenancy and Other.
Onboarding review feedback, grouped by theme.

“Every reporting cycle we email the data team three times. Once to confirm the property list, once to confirm the meters, once to ask why the totals are different from last month.”

ESG manager, customer fund

The complaint wasn't really about email. The platform was never the source of truth, so customers kept a parallel spreadsheet they trusted instead.

Where the old onboarding went quiet

Mapping who did what showed several teams and tools between a signed contract and a working account. The customer success manager created users by hand in a legacy platform, assets were uploaded to an instance, and access was switched on with a feature flag outside the product.

A swim-lane diagram across customer, customer success, legacy platform, current platform and a feature flag tool.
Current onboarding: the steps sat across several teams and tools, mostly outside the product.

Discovery

The interview themes were affinity-mapped into four problem categories, and four principles came out the other side. The biggest one was simple: the hierarchy is the product.

Information architecture, rebuilt around the entity tree

Funds contain properties, properties contain buildings, buildings contain spaces, and spaces contain meters. Navigation, permissions and data quality roll-ups all derive from this one tree, so every figure knows where it belongs.

A tree diagram from investment entity to property, building, space and meter, with the details held at each level.
The five-level hierarchy behind every screen.

Scenarios drawn out before any wireframe

Storyboards walked a real portfolio through the platform: a consultant spotting an underperforming building, the property and building managers getting access, and a renovation approved at the end. Drawing them out stopped us designing screens for cases we hadn't thought through.

Nine storyboard panels following a fund, a consultant and building managers through a renovation decision.
Storyboards: from a conversation about ESG positioning to an approved renovation.

The redesigned onboarding

The same journey, now owned by the platform. The customer creates their organisation, uploads assets in bulk, invites people and sets their permissions, with single sign-on where they use it. The hand-offs and the spreadsheet are gone.

A two-lane diagram: the customer and the redesigned platform, from creating an organisation to signing in.
Redesigned onboarding: one lane for the customer, one for the platform.