Doinn 2016

Allowing property managers
do what they do better: manage.

Doinn is a Lisbon based startup who connects property managers to service providers. It helps managers and hosts save time handling the cleaning, reception and laundry of their short-term rental apartments.

The Challenge

Simplify the current version of the software and ship new features that improve user engagement. The current version of the platform is complex. What reflects on client’s support load. They was always calling to do tasks that were possible in
the platform, they just don’t know how.

My Role

I was the head designer of the team.
Worked side-by-side with business developers
and engineers. I ran some user interviews, concepts, sketchs, prototypes, user flows
and visual design of the product.

Selected Work Buy Flow

Bringing to the company a
different way to design software.

I started, in my short period at Doinn, a few high fidelity wireframes for the new service flow. These studies was the kick start of a new product vision with a simple, honest and human approach. Bring these values to the company’s culture was one of my professional goals.

Some key aspects

The previous version was accessible only to registered users. After a few tests and interviews we discovered that clients was using it as a way to explore the available services and prices.

We had to deal with four different flows. The first was to set a property and others to buy services. We needed this because service prices were provided based on the house settings, such as location, neighborhood and schedule.

I tried to make the property setup as short as possible. For exemple, if any field like country and city where filled previously from a different route we display this information in a short single line, with an edit link.

As many bedrooms the apartment have, more beds and bathrooms the client can ask to be cleaned without extra costs. This simple prototype helped me to explain the idea to the team.

And after the house setup the client can request services. This is an example of how could be the request for a house cleaning. To save development time I used modules in the design system. This way one written component could be used several times just changing their content.

Selected Work Responsive Dashboard

Rethinking everything.
Again and again.

Iteration was important on the design process to find the best solutions and help deal with multiple conflicting requirements. These studies below are a good exemple of this exercise. It was for the main view of the dashboard. Here I had indicate several informations and features for different user profiles.

Quickly we saw that put everything on a weekly calendar was the best and simplest solution. It’s easily adapted to mobile, is gesture friendly and also accomplish all requirements.