The problem
Not a simple settings page
It started as “Configurator”, but it held so much data and so many processes that it was really a product of its own.
Case study · Climate tech · SaaS module
The settings page that became a product.
My Organization holds the core data every Bharat Carbon product runs on. I designed it to stay simple, even as it grew.
- Client
- Bharat Carbon
- Industry
- Climate tech · Carbon accounting & ESG
- Product
- Shared web module for a SaaS suite
- Timeframe
- 4–6 weeks
- My role
- UX strategy, UX research, wireframing, visual design, prototyping
- Tools
- Figma, FigJam, Phase, Microsoft Teams
- Links
- Read on Medium
01 · The short version
The project in a minute
What I did
Structure first, then screens
Fixed the information architecture, designed a clear navigation, and used side drawers so data entry never loses context.
The result
One source of truth
A central module that every Bharat Carbon product reads from, organised into six clear flows.
4–6weeks from strategy to prototype
6core user flows
5big challenges solved, from IA to user management
1shared module behind every product
02 · Who it's for
Used by the whole organisation
From admins setting up the company to staff adding suppliers, everyone touches this module. It had to work for all of them.
Primary users
Organisation‑wide staff
“Let me set up and update company data without getting lost in it.”The brief in one line, as I framed it
- Clear structureFix the information architecture before anything else.
- Easy navigationAlways know where you are and how to get back.
- Long lists, made calmTables of images, text and labels that stay readable.
- Data entry in contextAdd and edit without leaving the page.
- Simple user managementMany roles and staff, handled without confusion.
03 · How it came together
From a tangle to a system
The hard part wasn't the screens. It was deciding where everything should live.
- 1
Step 1
Untangle
Listed every piece of data and process, then rebuilt the information architecture.
- 2
Step 2
Structure
Navigation for six areas, table patterns and side drawers for data entry.
- 3
Step 3
Polish
Visual design and prototypes for every flow, ready for the product team.
04 · Key decisions
The choices that made it work
Decision 01
Side drawers, not new pages
- Why
- Staff add lots of records in a row. Jumping between pages loses their place.
- What I did
- Forms open in a drawer beside the list, so you can add, check and add again without leaving.
Decision 02
Tables built for long lists
- Why
- Some sections hold never‑ending lists of images, text, labels and linked items.
- What I did
- Clear columns, status labels, search and filters keep even long tables easy to scan.
Decision 03
Navigation that mirrors the company
- Why
- People think about their company by its parts: structure, suppliers, processes, people.
- What I did
- Six areas sit in a fixed side menu, in the same order every time, from organisation to user management.
05 · The screens
Six flows, one source of truth
Is your admin area a maze?
- I bring structure to modules that grew without a plan.
- Tables, forms and navigation that stay calm with lots of data.
- UX strategy as well as screens, so the product scales.
Next case study
Nexapol →
A modern website for a polymers manufacturer.
