the open-office trap

from www.newyorker.com/business/currency/the-open-office-trap

the open office, flourishes: some seventy per cent of all offices now have an open floor plan.

…. a growing body of evidence suggests that the open office undermines the very things that it was designed to achieve.

…. In 2011, the organizational psychologist Matthew Davis reviewed more than a hundred studies about office environments. He found that, though open offices often fostered a symbolic sense of organizational mission, making employees feel like part of a more laid-back, innovative enterprise, they were damaging to the workers’ attention spans, productivity, creative thinking, and satisfaction. Compared with standard offices, employees experienced more uncontrolled interactions, higher levels of stress, and lower levels of concentration and motivation.

….Physical barriers have been closely linked to psychological privacy, and a sense of privacy boosts job performance.

….the ability to control the environment had a significant effect on team cohesion and satisfaction.

….An open environment may even have a negative impact on our health.

….noise has been repeatedlytied to reduced cognitive performance. The psychologist Nick Perham, who studies the effect of sound on how we think, has found that office commotion impairs workers’ ability to recall information, and even to do basic arithmetic. Listening to music to block out the office intrusion doesn’t help: even that, Perham found, impairs our mental acuity.

….it seems that the more frantically you multitask, the worse you become at blocking out distractions.

 

user story mapping

by Jeff Patton: jpattonassociates.com/user-story-mapping-presentation/

identify holes and omissions in your backlog

…. plan holistic releases

…. supports ad hoc day to day conversations about the system

…. understand the big picture

from “How you slice it” pdf:

Design your project in working layers to avoid half-baked incremental releases

…. When using use cases, focus first on those where the actors are a single user and the system. Avoid planning with use cases that describe the internal workings of the system .

… usage sequence

from presentation:

User Story Mapping is an an approach to Organizing and Prioritizing user stories

Unlike typical user story backlogs, Story Maps:

  • make visible the workflow or value chain
  • show the relationships of larger stories to their child stories
  • help confirm the completeness of your backlog
  • provide a useful context for prioritization
  • Plan releases in complete and valuable slices of functionality.

Story Maps support the primary intent of user stories, rich discussion

The foundational building block of a story map is the user task

see also: jpattonassociates.com/the-new-backlog/

work with culture through storytelling

from Nancy Duarte: Strengthen and Sustain Culture with Storytelling

stories are more than content for marketing campaigns. They’re the fuel that feeds and sustains a strong corporate culture.

good stories remind employees and customers about the values of an organization.

tell if your company has a truly story-driven culture:

Information delivery reflects a balance of analytical and emotional content

…. anecdotes or narratives that explain their origin

….high value on activities that foster understanding between people and invests in training to build communication skills