Working Out Loud Behaviors to Develop during #WOLWeek

#wolweek

This week is going to be fun. Nov 17th through Nov 24th. WOLWeek 2014 People from all over the world coming together via the inter-webs to develop and practice the art of Working Out Loud…to improve their productivity…make connections…spark ideas…and further a movement. What a thrill it is to see the expansion of such a simple concept (When Will We Work Out Loud? Soon!) into the transition to a larger movement. Thanks to the likes of Jonathan Anthony, Austen Hunter and Simon Terry. You know that original post I wrote was posted on Nov 29th, 2010? So this version of #wolweek culminates within days of the four year anniversary of my first post on the topic. I’m moved myself reading some of the previews and set up for #wolweek:

As a precursor into this week’s activities, I would like to introduce some new classifications of behaviors that you may want to try and spread to others around you to help with the adoption and effectiveness of your own local #wol movement. I’ve taken the behaviors that I have observed in our own Enterprise Social Network (ESN) that drive the greatest success stories, and organized them in to “behaviors” that you can take and apply to your own application of bringing “social” and “sharing” into your work environment.

From Working Out Loud -> The xOL Light Bulb

Working Out Loud = Narrating Your Work + Observable Work

In the early days of trying to grasp the hows and the whys of this “enterprise social” thing, I focused very hard on the coaching behaviors of the individual, encouraging them to shift how they worked to make their knowledge, conclusions, activities and deliverables more open and visible to  others. Change you. Dare to share. Put yourself and your knowledge out there for more people to see, consume and contribute. I can even share from my own experience this past week, as I decided to put a lot of “future considerations” I was working on (but hadn’t prioritized yet) out in the open within my own organization (via blog posts, wiki pages, video demos). Via my own fears or reservations I’d been holding what I was considering close to the vest. And the return I received from sharing was immediate:

  • It provided incredible ease of educating multiple people about possibilities because I’d already captured the concepts openly (shared with people that wanted to leverage what I was working on, or people I’d need to get approval from before I could proceed with the work).
  • It helped identify new opportunities from corners of the organization I hadn’t considered…triggering their own ideas of how to leverage what I was thinking about, at a time when I didn’t know if any interest would exist at all.
  • And people openly responding with new ideas on how to apply that work that I hadn’t yet considered.

And that’s all great. Those behaviors and realization of the benefits has resonated…with some. But after a certain amount of time, I began to realize that there were other key “Out Loud” behaviors emerging by knowledge workers in our network that contributed just as much if not more to the cause than what we’ve described as “Working Out Loud”. Maybe we can call them sub-behaviors of WOL. And some of those behaviors seem to be even more natural for people to pick up as they look to leverage “social” technology to get work done and connect with others. Behaviors that seem to reduce the hurdles of being a contributor to communities & networks…more than just trying to narrate work via a blog, or create observable work by storing it in open locations that generate activity streams to interested communities. Let’s boil these down into the concept of “xOL” behaviors. At least those that I’ve observed and found to be most effective to date in my own experiences.

Are these acronyms going to get me into trouble? Hmmmm… In the interest of keeping everyone engaged the entire week, and not starting off with a 3,000 word manifesto, my plan during #wolweek will be to share a new post each day that further defines and explores each of the xOL concepts above with examples and descriptions of how they may help you personally and your organization. And maybe Friday we’ll save for a new xOL I haven’t identified yet that emerges from the sharing and conversation that takes place during the week. And we’ll see if, for fun, I can throw in a few related Spaceballs references as well just to keep the theme alive :). Stay tuned! I’m looking forward to being inspired while learning from all those that will be sharing and participating in #wolweek! *Open Leadership – Credit: Charlene Li **Open Innovation – Credit: Henry Chesbrough ***Learning Out Loud – Credit: Harold Jarche

Advertisements

Working Out Loud: The Use Cases

I’ve decided to dig back into my roots of IT Requirements Management practices to contribute to the public conversation and understanding of the concept of Working Out Loud. For more on my personal history contributing to this idea, read here: Working Out Loud: What Happened to Then? We’re at Now, Now!

The below is a flow of an idea of something I’d like to get rolling on, with some help. Certainly not a finished product. And the target benefactor is an individual worker…or someone coaching individual workers about adopting “working out loud” work behaviors into their daily practices.

The Idea:

Capture the “behaviors” of someone that is effective at Working Out Loud into a modular use case format, organized around typical work behaviors and how each of those can be shifted to the “new way” of working instead of how most people in today’s work environment might go about that activity. And organize those use cases / behaviors / activities using John Stepper’s Five Elements of Working Out Loud.

  • Organize it and build it in a process similar to how I used to capture and organize IT system requirements packages.
  • Work Out Loud while defining Working Out Loud 🙂 So what does that really mean? A few things that will be critical to this working:
      1. It’s an ongoing work in progress, not a finished product. But I’m publishing it in progress, not waiting until it’s done.
      2. It’s public. You know I actually started this as in internal blog post for my company only? Bad Bryce, Bad! (Sorry. We have a new puppy in the house…habit.)
      3. Many Will Contribute. That way, it will get better as it goes and hopefully people much smarter than me will contribute to it! As a result, this post will be a living and crowdsourced table of contents that gets updated to reference new use cases / behaviors / activities are developed and shared by myself or others. As a result it must be…
      4. Modular. This is the parent post that will define the patterns and then link to the real meat of the topic. Whether those are blog posts I write for a given use case, or one that someone else decides to contribute within their own respective blog (or elsewhere).
      5. Open to Suggestions. These rules. The structure of the use cases. The use cases listed below. They are all open to improvement and change. Let me have it. Let’s make it better together.
      6. This Should be a Wiki. I know. I know. But I didn’t have a good one set up in the public domain to start from. And I didn’t want to lose the concept before my son’s basketball game today 🙂 I can see this evolving and moving to something more like a wiki format that takes me out of the role of “curator”. Once I get more time I’ll shift it to some place where we can all work on it in that form or fashion.

Writing a Use Case:

Each detailed use case should contain the following:

  • Work Activity Description
  • The typical / default behavior of today’s worker
  • The “Working Out Loud” behavior of tomorrow’s worker
  • Benefits of shifting the behavior
  • Risk Considerations / Mitigation
  • Real Life Stories / Examples of this “new” behavior in action. What was the outcome?

Use this definition created by John Stepper and captured on the Working Out Loud wikipedia page as a guide to brainstorming the application of the behavior to daily work activities:

“Working Out Loud is working in an open, generous, connected way so you can build a purposeful network, become more effective, and access more opportunities.”

The Use Cases:

Each use case is meant to represent a typical daily work activity.

If you have some that you think I’ve missed that you’d like added, please comment or contact me directly and I can get them added. This is a work in progress and merely a suggested starting point, including the topic groupings. As we identify and write new use cases, we can regroup and come back here and link to each individual one. Or eventually move this structure into a more wiki like structure in the not too distant future:

  1. Making Your Work Visible (Observable Work / In The Flow)
    1. Seeking an answer to a question / problem
    2. Answering a question directed to you about your area of expertise
    3. Answering a question directed to you unrelated to your area of expertise
    4. Creating a presentation for a team / committee / department / town hall
    5. Collecting team input prior to starting a work deliverable
    6. Creating content for a work deliverable (WIP)
    7. Collecting feedback on an in-progress work deliverable
    8. Creating content for a work deliverable (Finished Product)
  2. Making Your Work Visible (Narrating Your Work / Above The Flow)
    1. Writing your objectives
    2. Writing a project status update to management / customers
    3. Taking meeting notes
    4. Capturing brainstormed ideas about a project / process / opportunity
    5. Sharing progress / status on an assigned task
  3. Making Work Better / Creating Shared Value by Default / Leading With Generosity
    1. Achieving awareness of work outside your direct responsibilities
    2. Coaching people outside of your team / department
    3. Discovering external resources about your role / area of expertise
    4. Leading / Participating in corporate responsibility projects
    5. Contributing to the Corporate Conversation (Engagement, Activities, Facilities, Corporate Policies, etc.)
  4. Building a Social Network / Making It All Purposeful
    1. Forming and collecting a community of experts on a topic
    2. Connecting with fellow employees on personal interests

*Initial groupings could change or break apart. This is just a first shot at it. And we may find some use cases fit within multiple top-level categories.

I’ve spent as much time as I can spare on this this morning…but as I promised…this is a work in progress. And I was hoping to have completed at least one real use case example. But that will have to come in another day or two.

More to come! Comments for improvement welcome. And a format / structure more suitable to content crowdsourcing as well.