aviv group · 2023-2024

Create a new solution for France, Belgium and Germany, paving the way for whole Europe

KPIs

Reduction of time to complete by 30%

From an average of 45min to less than 30min

Pragmatic value of UEQS at 2.25

Hedonic value of UEQS at 0.694

The company

Aviv group is a leader in digital real-estate in Europe. It operates a range of well-known portals (i.e. SeLoger, Meilleurs Agents, Immoweb, Immowelt,...) with the goal of creating Europe's premier real estate tech company.

Listing creation form with property details and map

The strategy I implemented

Aviv Group's listing creation funnels had grown independently across three countries, each with its own tech stack, design language, and codebase. One of the legacy products was fourteen years old. Maintenance costs were compounding, the user experience had fallen behind market standards, and the business was starting to see visible customer loss as a result.

The decision to merge all three funnels into a single unified product was driven primarily by engineering, but the UX case was equally strong. My goal was to lead the design of this new unified funnel, starting with France, Germany and Belgium.

I was the sole designer on the project. I owned the full design scope: research synthesis, information architecture, step sequencing, screen design, component creation, and contributing to the Aviv B2B design system as its design voice. I worked with a PM who had deep expertise in the German market, an engineering manager who later grew into a team of six to seven engineers, and a UX researcher I could consult, though she was not embedded in the project directly.

The big structural decisions of what steps to include, in what order, and what to prioritise for the first release were made collaboratively between me and the PM, with input from the EM. The step sequencing in particular was a design decision I owned and advocated for, including one significant pushback I will come back to in the approach section.

What was the problem?

For the business: six total different funnels meant 6 times more maintenance overhead, duplicated engineering effort, and an inability to ship improvements consistently across markets. With one legacy codebase dating back fourteen years, technical debt had become a real cost and a blocker to growth. The competitive pressure was sharpest in France and Germany; Belgium had little competition, but the product still needed to be brought up to standard. The business was already losing customers.

For users: the core pain was time. Creating a listing took between 45 minutes and an hour across the existing funnels, a significant friction point for estate agents who create listings regularly. The interfaces were inconsistent, outdated, and not built for the workflows agents actually had.

What we assumed: early on, I expected users would gather all the information they needed, property details, photos, documents, and complete the funnel in one sitting. This turned out to be wrong. In practice, agents filled in listings progressively, across multiple sessions, often because they were waiting on documents or photos from the property owner.

That single invalidated assumption shaped several key design decisions.

User research — sticky notes and affinity mapping

Activities

I started with an audit of the six existing funnels, mapping commonalities and divergences across markets, and running heuristic evaluations to surface the most critical UX failures. I also conducted a competitors benchmark across France, Germany, and Belgium to understand what the industry standard looked like, and to identify where we could lead rather than follow.

From there I developed user flows and wireframes to structure the new funnel, running iterative testing sessions with agents throughout. I collaborated closely with the PM on scope and feature prioritisation, with engineers on feasibility and component specs, and fed back into the Aviv B2B design system with new components created specifically for this product.

Edit listing — form with property details
Prioritization and research

Solution

The core insight from competitive benchmarking was that the step-by-step funnel model was already the industry standard. Agents knew it, expected it, and were comfortable with it. The innovation was not in reinventing the structure but in executing it better: cleaner sequencing, reduced cognitive load, smarter defaults, and one significant forward-thinking bet.

The biggest lever on time-to-complete was placing the document and photo upload step at the beginning of the funnel. By letting users upload property documents and listing photos first, we could use AI to pre-fill a significant portion of the remaining fields automatically. This was a deliberate design decision I pushed for in early 2023, forward-thinking at the time, and it required stakeholder alignment to execute. It turned out to be the primary driver of the 30% reduction in completion time.

Beyond that, the design addressed the multi-session reality directly: every step auto-saves, a persistent save indicator gives users confidence their work is not lost, and a wizard component I designed shows progress across all steps, making it easy to resume from the dashboard and pick up exactly where you left off.

The tension between users and the business was also navigated here. Agents instinctively wanted more fields for precision; the business rightly wanted a leaner funnel. We landed on a optimal field set designed to cover the vast majority of use cases, with a clear path to add edge-case fields in subsequent releases.

Creating components and contributing to design system

A core part of the project was building reusable, scalable components. As the design voice for the B2B side of the Aviv design system, I created new components including the wizard, and integrated existing ones, ensuring the new funnel would be maintainable and extensible as the product expanded to other European markets and with other edge cases.

Step component — states and variants
Wizard component — vertical stepper
Stepper component specifications

Challenges

The most complex challenge was managing the convergence of six funnels with genuinely different requirements: different fields, different validation rules, different market expectations. Making decisions that worked across France, Belgium, and Germany, while keeping the first release focused and shippable.

The other significant challenge was the multi-session usage pattern. Building a reliable save-and-resume experience required close collaboration with engineering, particularly around the auto-save mechanism, and some components proved harder to build than initially scoped. We found solutions each time, but it reinforced the value of involving engineers early in design decisions.

Speed / Quality indicators

Results

In user testing before launch, the new funnel achieved a 30% reduction in time to complete, from over 45 minutes down to on average 30, meeting the primary KPI we had defined from the start.

The UEQS evaluation returned a pragmatic score of 2.25, placing it in the excellent range. The hedonic score of 0.694 was what we expected : real estate agents are not using a listing tool to enjoy themselves; they are there to get the job done efficiently. A high pragmatic score was the right result.

The product was handed off and ready for launch in May 2024. I left Aviv shortly before it went live, so I do not have post-launch production data, but the testing results gave the team strong confidence going in.

Contact step — listing funnel
Location step — form and stepper

Take-away

The most important lesson from this project is that the best design decisions are not always the most visible ones. The AI prefill from documents and photos looks like a feature, but it was really an architectural choice about where to put friction and where to remove it. Pushing for that step order in early 2023 and holding the position through stakeholder conversations is what made the 30% reduction achievable.

If I were starting again, I would invest more time upfront in structured alignment sessions with all stakeholders, defining what success looks like before the design work begins. Early ambiguity about the target slowed us down initially, and clearer shared goals from day one would have made the first few months more efficient.

The open question I would have explored next: once live, how well did the tested metrics hold in production with broader audience ? And beyond the main use cases covered in this version, the edge cases, atypical property types and complex ownership structures, were the natural next design challenge.

You may also like