Whiteboard Friday: Give a Recurring Explanation a Recognisable Shape

Read the campaign story

Whiteboard Friday began on the SEOmoz blog in 2007. Doug Kessler’s 2016 account, based on an interview with Rand Fishkin, identifies Scott Willoughby as a co-originator and describes the familiar presenter-and-whiteboard format. The programme made recurring explanations part of the company’s educational publishing. It is considered one continuing series here, not a separate case for each topic, presenter or subsequent production change.

In a later Wellspring Digital interview, Fishkin describes the format’s practical origin and acknowledges that early videos were uneven in presentation and accuracy. Accounts differ in their recollection of how long it took to become a strong performer, so this study does not assign an exact universal payoff period. Nor does a retrospective success story establish that any weekly video series will generate customers if continued long enough.

Editorial interpretation: a recognisable format reduces the amount of new orientation required from a viewer. Once the audience knows what a session does, it can focus on the question being explained. The visible diagram can also make relationships easier to follow than an uninterrupted talking head, provided the writing is legible and the presenter does not ask the audience to process too much at once.

The advantage depends on substance and maintenance rather than the board itself. A growing archive can accumulate obsolete advice, especially in a changing technical field. Consistency should make the teaching trustworthy, not turn old claims into permanent authority. A responsible adaptation needs a clear scope, expert review and a way to update or retire explanations when the underlying practice changes.

Build a visual argument before recording

Choose one question and identify the minimum relationships a viewer needs to understand. Prepare the diagram as a sequence of ideas rather than a wall of keywords. Test it at the size people will actually watch, including a small screen. Use captions and an accessible written explanation. The presenter should guide attention through the structure, while the visual supports the reasoning instead of merely proving that a whiteboard was used.

Make repetition a production advantage, not an editorial shortcut

Standardise the parts that do not need reinvention: framing, sound checks, review steps and publishing metadata. Reserve effort for the explanation itself. A familiar template should make it easier to catch a weak argument because there is less decorative novelty to hide behind. Keep a manageable reserve of reviewed episodes and choose a cadence that the team can sustain without replacing expertise with rushed summaries.

Review the archive as part of the programme

Assign responsibility for checking older material, especially when tools, policies or evidence change. Add dates and clear update notices, and withdraw advice that can no longer be responsibly maintained. Preserve historical context where useful without presenting it as current instruction. Evaluate understanding through a small application task rather than assuming that watching to the end means someone can use the concept correctly. The archive should become easier to trust as it grows.

A small test for another brief

A small professional-services team records four short original visual explanations of recurring client questions, with expert review and a written companion for each.

Measure correct application, remaining misconceptions, production effort and voluntary repeat use. Keep views and completion separate from client acquisition or guaranteed search performance.

Revise or pause if the team cannot verify advice, viewers misapply the diagram or the schedule outpaces editorial review.

• Select one bounded question and a legible diagram per session.
• Test understanding with representative adults before publishing.
• Assign review dates and maintain a visible correction route.