Users do not need more guilt. They need orientation. When a product turns sustainability into concrete, bite-sized choices, the emotional barrier drops and action becomes more likely.

That insight influenced both content structure and interface hierarchy: lead with clarity, reduce the number of competing actions, and keep each next step specific enough to feel achievable.

From these interviews I developed two primary personas that would guide my design decisions throughout the project.

Given the tight timeline, I used a Kano-style prioritization to keep the MVP focused on the core loop: scan → clear sorting guidance → map to act on the result.

Motivation and community features were treated as secondary, because they add value only after the basics work and require longer-term validation.

With features confirmed, I mapped the complete user flow. The app's architecture centered on five primary areas: the Dashboard (entry point), the Scan feature (the AI camera), the Map (recycling station locator), the Community space (forum and eco-events), and the User Profile (badges, points, and history). Onboarding, sign-up, and log-in flows fed into the Dashboard, from which users could access any core feature naturally.

The flow was deliberately simple. I wanted a user to be able to open the app, scan an item, locate the nearest recycling bin, and deposit it - all within a few taps.

For the visual language of Ecospace, I built a system grounded in clarity and warmth. I chose Inter as the typeface for its high legibility across screen sizes. The grid system used a 10-point baseline with 11pt and 22pt margins for internal elements and 17pt padding for full-screen layouts - a structure that gave the UI a sense of rhythm and order without feeling rigid.

Accessibility was not an afterthought. I evaluated the prototype against WCAG AA standards, and in my audit I identified areas where the initial contrast ratios were failing particularly for small text.

I revised those elements until both small and large text passed AA requirements. The result was a more inclusive product that maintained its visual character without compromising legibility.

User testing revealed that the original, item-centric design did not align with how people think about or perform recycling. Even after improving navigation, naming, and visual clarity, users continued to struggle because they do not conceptualize recycling as a list of scanned items. Instead, they think in terms of recycling sessions, locations, and consistency over time.

This insight led to the conclusion that incremental UI improvements were not enough. The product required a fundamental redesign of the recycling journey, shifting from item-based tracking to a session- and habit-focused experience that prioritizes speed, clarity, and behavior formation.

Users do not recycle in items - they recycle in moments.

To improve the experience, I needed to design around the whole recycling session, not a particular item.

After presenting to the hackathon jury, we received detailed feedback that shaped my thinking about the product's future. The judges challenged the reward system, arguing that points alone were not sufficient motivation. They suggested partnerships with local businesses to offer tangible rewards such as coupons, discounts, or gift cards redeemable through the app.

Another juror raised a practical issue with the scanning flow: requiring users to scan each piece of waste individually would be too time-consuming for anyone recycling more than a few items at once. A better long-term direction would be multi-item recognition from a single camera frame.

On the business model, the jury pushed us to think more seriously about monetization. They suggested a paid promotional package for local businesses wanting to showcase recycling efforts through the app, and a donation feature that would allow users to contribute to environmental organizations, with part of in-app purchases directed toward those causes.

These were the kind of challenges that do not diminish a project - they mature it.

This project was formative far beyond the product itself. Working in a cross-functional team under significant time pressure accelerated my growth across several dimensions.

I learned to collaborate across disciplines. Coordinating with a team leader, an economist, and a marketer meant translating design thinking into the language of budgets, markets, and business logic. I also strengthened my ability to communicate design decisions clearly and persuasively.

The research process gave me hands-on experience with both quantitative and qualitative methods - understanding not just what users do, but why - and taught me how to synthesize that data into actionable design decisions. The Kano Model exercise, in particular, sharpened my instinct for feature prioritization.

Finally, the hackathon's pace forced adaptability. Problems emerged that were not anticipated, and solutions had to be found quickly. That sustained pressure over three weeks is something no classroom exercise can fully replicate.

The scanning mechanic was central to the product's architecture from the beginning, but in retrospect it was a solution in search of validation. If I approached this again, I would pressure-test the core interaction model earlier and explore alternatives such as QR-code receipts issued by recycling facilities, which users could scan to confirm completed actions.

That approach would reduce friction, work within existing recycling infrastructure, and avoid the compliance burden of item-by-item scanning.

More significantly, the research revealed that a substantial portion of users were more drawn to the app's educational content than to its recycling confirmation mechanics. That is a meaningful signal about where the real product opportunity might lie, and one I would pursue more deliberately in a second iteration.

The next research focus would be habit formation rather than session-level engagement. The open question is not whether users find the app motivating in a single session, but whether the product supports consistent, repeated behavior over time.

I would design studies around long-term usage patterns, specifically looking at how the app can reinforce recycling as a routine rather than an occasional action. The variables I would prioritize are progress visibility, friction reduction in repeat interactions, and consistency cues that fit naturally into users' existing routines.

Three things stayed with me from this project.

First: users do not conform to the mental models we build for them. Designing for behavior means designing for people as they actually are, not as we assume they will respond.

Second: reducing friction does more work than increasing motivation. The simpler the action, the more likely it is to happen. Complexity, however well-intentioned, creates the conditions for abandonment.

Third: the most valuable output of research is not validation - it is the moments when data challenges the product direction entirely. That kind of challenge, taken seriously, is what separates good design from meaningful design.