This article explains the 70-20-10 distributed teams approach and how to adapt it for remote work. It defines each bucket, gives remote-specific examples, a 30-day L&D checklist, common misconceptions, and a case vignette with a quiz template to make on-the-job remote training measurable and equitable.
The 70-20-10 distributed teams concept answers a simple question: where do people learn most effectively at work when teams are remote? In our experience, the classic 70-20-10 model (70% on-the-job, 20% social, 10% formal) still holds value, but it requires intentional redesign for the realities of distributed team learning.
This article defines each component in plain language, gives practical remote-first examples, offers a quick-start checklist for L&D, debunks common misconceptions, and finishes with a short case vignette plus a simple assessment quiz template L&D teams can use today.
A pattern we've noticed is that teams who explicitly label learning activities avoid confusion about expectations. The 70-20-10 distributed teams framework maps to three practical buckets:
70% - On-the-job experience: Learning by doing. This includes stretch assignments, real projects, shadowing, and iterative feedback while executing actual work.
70% refers to high-impact, practical learning embedded in daily work. For remote teams this is on-the-job remote training—structured shadowing over video, collaborative pair work, and live project rotations that build skills through context.
The 20% bucket covers learning from others: feedback, coaching, mentoring, peer review, and knowledge sharing. For distributed teams, this becomes deliberate virtual coaching, asynchronous feedback loops, and community building.
The 10% portion is formal: courses, workshops, certifications. In remote contexts, this emphasizes high-quality, bite-sized digital content, followed by applied tasks so learning translates into work.
Below are concrete remote-first examples you can adopt immediately. Each example ties back to a specific bucket so teams avoid vague “learn more” directives.
Two practical concepts to adopt: sequenced practice (teach → do → reflect) and asynchronous artifacts (recordings, playbooks, annotated code) that preserve social learning for different time zones.
Focus on three tactics: make the work the curriculum, schedule short, documented shadowing sessions, and require a brief reflection or artifact after each stretch task. These create observable evidence of learning and reduce the “invisible” learning gap that remote workers often face.
Adapting 70-20-10 to distributed teams requires converting informal signals into intentional processes. A pattern we've found: distributed teams need more scaffolding for the 20% and clearer alignment for the 70%.
Start by converting spontaneous hallway coaching into repeatable touchpoints: scheduled mentorship sessions, asynchronous peer reviews, and documented playbooks. Use collaborative tools to tag learning moments and ensure equitable access so remote isolation and uneven access to learning don’t widen skill gaps.
Some of the most efficient L&D teams we work with use platforms like Upscend to automate this entire workflow without sacrificing quality. That approach helps teams link micro-lessons to on-the-job tasks and capture social learning artifacts for later review.
Operational changes to consider:
Use this checklist to move from design to action in under 30 days. In our experience, short cycles and visible wins build momentum across remote orgs.
Key governance controls to add immediately:
Misunderstandings about the model can derail implementation. Address these early.
Addressing these myths early reduces friction and sets clearer expectations for remote employees about what successful learning looks like.
Case vignette — A distributed product team with senior engineers across four time zones struggled with onboarding new hires. In our experience, their learning was ad-hoc: lots of documents, few guided experiences.
They piloted a 30-day program that leaned on the 70-20-10 distributed teams idea: a 70% rota where new hires led a small feature under a peer shadow; a 20% structured mentor check-in twice weekly; and a 10% microcourse on the codebase with an applied mini-project. Within a quarter their ramp time fell by 30% and new-hire satisfaction rose sharply.
Deploy this short quiz as a competency and perception check. Tailor questions to role and project.
Use responses to adjust the next sprint: increase mentor touchpoints where confidence is low, or add applied modules where formal resources were insufficient.
To summarize, 70-20-10 distributed teams is a useful lens rather than a strict mandate. The core work for L&D is to translate informal, in-person cues into repeatable remote processes: make the 70% visible and measurable, structure the 20% with explicit rituals, and design the 10% to be bite-sized and directly applied.
Start small: pick one role, run a 30–60 day pilot, measure outcomes, and iterate. Use the checklist and quiz above to keep implementation concrete and equitable. Address pain points—unclear expectations, remote isolation, and uneven access—by documenting learning pathways and sharing artifacts.
If you want to experiment with automation and archiving social learning artifacts, consider testing one platform to reduce admin overhead and make learning signals visible across time zones. Small, deliberate changes produce outsized results when teams are distributed.
Next step: Choose one role to pilot a 30-day 70-20-10 distributed teams program this week and schedule your first mentor pairing. That single action will surface the real operational gaps to fix next.
The Upscend Team provides actionable insights on technology and business strategy.
Book a walkthrough and we'll show you how it applies to your own content.
GeneralDecember 14, 2025
This article explains how to diagnose and fix remote work issues in hybrid teams by categorizing problems (communication, engagement, process, technology) and running a short audit. It provides a meeting and documentation playbook, engagement programs, policy design principles, tooling checklist, and a four‑phase assess–design–pilot–scale roadmap to run 90‑day experiments.
Psychology & Behavioral ScienceJanuary 12, 2026
This article lists 12 short, peer-led social learning activities for remote teams with scripts, durations, ideal sizes, required platform features, and success metrics. It explains why peer-based learning raises retention and psychological safety, shows common failure modes, gives two real examples, and offers fixes for low participation.
Psychology & Behavioral ScienceJanuary 12, 2026
This article explains how small remote teams can build a social learning community on a tight budget using simple routines, free/low-cost tools, and peer-led formats. It provides a 3-month starter plan, templates, facilitation tactics, measurement methods, and quick fixes to sustain engagement without dedicated L&D staff.
Psychology & Behavioral ScienceJanuary 12, 2026
Run a focused six-week pilot to test social learning features in remote teams, using matched cohorts, a small feature set, and clear KPIs. Combine randomized or stratified sampling with mixed-methods analysis (time series, propensity matching, interviews) and pre-specified go/no-go criteria to judge impact and scalability.