Liliia Orlenko
Immoforce property management dashboard showing the property listings grid
2019 — 2021 · Product Designer · Berlin · Full-time

McMakler

Three internal tools. One fragmented platform.

A full redesign of the internal tools one of Germany's fastest-growing real-estate companies relied on every day, plus a fourth built from scratch. Grounded in hands-on research, and along the way I helped set up a stronger design and research culture inside the company.

18→32%
User satisfaction across the platform post-redesign
75%
First-round design approval rate across stakeholders
3+1
Tools redesigned or built: Immoforce, Alla, Brokerforce

Three tools. No single source of truth.

McMakler is a German real estate company built around in-house agents backed by its own software. When I joined, the tools those agents used every day were fragmented. Data sat inside each system on its own, and there was no reliable place to see what was happening across a whole transaction.

My work covered Immoforce (central property management), Alla (broker scheduling), and Brokerforce (broker task management, built from scratch). None of them talked to each other. Agents kept their own spreadsheets to track what the software should have shown them.


Property Management · CRM

The brief said UI refresh. The product said otherwise.

The PM's brief was simple: a basic UI refresh, a few flow improvements, reuse the existing MUI components, tight timeline, no research phase.

But the product showed me something the brief had assumed away. The app's logic wasn't written down anywhere. The business rules, the required field order, which states set off which workflows, none of it lived outside the heads of the people who'd built or used the system. The brief was asking me to improve a UI without knowing what the UI actually did.

Immoforce redesign: global search, applicant management, unified data, drag-and-drop
Immoforce: property management CRM redesign across search, applicants, documents, and data

I proposed a one-week research sprint, not an open-ended discovery phase. One week, one deliverable: the logic written down, findings from users, and one direction to test. Three days in person with customer care, SWAT team leads, and ops, plus FullStory session recordings to check what users said against what they actually did.

When someone pushed back in a review, I had a session recording to show them. 75% of designs got approved on the first round, because they were grounded in how the system actually worked.

Constraint
MUI component library, with custom patterns where the existing components couldn't carry the need
Research
In-person interviews, FullStory, undocumented logic mapping with ops leads
Immoforce advertisement view with multi-portal publishing to ImmoScout24, eBay, and others
Immoforce: property advertisement, online status, and multi-portal publishing

Broker Scheduling

The page took 80 seconds to load

Not 8 seconds, 80. Agents used Alla to manage their calendars and coordinate property viewings. The load-time problem was a backend issue that engineering handled separately. My job was making the product worth using once it finally loaded.

Alla appointment booking calendar with optimal slots and meeting type selection
Alla: appointment booking calendar with optimal-slot suggestions and meeting type

Three design iterations:

01 Information architecture: how appointments were organized and surfaced
02 Viewing request flow: how agents handled incoming scheduling requests
03 Calendar-centric layout built around how agents actually structured their day

Alla was shut down about three months after the redesigned version launched. Adoption was low. Some agents stuck with tools they already knew, and part of the scheduling work happened over the phone, not in any software.

What I took from Alla: we hadn't asked enough agents, early enough, whether they'd use any tool for this at all, or what it would take to replace what they had. That question should have come before the third iteration, not after. Low adoption after a redesign is usually both an adoption problem and a research problem.

Alla events and tasks panels with a structured appointment report
Alla: events, tasks, and structured appointment reports

Task Management · 0→1

From paper to product

Broker workflow was running on paper and in spreadsheets. Tasks got assigned, tracked, and closed by hand. The goal was software that could replace all that while still fitting how brokers already thought about their work.

With brand-new enterprise tools, people won't adopt software that thinks about the work differently than they do. The design had to match the mental models already in place, then improve the mechanics underneath.

Brokerforce: dashboard, opportunities, and task tracking built from scratch

This ran alongside the Immoforce redesign, so I was switching between reworking an existing product and building a new one from scratch. The modular patterns and component decisions from Immoforce fed straight into Brokerforce, so agents using both tools weren't learning two different visual languages.

Scope
Task creation, assignment, status tracking, completion states, notifications
Approach
Mirror existing mental models first, then improve mechanics underneath

What in-person research reveals that interviews don't

McMakler was the first job where in-person research was a regular habit for me, not a one-off phase. Sitting with the customer care team while they used Immoforce showed me things a 30-minute interview would have missed.

Watching people work reveals the shortcuts, workarounds, and little hesitations they never think to mention, because they don't see them as problems. To them it's just how the thing works. That changed how I run research. The most useful things I learned at McMakler, I learned by being in the room while someone did their job.