2020 at Dalia was mostly divided in two parts:

I. SURVEY INTERFACE

• Retention
• Design System

I. SURVEY INTERFACE
—

In the Survey Interface field, we stared talking to users even more and testing our hypothesis even earlier. That is why in the first part of the year Daily Bonus, Goal Setting and Marketing Campaign in our Panel showed up green in the AB tests:

• Goal setting: +35% in POCs creation
• Daily Bonus: +13% in Completions
• Marketing Campaigns: +23% in revenue increase

Then we went to improving our Panel by Updating Rewards and Account pages to increase retention. We also maintained and presented the design system for the Panel.
More User Research was held, and eventually we created User Research Documentation:

Another fun were little changes in Target Group Generator — an internal tool that the Support Team uses to run client projects.

To improve acquisition of users, we delivered:

• Social login
• Onboarding
• Opinion Scale improvements
• Smarter Email Templates
• Friendlier GDPR communication
• and new survey subscription management

II. LATANA
—

Communication Design was growing. Amazing Katja and Niels delivered new Latana Brand, Communication guidelines, Presentation templates, New Latana Website and tons of marketing materials.

Latana helps brands make better marketing decisions by delivering understandable insights. We script a survey, run it with specific audiences and deliver that data to our customers through the dashboard.

In August, we started conversations about an update. Product no longer fulfilled clients needs, was hard to grow and maintain.
I started on-boarding. Having a lot of conversations with different team members, from Product owner and QA to Frontend and Backend developers.

Together we defined a general direction for the new version:

• Make information more readable
• Easier to get actionable insights
• Make information more granular
• Support hyper-local targeting

I created a materials repository and after precisely going through it stated drafting some prototypes.
When we had our first low-fidelity prototypes we prepared the script and went to talk and test with several clients like Duolingo, N26 and others.

I also coded a prototype to play around with data we had. To understand how we should manipulate it to meet client's needs.

We did the tests, collected our observations and went to implement some changes.

I described all the flows, collected and updated all the prototypes and mock-ups and presented them to the team. Needless to say that mostly all team members were embedded and informed about all the work in advance.
Afterward, we described the solution and presented the progress to the company.

In the end of the year we spent most of the time on updating solutions and creating mother-lists of changes, improvements and debts from the previous rush.