Career journal for

Technical Writers

Technical writing impact is the support ticket that did not get filed because the doc was clear. The deflection is invisible at any single calibration.

Bloomly is the career journal built for the moments the work actually happens, not the night before the review.

A captured day for a Technical Writer

1. 01

   9am: shipped the rebuilt auth-flow doc page.

2. 02

   12pm: pair with Marcus (eng) on his service's API spec.

3. 03

   3pm: review the doc-CI pipeline for the new spec linter.

4. 04

   5pm: information-architecture review of the docs sidebar.

What a Technical Writer captures

• Docs pages shipped and maintained
• Doc-quality metrics (deflection, satisfaction)
• Eng-team partnerships
• Doc-tooling and CI improvements
• Information-architecture work

Shipped 142 doc pages and rebuilt the API reference. Doc-deflection on support tickets 18% to 31%. Authored eng-team doc-style guide adopted across 6 services.

Promotion rubric, mapped to capture

• Documentation outcomesCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Process and toolingCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Engineering partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Information architectureCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.