My Wins

Inspiration

As a product designer, I spend a lot of time helping teams build products that solve real problems. But when it came to documenting my own achievements, I realized I had a problem of my own.

Whenever I updated my résumé, prepared for a performance review, or applied for a new opportunity, I found myself digging through Slack messages, emails, Figma files, GitHub pull requests, meeting notes, and screenshots, trying to remember what I had accomplished.

I wasn't forgetting because I hadn't done meaningful work. I was forgetting because there wasn't a single place to capture it.

That experience inspired My Wins.

I believe people shouldn't have to rely on memory to prove their value. They should be documenting their achievements as they happen.

What it does

My Wins is an offline-first career memory that helps professionals capture, organize, and revisit their achievements throughout their careers.

Each achievement, called a Win, becomes a complete record of what happened and why it mattered.

Users can:

Capture achievements in under a minute. Organize wins by category and project. Record measurable impact and outcomes. Attach supporting evidence such as screenshots, documents, and links. Save recognition from managers, teammates, or clients. Reflect on lessons learned. Browse a searchable career timeline. Export selected wins for interviews, promotions, performance reviews, or portfolio updates.

Instead of rebuilding your career story every time an opportunity comes along, My Wins helps you build it continuously.

How we built it

I approached this project the same way I approach every product: by understanding the problem before thinking about the solution.

I started by defining the user journey, writing a detailed product requirements document, and refining the information architecture until the experience felt simple and intuitive.

The biggest design decision was to make everything revolve around one core object: a Win.

Rather than creating separate modules for recognition, evidence, and reflection, I integrated them into each Win. This keeps the experience focused and makes every achievement a complete story instead of scattered pieces of information.

Once the product direction was clear, I designed the interface and built it as an offline-first Progressive Web App using Next.js, React, TypeScript, Tailwind CSS, shadcn/ui, and IndexedDB with Dexie.js for local-first storage.

I intentionally chose an offline-first architecture because your career history should always be available, even without an internet connection or an account.

Challenges we ran into

The hardest part of this project wasn't writing code, it was deciding what not to build.

Early versions included analytics dashboards, separate pages for recognition and evidence, and several additional features.

As I tested the product concept, I realized I was solving too many problems at once.

The breakthrough came when I simplified everything around a single idea:

Every feature should make a Win more meaningful.

That decision shaped the entire product.

Recognition became part of a Win.

Evidence became part of a Win.

Impact became part of a Win.

Reflection became part of a Win.

By reducing complexity instead of adding more features, the product became much easier to understand and much more valuable.

Accomplishments that we're proud of

The accomplishment I'm most proud of wasn't writing code, it was turning a personal frustration into a focused product.

During development, I realized I was trying to build too many features at once. Instead of continuing down that path, I stepped back and redesigned the product around a single core idea: every achievement should be captured as a Win, with its impact, evidence, recognition, and reflection all in one place.

I'm also proud of designing My Wins as an offline-first application. Users don't need an account or an internet connection to preserve their career history, making the experience private, fast, and always available.

Finally, I'm proud of creating a product that solves a problem many professionals face but rarely talk about forgetting their own achievements when it matters most. My Wins helps people build a career story backed by proof, one Win at a time.

What we learned

This project reinforced one of my strongest beliefs about product design:

Great products are usually the result of removing features, not adding them.

I also learned how important it is to define a clear product philosophy before writing code. Once I established that every feature should support a Win, product decisions became simpler, the interface became cleaner, and the development process became more focused.

Finally, building an offline-first application gave me a deeper appreciation for local-first architecture and designing experiences that work reliably regardless of internet connectivity.

What's next for My Wins

This hackathon version focuses on helping professionals capture and preserve their achievements.

The next step is to make My Wins an even more valuable companion throughout a person's career by introducing optional cloud sync, richer export options, productivity integrations, and public portfolio pages generated from selected wins.

My long-term vision is simple:

I want professionals to stop underestimating themselves because they forgot what they've accomplished.

With My Wins, every achievement is captured, every contribution is backed by evidence, and every career story is ready when opportunity comes knocking.

Built With

• dexie.js
• framer
• indexeddb
• next.js
• progressive
• react
• tailwind
• typescript