Skip to content

brag-doc-template.md

Latest commit

 

History

History
337 lines (207 loc) · 7.31 KB

brag-doc-template.md

File metadata and controls

337 lines (207 loc) · 7.31 KB

Brag Doc - Weekly Progress Tracker

Week of [Start Date] - [End Date]

Sprint/Iteration: [If applicable] Overall Status: On Track | Ahead | Behind | Blocked

This Week's Mission

Planned Goals

  • Goal 1: [Description] - Priority: High/Med/Low
  • Goal 2: [Description] - Priority: High/Med/Low
  • Goal 3: [Description] - Priority: High/Med/Low
  • Goal 4: [Description] - Priority: High/Med/Low

Why These Goals Matter

Mission Accomplished

Completed This Week

  • ✅ [Task/Goal]

    • Impact: [How did this help the team, users, or product?]
    • Skills Used: [Technologies, methodologies, soft skills]
    • Link: [PR, ticket, or doc if applicable]

  • ✅ [Task/Goal]

    • Impact: [Quantify when possible: "Reduced load time by 30%" or "Unblocked 3 teammates"]
    • Skills Used: [What did you practice or learn?]
    • Link: [Reference]

  • ✅ [Task/Goal]

    • Impact:
    • Skills Used:
    • Link:

Unexpected Wins

  • 💡 [Unexpected achievement]

    • Context: [What happened?]
    • Value: [Why it matters]

  • 💡 [Another win]

    • Context:
    • Value:

Challenges & Problem-Solving

Obstacles Encountered

Challenge Impact How I Addressed It Status
[Technical blocker, unclear requirements, etc.] [How it affected progress] [Steps taken to resolve] Resolved / In Progress / Need Help

Skills Developed Through Challenges

Blockers Needing Support

  • 🚨 [Blocker 1]
    • Impact: [How it's affecting your work]
    • What I've Tried: [Steps already taken]
    • Help Needed: [Specific ask]
    • Urgency: High / Medium / Low

Collaboration & Teamwork

Teammates I Helped

  • [Teammate Name] - [What you did to help]
  • [Teammate Name] - [What you did to help]

Teammates Who Helped Me

  • [Teammate Name] - [How they helped]
  • [Teammate Name] - [How they helped]

Cross-Team Collaboration

Learning & Growth

New Skills or Technologies

  • [Skill/Tech]: [How you learned it, how you applied it]
  • [Skill/Tech]: [Context]

Resources That Helped

  • [Resource title/link] - [What you learned]
  • [Resource title/link] - [What you learned]

Areas for Improvement

  • [Skill or area to develop]
  • [Skill or area to develop]

Code & Technical Contributions

Pull Requests / Commits

PR # Title Status Impact
#123 [PR title] Merged / In Review [What it does]

Code Reviews Given

  • [PR link] - [Teammate name] - [Brief note on feedback given]
  • [PR link] - [Teammate name] - [Brief note]

Technical Decisions Made

Meetings & Visibility

Key Meetings This Week

  • [Meeting name] - [Your contribution or key takeaway]
  • [Meeting name] - [Your contribution or key takeaway]

Presentations / Demos Given

Impact Metrics

User Impact

  • [e.g., "Feature launched to 10,000 users"]
  • [e.g., "Bug fix improved success rate from 75% to 95%"]

Team Impact

  • [e.g., "Reduced deployment time from 30 min to 5 min"]
  • [e.g., "Documented process saved team 2 hours/week"]

Business Impact

  • [e.g., "Optimization reduced server costs by $500/month"]
  • [e.g., "Improved conversion rate by 3%"]

Next Week's Focus

Priorities for Next Week

  1. Priority 1: [High-impact task]
  2. Priority 2: [Important work]
  3. Priority 3: [Secondary goal]

Preparation Needed

  • [Research, meetings, resources needed]
  • [Coordinate with teammates]
  • [ ]

Personal Reflections

What Went Well

What Could Be Better

Energy & Wellbeing

Energy Level: ⚡⚡⚡⚡⚡ (1-5 lightning bolts) Work-Life Balance: [Good / Needs attention] Notes:

Career Development Notes

Progress on Career Goals

Opportunities Identified

Templates for Common Entries

For Bug Fixes

  • ✅ Fixed [bug description]
    • Impact: [Users affected, severity]
    • Root Cause: [What caused it]
    • Solution: [How you fixed it]
    • Link: [Ticket/PR]

For Features

  • ✅ Implemented [feature name]
    • User Story: [What user need it addresses]
    • Technical Approach: [High-level how]
    • Impact: [Metrics or expected outcome]
    • Link: [PR/Demo]

For Process Improvements

  • ✅ Improved [process/workflow]
    • Previous State: [How it worked before]
    • New State: [What changed]
    • Benefit: [Time saved, quality improved, etc.]
    • Documentation: [Link]

Tips for Maintaining Your Brag Doc

Make It a Habit

  • Set a recurring time - Friday afternoon is perfect for weekly review
  • Block 15-30 minutes - It's quick once you build the habit
  • Use calendar reminders - Don't let it slip

Be Specific

  • Vague: "Worked on the dashboard"
  • Specific: "Implemented real-time updates for dashboard metrics, reducing data lag from 5 minutes to 10 seconds"

Track Small Wins Too

  • Helped a teammate debug
  • Improved documentation
  • Shared knowledge in Slack
  • These add up!

Use It Actively

  • Performance reviews - You have receipts!
  • Resume updates - Concrete accomplishments ready to go
  • Interviews - Real examples of your work
  • Manager 1-on-1s - Show your impact

Remember: Your accomplishments are worth documenting. Track your wins, learn from challenges, and build a record of your growth. You're doing great work - make sure it's visible! Excellence in All We Do!