Menu
Tomek's blog
  • Contact & About
Tomek's blog

4DX: Scoreboard

Posted on May 22, 2019November 2, 2022 by Tomek Kaczanowski

This blog post is based on my experience with 4DX (4 Disciplines of Execution) framework (check this introduction to 4DX if you are not familiar with the framework yet). Today we will look at the role the 4DX scoreboard plays in the process.

Information Radiators

First things first – what do I mean by “scoreboard”? I will answer with a question: have you ever heard of “information radiators”? Their job is to inform you about some important information about projects (even if you do not want to know). Usually they are visual-based (e.g. a big screen with build status or a lava lamp turning red when there is some issue on production) but not necessarily (e.g. cantine bell telling you that a dinner is ready). Their common properties: they are hard to miss & they inform about something important.

The scoreboard fits nicely into this category as we will soon see.

Out of sight, out of mind

The first gain of having a scoreboard is that it reminds you constantly about your WIG. So you better keep it well visible. If it goes out of sight other urgent matters will come into play and you’ll start working on them forgetting about the WIG.

Are we winning?

The main purpose of the scoreboard is that you can tell at a glance whether you win or lose. No head scratching or any computations needed – you take a look and you know instantly.

Some sport scoreboards have this property. For example:

NBA scoreboard (source: depths of Internet)

Another example is a burndown chart used by many Scrum teams. At any given moment you can see instantly whether you are above the trend line (losing) or below the trend line (winning):

Burndown chart example (source: Wikipedia)

Your scoreboard might look differently from any other in the world, but it has to show clearly whether you win the game or you lose it.

Give it all you’ve got!

Have you ever played card game without any prize or penalty? Not very exciting, right? But once you decide to play for some tokens (even valueless but something you can gain or lose), the game changes instantly. You start to care more.

And this is what happens when you have a scoreboard. The team knows the game is for real. The team realizes that what they do impacts the result of the game (the WIG). And this a real game-changer.

Who owns it?

An now something slightly different. Who should own the scoreboard? The answer is clear: the team that the lead measures presented on the scoreboard belong to.

As a rule of the thumb: you should never measure the performance of others; you should measure your own.

Share this:

  • Twitter
  • Facebook
  • LinkedIn
  • Reddit
  • Pocket
  • Email
  • Print

Like this:

Like Loading...

Related Posts

  • 4dx
  • information radiator
  • visualization
  • wig
  • Leave a ReplyCancel reply

    Follow me on Twitter

    My Tweets

    Subscribe to Blog

    My Books

    Practical Unit Testing - JUnit Practical Unit Testing - TestNG Bad Tests, Good Tests kanban for your team 1,2,3 kanban Złe testy, dobre testy

    Tags

    4dx agile book review capacity planning conference constraints continuous improvement daily scrum decision taking discussion effectiveness review estimation experiment facilitation feedback funny getting things done goals interview kanban leadership management management 3.0 meetings notes organisational culture procrastination productivity psychological safety rant remote work retrospective scrum scrum sprint sociocracy sociocracy 3.0 team testing tips & tricks tools transparency visualization wip work in process work in progress

    There is no Planet B. Act Now!

    There is no Planet B. Act Now!
    There is no Planet B. Act Now!

    Follow me on LinkedIn

    Tomasz Kaczanowski

    Top Posts & Pages

    • Journey Lines - A Team Building Activity
      Journey Lines - A Team Building Activity
    • 4DX: LAG vs. LEAD
      4DX: LAG vs. LEAD

    Categories

    • agile (32)
    • book (7)
    • event (2)
    • facilitation (2)
    • organization (11)
    • productivity (32)
    • sociocracy (10)
    • team (5)
    • testing (2)
    • tools (16)
    • Uncategorized (9)
    • varia (30)
      • remote work (2)
      • ux (2)

    No Business On A Dead Planet

    No Business On Dead Planet
    No Business On Dead Planet
    ©2025 Tomek's blog | WordPress Theme by Superb Themes
    %d