lyearn • shipped • 2026

Rearchitecting

Rearchitecting

org

org

setup

setup

to

work

at

scale

to

work

at

scale

Turning a rigid, one-dimensional org model into a flexible system that mirrors how companies are actually structured, and making setup something teams could finish in days instead of weeks.

my role

Product Designer. Owned research, end-to-end design and finalised the new architecture concept (detailed out by backend lead).

team

1 Produce Designer (Me), 1 Design Lead, 2 Engineers

type

Full-Time

duration

3 Weeks

The information presented is solely my experience and process. Visuals are recreated for representation purposes. Sensitive details, Final UI Design, and detailed impact metrics are protected under a Non Disclosure Agreement (NDA)

Details and some final designs are protected under a Non Disclosure Agreement (NDA)

impact

59% less time for CSV set-up

75% less support tickets

80% less time for integration

the problem

The old model forces every org into one rigid shape, and most companies couldn't fit into it.

The old model forces every org into one rigid shape, and most companies couldn't fit into it.

The old model an org as a single linear chain: Departments → Tracks → Roles → Employees. It worked for simple teams, but real companies vary in depth and shape, and the chain couldn't bend to fit them.

1

Fixed depth

Smaller teams were able to fit into the old fixed hierarchy. A larger org needed an extra level and there was no way to add it.

2

Inconsistent Duplicate Job Profiles

A role like "Senior Product Designer" sat inside one track, inside one department. If two teams needed the same role, they had to duplicate it, and every duplicate was an inconsistency.

research

Most HR platforms keep org hierarchy and job architecture separate.

Most HR platforms keep org hierarchy and job architecture separate.

I looked at how other platforms handle this. Workday was the benchmark for large, multinational orgs, and newer tools like HiBob and BambooHR for smaller, SMB-focused companies.

1

Legacy Platforms are Rigid

Platforms like Workday have rigid structures and need a lot of manual setup, but the data stays clean at scale, which is what large orgs need most.

2

Modern Platforms are flexible

Platforms like HiBob and BambooHR offer more flexibility in hierarchy depth and how structured job profiles are, built for SMBs who move quickly.

chosen solution

Ditched the combined structure and split it into three

Instead of one chain doing three jobs, I built three independent structures and connected them with a single container called “Position”.

introducing positions

A Position is a seat that ties the three structures

1

Reuse without duplication

One job profile applied across many orgs. Update it once and every seat updates.

2

Vacant Positions

A seat can sit empty when someone leaves — a real, represented vacancy. The old model couldn't show this at all.

3

Headcount Planning

A position can hold more than one seat — the starting point for headcount planning.

org tree

Visualising the org tree

For the org tree, the goal was to visualise the real architecture transparently. People didn’t live inside orgs, they occupied the positions inside the orgs, and the row order reflected that.

impact

Setup got faster and support tickets dropped

59% less time for CSV set-up

75% less support tickets

80% less time for integration

Project Details Protected by NDA

Project Details
Protected by NDA

Get in touch with me for a walkthrough

kartikgoel.design@gmail.com

kartikgoel.design@gmail.com

Thank you for reading!

Thank you for reading!