The Maintenance Habit Nobody Teaches You
There's a skill nobody puts on a syllabus: keeping a usable record of your own work.
You learn project management. You learn your domain. Somewhere along the way you might learn to write a decent resume — usually in a panic, the week you need one. But the quiet discipline that makes all of that easier, the habit of capturing what you did while you still remember it, is something almost no one is taught. You're expected to just have it. Most people don't.
I didn't. I learned it the hard way, the way most people do — by reconstructing my career from memory across more than twenty engagements and realizing, every single time, how much had evaporated. Outcomes I couldn't put a number to. Projects I knew I'd led but couldn't describe with any precision. The work was real. The record wasn't.
This is the first piece in a series about what keeping a record actually looks like — not the argument for why (we covered that), but the practice of how. And the practice starts smaller than you'd think.
The habit is fifteen minutes, not a second job
The reason most people don't keep a record isn't laziness. It's that they imagine the wrong thing. They picture a sprawling personal database, a weekly journaling ritual, some system they'll have to maintain forever. That sounds exhausting, so they don't start.
The actual habit is about fifteen minutes a week. Once a week — pick a time, end of Friday works for a lot of people — you capture three things while they're still fresh:
1. What you delivered. Not what you were busy with. What actually shipped, closed, launched, or moved. The outcome, not the activity.
2. The number, if there is one. Dollar figure, percentage, headcount, timeline, volume. "Cut the close cycle from nine days to five" beats "improved the close process" every time, and you will not remember "nine to five" in eleven months.
3. The part only you'd know. The constraint you worked around. The call you made when the data was ambiguous. The thing that would be invisible on an org chart but mattered. This is the part that's gone first and matters most.
That's it. Three lines, once a week. The discipline compounds in a way almost nothing else in a career does — because every week you don't do it is a week you'll later try to reconstruct, and reconstruction is lossy.
What it looks like across different work
The habit is the same everywhere. What goes in the three lines changes by profession. Three examples from very different kinds of work:
Project / program management. A Friday entry might read: Closed the vendor migration two weeks ahead of the revised date. Held the rollback option open until cutover — the call that saved us when the data-sync lagged. Net: zero downtime on a system 400 people touch daily. Six months later, that's a resume bullet, an interview story, and a performance-review line. At the time, it was ninety seconds of typing.
Finance / analysis. Built the variance model that caught the $1.3M forecasting gap before it hit the board deck. Nobody asked for it — I noticed the trend lines didn't reconcile and dug in. The number anchors it. The "nobody asked" is the part-only-you'd-know — the initiative that never shows up in a job description but is exactly what distinguishes you from someone who only does what's assigned.
Clinical / healthcare. Redesigned the discharge handoff checklist after the third near-miss; readmissions on the unit dropped over the next quarter. Got nursing and pharmacy aligned on it, which was the actual hard part. The outcome is patient-facing and measurable. The "actual hard part" — the cross-functional alignment — is the invisible work that a year from now you'd struggle to reconstruct, and that hiring managers and review committees most want to hear.
Different fields, identical habit. Capture the delivery, capture the number, capture the part only you'd know. Fifteen minutes.
Why "while it's warm" is the whole game
Here's what makes reconstruction so costly, and why timing is everything.
Memory doesn't just fade — it flattens. A year out, a project you led for six months collapses into a single sentence: "managed the migration." The texture is gone. The ahead-of-schedule, the rollback call, the 400 daily users — all the things that made it yours and made it good — those are the first to go. You're left with a flat noun where there used to be a story.
Capturing it while the work is warm preserves the texture. You write "two weeks ahead" because two weeks ahead is still a fact in your head, not a vague sense that it went well. You write "$1.3M" because the number is right there. You can't reconstruct precision. You can only preserve it.
This is the difference between a career that's maintained and one that's reconstructed. Maintained is fifteen minutes a week of preservation. Reconstructed is a frantic weekend of excavation, six months too late, recovering maybe half of what was actually there.
Start this week
You don't need a system. You don't need software to begin. Open a note, put three headers in it, and on Friday write three lines about the week.
That's the habit. The rest of this series is about what to do with it once it's running — how the record becomes interview prep, how it becomes review ammunition, how it becomes the thing you reach for the Friday a recruiter actually calls. But none of that works without the fifteen minutes. Start there.
Your career is an asset. Like any asset, it's maintained — not reconstructed. The maintenance is smaller than you think. The reconstruction is always bigger.
Tenure is the platform built around keeping that record. It's live at owntenure.ca. 14-day trial, no credit card required.