The 10‑Minute Weekly Update That Replaced My Mentor Calls
I stopped chasing late mentor calls and started sending a focused, 10‑minute weekly update — the exact format that kept my growth on track and where it still falls short.
Written by: Rohan Deshpande
It was 10:15 pm on a Tuesday in Bengaluru. My mentor was five time zones away and, as usual, our call was teetering between “quick sync” and “deep, derailing one-hour chat.” My internet dipped twice that week. I had dinner waiting. He had a backlog of career advice. We both left the call with fuzzy action items and the same questions we’d had before.
That’s a terrible use of two people’s time. So I tried something small: I stopped asking for a weekly call and started sending a structured one‑page update instead. Ten minutes to write. Ten minutes for him to scan. The experiment lasted six months. It saved hours and — more importantly — forced clarity. It also exposed what asynchronous mentoring cannot replace.
Why I needed to change
I pay attention to time. My workdays in a startup are already full: async reviews, standups at odd hours, and the commuting I haven’t given up entirely. Mentor calls were supposed to be high‑leverage, but they were routinely noisy.
- Calls got scheduled when one of us could squeeze them in, often 9–11 pm IST after a day of meetings and slow Wi‑Fi.
- We would spend the first 10 minutes catching up on context that I should have written down.
- I left with fuzzy next steps and zero record I could look back on.
The worst part: the call itself made me perform. I rehearsed progress. I glossed over blockers because I didn’t want to derail the meeting. That robbed the whole point of mentorship.
The 10‑minute weekly update (the exact format)
I needed three things from mentor time: an accurate record, focused feedback on the right problems, and predictable cadence. My update has three parts and a subject line convention. It takes me at most 10 minutes to write.
Subject: [Week X] Quick Update — 2 mins to read
- One-sentence progress headline
- Example: “Deployed feature-flag rollout to 20% of users; rollback path tested.”
- Two concrete wins (what I did)
- Each bullet is one line, with a metric if possible.
- Example: “Reduced page render time by 180ms (18%) on key flows.”
- One clear blocker (what I need)
- Describe blocker, what’s already tried, and the specific ask.
- Example: “Need advice on stakeholder pushback to dark‑launch; tried doc + demo, they ask for metrics I don’t have. Ask: should I ask PM for a canary cohort or propose a staged feature flag?”
- One‑week plan (3 bullets)
- What I’ll do next and how I’ll measure it.
- Optional context (links)
- One link to a PR, design doc, or a numbered screenshot.
That’s it. Write it in plain text, send as a Slack DM or email on Monday morning IST. My mentor replies in-line or with a voice note if needed. If something looks sensitive or complicated, we flag it for a 30‑minute call.
Why this worked for me
The constraint of “10 minutes” forces discipline. You can’t cram emotional venting and a roadmap into one message. It forces prioritisation: what really matters this week?
A few practical wins:
- Less scheduling overhead. No late-night reschedules. No time-zone guesswork.
- Better records. I have 26 updates in a Slack thread I can search when I forget why a decision happened.
- Faster feedback loop. Mentor replies with one focused suggestion most times; no need to summarize an hour of verbal context.
- Lower friction for both of us. He skimmed between meetings; I retained the same advice over months.
It also improved my follow-through. Because I had to write a one‑week plan every week, I became ruthless about small measurable steps. That’s where real growth happened — not in pep talks, but in incremental, documented action that both of us could see.
Where it failed (and the tradeoff I accepted)
Asynchronous updates aren’t a silver bullet. After three months I noticed two problems.
First, nuance is lost. A blocker like “team politics” needs tone and calibration. My mentor missed the emotional undercurrent a few times and suggested technically correct but politically tone‑deaf moves. That led to a misstep: I followed advice that created friction with a senior PM and cost me two weeks of trust-building.
Second, the relationship felt thinner. Mentorship isn’t just transaction; it’s trust, empathy, and career framing. My mentor was candid: “I learn a lot from conversations too.” I was missing those lateral lessons.
So I added a rule: asynchronous updates for routine weeks; a 30‑minute call once a month reserved for career framing, messy problems, and shared learning. The cost is small (one hour a month) and offsets the lack of nuance.
How I introduced it to my mentor (so you can too)
I did three simple things that made the switch painless:
- I proposed the experiment. “Can we try this for six weeks? If it sucks, we resume calls.”
- I shared the exact format and the time budget: 10 mins to write, 10 mins to skim.
- I kept at least one call per month for high‑bandwidth conversation.
He agreed immediately. People who mentor a lot value signals that you respect their time. A crisp update gives that signal.
A practical note for Indian professionals
If you’re in India and juggling odd hours, poor evening Wi‑Fi, or a mentor in the US, asynchronous mentoring is especially useful. Send your update in the morning IST so your mentor can skim it during their afternoon. Put links to PRs or MRs — if mobile data caps are a problem, note that and paste numbered screenshots instead.
A final trade: not everything scales
This works best when the mentor and mentee trust each other’s competence and communication discipline. For new relationships, or highly political problems, skip the update and take the call. I learned that the hard way.
What I walked away with
The honest takeaway: replacing weekly mentor calls with a focused 10‑minute update saved time and forced clearer thinking. It didn’t replace deep conversations; it reduced them to a single monthly hour. That balance — asynchronous for execution, synchronous for nuance — is what actually moved me forward.