Cut 10% of your calendar by default: why I set meetings to 25/50 minutes
I started sending 25/50‑minute invites instead of 30/60. It bought me breathing room, fewer overruns, and clearer agendas — with one embarrassing client fail.
Written by: Rohan Deshpande
My Tuesday looked like a train timetable: 9:00–9:30 sync, 9:30–10:00 client call, 10:00–10:30 code review, 10:30–11:00 all‑hands. The same pattern repeated that afternoon. By 4pm my head felt like it had been through a conference bridge: re‑contexted five times, half my notes in miscellaneous chat messages, and a feeling that nothing I’d promised was actually done.
This isn’t flair. It was real friction: a Bangalore office with intermittent Wi‑Fi, US stakeholders who booked on their lunch, and my calendar defaults set to 30/60 minutes because that’s what every corporate calendar does. So I tried a stupidly small change: I made most invites 25 or 50 minutes instead of 30 or 60. That tiny shave created breathing room. It also taught me where meetings are useful — and where they’re not.
Why 25 and 50, not 20 or 45 Most calendar defaults exist for historical reasons, not because they help focus. Thirty and sixty minute blocks are neat, but they also encourage sloppy timing. They fit into the quarter hour cadence, leaving no gaps. I needed gaps.
Twenty‑five and fifty minutes are simple social nudges. They’re long enough for structured discussion, short enough to force focus, and noticeably different so people actually notice the end time. The math is straightforward: if you replace eight 30‑minute meetings a week with 25 minutes, you get 40 extra minutes. It isn’t a silver bullet, but for me the real win was the breathing room between commitments.
How I rolled it out (without starting a war) I didn’t decree a policy. I treated it like an experiment and started with my own invites.
First, I changed my Google Calendar default to 25 minutes for new events and 50 for recurring ones. If you use Outlook, you can set custom durations in Calendar options or manually type the end time when composing the invite. I also created two event templates — “25m sync” and “50m review” — that auto-populate a short agenda in the description: 1–2 bullets, owner for each item, and a clear desired outcome (decide/align/next steps).
Next, I made the start of every invite explicit: “Start on time — end on time” and the agenda on the first line. That matters in Indian companies: people default to showing up late or extending if no one asserts structure. The title change forces an expectation.
I used the 25/50 rule mostly for internal and recurring meetings: standups, quick syncs, reviews, demos that don’t need whiteboarding. For workshops, architectural design, or client negotiations, I stuck with longer slots but tried to reserve them less often and with clear prep asked in advance.
The tradeoffs and the meeting that embarrassed me The rule is not magic. It pushed work earlier and sometimes made conversations more abrupt. The single most embarrassing failure: I scheduled a 25‑minute kickoff with a new client in the US who had limited availability. We were halfway through a technical deep dive when the timer hit the end. I closed the call politely, thinking we had covered the main points. The client called me out in chat five minutes later — they felt rushed and wanted an extended run. We ended up scheduling a follow‑up, which cost us more cumulative time and damaged rapport on that first interaction.
That failure taught me a concrete constraint: never apply 25/50 to first meetings with external stakeholders unless you explicitly agree on timeboxing. First meetings often need slack for rapport, context, and unexpected questions. Internally, the rule works better because teams know the rhythms.
Other tradeoffs: shorter meetings sometimes shift work into async messages. That’s OK if you accept the trade — more focused meetings, more thoughtful async followups. But if your team is already poor at writing agendas or following up, the rule just turns meetings into fragmented tasks.
Why it actually reduced overruns Two small behavioral things explain most of the wins.
First, the shorter duration forces an agenda. If you have 25 minutes, you can’t meander. I started insisting on a one‑line outcome in the invite. That alone removed 30% of my meeting bingo (status updates that could have been an email). Second, people keep track of time when the end is off the half hour. There’s something about the odd end time that makes people glance at the clock.
I also learned to run meetings differently. I put the agenda front and centre, I assigned timeboxes, and I called the last five minutes “actions and owners.” That five‑minute ritual converted meetings from chatty to useful. If a point needed more time, we agreed on a follow‑up and the owner took responsibility.
Small operational tips that helped I don’t want to make a long checklist, but a few practical things matter:
- Change your calendar default and make agenda templates (Google Calendar settings -> Event settings -> Default duration).
- Put the desired outcome on the first line of the invite. Don’t make recipients hunt.
- Use “end on time” language and reserve the last 3–5 minutes strictly for next steps.
- For external or first‑time meetings, ask if the other party prefers a longer slot. Be explicit.
- When a meeting does need to overrun, ask the group if you should continue or reconvene. People appreciate the permission to stop.
What I actually walked away with The main takeaway is not that every meeting should be 25 minutes. It’s that tiny defaults are affordances. Changing your default meeting length changes behaviour in ways that polite requests rarely do. It’s easier to reclaim five minutes here and there than to negotiate a work‑life revolution. After three months I had an extra 45–75 minutes a week of uninterrupted time — real, usable focus blocks. That time didn’t magically produce more output, but it stopped my days from feeling like navigation between conveyor belts.
If you’re in a startup in Bengaluru, Hyderabad, Pune, or anywhere with cross‑continent calendars and spotty internet, try pushing one meeting a day to 25 minutes for a month. Keep the agenda. Notice what moves to async. And for the love of all things, don’t use 25 minutes for your first client kickoff unless you both agree.