Gabriela García

All cases

07 / Rental insurance · Web app redesign · 2025

NOWO

Planning and redesigning a multi-role web app through MVPs.

I redesigned the NOWO web app: flow architecture, UX/UI and responsive behavior for registration, evaluation, properties and invitations.

2025 redesign · incremental MVP delivery · no conversion metrics

  • Detail of NOWO “My properties” (Spanish UI): a property card with an “Invite tenant” button and a card to add a new property.
Property management in the web app redesign · sample data (Spanish UI).
Role
Product Designer
Period
2025
Scope
Flow architecture · UX/UI · responsive
Delivery
MVP planning · sprints 1–11

The challenge

Making the product and next steps easier to understand

The goal in 2025 was to improve the NOWO web app for property owners, tenants and other rental participants. The challenge was to turn long processes—registration, adding a property, invitations and evaluation—into clear workflows with understandable states and next steps.

My contribution

Role-based workflows, from property to invitation

I redesigned the web app workflows so each role could understand what to complete, which information was reused and what came next: role-based registration, property management, property registration, rental details and invitations.

The work covered alternate states—validation, errors and recovery—as well as desktop and mobile versions.

The work was organized through MVPs and sprints. The first four covered general registration, access, property owner registration, property setup and invitations. The complete plan runs through sprint 11 and expands into tenant and guarantor journeys, pre-qualification, validation, payments and exceptions.

Value proposition

Property, rent and invitation in one coherent experience

Guide each role through their tasks and connect properties, rental details and invitations in a coherent web experience.

Decisions and evidence

From MVP planning to complete workflows and recoverable states

MVP planning

Planning made the first release scope and later dependencies visible. Registration, access, property setup and invitations created the foundation; later sprints expanded roles, evaluation, payments and exception paths.

NOWO planning board organized across sprints 1 to 4: general registration, access, property owner registration, property setup and invitation flows.

Original NOWO planning board · sprints 1 to 4. The complete evidence continues through sprint 11 (Spanish).

Property, rental details and invitation

Instead of placing the entire operation in one long form, the workflow separates intent, property details and rental conditions. This sequence is meant to reduce context switching and makes the relationship between the property and the invitation explicit.

NOWO “My properties” screen (Spanish UI): a property card with an “Invite tenant” button and another card to add a new property.
Property management Inventory, status and differentiated actions: invite or add.
“Add a rental property” form (Spanish UI) with address search and fields for street, numbers, postal code, neighborhood, municipality, state, square meters and nickname.
Property registration Assisted address entry and verifiable fields before saving the property.
Invitation “Rental details” step (Spanish UI): monthly rent with the allowed range, rental term and insurance duration.
Invitation details Rent amount, rental term and insurance duration connected before continuing.

Screens from the NOWO web app redesign (Spanish UI). Visible data is treated as sample content; the user name and address were replaced.

States and responsive behavior

Each role chooses its path from registration, on mobile too. Errors are resolved in context: the message explains what happened and the action takes people back to what they need to fix.

Mobile registration (Spanish UI): email, phone number and a choice of owner, real estate agency or tenant.
Mobile registration Email, phone and role—owner, agency or tenant—on a single screen.
“Confirm your identity” screen (Spanish UI) with a five-digit code highlighted in red, an invalid-code message and a resend option.
Verification error An invalid code is flagged without losing context; resending stays available.
“Address not found” modal (Spanish UI) with a “Check information” button.
Address not found The message explains the problem and returns people to check the information.

Screens from the web app redesign file · sample data (Spanish UI).

Impact and actual scope

Continuity from planning to updated workflows

The redesign moved from incremental MVP planning into workflows updated in June 2025. Registration, evaluation, property management and invitations were documented through desktop and mobile screens, alternate states and interaction criteria. The evidence shows continuity across prioritization, design and preparation for development.

Learnings

In a multi-role web app, hierarchy is also orientation

Hierarchy has to show which task belongs to each person, which information already exists and what is still needed to move forward.

What can’t be claimedwithout measurement

Design scope, not conversion outcomes

  • The reviewed files include no conversion, purchase, usage or satisfaction data.
  • The evidence confirms planning, workflows and screens; it does not confirm which version reached production.
  • The case does not attribute business or behavior improvements without post-release measurement.