Why U In Review
It's December. And Q1 feels like a different lifetime.
You're trying to write your annual review. You're staring at twelve months of work, and most of it has already evaporated. You can remember the last six weeks in detail. October is fuzzy. The first half of the year is a haze of meetings, projects, and outcomes you know mattered — you just can't quite reconstruct what mattered, or why.
I watched this happen to myself, and to every team I worked with. By December, the wins from January felt impossibly far away. People ended up underselling their year — not because they hadn't done the work, but because they couldn't remember the work.
That's the first reason this exists. You should get credit for all of it. Not just the last two months.
The progress you can't see day-to-day
There's a second pattern, and it's quieter.
Most days, you don't feel like you're moving. The work is incremental. The wins are partial. The big stuff is always over the next hill. It's easy to end a week thinking, what did I actually do?
But when you go back and read the weeks — really read them, week by week, month by month — something shifts. You see decisions that compounded. Conversations that turned into projects. Skills you picked up without noticing. Problems you solved so completely you forgot they used to be problems.
You were making progress the whole time. You just couldn't see it from inside the day.
Reflection, done well, is how you find the progress you've already made.
A GitHub for the rest of what you do
Here's the third idea, and it's the one I keep coming back to.
When developers want to show what they've been up to, they point to GitHub. You don't see every line of code — but you see the rhythm of someone's work. How active they are. What they're contributing to. What they're building. It's a record that speaks for itself.
Most of us don't have anything like that.
We have a résumé that flattens a year into three bullets. A LinkedIn post we never write. A vague sense that we did a lot this year, and a deep inability to say what.
U In Review is the thing in between. A quiet, ongoing record of what you actually did — the decisions, the wins, the hard calls, the things you learned. Sometimes you'll use it for yourself, before a self-review or an interview, just to remember. Sometimes you'll share a recap directly. Sometimes it'll just be there, building, the way GitHub builds in the background of a developer's life.
What this is, in one sentence
A place to capture your wins, surface your progress, and never lose another year to forgetting.
Start where you are
You don't need to have a plan. You don't need to have had an impressive week. You just need a few minutes and some honesty about what you did.
Your first weekly recap arrives in seven days. Your first monthly in thirty. And by the time next December rolls around, you'll have something most people don't: the actual story of your year, written while you were living it.
Ready when you are.
Start your review →