Difference between revisions of "Visual management"

From Pearl Language
Jump to navigation Jump to search
m (→‎To process: {{tag|management}})
(→‎Sources: += Visual Management Blog » Xavier Quesada Allue » Scrum of Scrums: Making it visual)
Line 22: Line 22:
*http://en.wikipedia.org/wiki/Learning_styles#Neil_Fleming.27s_VAK.2FVARK_model
*http://en.wikipedia.org/wiki/Learning_styles#Neil_Fleming.27s_VAK.2FVARK_model
*{{web|url=http://blogs.hbr.org/schrage/2013/03/the-question-all-smart-visualizations.html|person=Michael Schrage|site=HBR|title=The Question All Smart Visualizations Should Ask}}
*{{web|url=http://blogs.hbr.org/schrage/2013/03/the-question-all-smart-visualizations.html|person=Michael Schrage|site=HBR|title=The Question All Smart Visualizations Should Ask}}
*{{web|url=http://www.xqa.com.ar/visualmanagement/2009/08/scrum-of-scrums-making-it-visual/|site=Visual Management Blog|person=Xavier Quesada Allue|title=Scrum of Scrums: Making it visual}}


==To process==
==To process==

Revision as of 09:55, 16 April 2014

NLP demonstrates there are different ‘learning styles’:

  • visual learners;
  • auditory learners
  • kinesthetic learners.

A daily meeting next to a wall with visual management recalls all learning styles—auditive, visual and kinesthetic dimensions that suit all team participants.

visual management:

  • is a way to present information visually on a physical material—paper, post-it notes, …;
  • sits in a strategic location—a wall close to the team or a whiteboard;
  • reaches out to impacted people so they can reach the information easily;
  • gives immediate access to the information;
  • encourages commitment from all involved;
  • attracts people, even from other teams;
  • educes interesting and valuable feedback;
  • is an excellent tool of communication and collaboration;
  • improves team’s ability to take ownership of a task;
  • gives immediate view on tasks’ progress;
  • increases communication and sharing of information.

Sources

To process

  • E-mail Olav Maassen on Digital scrum boards, 2013-08-25