AGILE IN ACTION

Monday, 6 February 2006

Ba

Posted by Simon Baker

Roughly translated, Ba means place .

Ba is a time and space where creative energy flows, existing knowledge is shared and new knowledge is created. Through their interactions with one another and the environment, people become attuned to the context of ba and they’re able to look beyond their own limited perspective. They view problems as opportunities to learn, and they’re inspired to be creative and to develop innovative solutions.

Here’s an extract from one of the case studies in Hititsubashi on Knowledge Management :

Seven-Eleven Japan uses the shop floors of its stores as ba to create knowledge, where store employees accumulate tacit knowledge abut customers’ needs through face-to-face interactions. Long-term experiences in dealing with customers give store employees unique knowledge and insight into the local market and their customers. They often say that they can just ‘see’ or ‘feel’ how well certain items will sell in their stores, although they cannot explain why. Seven-Eleven Japan emphasises the importance of its stores as ba to keep creating knowledge in order to adapt to ever-chaing customers needs.
Ba happens spontaneously, but it’s possible to supply the necessary conditions that allow ba to occur naturally: Autonomy, self-organisation , creative chaos, and diversity. An informative workspace provides a physical space that facilitates collaboration and encourages interaction between people. While a mental space transpires from the reciprocating trust and commitment felt among the people present, and from their common values and goals.

References:
[1] Hititsubashi on Knowledge Management
[2] The courage to be creative

Creative Commons Licence

Recent Posts

  1. Managing costs provides a false sense of security
  2. State of Agile survey for 2011 tells a familiar story
  3. (I can't get no) satisfaction, let alone customer delight
  4. Positive emotions and purpose
  5. People don't buy what you do, they buy why you do it
  6. Too busy chopping wood to sharpen the axe
  7. So you want a fresh apple
  8. Systems are seductive
  9. Crack cocaine problem-solving and complexity
  10. Beware the Coefficient of Fiction

Archives

  1. 2012 (4)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
  7. 2006 (128)
    1. December (16)
    2. November (26)
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
      1. Don't be afraid to make mistakes
      2. APLN and collaborative leadership
      3. Scrum ba
      4. Ten-minute build, continuous integration and developer rhythm
      5. User stories part 3: Using spikes to help estimate user stories
      6. User stories part 2: Adaptive planning
      7. User stories part 1: What is a user story and who writes them?
      8. Ba
      9. Watch out for the mini-series
      10. Ideal time vs. story points
      11. Making the quality-factor visible
      12. User stories and tasks
      13. Knowing when you're done
      14. Switching pair-programming partners
    12. January (24)
  8. 2005 (63)
  9. 2004 (2)

Tags

agile (43) big visible chart (15) conference (39) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (18) team (30) testing (18) xpday (19)