For people and communications teams

Recognition should be specific enough that only one person or team could receive it

Fireside finds verifiable work in the systems your company already uses, then drafts recognition that names the contribution and its effect. A human confirms or adds the credit before anything is published.

The swap test, applied to real work

The Better Recognition swap test asks whether the same praise could be sent to someone else unchanged. The longer guide explains how to ground recognition in evidence without automating judgment.

Generic shout-out
TEAM UPDATE

Great work, platform team! Your dedication and collaboration made a real difference. We are lucky to have such talented people driving us forward.

This could be sent to almost any team.
→
Reviewed draft · credit added by a human
LinkedIn
Sean put a stopping rule around a GitHub source that could not recover on its own.

After three consecutive 404s, Fireside now disables the source and tells the operator what to fix. A successful fetch resets the count, while timeouts and server errors are handled separately.

That ends the repeated fetches and the same once-a-day Slack alert. Thank you, Sean, for turning a recurring failure into a clear operator action.
Work details: private Fireside repo · PR #109 Sean's name comes from the commit record and still requires human confirmation before publication.

How the system handles credit

1

Find the evidence

Fireside reads the source material behind the win: a merged PR, meeting transcript, project update, or another record of work.

2

Draft the contribution

The first pass names what changed and why it mattered. If the source identifies an owner, the draft can include them. Unknowns stay unknown.

3

Confirm the credit

A manager or teammate confirms or adds the attribution, supplies context the source missed, and approves the final wording.

What makes the recognition credible

The work

Name the thing that changed. “Improved reliability” means little; stopping retries after three 404s can be checked.

The ownership

Credit the person or team that did the work, then let someone close to it correct the draft before publication.

The effect

Explain what became easier, safer, faster, or clearer. If the source does not support a result, the draft should not claim one.

Part of a bigger idea

Employee recognition is one use for a company story engine: evidence from company activity becomes a draft, then a person decides whether the attribution is fair and the detail is useful.

What is a company story engine? →

Give the work enough detail to be remembered

I connect Fireside to your sources, tune the drafts, and build the approval loop with your team.

Operated by Fireside Systems Pty Ltd, A.C.N. 695827322 · sean@fromfireside.com · Terms · Privacy