The Time-Blocking Workflow — 60-Min Training in 2027

The two ways teams buy back an hour a week

Every sales org that wants recurring skill work faces the same fork in the road, and the choice is not really about content. It is about where the hour comes from. Option one is the fixed block: a standing 60-minute calendar hold, same weekday and time for the whole team, defended by the manager. Option two is the distributed block: the same 60 minutes broken into shorter chunks — say four 15-minute drills, or two 30-minute pairings — scattered across the week at each rep's discretion.

The fixed block wins on ritual and on coaching economics. One room, one facilitator, one topic, one set of reps hearing the same feedback. The manager prepares once. Peer learning is real — a rep watching a teammate fumble an objection learns nearly as much as the rep fumbling it. And attendance is measurable in a single glance at the calendar. The cost is rigidity: if the hour lands during a customer's preferred meeting window, you lose deals or you lose attendance, and one of those is worse than the other.

The distributed block wins on friction. Fifteen minutes is a gap that exists between calls; sixty is a gap you have to manufacture. Reps who cover multiple time zones, or who sell into industries with narrow buyer availability windows (contractors before 7am, restaurant owners between 2 and 4pm, hospital procurement basically never), can slot micro-drills into dead space. The cost is that distributed training decays fastest. Without a shared room, the drills quietly become "I'll watch the recording," which becomes nothing. Completion rates on self-directed micro-learning are the softest number in any enablement dashboard.

There is a third posture worth naming because a lot of teams land there by accident: the floating block — 60 minutes reserved but rescheduled weekly around pipeline. It looks like a compromise and behaves like no program at all. The floating block inherits the fixed block's coordination overhead and the distributed block's decay. If your calendar invite has been moved three weeks running, you do not have a time-blocking workflow; you have a recurring apology.

The practical read for most teams under thirty reps: run the fixed block as the spine, and let distributed micro-drills be the *supplement* between sessions, never the substitute. The fixed hour sets the topic; the 10-minute reps during the week make it stick.

How to decide between them

The decision is mostly mechanical once you know four things about your team: coverage window, headcount, tenure mix, and whether managers are individual contributors. A player-coach manager carrying quota cannot reliably defend a weekly hour — the pipeline always has a louder claim — so those teams either need a dedicated enablement owner or should default to shorter, more frequent formats that survive a bad week.

Tenure mix matters more than most leaders expect. A team where half the reps are inside their first 90 days needs the fixed block, full stop. New reps do not know what they do not know, so self-directed micro-drills send them to practice the thing they are already comfortable with. Veterans are the opposite case: they benefit more from targeted, self-selected reps on a specific weak spot than from sitting through a discovery-questions refresher for the fourth year running.

Coverage window is the hard constraint. If your team spans US Eastern to Central Europe, there is no hour that is both reasonable and shared. Splitting the fixed block by region and running the same agenda twice is more work for the facilitator but preserves everything that makes the format work. Recording one session and asking the other region to watch it does not — passive viewing is not practice, and the whole point of the hour is that reps talk.

One more filter: what does the training actually need? Role-play, call review, and objection handling require live humans and are fixed-block work. Product knowledge, competitive updates, tool walkthroughs, and compliance refreshers are information transfer and belong in async format. Teams burn their scarce live hour on slide decks, then wonder why skills do not move. If a session could have been a doc, it should have been.

The numbers behind an hour a week

Start with the arithmetic, because "one hour a week" sounds trivial and is not. Fifty-two hours a year per rep, minus holidays and quarter-end weeks when nobody shows, realistically lands at roughly 40 to 45 delivered hours. For a ten-rep team that is on the order of 400 to 450 rep-hours plus the facilitator's prep. If prep runs 30 to 45 minutes per session — which it does once you are pulling real call recordings and building a scenario — the manager is spending a substantial number of hours annually on preparation alone.

Against that, the selling-time cost. A rep with a typical quota and working year produces a certain bookings-per-hour figure on average. Forty-five hours of training is nominally a meaningful slice of "lost" capacity per rep. That number is misleading in both directions: reps do not sell every hour they are not in training, and the hour usually gets taken from admin time rather than customer time. But it is the number a CFO will run, so run it first and be ready for it.

The break-even framing is more useful than the cost framing. If the program lifts win rate by even a couple of points on the same funnel volume, on a typical number of opportunities per year at an average deal size, that is a substantial amount of incremental bookings per rep — often exceeding the notional time cost. A two-point win-rate move is aggressive but not fantasy for a team that has never run structured practice. A more conservative planning assumption: one point of win rate, or an equivalent shortening of the ramp period.

Ramp is where the math is least arguable. If structured weekly practice pulls a new rep to full productivity a couple of months sooner, and full productivity is a meaningful bookings-per-month figure, those months are worth a significant amount per new hire depending on the partial-productivity curve. A team hiring several reps a year recovers the entire program cost on ramp alone, before touching win rate.

Session composition drives whether any of this materializes. A 60-minute block that is 45 minutes of talking and 15 minutes of practice is a meeting. Target the inverse: 10 minutes of framing, 35 to 40 minutes of live reps with the group watching, 10 minutes of debrief and commitment. With eight attendees, 35 minutes of live reps means roughly four reps get the chair each week — which means every rep practices in front of the group about every other week. Below eight attendees, everyone gets a turn weekly. Above twelve, break into two rooms or accept a three-week rotation.

Attendance is the number to actually instrument. Anything above 85% sustained over a quarter means the block is real. Between 70 and 85% means it is drifting and needs a manager conversation. Below 70% means the hour is not defended and the honest move is to kill it and rebuild rather than let it limp.

Standing it up without it collapsing in week four

Most time-blocking programs die between weeks three and six. The launch has energy, the first two sessions are well-prepared, and then a quarter-end lands, one session gets cancelled, and cancellation becomes the norm. Sequencing the rollout is what prevents that, and the sequence is deliberately slower than most leaders want.

Weeks one and two are calendar and topic work only. Put the recurring hold on every calendar as an accepted, non-optional meeting — not a tentative invite. Pick the slot by looking at actual meeting density in the CRM or calendar exports: find the hour with the fewest historical customer meetings, which for most B2B teams is Friday morning or Monday late-afternoon, and avoid Monday morning entirely because that is where pipeline reviews live. Then build a twelve-week topic map so no session ever starts with "what should we cover today." One skill per session, sequenced from foundational to advanced — discovery framing before objection handling before multithreading before negotiation.

Weeks three through six are the fragile stretch. Two rules carry it: the session runs at four attendees or forty, and the manager never cancels it for their own conflict. Delegate facilitation to a senior rep before you cancel. The signal reps read is not "this hour is valuable" — it is "does leadership move this when things get busy." One cancellation for a legitimate reason resets that signal for a month.

Weeks seven through twelve introduce peer facilitation. Each session, one rep owns fifteen minutes of the agenda — usually presenting a call of their own and asking the group to critique it. This does two things: it distributes prep load off the manager, and it converts the block from something done *to* reps into something owned *by* them. Ownership is the single strongest predictor of whether the program survives a leadership change.

From quarter two onward, stop picking topics from a curriculum and start picking them from the funnel. Pull stage-conversion data monthly. If discovery-to-demo is converting well but demo-to-proposal is lagging, the next four sessions are about what happens inside the demo. Tying the topic map to a visible funnel gap is what keeps senior reps engaged — they will sit through anything that is obviously connected to their own stuck deals.

Two failure modes to watch for specifically. The first is content inflation: the hour gradually fills with product updates, comp plan explanations, and announcements because it is the only time the team is together. Defend the hour ruthlessly; put announcements in the pipeline review. The second is the volunteer trap: the same three confident reps take the chair every week while the quiet reps watch. Track who has practiced in the last month and assign turns rather than asking for volunteers.

Adjacent blocks worth stealing the pattern for

The same mechanic — protected recurring time, single purpose, defended by a manager — generalizes well beyond training, and teams that succeed with the training block usually end up running two or three of these. Worth knowing which ones pay off.

Prospecting blocks are the most common sibling and the most abused. The pattern is two 90-minute blocks a week where the entire team does outbound simultaneously, phones and email, no internal meetings allowed. The group dynamic matters more than the time: hearing a teammate connect makes the next dial easier. The failure mode is that the block becomes "list building time," which is not prospecting. Require that the block starts with a list already built.

Pipeline hygiene blocks are 30 minutes weekly, usually Friday, where reps update close dates, next steps, and stage on every open opportunity. Unglamorous and enormously valuable — forecast accuracy improvements from a disciplined hygiene block are typically larger than anything a forecasting tool delivers on dirty data. Pair it with a report that lists opportunities with no activity in 14 days so the block has an agenda.

Deal review blocks differ from training because they are about specific opportunities rather than general skill. Run them separately. Merging them is tempting and always ends with the training hour becoming a deal review, because a live deal is more urgent than a hypothetical skill. Same reason you keep announcements out.

The pattern travels outside sales too. Support teams block time for case-review sessions on escalated tickets; customer success teams block time for account-health reviews before QBR season; RevOps teams block a recurring hour for data-quality work that otherwise never gets prioritized. In each case, the mechanic is identical — the work is important but never urgent, so it needs a calendar slot to exist at all. Anything that is important and not urgent will lose every scheduling contest it enters unless it has a defended block.

One upstream dependency worth flagging: none of these blocks work if the calendar itself is chaos. If reps are getting same-day internal meeting invites from three directions, no block survives. Establishing a team-wide meeting protocol — internal meetings only in defined windows, 24-hour notice minimum — is often the prerequisite fix, not the training program itself. Teams frequently discover that the real problem was never training frequency; it was that nobody controlled the calendar.

What tends to break and how to catch it early

The most common quiet failure is that the block runs perfectly and changes nothing. Attendance is high, sessions are well-run, everyone says they are useful, and no metric moves. This happens when the training is disconnected from the behavior it is supposed to change — reps practice a discovery framework in the room and then run their normal call the next day, because nothing in their workflow reminds them or checks.

The fix is a commitment mechanic in the last ten minutes. Each rep names one specific thing they will do on a named call before the next session, and the next session opens by asking three of them what happened. It takes six minutes and it is the difference between a practice hour and a performance change. Managers who listen to calls can close the loop harder by pulling one recording per rep per month and checking specifically for the skill from the last four sessions.

The second failure is topic thrash — changing what the hour covers every week based on whatever went wrong most recently. Skills need three to four sessions of repetition to stabilize. A twelve-week map with three or four topics, each getting three sessions, moves behavior. Twelve topics in twelve weeks produces twelve pleasant conversations.

The third is measurement theater: tracking hours delivered and completion rates because they are easy, rather than the things that would tell you whether it worked. Hours delivered is an input. The honest scorecard is attendance percentage, one behavioral metric tied to the current topic (talk-to-listen ratio, number of discovery questions, multithreading rate on open deals), and one lagging outcome reviewed quarterly (stage conversion, win rate, or ramp time). Three numbers, reviewed on a fixed cadence, and a genuine willingness to kill the program if all three are flat after two quarters.

Finally, watch for the block outliving its usefulness. A weekly hour that made sense with eight new reps may be the wrong shape at forty reps with three years of average tenure. The mature version is often a fixed monthly all-hands skill session plus manager-led small-group blocks by segment. Reviewing the format quarterly — not the content, the *format* — keeps it from becoming a ritual nobody remembers agreeing to.

Related questions

How long should a sales training block be?

Sixty minutes is the practical ceiling for a full-team live session; attention and calendar defensibility both degrade past it. Thirty minutes works for small-group or manager-and-rep formats. Under fifteen minutes, only single-drill practice fits — useful as reinforcement, not as the primary session.

What day of the week works best for a training block?

Look at your own calendar data rather than following convention. Most B2B teams find the fewest customer meetings on Friday morning and Monday afternoon. Avoid Monday morning, which collides with pipeline review, and avoid the last two days of a month or quarter entirely.

Should managers make training attendance mandatory?

Yes, and treat it like a customer meeting rather than an internal one. Optional attendance selects for the reps who least need it. The exception worth granting is a live customer conflict, with the expectation that the rep does a makeup session with their manager that week.

How do you train reps across multiple time zones?

Split the block by region and run the same agenda twice rather than recording one session for the other region. Passive viewing is not practice. If two live sessions are impossible, use a rotating time so the inconvenience is shared rather than permanently assigned to one region.

FAQ

How many reps can attend one 60-minute block before it stops working?

Around twelve. The constraint is live practice time: with roughly 35 minutes of reps in the hour, twelve attendees means each person takes the chair once every three weeks, which is too sparse for a skill to stabilize. Above twelve, split into two rooms with the same agenda or move to segment-based small groups.

What should the first four sessions cover?

Start foundational and sequenced, not with whatever is most broken. Discovery framing, then qualification, then objection handling, then a call-review session using real recordings from the team. Beginning with real recordings before the group has shared vocabulary produces vague feedback; beginning with a framework gives everyone the same language to critique with.

Can this replace onboarding for new reps?

No. Onboarding is dense, daily, and mostly information transfer; the weekly block is thin, recurring, and mostly practice. New reps should attend the weekly block from day one for the culture and the peer exposure, but their ramp needs a separate structured program running alongside it for at least the first 60 days.

How do you keep senior reps from checking out?

Give them the chair. Peer facilitation — a senior rep presenting one of their own calls for critique — converts them from audience to owner. Tying topics to visible funnel gaps also helps, because veterans will engage with anything obviously connected to a deal they are personally stuck on.

Is asynchronous training ever the better choice?

For information transfer, almost always. Product releases, competitive positioning, tool changes, and compliance content should be documents or short recordings that reps consume on their own schedule. Reserve live time for anything requiring a human on the other side — role-play, call critique, negotiation practice, objection handling.

How do you know when to shut the program down?

Two consecutive quarters where attendance is under 70%, the behavioral metric is flat, and the lagging outcome has not moved. At that point the honest move is to stop, run a short retrospective with the team on why, and rebuild in a different format rather than letting a dead meeting occupy an hour a week indefinitely.

Sources

• https://hbr.org/2016/07/what-great-managers-do-to-engage-employees
• https://www.gartner.com/en/sales/insights/sales-enablement
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://hbr.org/2018/05/how-to-spend-way-less-time-on-email-every-day
• https://sloanreview.mit.edu/article/the-surprising-power-of-questions/
• https://www.atlassian.com/blog/productivity/time-blocking
• https://www.linkedin.com/business/sales/blog

Related on PULSE

• [Top 10 sales training workshops for B2B SaaS teams](/knowledge/st0635)
• [Top 10 multi-threading training drills for B2B sales reps](/knowledge/st0555)
• [Top 10 Challenger Sale sales training drills for AEs](/knowledge/st0503)
• [Top 10 prospecting training drills for B2B sales reps](/knowledge/st0543)
• [Top 10 Miller Heiman sales training drills for AEs](/knowledge/st0527)