Daily property work
Daily property work
Property managers
Property managers
Find records, update details and follow the progress of a change.
Find records, update details and follow the progress of a change.
PIM App
One place for property information. A clearer path from update to approval.
Enterprise product designLINK LOGISTICS0 → 1 WEB APPLICATIONPORTFOLIO INFORMATION MANAGEMENT
Property information is only useful when people can find it, trust it and keep it up to date.
Property information is only useful when people can find it, trust it and keep it up to date.
I designed PIM from the ground up for Link Logistics, bringing portfolio navigation, property records and approval workflows into one shared workspace. The goal was to help real estate teams move from scattered spreadsheets and email chains to a consistent way of managing property information.
I designed PIM from the ground up for Link Logistics, bringing portfolio navigation, property records and approval workflows into one shared workspace. The goal was to help real estate teams move from scattered spreadsheets and email chains to a consistent way of managing property information.
My role
My role
Sole UX/UI Designer
Sole UX/UI Designer
Scope
Scope
Research & user flows
Interface design
Design system
Research & user flows
Interface design
Design system
Project
Project
9 months · Enterprise web app
Product, engineering, business stakeholders & Yardi integration team
9 months · Enterprise web app
Product, engineering, business stakeholders & Yardi integration team
01 / The challenge
01 / The challenge
Many properties.
Too many places to look.
Many properties.
Too many places to look.
Many properties.
Too many places to look.
Before PIM, property managers relied on spreadsheets, email and separate tools. Property attributes lacked a single source of truth. Updates took time to review, and manual data entry created inconsistencies.
Before PIM, property managers relied on spreadsheets, email and separate tools. Property attributes lacked a single source of truth. Updates took time to review, and manual data entry created inconsistencies.
The challenge was to let people update shared property information without confusing a proposed change with an accepted value. The experience also had to respect approval responsibilities, work with Yardi and support branding across portfolio companies.
The challenge was to let people update shared property information without confusing a proposed change with an accepted value. The experience also had to respect approval responsibilities, work with Yardi and support branding across portfolio companies.
01
Find the right information
Find the right information
Bring scattered property records into a consistent structure.
Bring scattered property records into a consistent structure.
02
Keep changes moving
Keep changes moving
Make pending updates and review actions easy to find.
Make pending updates and review actions easy to find.
03
Build for what comes next
Build for what comes next
Create patterns that can scale across portfolios and companies.
Create patterns that can scale across portfolios and companies.
02 / User experience
02 / User experience
The right information.
For the work at hand.
The right information.
For the work at hand.
The right information.
For the work at hand.
I organised research findings around three groups: property managers, market officers and admin users. The research board captured their responsibilities, needs and recurring challenges.
I organised research findings around three groups: property managers, market officers and admin users. The research board captured their responsibilities, needs and recurring challenges.
Property managers needed a central place to manage updates. Market officers needed clearer approval workflows and regional oversight. Admin users needed control over permissions and system setup.
Property managers needed a central place to manage updates. Market officers needed clearer approval workflows and regional oversight. Admin users needed control over permissions and system setup.
Approvals & oversight
Approvals & oversight
Market officers
Market officers
Review property information and keep approval decisions moving.
Review property information and keep approval decisions moving.
Access & setup
Access & setup
Admin users
Admin users
Manage access and maintain a consistent working environment.
Manage access and maintain a consistent working environment.
Portfolio context stays visible as users work through a property record. Click to explore ↗
Portfolio context stays visible as users work through a property record. Click to explore ↗
From insight to structure
From insight to structure
Start with the workflow.
Then shape the screen.
Start with the workflow.
Then shape the screen.
Start with the workflow.
Then shape the screen.
I mapped how users moved from a portfolio to a property, edited its information and submitted changes for review. This gave the team a shared structure before we moved into detailed interface design.
I mapped how users moved from a portfolio to a property, edited its information and submitted changes for review. This gave the team a shared structure before we moved into detailed interface design.
Search, filters and a consistent property hierarchy helped users reach the right record. Focused sections kept details, buildings and units, contacts and reports manageable.
Search, filters and a consistent property hierarchy helped users reach the right record. Focused sections kept details, buildings and units, contacts and reports manageable.
From user need to design response
From user need to design response
User need
Design response
Property managers: one place to find and update information.
Property managers: one place to find and update information.
Portfolio search, structured records and focused editing states.
Portfolio search, structured records and focused editing states.
Market officers: clearer approvals and regional oversight.
Market officers: clearer approvals and regional oversight.
A pending-work queue, current and proposed values, and review actions.
A pending-work queue, current and proposed values, and review actions.
Admin users: manageable permissions and system setup.
Admin users: manageable permissions and system setup.
Individual privileges, approver assignments and notification preferences.
Individual privileges, approver assignments and notification preferences.
View research board ↗
View research board ↗
Working through the edit-property journey in wireframes.
Working through the edit-property journey in wireframes.
03 / Information architecture
03 / Information architecture
A portfolio view.
A property focus.
A portfolio view.
A property focus.
A portfolio view.
A property focus.
The records had several levels: a portfolio contained properties, properties contained buildings, and buildings related to units. I made those relationships visible through breadcrumbs, related-record lists and consistent detail pages.
The records had several levels: a portfolio contained properties, properties contained buildings, and buildings related to units. I made those relationships visible through breadcrumbs, related-record lists and consistent detail pages.
Users could move from a property to its buildings and units while keeping track of where they were. Grouped attributes and an attribute filter helped them work through dense records.
Users could move from a property to its buildings and units while keeping track of where they were. Grouped attributes and an attribute filter helped them work through dense records.
01
Portfolio
Portfolio
Find the relevant property.
02
Property
Property
Review the shared record.
03
Building
Building
Explore related buildings.
04
Unit
Unit
Reach the individual unit.
The workspace brings the property record and its surrounding tasks together.
The workspace brings the property record and its surrounding tasks together.
01 — Navigate the portfolio and find a property.
01 — Navigate the portfolio and find a property.
02 — Read the property record, then make an update.
02 — Read the property record, then make an update.
04 / Workflow design
04 / Workflow design
Less chasing.
More reviewing.
Less chasing.
More reviewing.
Less chasing.
More reviewing.
The previous process relied on email chains involving people with different responsibilities. PIM’s requirements already called for in-app approval controls. My work was to make those controls understandable and connect the queue, property context and decision.
The previous process relied on email chains involving people with different responsibilities. PIM’s requirements already called for in-app approval controls. My work was to make those controls understandable and connect the queue, property context and decision.
In-app notifications, attention banners and a task list helped reviewers see what needed action. New activity appeared without requiring a page refresh, reducing interruptions during the workflow.
In-app notifications, attention banners and a task list helped reviewers see what needed action. New activity appeared without requiring a page refresh, reducing interruptions during the workflow.
01
Update
Update
Make a change to the property record.
Make a change to the property record.
02
Submit
Submit
Send the update for review.
Send the update for review.
03
Review
Review
Check the proposed changes in context.
Check the proposed changes in context.
04
Decide
Decide
Approve or reject the pending update.
Approve or reject the pending update.
Original product demonstration — a property update moves from submission to review and approval.
Original product demonstration — a property update moves from submission to review and approval.
The design decision
The design decision
Show what is changing before asking for a decision. Keep the current value, proposed value and reason close to the approval action.
Show what is changing before asking for a decision. Keep the current value, proposed value and reason close to the approval action.
A dedicated view for pending work, with review actions close to the information.
A dedicated view for pending work, with review actions close to the information.
05 / Visual foundations
05 / Visual foundations
A shared system.
Room to grow.
A shared system.
Room to grow.
A shared system.
Room to grow.
I used Google Material Design as a starting point, then progressively customised the system for PIM. The shared library grew to more than 100 reusable custom components.
I used Google Material Design as a starting point, then progressively customised the system for PIM. The shared library grew to more than 100 reusable custom components.
Neutral styling and flexible branding supported different portfolio companies. Working with developers on shared patterns kept screens consistent as the product expanded.
Neutral styling and flexible branding supported different portfolio companies. Working with developers on shared patterns kept screens consistent as the product expanded.
Reusable components for a product with many screens, states and user roles.
Reusable components for a product with many screens, states and user roles.
Consistency in the details.
Flexibility across the product.
Consistency in the details.
Flexibility across the product.
Built around the product
Built around the product
Navigation · Forms & validation
Tables & bulk actions · Review panels
Permissions · Notifications
06 / Beyond the core journey
06 / Beyond the core journey
Details that make
daily work easier.
Details that make
daily work easier.
Details that make
daily work easier.
The core property workflow was only one part of PIM. I also designed property creation, contacts, user security and permissions, reports and notifications.
The core property workflow was only one part of PIM. I also designed property creation, contacts, user security and permissions, reports and notifications.
Each area followed the same visual and interaction patterns, helping users move between tasks with a familiar structure.
Each area followed the same visual and interaction patterns, helping users move between tasks with a familiar structure.
Contacts — keep the people connected to a property close to its record.
Contacts — keep the people connected to a property close to its record.
Reports — choose fields, arrange columns and filter the properties included in an export.
Reports — choose fields, arrange columns and filter the properties included in an export.
Notifications communicate what has changed and what needs attention.
Notifications communicate what has changed and what needs attention.
07 / Design decisions
07 / Design decisions
The choices behind
the experience.
The choices behind
the experience.
The choices behind
the experience.
The interface came from decisions about how people find information, make changes and review them. These are six choices I made to connect the product to that work.
The interface came from decisions about how people find information, make changes and review them. These are six choices I made to connect the product to that work.
01
Approvals / Reduce context switching
Approvals / Reduce context switching
Bring the review
back into PIM.
Bring the review
back into PIM.
Bring the review
back into PIM.
The problem
The problem
Email chains made it difficult to follow requests across people and roles. Within PIM, reviewers also needed to distinguish an accepted value from a change still awaiting approval.
Email chains made it difficult to follow requests across people and roles. Within PIM, reviewers also needed to distinguish an accepted value from a change still awaiting approval.
My decision
My decision
I connected in-app notifications, attention banners and the approval queue. In the property view, pending labels and current/proposed values made changes visible. The approval queue added requestor comments, individual decisions and bulk actions.
I connected in-app notifications, attention banners and the approval queue. In the property view, pending labels and current/proposed values made changes visible. The approval queue added requestor comments, individual decisions and bulk actions.
Why this choice
Why this choice
The reviewer could see what would change and why, then approve or reject it. Rejection required a reason, giving the person requesting the change a clear response.
The reviewer could see what would change and why, then approve or reject it. Rejection required a reason, giving the person requesting the change a clear response.
Design balance
Email remained a notification option. The interaction design brought the decision and its supporting information together inside PIM.
Email remained a notification option. The interaction design brought the decision and its supporting information together inside PIM.
Property review state: pending labels distinguish proposed updates from the current record.
Property review state: pending labels distinguish proposed updates from the current record.
02
Navigation / Preserve context
Navigation / Preserve context
Keep the portfolio
and property connected.
Keep the portfolio
and property connected.
Keep the portfolio
and property connected.
The problem
The problem
Property managers struggled to track information across tools. Within PIM, each property also contained several types of information that users needed to move between.
Property managers struggled to track information across tools. Within PIM, each property also contained several types of information that users needed to move between.
My decision
My decision
I organised navigation around the portfolio and property hierarchy, with search and filters to locate records. Property details, buildings and units, contacts and reports followed a consistent structure.
I organised navigation around the portfolio and property hierarchy, with search and filters to locate records. Property details, buildings and units, contacts and reports followed a consistent structure.
Why this choice
Why this choice
Users could narrow down to a property and explore its information while retaining the wider portfolio context. The same structure across records made the next place to look more predictable.
Users could narrow down to a property and explore its information while retaining the wider portfolio context. The same structure across records made the next place to look more predictable.
Design balance
Progressive disclosure kept the overview manageable while allowing users to reach detailed information when needed.
Progressive disclosure kept the overview manageable while allowing users to reach detailed information when needed.
A consistent route from portfolio to property information.
A consistent route from portfolio to property information.
03
Data entry / Support accurate changes
Data entry / Support accurate changes
Help users get an update
right as they make it.
Help users get an update
right as they make it.
Help users get an update
right as they make it.
The problem
The problem
Manual entry contributed to inconsistent property information. Users needed to edit records efficiently while keeping changes clear enough for someone else to review.
Manual entry contributed to inconsistent property information. Users needed to edit records efficiently while keeping changes clear enough for someone else to review.
My decision
My decision
I designed single-field and page editing states, address validation and a reason-for-change step. Fields requiring approval displayed pending changes; other updates could be saved directly.
I designed single-field and page editing states, address validation and a reason-for-change step. Fields requiring approval displayed pending changes; other updates could be saved directly.
Why this choice
Why this choice
Address validation helped users check an update before submitting it. Showing the proposed value and its reason gave the next reviewer enough context to assess the request.
Address validation helped users check an update before submitting it. Showing the proposed value and its reason gave the next reviewer enough context to assess the request.
Design balance
Approval requirements varied by data point. The design needed to make that distinction clear without adding the same review step to every edit.
Approval requirements varied by data point. The design needed to make that distinction clear without adding the same review step to every edit.
Structured property details and focused editing states.
Structured property details and focused editing states.
04
User roles / Make responsibilities clear
User roles / Make responsibilities clear
Match the experience
to the responsibility.
Match the experience
to the responsibility.
Match the experience
to the responsibility.
The problem
The problem
Property managers, reviewers and admins used the same platform for different tasks. A shared product had to support those responsibilities without giving every user the same actions.
Property managers, reviewers and admins used the same platform for different tasks. A shared product had to support those responsibilities without giving every user the same actions.
My decision
My decision
I designed individual privileges for editing attributes, creating records, managing users and approver assignments, and overriding approvals. The profile also included notification preferences and an out-of-office approver with start and end dates.
I designed individual privileges for editing attributes, creating records, managing users and approver assignments, and overriding approvals. The profile also included notification preferences and an out-of-office approver with start and end dates.
Why this choice
Why this choice
People could share the same property workspace while having different responsibilities. Delegation provided a way to cover approvals when the usual approver was away.
People could share the same property workspace while having different responsibilities. Delegation provided a way to cover approvals when the usual approver was away.
Design balance
The interface used a shared structure. Specific privileges controlled actions, while approver assignments determined who could make a decision.
The interface used a shared structure. Specific privileges controlled actions, while approver assignments determined who could make a decision.
Profile design: individual privileges, notification preferences and out-of-office approval cover.
Profile design: individual privileges, notification preferences and out-of-office approval cover.
05
Design system / Build a flexible foundation
Design system / Build a flexible foundation
Start with Material.
Shape it around PIM.
Start with Material.
Shape it around PIM.
Start with Material.
Shape it around PIM.
The problem
The problem
PIM was a new product with no existing design system. The team needed consistent patterns for delivery and a foundation that could support different portfolio companies.
PIM was a new product with no existing design system. The team needed consistent patterns for delivery and a foundation that could support different portfolio companies.
My decision
My decision
I started with Google Material Design, then progressively customised the library for PIM. It grew to more than 100 reusable custom components, with neutral styling and flexible branding.
I started with Google Material Design, then progressively customised the library for PIM. It grew to more than 100 reusable custom components, with neutral styling and flexible branding.
Why this choice
Why this choice
An established starting point gave design and engineering shared patterns early. Customising those patterns around the product’s workflows supported consistency as its scope grew.
An established starting point gave design and engineering shared patterns early. Customising those patterns around the product’s workflows supported consistency as its scope grew.
Design balance
Reuse supported delivery, while custom components and branding flexibility addressed PIM’s enterprise requirements.
Reuse supported delivery, while custom components and branding flexibility addressed PIM’s enterprise requirements.
A shared library customised around PIM’s screens and workflows.
A shared library customised around PIM’s screens and workflows.
100+ reusable custom components
100+ reusable custom components
06
Reporting / Make configuration reusable
Reporting / Make configuration reusable
Choose the data.
Keep the setup.
Choose the data.
Keep the setup.
Choose the data.
Keep the setup.
The problem
The problem
Different reporting tasks needed different fields and property groups. A single fixed export could not cover every need.
Different reporting tasks needed different fields and property groups. A single fixed export could not cover every need.
My decision
My decision
I organised the report builder around three steps: select fields, organise their order and choose the property scope. Search and grouped fields helped users find data. Named parameter sets let them save and reload a configuration.
I organised the report builder around three steps: select fields, organise their order and choose the property scope. Search and grouped fields helped users find data. Named parameter sets let them save and reload a configuration.
Why this choice
Why this choice
The layout separates what appears in a report from which properties it covers. Users could prepare a specific export and reuse the setup for recurring work.
The layout separates what appears in a report from which properties it covers. Users could prepare a specific export and reuse the setup for recurring work.
Design balance
The designs also explored subscriptions. The initial reporting requirements treated subscriptions as a later phase.
The designs also explored subscriptions. The initial reporting requirements treated subscriptions as a later phase.
Report configuration: select fields, arrange columns, choose the scope and save parameters.
Report configuration: select fields, arrange columns, choose the scope and save parameters.
08 / The result
08 / The result
Clearer information.
Fewer bottlenecks.
Clearer information.
Fewer bottlenecks.
Clearer information.
Fewer bottlenecks.
PIM gave real estate teams a shared way to find, update and review property information.
PIM gave real estate teams a shared way to find, update and review property information.
40%
40%
40%
Faster approvals
Faster approvals
Approval time reduced through the wider workflow change.
Approval time reduced through the wider workflow change.
50%
50%
50%
Less time searching
Less time searching
Clearer navigation, search and filtering.
Clearer navigation, search and filtering.
20%
20%
20%
Better data accuracy
Better data accuracy
Reported improvement in property data accuracy.
Reported improvement in property data accuracy.
60%
60%
Fewer approval-related emails.
Fewer approval-related emails.
Reported project outcomes across the wider delivery, including design, engineering and Yardi integration.
Reported project outcomes across the wider delivery, including design, engineering and Yardi integration.
What I took forward
What I took forward
Design around the work.
Build the system alongside it.
Design around the work.
Build the system alongside it.
Design around the work.
Build the system alongside it.
Building PIM from scratch meant designing the journey and its visual foundations together. Research helped us decide where users needed structure, where they needed flexibility and which actions deserved priority.
Building PIM from scratch meant designing the journey and its visual foundations together. Research helped us decide where users needed structure, where they needed flexibility and which actions deserved priority.
The biggest lesson was to make the state of the information clear. Users needed to know what was current, what was proposed and who could approve it. Bringing that context into the record made the workflow easier to follow.
The biggest lesson was to make the state of the information clear. Users needed to know what was current, what was proposed and who could approve it. Bringing that context into the record made the workflow easier to follow.
Link Logistics PIM / Product design by Enes Gundogdu
Link Logistics PIM / Product design by Enes Gundogdu
Design
Design
Enes Gundogdu
UX/UI, user flows & design system
Enes Gundogdu
UX/UI, user flows & design system
Collaboration
Collaboration
Product managers, developers,
business stakeholders & Yardi integration team
Product managers, developers,
business stakeholders & Yardi integration team
Enes Gundogdu 2026
Making complex
work easier to use.