Skip to main content

Missing Affordances

What are the affordances that are missing from the virtual task board?  There are quite a few.

The perceptual psychologist J. J. Gibson coined the term in the late 1970s to mean the relationships that an actor (person) can have with objects in the world.  Then Donald Norman popularized the term in his book "The Design of Everyday Things."

You may think these affordances don't matter much.  But after you have them (via using a physical task board) you will find they are sorely missing.

I can:
  • Hold a task and show it to you. Now you know exactly what I'm talking about. Many virtual task board have no way of denoting a selected task. 
  • Pick a different task and hold it. Now I know you are talking about that one, but I'm still referring to the one I hold. 
  • Move a task. The motion is the affordance. Not the before and after location of a task - don't confuse position with motion. 
  • Pass a sticky note to you, now you have it and this denotes responsibility to perform the task perhaps. You may choose to stick it on your monitor as a reminder to perform the task later that day. 
  • Wad up a task and toss it on the floor. You may infer that I don't think we need this task any more. 
  • Retrieve a task from the floor and straighten it out and place it back on the board. Does your virtual tool have an undo feature? 
  • Slice the task into and hand you part of the task. Now you have a portion to own and I have a portion to own. 
  • Stack multiple task upon each other, this grouping may imply order or just a collection of like task. 
  • Annotate the task with yet another sticky note - this one could be a red sticky with an exclamation mark (meaning impeded). 
  • Revise the task with a simple swipe of the ink pen, to mark out a word. 
  • Augment the task with a new inserted word to provide more meaning with just a simple writing tool. 
  • Draw a diagram on the task - that's worth 1000 words! 
As an exercise try this with your team.  Make a list of all the tacit protocols that have developed to indicate affordances that are missing with your virtual task board.  For example:  selecting the task and highlighting it in some way to make people understand which task you are "holding."

Want an example of affordances on a dashboard or infographic?

Affordances and Signifiers: applying design theory to your dashboards


Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…