Abhay Pratap Mishra

@abhay • 1 months ago

Brutally Honest Review of How I Actually Spent My Week

Paste your stated priorities and a rough log of your week; get a no-flattery audit of where the hours went and the patterns you are avoiding.

At a glance

Best for: Anyone who ends the week busy but unsure they moved their real goals, and wants a blunt time audit instead of a pep talk.
Tested on: Claude · Opus 5.5
You fill in: prioritiesweek_log
You get: Verdict No. Three priorities, and this week served roughly one of them, and that one ran in the wrong direction. Where the time went (30.5 logged… (full result below)

productivity

personal-growth

career

Prompt

Be my brutally honest reviewer. Compare what I say matters with where my time actually went this week.

My stated priorities: {{priorities}}

My week, as honestly as I can reconstruct it (with rough hours): {{week_log}}

Rules:

• No reassurance and no compliments unless a specific line in the log earns them.

• Do not write "it's great that", "be kind to yourself", "you've got this" or anything similar.

• Every criticism must point to a specific entry in my log.

• If the log is too vague to judge something, say "can't judge from the log" instead of guessing.

• Add up the hours yourself and show the totals, so I can check your math.

Output, in this order:

1. Verdict: one sentence. Did this week serve my priorities: yes, partly or no?

1. Where the time went: hours and % per priority, plus one "everything else" bucket, with how you assigned items.

1. Three patterns I'm avoiding looking at: each with the evidence from the log.

1. Next week: one thing to stop, one to start, one to protect.

1. The question I should be asking myself: one line.

Fill in

{{priorities}}: The 2-4 goals you have said matter most this month or quarter.e.g. 1) Ship onboarding v2 by Oct 15. 2) Do 5 customer interviews. 3) Stop being the code-review bottleneck.
{{week_log}}: Day-by-day list of what you did, with rough hours. Honest beats neat.e.g. Mon: 3h reviewing 11 PRs, 1h onboarding wireframes, 2h Slack/email...

Example input

priorities: 1) Ship the onboarding v2 flow by Oct 15. 2) Complete 5 customer interviews this month. 3) Stop being the bottleneck on code review for my team.

week_log:
Mon: 1.5h standup + syncs; 3h reviewing 11 PRs; 1h onboarding wireframes; 2h Slack/email.
Tue: 4h fixing a billing bug another team owns (I volunteered); 1h of 1:1s; 1.5h Slack.
Wed: 2h all-hands + prep; 2.5h PR reviews; 0.5h drafting the customer interview outreach email (not sent yet); 1h onboarding API work.
Thu: 3h onboarding API work (good focus); 2h interviewing a candidate for our team; 1h PR reviews.
Fri: 2h reorganizing our Linear board; 1.5h reading about the new model releases and trying them; 1h PR reviews. Left early.

2.4k0

Generated Outputs (1)

2 hours ago

Claude

Opus 5.5

2 hours ago

Generated Output

1. Verdict
No. Three priorities, and this week served roughly one of them, and that one ran in the wrong direction.

2. Where the time went (30.5 logged hours)

• Onboarding v2: 5h (Mon 1, Wed 1, Thu 3), 16%

• Customer interviews: 0.5h, an email drafted and not sent, 2%

• Code review: 7.5h (Mon 3, Wed 2.5, Thu 1, Fri 1), 25%. This is the priority you said you wanted to do less of personally.

• Everything else: 17.5h, 57%: billing bug 4, meetings and all-hands 4.5, Slack/email 3.5, hiring interview 2, Linear reorg 2, reading about models 1.5

How I assigned items: one bucket per item, your hours as written. The hiring interview is real work, but it serves none of your three stated priorities. The 1:1s: can't judge from the log whether they moved anything.

3. Three patterns you're avoiding

• You fill avoidance with useful-looking work. The interview outreach email was drafted Wednesday and never sent. Friday then got 2h of board reorganizing and 1.5h of reading. Both are defensible, and neither is the thing you're dodging. Sending one email is a two-minute task, and it is currently blocking an entire priority.

• "Stop being the bottleneck" has become "be a faster bottleneck." You reviewed 11 PRs on Monday alone and did review on four of five days. Reviewing more doesn't reduce the team's dependency on you. Nothing in the log shows you handing review to anyone else.

• You volunteer for rescues. You gave Tuesday's 4h to another team's bug, by your own offer. That is more than onboarding got on any day except Thursday. Oct 15 is three weeks away, and at 5h a week you only ship if the remaining work is small. Your log doesn't say how much is left, and that gap is its own warning.

4. Next week

• Stop: volunteering to fix other teams' incidents. Offer 30 minutes of pairing, not the fix.

• Start: send the outreach email on Monday before opening Slack, and name two teammates who can approve PRs without you.

• Protect: Thursday-style blocks. Three uninterrupted hours gave you your best day. Book two more of them before anyone else books that time.

5. The question
What would I have to let someone else do imperfectly for a while so that I can ship onboarding?

Why it works

The prompt makes the model count before it judges: "add up the hours yourself and show the totals" turns a vague vibe ("I was busy") into a checkable split, and the split is usually the whole story.

"Every criticism must point to a specific entry" blocks the generic productivity advice models default to, and the banned-phrases line removes the reassurance reflex. Asking for patterns you are avoiding pushes it past "you had too many meetings" toward the uncomfortable stuff, like drafting an email and not sending it. "Can't judge from the log" gives the model permission to admit gaps instead of inventing them. Ending on one question gives you something to carry into Monday rather than a list you will skim.

When not to use it

It is only as honest as your log. If you reconstruct the week from memory on Friday night, the hours will be flattering and so will the review. Keep a rough running log for a week first. Skip it in a week that was genuinely derailed by illness or a crisis; a time audit of a bad week just produces guilt. It judges time, not quality of output.

Comments (0)

No comments yet. Be the first to share your thoughts!