Guide

Glue work: how to get credit for the work nobody sees

Updated November 2026 · by Jerry Liu, Dayflow's founder

Get credit for glue work by recording it as it happens, writing each item as an outcome, and putting it in front of your manager weekly, not just at review time. A paper log or notes file wins for most people. A weekly status update makes it visible. Dayflow, a free Mac app, helps if you forget to log, because it builds a timeline from your screen automatically.

You spent Tuesday morning figuring out why the new hire’s local setup kept failing, then rewrote the setup guide so the next person would not hit the same wall. After lunch you joined another team’s planning call because you were the only one who remembered why the API works the way it does. Between those, you answered a steady trickle of questions in chat, nudged a stalled decision along, and flagged a launch-date problem before it turned into one.

By Friday your board shows one ticket moved. Then review season arrives, the form asks what you delivered, and you stare at a blank box trying to remember a year of work that left no artifact behind. The people you helped remember it vaguely. You remember it vaguely. The work was real, but the record is not.

That work has a name, glue work, and this guide covers why it slips out of view, seven things to try (most need only paper and a calendar), and how to turn it into something a manager can see. Dayflow, the Mac app that publishes this blog, comes up once near the end. Details about Dayflow come from its own documentation as reviewed on 2026-09-06.

The short version

Why does glue work go unnoticed?

Glue work goes unnoticed for a few plain reasons, and none of them mean you are bad at your job or bad at self-promotion.

It has no artifact. A shipped feature has a pull request, a demo and a launch note. Unblocking three teammates has nothing. Most review systems are built around things you can point to, so work without a pointer falls through.

Its success looks like nothing happening. When you catch a problem early, the result is the absence of a crisis. Nobody notices the fire that never started, including you.

It is scattered. Glue tends to come in five- and fifteen-minute pieces spread across chat, calls, docs and hallway conversations. Each piece feels too small to mention. Added up over months, it can be a large share of your week.

You forget it too. Many people find that when they try to list what they did last month, the planned work comes back easily and the reactive work does not. If you cannot remember it, you cannot claim it.

Somebody has to do it. On many teams, glue lands on whoever is reliable, approachable or newest, and it keeps landing there because it gets done. That is not a personal failing. It is how unowned work finds an owner.

The fixes below go after these causes directly: a record, better wording, regular visibility, and an explicit agreement about what counts.

1. Keep a running glue log

What to do. Pick one place you already look every day: a paper notebook on your desk, a pinned notes file, or a copy of the daily work log template. Each time you finish a piece of glue, write one line: the date, what you did, and who it helped. Do not polish it. Speed is the point.

If you forget during the day, add a fixed slot. A kitchen timer or a recurring calendar block at 4:45 pm, five minutes long, titled “What did I unblock today?” works for many people.

Illustration. A Thursday entry might read:

How to tell after a week. Count the days with at least one line. If it is most of them, the habit is holding. If the log is empty but you know you helped people, the capture point is in the wrong place. Move it somewhere you look more often, or switch to the end-of-day slot.

2. Rewrite each item as an outcome

What to do. Once a week, take your log and rewrite the best few lines in this shape: what was wrong, what you did, what changed. If you cannot name a change, ask the person you helped, or note the risk you removed.

Activity words like “helped,” “supported” and “was involved in” are easy to skim past. Outcome words give a reader something to weigh.

Illustration.

How to tell after a week. Read your rewritten items to someone outside your team, a friend or partner works fine. If they can explain back why each one mattered, the wording is doing its job. If they say “so you went to a meeting,” add the outcome.

3. Put glue in your weekly update

What to do. If your team already shares weekly updates, add a short, consistent section for glue. If it does not, send your manager a brief note each Friday anyway. The guide to writing a weekly status report covers the full format, and the weekly status report template gives you a starting point.

Keep the glue section to two or three outcome-shaped lines. Title it something neutral and specific, such as “Unblocking and coordination,” so it reads as part of the job rather than a plea for notice.

Illustration. A Friday note might end with:

Unblocking and coordination

  • Got design and backend aligned on error states, unblocking the checkout work
  • Updated the incident runbook after Tuesday’s outage, now matches the current alerting

How to tell after a week. Watch for any response that refers to those lines: a question, a thank-you, a follow-up in your one-on-one. After three or four weeks, the real test is whether your manager mentions glue work without you raising it first.

4. Ask your manager which glue counts

What to do. Book part of your next one-on-one for this. Bring a short list from your log and ask two direct questions: Is this the work you want from me at my level? How will it show up in my review?

You are not asking for praise. You are asking for an agreement. Some glue will be valued and may even be what your role needs. Some will be seen as nice but off-target. Knowing which is which is worth more than doing more of either.

Illustration. You might say: “Over the last month I’ve spent a fair amount of time on onboarding and keeping the billing team in sync with us. I want to check that’s where you want my time, and how it should appear in my self-review. Here are the main items.”

How to tell after a week. You should leave with a clear answer for at least one category, such as “onboarding counts, keep doing it” or “let the billing sync rotate.” If the answer is vague, write down what you heard and send it back in a short message: “Just to confirm, you’d like me to keep onboarding and hand off the cross-team sync.” A written summary turns a vague answer into something both of you can refer to later.

5. Let the people you helped speak for you

What to do. Glue work is easier to credit when someone other than you describes it. When a person thanks you, ask if they would mention it to your manager or in the peer feedback round. Most people are glad to, and many simply did not think of it.

Make it reciprocal. Agree with one or two trusted peers to name each other’s glue in public channels and peer reviews. A short note in the team channel (“thanks to Sam for catching the migration clash”) creates a record that your log alone cannot.

Illustration. After a teammate says “you saved my week with that deploy walkthrough,” you reply: “Glad it helped. If you’re writing peer feedback this cycle, a line about it would genuinely help me.”

How to tell after a week. Look for one public mention of your glue work that you did not write yourself. Over a review cycle, check whether peer feedback names specific glue items rather than general niceness.

6. Hand off or time-box the glue nobody will reward

What to do. After the conversation with your manager, sort your glue into three piles: counts, essential but unrecognized, and neither. Keep the first. For the second, propose a rotation, write a doc so the knowledge stops living only in your head, or ask for it to be formally assigned. For the third, step back gradually.

For glue that keeps expanding, give it a fixed container on your calendar: office hours twice a week, a single daily window for questions. If recurring meetings are the problem, the meeting cost calculator can help you put a rough number on a standing call before you suggest changing it.

Illustration. You notice you answer the same setup questions every few days. You turn the answers into a short FAQ doc, pin it in the channel, and offer a 30-minute Tuesday slot for anything it does not cover.

How to tell after a week. Compare your log against the week before. Fewer interruptions, more time on the work you are evaluated on, and no sense that things are falling apart behind you means the change is holding. If things are falling apart, that is a strong signal the glue was essential, and evidence for getting it formally recognized.

7. Bring it all to review season

What to do. When the review form opens, you should not be starting from memory. Pull your log, your weekly updates and any public thanks into one document. Group items under the headings your review form uses, such as impact, collaboration or leadership. The performance review prep guide walks through the rest.

Illustration. Under “Collaboration” you list: rewrote the setup guide and new hires now start in a day, aligned design and backend on error states for checkout, caught the billing migration clash before launch. Each item has a date and, where possible, a name.

How to tell it worked. In the review conversation, your glue items get discussed as contributions, not skipped. If they still get skipped, go back to step 4 with that specific example.

Where seeing your actual day helps

Every step above depends on a record, and the record is the part people struggle with most. You mean to log the unblocking, then the next interruption arrives. By Friday, half of it is gone. If you have ever looked at a week and asked where did my day go, you know the feeling.

Dayflow is a Mac app that captures your screen at one frame every 10 seconds and has AI write the day into a readable timeline. You do not start or stop anything. The recordings and timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. You can also send selected screenshots to your own cloud provider or use Dayflow Pro. The local and cloud processing page explains the difference.

For glue work, the useful part is the gaps it fills. The afternoon you could not account for turns out to be a long chat thread with a teammate, an edited runbook, a call with another team. You can export a date range as Markdown and turn it into log entries or a weekly update. The AI summaries can miss or misread work, so check each item before sharing it.

Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month, and it needs macOS 14 or later. Dayflow publishes this article.

Where Dayflow is the wrong pick

You are not on a Mac. Dayflow runs only on macOS 14 or later. A paper log works on every platform.

Your glue happens away from the screen. Hallway conversations, phone calls and in-person onboarding do not appear. Dayflow can show that you were in a video call app for 40 minutes, not what you said or decided. For many people the most valuable glue happens here, and a notebook wins.

You need team-wide visibility. Dayflow has no team reports. If a team wants to recognize glue work across everyone, a label or column in the tracker your team already shares does that better.

You want a coach or a blocker. Dayflow is a record. It will not tell you to stop answering questions, will not block distracting sites, and will not argue your case in a review. Steps 4 through 6 are yours to do.

Your employer restricts screen recording. Work screens hold colleagues’ messages and company data. Check your company’s policy before running any screen recorder on a work machine. Cloud analysis also sends selected screenshots off your Mac, so use local AI if that matters.

You need billing or payroll. Dayflow does not provide invoices or payroll approvals. If you are comparing options for that, start with this roundup of Mac time trackers.

The bottom line

Glue work is real work that leaves no trace unless you leave one for it. Write it down the day it happens, describe what changed, show it to your manager every week, and get an explicit answer about which parts count. Let the people you helped say so in public. Hand off what nobody will reward.

Start today with one line in a notebook about something you unblocked this week. If you keep forgetting to write those lines, an automatic record can fill the gaps, but the habit of naming your work matters more than the tool you use to remember it.

Frequently asked questions

What is glue work?

Glue work is the work that holds a team together but rarely appears in a ticket or a launch announcement. Examples include onboarding new people, unblocking teammates, writing the doc nobody owned, running retros, chasing decisions across teams and noticing problems early. It matters to how a team performs, but because it produces no single artifact, it is easy for everyone, including the person doing it, to forget it happened.

How do I put glue work on my performance review?

Write each item as an outcome with a before and after, not as an activity. Instead of "helped onboard new hires," write "rewrote the setup guide, and the next two hires were committing code in their first week instead of their second." Group items under the themes your company's review form uses, and pull them from a log you kept during the year rather than from memory.

Is glue work bad for my career?

Not by itself. It becomes a problem when it is invisible, unrewarded, or crowds out the work your role is actually judged on. The fix is usually a conversation with your manager about which glue counts for your level, plus a habit of recording it. Some glue is worth handing off or time-boxing if nobody is going to recognize it.

How do I tell my manager I'm doing a lot of glue work without sounding like I'm complaining?

Bring a short list of specific items and ask a question rather than making a complaint. For example: "I've spent a good part of the last month on onboarding and cross-team coordination. Is that the work you want from me at this level, and how should it show up in my review?" A concrete list and a genuine question keep the conversation practical.

How do I keep track of small things I do at work every day?

Keep one running log in a place you already open, such as a paper notebook, a pinned notes file or a daily work log template. Write one line the moment you finish something, or set a fixed five-minute slot at the end of the day. If you often forget to log, an automatic record of your screen, such as Dayflow on a Mac, can fill in what you missed.

Can Dayflow track glue work for my whole team?

No, and for team-wide visibility another tool beats it. Dayflow has no team reports. It is a personal Mac app that records one person's screen. If a team wants to see glue work across everyone, a shared tracker your team already uses, with a label or column for coordination and support work, is the better choice.

Does Dayflow capture meetings and hallway conversations?

Only what appears on your Mac's screen. A video call on your Mac shows up in the timeline as time in that app, but Dayflow does not know what was said or decided. Conversations in person, calls on your phone and anything away from the computer are not recorded, so you still need a quick note for those.

Is Dayflow free?

Dayflow costs $0 and is MIT licensed. There is an optional Pro plan at $20 a month, in which Dayflow manages cloud analysis of selected screenshots. You can also run analysis with local AI on your Mac or with your own cloud provider, whose own charges and terms apply. It requires macOS 14 or later.

Should I stop doing glue work?

Usually not all of it. Some glue is the reason your team works, and doing it well is a real skill. Sort it instead: keep the glue your manager agrees counts, hand off or rotate the rest, and time-box anything that keeps expanding. If none of it is recognized after an honest conversation, that tells you something useful about the team.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required