Nasil Sence

Designing a Consumer Research Platform That Connects Brands with Real People

When I joined the Nasil Sence project, it wasn't just about designing another mobile application or dashboard. The vision was much bigger: to build a complete digital ecosystem that would change how brands gather consumer feedback while making the experience enjoyable enough for people to actively participate.

The platform brings together three different products—a marketing website, an administrative dashboard, and a native mobile application—all working together to simplify consumer research. Brands can launch research campaigns, distribute products to selected participants, collect authentic feedback, and monitor the entire process from a single platform. On the other side, consumers can discover available campaigns, reserve products, complete surveys, upload purchase details when required, and receive rewards for sharing their experiences.

Although these experiences serve different users with different goals, they needed to feel like one unified product. Creating that consistency while ensuring every platform solved its own unique problems became the foundation of my work throughout the project.

Over the course of six months, I worked closely with stakeholders, developers, and the QA team to transform an evolving business idea into a polished product that was intuitive, scalable, and ready for thousands of users.

Project Overview

Nasil Sence is a digital consumer research platform that enables companies to validate products using real consumer feedback instead of relying solely on traditional market research methods. Businesses can launch research campaigns, monitor participation in real time, review insights, and make informed product decisions based on genuine customer experiences.

The platform was designed as a complete ecosystem rather than a standalone application. The marketing website introduces the product and builds trust with potential business clients, the dashboard provides tools for managing campaigns and analysing collected data, and the mobile application serves as the primary touchpoint for participants completing product testing and surveys.

Designing these three platforms simultaneously required every interaction, component, and workflow to feel connected. Whether someone was launching a campaign through the dashboard or completing a survey on their phone, the experience needed to communicate the same product language and level of quality.

My Role

As the Product Designer, I was responsible for shaping the experience from the earliest planning stages through final implementation. My work extended beyond creating interfaces; it involved understanding business objectives, defining user flows, structuring information, building a scalable design system, and collaborating closely with developers throughout the implementation process.

I contributed across every major phase of the project, including UX research, stakeholder discussions, journey mapping, wireframing, interface design, prototyping, design system creation, usability improvements, implementation reviews, and quality assurance. Rather than treating design handoff as the end of the process, I remained actively involved during development to refine interactions, solve usability issues, and ensure the final product reflected the intended user experience.

This close collaboration allowed design and development to evolve together through continuous iterations instead of following a traditional handoff approach.

Team

The project was completed by a compact, highly collaborative team, allowing decisions to be made quickly and iterated efficiently.

• Product Designer
  Responsible for UX research, product strategy, user experience, interface design, design system creation, prototyping, implementation support, and QA collaboration.

• Backend Developer
  Developed the platform architecture, APIs, business logic, and data management required to support campaigns and participant workflows.

• Mobile Developer
  Built the native mobile application and collaborated closely during implementation to ensure interactions matched the intended design experience.

• Client & Stakeholders
  Worked closely with the team throughout the project, providing business requirements, validating research workflows, and shaping product priorities through regular discussions.

The Challenge

At first glance, Nasil Sence appears to be a straightforward consumer feedback platform. In reality, the product needed to support two completely different audiences with very different expectations.

Businesses wanted a platform that could simplify campaign management, reduce operational effort, and provide reliable research data. Participants, however, expected a fast, rewarding, and effortless experience that made joining campaigns and completing surveys feel worthwhile.

Balancing these expectations became one of the biggest design challenges. Every additional step introduced into the participant journey risked reducing completion rates, while oversimplifying the business experience could limit the platform's flexibility. Finding the right balance between operational functionality and ease of use became a recurring theme throughout the design process.

Another challenge was designing three connected products at the same time. Decisions made for the website influenced the dashboard, while interactions designed for the dashboard often affected how users experienced the mobile application. Instead of thinking about individual screens, I approached the project as one interconnected ecosystem where consistency was just as important as usability.

Design Goals

From the beginning, the objective wasn't simply to create attractive interfaces. The focus was to design an experience that people could understand quickly, navigate confidently, and continue using without unnecessary friction.

Several principles guided every design decision throughout the project.

The first was clarity. Research campaigns, surveys, reservations, and rewards involve multiple steps, so the interface needed to communicate progress clearly without overwhelming users.

The second was efficiency. Whether a business was creating a campaign or a participant was completing a survey, every interaction was reviewed to remove unnecessary complexity and reduce the number of decisions users had to make.

The third principle was consistency. Since the product existed across a marketing website, dashboard, and mobile application, maintaining a unified visual language became essential. Components, typography, spacing, interaction patterns, and navigation were designed as part of a shared system rather than independently for each platform.

Finally, the platform needed to be designed with growth in mind. As new campaign types, product categories, and research features were introduced, the experience had to remain scalable without requiring significant redesigns.

These principles became the foundation for every decision that followed, from the earliest wireframes to the final implementation.

Looking Ahead

With the overall product vision established, the next phase focused on understanding the people behind the platform. Before designing interfaces, I needed to understand how businesses planned research campaigns, how participants discovered and joined them, and where friction was most likely to occur throughout the journey.

Rather than jumping directly into visual design, the project began with stakeholder discussions, competitor research, and journey mapping to ensure every design decision addressed a real business or user need.

Understanding the Problem

Designing Nasil Sence wasn't about improving an existing product—it was about creating an entirely new ecosystem around a business idea. While the vision of connecting brands with consumers through product research was clear, the experience itself was still evolving. There wasn't an established workflow to follow, which meant every decision had to be validated through discussions, research, and continuous iteration.

Before opening Figma, I spent time understanding how consumer research traditionally works and where the existing process creates friction for both businesses and participants. The objective wasn't to redesign research itself, but to remove the operational complexity that often makes research campaigns slow, expensive, and difficult to manage.

For businesses, running a campaign typically involves coordinating participants, tracking submissions, validating responses, and organizing results across multiple tools. For participants, the process can be equally frustrating, with lengthy forms, unclear instructions, inconsistent communication, and very little transparency about what happens after they submit feedback.

The challenge was to simplify both experiences without oversimplifying the product. Businesses still needed powerful management tools, while participants needed an experience that felt quick, intuitive, and rewarding.

Discovery & Research

The project began with stakeholder workshops to understand the business vision, campaign workflow, operational requirements, and long-term product goals. Since the platform was being built from scratch, these conversations became the foundation for defining both the product architecture and the overall user experience.

Alongside stakeholder discussions, I explored existing research platforms, survey products, and reward-based participation systems to understand how similar products approached campaign management, participant engagement, and feedback collection. Rather than copying existing patterns, the goal was to identify opportunities to simplify the experience while creating something that felt more modern and approachable.

One important realization during this phase was that the platform wasn't solving a single problem—it was balancing two completely different journeys that constantly influenced one another. Every improvement made for businesses could potentially introduce friction for participants, and every simplification for participants had to preserve the quality of the data businesses relied on.

This understanding shaped the product from the very beginning.

Understanding the Users

Although the platform serves many different industries, the product ultimately revolves around two primary user groups.

The first group consists of businesses that want to validate products before or after launching them. These users are focused on creating campaigns, assigning products, monitoring participation, reviewing survey responses, and extracting meaningful insights. Their priority is efficiency. They need powerful tools, but they also expect those tools to remain easy to manage as campaigns grow larger.

The second group consists of participants who use the mobile application to discover available campaigns, reserve products, complete surveys, upload purchase information when required, and receive rewards for contributing honest feedback. Their motivation is entirely different. They want an experience that feels effortless, transparent, and worth returning to.

Designing for these two audiences meant every workflow had to answer a simple question: Does this make the process easier without reducing trust or quality?

Mapping the Experience

Once the user groups were defined, I mapped the complete product journey to understand how every platform connected together.

The experience begins with a business creating a research campaign through the dashboard. Campaign details, eligibility, product information, participant limits, and survey requirements are configured before the campaign becomes available to users.

Participants discover the campaign through the mobile application, review its details, reserve a place if eligible, complete the required tasks, submit their responses, and receive rewards after successfully finishing the research.

Meanwhile, businesses can monitor participation in real time, review incoming feedback, track campaign progress, and generate reports without relying on manual coordination.

Mapping this complete journey early in the project made it much easier to identify where information needed to move between the dashboard, mobile application, and backend systems. Instead of designing isolated screens, every interface became part of one connected workflow.

Defining the Product Architecture

With the overall journey established, the next step was organizing the platform into clear functional areas.

The marketing website was designed to introduce the product, explain how the platform works, showcase its capabilities, and build confidence for potential business clients.

The administrative dashboard became the operational center of the product. It included campaign management, participant management, analytics, reports, billing, notifications, product assignment, and administrative settings. Since businesses spend extended periods working within the dashboard, usability and information hierarchy became major priorities throughout the design process.

The mobile application focused entirely on participant engagement. Every screen was designed to reduce friction—from browsing campaigns and booking available products to completing surveys and tracking participation history. The mobile experience intentionally minimized unnecessary complexity while maintaining enough flexibility to support different campaign types.

Separating responsibilities across these three products created a clearer mental model for users while ensuring every platform could evolve independently without breaking the overall ecosystem.

Design Principles

As the product continued to evolve, I established several design principles that helped maintain consistency across every decision.

The first principle was reducing cognitive load. Whenever users were presented with forms, survey questions, campaign information, or analytical data, the interface was structured to reveal information progressively instead of displaying everything at once. Breaking complex tasks into smaller, manageable steps helped users stay focused and reduced the feeling of being overwhelmed.

The second principle was transparency. Users should always understand where they are in the process, what information is required, and what happens next. Whether reserving a product or reviewing campaign analytics, clear progress indicators and straightforward communication became an important part of the overall experience.

Another guiding principle was scalability. The product was expected to grow over time with new campaign types, additional product categories, and more advanced reporting capabilities. Rather than designing for the current requirements alone, I focused on creating reusable components and flexible layouts that could support future expansion without requiring a complete redesign.

Finally, consistency became the thread connecting every platform. Typography, colors, spacing, interaction patterns, and components were treated as a shared design language rather than individual decisions. This not only improved the user experience but also made collaboration with developers more efficient throughout implementation.

From Research to Design

By the end of the discovery phase, the product had transformed from a collection of ideas into a structured ecosystem with clearly defined users, journeys, and objectives. Instead of asking what each screen should contain, the focus shifted toward designing experiences that felt intuitive from start to finish.

With the research complete and the product architecture established, the next phase focused on translating these insights into wireframes, user flows, and interface explorations that would eventually become the foundation of the final website, dashboard, and mobile application.

Designing the Experience

With the product strategy established and the overall ecosystem mapped, the focus shifted toward transforming ideas into tangible experiences. Since Nasil Sence was being built from scratch, there were no existing design patterns or interfaces to improve. Every screen, interaction, and workflow had to be thoughtfully designed while ensuring the experience remained consistent across the website, dashboard, and mobile application.

Rather than designing individual screens in isolation, I approached the project by designing complete user journeys. Every interaction was connected to the next, allowing users to move naturally through the platform without feeling lost or overwhelmed. This approach helped maintain consistency while reducing unnecessary complexity throughout the product.

The design process was highly iterative. Early concepts were discussed with stakeholders, refined based on developer feedback, and continuously improved during implementation. Instead of following a linear design process, the product evolved through multiple cycles of designing, testing, reviewing, and refining.

Information Architecture

One of the biggest challenges was organizing a large amount of functionality into a structure that felt simple and intuitive.

The dashboard alone contained campaign management, participant management, analytics, reporting, billing, product assignment, notifications, administrative settings, and several supporting workflows. Presenting all of this information without overwhelming users required careful planning of the navigation and page hierarchy.

I started by grouping related features together and identifying the primary tasks businesses perform most frequently. This allowed the interface to prioritize everyday actions while keeping secondary functionality easily accessible without cluttering the workspace.

Instead of forcing users to navigate through multiple layers of menus, the dashboard was designed around clear navigation patterns that reduced the number of clicks required to complete common tasks.

For participants using the mobile application, the structure was intentionally much simpler. Their primary goal was not managing research but participating in it. Every screen was designed around a single action, allowing users to browse available campaigns, reserve products, complete surveys, and track rewards without unnecessary distractions.

Wireframing & Early Exploration

Before focusing on visual design, I explored multiple wireframe variations for the core user flows. This stage allowed me to experiment with layouts, information hierarchy, and interaction patterns without being influenced by colors or branding.

Creating low-fidelity wireframes helped identify usability issues early in the project while making stakeholder discussions more productive. Since changes during this stage are significantly easier than modifying high-fidelity designs, many structural improvements were made before visual design began.

Several iterations focused on simplifying campaign creation for businesses while reducing the number of steps participants needed to complete research. Every screen was evaluated based on one question: Does this help users complete their task faster and with greater confidence?

This iterative process established a strong foundation before moving into interface design.

Designing the Marketing Website

Although the dashboard and mobile application handled the platform's core functionality, the website served an equally important role. It became the first impression for potential business clients and needed to communicate the platform's value clearly within a short amount of time.

Rather than overwhelming visitors with technical information, the website was designed to tell a simple story. It explains what the platform does, how the research process works, the industries it supports, and the value businesses receive by collecting authentic consumer feedback.

Visual hierarchy played an important role throughout the website. Sections were structured to guide visitors naturally from understanding the product to exploring its capabilities and eventually taking action. Clean layouts, consistent spacing, and modern visuals helped reinforce trust while maintaining a professional appearance.

Because the website represented the entire product ecosystem, maintaining visual consistency with the dashboard and mobile application became a key consideration throughout the design process.

Designing the Dashboard

The dashboard became the operational heart of the platform and one of the most complex parts of the project.

Businesses needed access to large amounts of information without feeling overwhelmed. They needed to create campaigns, assign products, monitor participant activity, review responses, analyze campaign performance, manage notifications, configure platform settings, and generate reports—all from one interface.

To support these tasks, I focused heavily on information hierarchy. Frequently used actions were given greater visual priority, while supporting tools remained accessible without competing for attention.

Large datasets were presented using cards, tables, filters, graphs, and clear status indicators to make information easier to understand at a glance. Instead of requiring users to search through multiple screens, related actions were grouped together to create smoother workflows.

Every dashboard page was designed to balance functionality with simplicity, ensuring that experienced users could work efficiently while new users could learn the platform without extensive training.

Designing the Mobile Experience

The mobile application became the primary touchpoint for participants and required a very different design approach.

Unlike business users, participants were not interested in managing campaigns or analyzing reports. Their objective was simple: discover opportunities, participate in research, complete surveys, and receive rewards.

This meant every interaction needed to be fast, intuitive, and engaging.

Navigation was kept intentionally lightweight, allowing users to move between available campaigns, active participation, completed research, notifications, and profile settings with minimal effort.

Forms and surveys were designed to feel manageable by breaking long tasks into smaller sections instead of presenting everything at once. Clear progress indicators reassured users that they were moving toward completion, helping reduce fatigue during longer research sessions.

Throughout the mobile experience, the focus remained on minimizing friction while maintaining enough flexibility to support different campaign requirements.

Building a Unified Design System

Designing three platforms simultaneously made consistency one of the project's highest priorities.

Rather than creating separate visual languages for the website, dashboard, and mobile application, I developed a shared design system that established consistent rules for typography, colors, spacing, buttons, form elements, cards, icons, navigation patterns, and reusable components.

This system ensured that users experienced the same visual language regardless of which platform they were using.

Beyond improving consistency, the design system also streamlined collaboration with developers. Reusable components reduced implementation inconsistencies, simplified design updates, and allowed new features to be introduced more efficiently throughout development.

As the project evolved over several months, this shared foundation became increasingly valuable, supporting continuous iterations without sacrificing visual cohesion.

Designing for Scale

One important consideration throughout the project was preparing the platform for future growth.

Consumer research platforms naturally evolve over time as new campaign types, industries, reporting tools, and participant experiences are introduced. Instead of designing only for the immediate requirements, I considered how each screen and component could adapt as the product expanded.

Layouts were designed with flexibility in mind, navigation structures allowed room for additional modules, and reusable components made it easier to introduce new functionality without disrupting the overall experience.

Designing for scalability from the beginning helped create a stronger long-term foundation while reducing the need for major redesigns as the platform matured.

Transition to High-Fidelity Design

By the end of this phase, the product had evolved from research and wireframes into a complete, connected design system spanning more than 160 screens across the website, dashboard, and mobile application.

With the structure, navigation, and user journeys established, the next stage focused on refining the experience through visual polish, usability testing, implementation feedback, and continuous iteration as the product moved closer to launch.