Working Out Loud¶

Strategy · All strategies
Evidence · 1 claim (1 for) · 2 studies (2 causal), q3 · 0 of 2 report an effect size

Description¶

Working out loud is the practice of narrating one's work in progress — sharing drafts, questions, failures, and reasoning in a public or semi-public venue — so that others can see, respond to, and build on it. Coined by Bryce Williams (2010) and developed by John Stepper (2015), it combines visible work with relational generosity: posting is directed at people who can help, not merely archived. In learning contexts, learners post artifacts, explain their thinking, and solicit critique from peers, mentors, or a wider professional network.

Design Implications¶

Working out loud externalizes the learning process, converting private struggle into inspectable artifacts that invite feedback and social learning [~M]. Its effectiveness depends on the presence of an actual audience that responds: posting into a void produces compliance posting, not learning. Because it makes reasoning visible, it functions as a form of Cognitive Apprenticeship in which learners, not just experts, model their thinking.

Context¶

Requirements¶

• A low-friction sharing venue with a real audience (course forum, cohort channel, portfolio, professional network)
• Norms of psychological safety — learners must believe that showing unfinished work will not be punished
• Structured prompts for what to share (artifact + question + what I'd do differently), since unstructured "share your progress" prompts yield shallow updates
• A response mechanism: peers or instructors commit to commenting within a defined window

Constraints¶

• Without responses or visible uptake, sharing decays into performative updates and adds workload without learning benefit [-M]
• Public visibility raises evaluation anxiety for novices and learners with low sense of belonging; premature public critique can suppress risk-taking [-M]
• In competitive or graded contexts, learners hide difficulties and share polished work only, defeating the purpose [-M]
• High-volume feeds can produce shallow scanning rather than substantive peer engagement [~W]

Implementation Variability¶

• Cohort-internal: sharing limited to a class or team — safest starting point for novices
• Networked: learners post to professional communities or public blogs, building identity and connections (Stepper's original framing)
• Structured rituals: weekly "demo days," standups, or learning journals with peer comment quotas
• Artifact-focused vs. process-focused: sharing finished work for critique vs. narrating decisions and dead ends as they happen

Target Learners¶

• Adult and professional learners building networks and reputations alongside skills [+W]
• Learners in project-based or portfolio contexts where process documentation has intrinsic value
• Requires scaffolding for novices and learners from groups underrepresented in the field, for whom public visibility carries higher social risk; belonging supports moderate these effects Belonging interventions improve outcomes. [+M]

Target Learning Goals¶

• Metacognition: articulating one's own reasoning and monitoring progress
• Feedback-seeking and revision: learning to solicit, interpret, and act on critique
• Professional identity and community participation: learning the discourse of a field by practicing it publicly
• Collaborative knowledge building: making work reusable and improvable by others

Instructions¶

1. Establish the venue and norms: where work is shared, who responds, and how critique is offered (kind, specific, actionable).
2. Model the practice first — the instructor works out loud on their own project, narrating decisions and mistakes (see Cognitive Apprenticeship).
3. Give a sharing template: what I made, what I'm unsure about, what help I need.
4. Schedule peer response: assign rotating comment partners so every post receives at least one substantive reply.
5. Progressively widen the audience — from cohort to program to public network — as learners build confidence and judgment about what to share.
6. Close the loop: learners revise based on feedback and post a brief "what changed and why" follow-up.

Related Strategies¶

• Learning journals and portfolios — private counterparts that can seed public sharing
• Peer critique protocols — the response mechanism that makes sharing consequential
• Demo days and exhibitions — scheduled, synchronous variants
• Use the DOT Framework's Empathize and Test/Feedback stages as practical checklists, and build professional learning communities around shared prompting and critique practices
• Solicit and formally review unsolicited scholarly responses when publishing a controversial position

Examples¶

• Stepper's Working Out Loud circles (workingoutloud.com) — peer groups meeting weekly for 12 weeks, each member working toward a goal while sharing progress and making contributions to others.
• GitHub pull requests and open-source contribution — learners narrate proposed changes and receive expert review; the review thread is a durable record of reasoning.
• DS106 (University of Mary Washington) — an open digital storytelling course where participants post daily assignments to a public feed and comment on each other's work.
• Agile standups and sprint demos — workplace variants where teams narrate in-progress work to surface blockers early.

Key Sources¶

• Stepper, J. (2015). Working out loud: For a better career and life. Working Out Loud LLC.
• Kleon, A. (2014). Show your work!: 10 ways to share your creativity and get discovered. Workman Publishing.
• Wenger, E. (1998). Communities of practice: Learning, meaning, and identity. Cambridge University Press. doi:10.1017/CBO9780511803932
• Bandura, A. (1977). Social learning theory. Englewood Cliffs, NJ: Prentice Hall.
• Dalsgaard, C., & Paulsen, M. F. (2009). Transparency in cooperative online education. The International Review of Research in Open and Distributed Learning, 10(3). doi:10.19173/irrodl.v10i3.671