How to Actually Finish a Project When No One Is Checking on You
A practical routine for keeping your self-led project honest when the calendar has no reviewers.
Read the piece →How to ship work, manage risk, and build a reputation for follow-through.
Your first big win isn’t about brilliance. It’s about trust. The thesis of execution, in one line: deliver what you said you’d deliver, when you said you’d deliver it. Do that for six months straight and you will quietly out-earn people who are smarter but unreliable.
The technique that makes this possible is under-promising at the commit and over-communicating through the middle. Give yourself a buffer on the estimate — not because you’re lazy, but because new jobs are full of hidden work you can’t see from the outside. Then, while the work is in flight, send small, unprompted updates: what’s on track, what’s at risk, what you’re doing about it. Surprises are the enemy; early flags are a gift.
A warning about execution-as-identity. It’s possible to become the person who ships, and nothing else — head down, output up, invisible above. That’s how you plateau. Ship cleanly and also make sure the right people see it: a crisp summary in a team channel, a line in the weekly update, a demo in the staff meeting. The work speaks, but only if you give it a microphone.
How to spend 20 minutes capturing tasks, priorities, and blockers so Monday starts with clarity instead of crisis.
Stop hunting for the perfect productivity app and start using a system that actually prevents things from slipping.
Why stacking your calendar with zero gaps is a trap and how to mathematically reclaim your focus.
Stop wondering why you're working until 8 PM; use a calendar audit to expose the hidden time-sinks in your corporate schedule.
If your PM rewrites your briefs, the issue isn't writing quality. It's structure. A six-line template and the two sentences that tend to break.
Staying late doesn't signal dedication. It signals that you're behind. Here's how to manage your time so the work finishes before you do.
A simple Week 1 setup so you look competent fast: define success, build your note system, and stop guessing what matters.
A simple day-by-day plan for your first week: relationships, clarity, and one small win.
How to stop worrying if you belong and start measuring if you're actually doing the job.
Short rules for running crisp meetings: agendas, outcomes, and follow-ups — even if you're not the one in charge.
A 30-60-90 plan isn't a deliverable for your manager. It's a thinking tool for you. Here's how to build one that actually shapes your first three months.
Generic 30-60-90 plans look identical and say nothing. Here's what a specific, role-appropriate plan looks like across three different job types.
How to stay ambitious without turning your team into a zero-sum game — especially in your first 90 days.
A simple prioritization at work framework for showing what you are doing, what you are not doing, and where tradeoffs are being made.
Turn vague ambition into a plan you can execute — with examples for your first 90 days.
Stop treating Monday morning like an emergency room triage and start using a deadpan 15-minute planning routine.
A first-job guide to expense policies, gray areas, and how to stay above board without being a pain to work with.
Mistake management is about quick clarity, precise fixes, and keeping trust after the fact.
A step-by-step guide to asking the four clarifying questions that stop vague requests from hijacking your time.
A practical system new hires can use to keep their inbox predictable and avoid becoming the fallback when every request lands all at once.
A practical guide to using slow moments to build trust, skills, and momentum.
A simple structure for a one-page summary that leaders will actually read.
A practical checklist for finding quick wins in a new job without turning your first month into performance theater.
Your memory is a leaky bucket. Build a lightweight capture habit so you stop asking the same three questions twice.
This topic maps to Chapter 3 — Shipping work of the book. See the full chapter →