BragBook
Track work wins as they happen
Documenting your accomplishments is tedious and easy to deprioritize, so the work that drives promotions and raises often goes unrecorded. As the founder and lead product designer, I created BragBook, a tool purpose-built for tech professionals that makes capturing them effortless and quickly turns everyday work into clear proof of your impact.
- Role
- Founder, Product Designer
- Years
- 2025-2026
- Scope
- Strategy, UI/UX Design, 0 to 1
Challenge
Important and impactful work is easy to lose track of. By the time the review cycle or interviews come around, months of it are hard to recall, and the rough notes that do exist aren’t ready to show anyone. The challenge was to make capturing accomplishments fast and easy, and to turn those notes into clear, usable career content.
Impact
0+
Users
0+
Entries Logged
0+
Site Impressions
Collaboration
As the founder and sole designer, I owned every product and design decision throughout the process, then designed and developed the entire app myself in four months.
Identifying Target Users
I focused on the four roles I know best. I’ve spent my career on big tech teams as a designer working alongside researchers, product managers, and engineers, and I’ve seen the same problem in all four. To better understand them, I reached out to some industry contacts in each of these roles.
Role 1
Designers
My own role. The work is visible, but the reasoning and results behind it often go undocumented.
Role 2
Product Managers
Constantly shipping work across various tickets and launches, but the true impact story often gets skipped.
Role 3
Software Engineers
Commits and pull requests capture the code they shipped, but big-picture impact is quite often missed.
Role 4
Researchers
Their research shapes what gets built, but that influence often goes uncaptured as their real impact.
Role 1
Designers
My own role. The work is visible, but the reasoning and results behind it often go undocumented.
Role 2
Product Managers
Constantly shipping work across various tickets and launches, but the true impact story often gets skipped.
Role 3
Software Engineers
Commits and pull requests capture the code they shipped, but big-picture impact is quite often missed.
Role 4
Researchers
Their research shapes what gets built, but that influence often goes uncaptured as their real impact.
Research & Planning
I interviewed tech professionals about how they track their work and where it breaks down, then synthesized those conversations into the core needs the product had to address. From there I mapped the key features and where each would live, giving the product a clear structure before design started.
Initial Wireframes
These wireframes were a good starting point, covering the core structure and meeting basic requirements. However, the structure and flow felt like something I could improve, the pieces were there, but they didn’t connect as clearly or intuitively as they needed to. A good foundation, and enough to work off of and improve.
Final Design Direction
The final direction landed on a lightweight timeline, closer to Bluesky or Twitter than a traditional productivity tool. It made accomplishments read as a clean, scannable feed you can take in at a glance, and it’s familiar by design, people already know how to read a timeline, so there’s nothing to learn.
Key Experiences
Key Experiences
Timeline
Accomplishments live in a clean, scannable feed structured like a social timeline, making a full history of work easy to build up over time and read back at a glance.
Adding Entries
Quick notes become structured entries, with AI that drafts them into polished impact statements, so a rough thought captured in the moment turns into something clear and usable later.
Generating Career Content
Tracked accomplishments become the raw material for summaries, self-reviews, resume bullets, and LinkedIn posts, generated from work already logged rather than written from scratch.
Automatic Import
Completed work imports automatically from GitHub, Linear, Jira, Asana, and Dovetail, keeping entries current.
Sharing
An optional public profile gathers accomplishments in one place to share with managers, recruiters, or a professional network, and stays private until it’s deliberately shared.
Focus on Mobile Experience
Most competing tools ignore mobile, but logging an entry the moment it happens is something people often do from their phones. So I built a dedicated mobile experience designed for quick, in-the-moment capture, not a scaled-down desktop view.
Marketing Website
The marketing site needed to explain the product and convert visitors into signups. BragBook does a lot, capture, AI generation, integrations, sharing, so I led with the core idea and broke the rest into focused feature sections with product visuals. That kept it easy to understand without overwhelming website visitors.
Technical Workflow Using AI
This is the technical workflow behind BragBook. I designed and planned everything in Figma, did the coding work with Claude Code, directing and reviewing as the code comes together. From there, GitHub holds the source, Supabase manages the data and auth, and Vercel deploys the live product to the users.
