We have a pretty clear picture of what a social organization looks like on the outside - marketing and sales becomes a pull rather than a push discipline and customers are much more involved throughout the customer lifecycle. But what does this new organization look and feel like on the inside? There are not many discussions of how employment and management structures change to become more agile.
There is more agreement on the issues:
- Slow moving, rigid organizations do not adapt to increasingly fast moving markets.
- Siloed information within organizations creates huge redundancy issues and makes efficiency difficult.
- It is quite challenging to hire individuals that can operate in large inefficient organizations and drive innovation or think differently and therefore organizations lack the 'best and the brightest' talent.
- Certain kinds of talent, particularly in the area of collaboration, are poorly identified and rewarded.
- Middle management is incented to protect their turf and hoard information leading to archaic corporate politics and huge inefficiency for the organization.
- The hiring and layoff cycles have created immense distrust of employers.
- Employees are increasingly stressed due to unease about their job stability, the deluge of information, and increasing responsibility to fund their own health insurance and retirement.
- Families with two working parents are strained for time. Families with one working parent are increasingly uneasy about the risk of one paycheck. Single adults are increasingly stressed because they are viewed as the employees most ready to work long hours.
- More and more individuals want to be in control of their own work life since the perceived risk of working for a large organization is not significantly lower (and may be greater) than the risk working for themselves.
Most organizations have a long way to go to be places that employees are clamoring to work for but in the new communications environment that clamoring employee enthusiasm will drive revenues and market share if it exists. That employee enthusiasm also drives alignment with corporate values and messaging, increases opportunities because all employees are advocates, an decreases risks because employees feel more individual responsible for protecting the interests of the organization.
So what might this organizational nirvana look like?
Employment becomes a cross between a long-term commitment and free-agency: The organization provides employee overhead (benefits) in exchange for a commitment to work a minimum number of hours on organizational projects.
Managers are either focused on professional development or projects: Managers no longer 'own' a functional piece of the business but either manage a group of employees to help them choose projects and navigate their career or they manage projects.
Employees and Project Managers Negotiate Work Commitments: Employees are free to self-commit to projects for which they are interested and have time. Project managers define project roles, time needed, and associated pay and are responsible for recruiting team members and managing the project to completion. Employees can work as little (as long as the reach the minimum required for employment) or as much as they feel they are able to at that time. Project managers can solicit specific employees or change the pay to get employee commitment. This has the side affect of paying more, not less, for tedious or unappealing jobs.
Employees Manage Their Schedules. If an employee has a family member with an illness and needs to work the minimum required, they choose their project commitments accordingly. If on the other hand, they have time and want more hours to maximize their income, they can choose a heavy schedule.
Employees define themselves by skill sets, attributes, and experience based on a published taxonomy so that project managers can find and solicit team members.
360 Degree Reviews. Everyone on a project gets to review the performance of everyone else, with some templates and guidelines to do so based on organizational values and goals.
Executive Tasks Are Earned. Based on the successful completion of projects that represent bigger and bigger pieces of business, executives earn the right to budget or more loosely defined (risky/innovative) projects. Some executives will continue to select projects with bigger budgets and some executives will likely continue to choose more innovative projects, depending on their interests.
A Senior Executive Team Is Still Necessary. The C-Suite will still set the overall strategic direction and priorities for the organization - with plenty of input. The C-Suite will also oversee the initiation of projects, the arbitration of issues between teams, and they will ensure gaps are being addressed.
All Projects Are Vetted, Prioritized, Budgeted and Scheduled. Any employee or customer can initiate a project but there are various committees, depending on the size and purpose of the project, that vets and schedules them. These committees are filled with project managers that rotate on and off of them, based on the interest of the project manager themselves in participating.
Customers Can Be Project Team Members. If a customer is particularly invested in a particular project and have the appropriate skills, they are incorporated into projects.
The overhead of organizing in this way has been too high in the past, particularly for very large organizations. However, technology - both enterprise functional software as well as networked communications software - has made the overhead of managing this complexity much easier. Models similar to this exist in the professional service world - the big management consulting, marketing, and accounting firms. I think it's time to test it out in more traditional organizations as well.
Generally we need to get away from the parental model of the organization to one that views employees as partners and both treats them and expects them to act like adult peers. This will require an adjustment for many employees as well - there are many people who like the easiness of just being told what to do but that makes them sub-performing employees which organizations can no longer aford if they want to compete globally.
This model also introduces new issues and risks - what are some of these issues in your mind?
Update: One emerging model that I really love is uTest - for more on their business model innovations, built around community, read their latest update here.

Hi Rachel-
indeed I do love this vision, especially the ways that you've extended out some specifics from the general (generic?) claims about what social work tools might make possible.
This vision (so far) focuses on how to get work done, by explicitly considering members' compensation, scheduling, work limits/thresholds, content focus, and careers. I appreciate that you've taken the individual members' standpoint to look at what changes would be desirable, and not stayed stuck in what's in it for executives, for investors, for the bottom line.
And, in terms of the tech systems that would be utilized first, the emphasis would be on (what Stowe Boyd likes to call) systems of work -- knowledge work & worker management.
An element yet to develop (which you know is a concern of mine) is the role that social organizational systems/networked communications will play in creating collective meaning, individual meaning, the experience of contribution over the experience of extraction, and more democratic power distribution. But, I think that these more socio-political elements can emerge from a well-executed work-focused systems implementation.
This is all very exciting. Thanks so much for pushing the envelope with this conversation (exclam pt). cv
Posted by: twitter.com/cvharquail | May 11, 2011 at 10:24 AM
I've been giving this topic a lot of thought lately Rachel. Would love to convene a "roundtable" topic around this idea on site in Boston, perhaps?
Moving to a more flat, self-organizing, fluid operating model for the largest organizations (not modeled on billable hours income), is more dream than vision today, sadly. Although, I LOVE the vision, don't misunderstand me. I was reminded of this recently when I read the Wired piece on Steve Jobs and the Apple culture. http://www.wired.com/gadgetlab/2011/05/steve-jobs-magic The parental model works really well, unfortunately. I will say, on behalf of the Council members, they're working really hard to introduce these changes. But it will be slow and quite possibly painful. Great post, though. Love it.
Posted by: twitter.com/ITSinsider | May 11, 2011 at 11:43 AM
Rachel,
Great post! That is all. Hope you are well.
Brian
Posted by: Freecrmstrategies.wordpress.com | May 11, 2011 at 03:47 PM
By far the best part is that customers can be team members. As with most companies, employees don't want to see how 'messed up' they are - but ask anyone, the customer know you aren't perfect and including them in your improvement does more for business and collaboration than imaginable!
Posted by: CollaborateKing | May 11, 2011 at 04:38 PM
Great post, Rachel. Among the many thoughts it will make me ponder were:
- How does this framework interact with the notion of employees vs. contractors/partners? With the fluid nature of what you describe, what is the benefit to the business of having anyone be an actual employee, as opposed to a contractor (or employee of a sourcing partner) that is only connected for the course of the project they signed up for?
- What, if any, is the appropriate role for restricted access to information (proprietary, IP, secret sauce...) within this framework?
- How is performance to corporate goals effected by a more "contractor-like" existence by all/most employees?
I could go on. Needless to say, it's a thought-provoking post...thanks!
Posted by: Dmeiselman | May 11, 2011 at 04:58 PM
Excellent post! Most reading managers might get scared on the thoughts this post sparks. Needless to say how scared they might get if they don't face it!
For regions under serious trouble, this could mean a quantum leap! For the very accustomed to parental (fine tuned and indulgent) organizations this might look a bit naïve...
Very good food-for-thought!
I would love to translate it to spanish, may I?
Posted by: NeiraSchliemann | May 11, 2011 at 06:29 PM
A lot of organizations already operate with some of the things you've outlined. "project based" or matrixed organization that have 60% fulltime and 40% contractors. I'm not sure this is a vision for an organization to be "social". Being social is more about community building and the ability to manage and capture relationships, conversations, and business activities....which are generally informal, undocumented, via email, in-person, over the phone. I am writing a series of related blog posts on AIIM: http://www.aiim.org/community/blogs/expert/The-Social-Organization-Part-I
Posted by: Pmpinsights | May 11, 2011 at 09:17 PM
Wow - great comments. Apparently I shouldn't post and dive into a big project :)
I realize that this construct leaves a lot yet to think about so thank you all for adding those things that struck you and Susan, to your point, I also don't know if many organizations can make a transition from very hierarchical to somewhat flat. The cultural barriers may just be too big.
@David I think that organizations need some easy/guaranteed/verified 'employees' and on the opposite side, employees want some commitment as well. So hence the something between employee and contractor. That relationship would also cover proprietary IP. But you are right, the details would need to be sorted out on how that works in various contexts.
@Neira - Please feel free to translate and thank you for asking.
@Rich I see employee flexibility and control as the logical conclusion of an organization being more conversational. If you are really going to listen and hear what employees need, they need more flexibility and control over their jobs. So... in my mind they are very closely related, all part of a much more fluid set of relationships, as you speak to in your post.
Posted by: Rhappe | May 11, 2011 at 09:48 PM
Hi Rachel. Great post and im dropping you a line, would love to talk more. Couple of points i would raise though:
1) Its not Nirvana! We only think it is against a backdrop of decades of command and control org structures which, given we are almost in the worlds deepest financial mess, raises questions about the validity of this model we hold so dear.
2) You say "The overhead of organizing in this way has been too high in the past, particularly for very large organizations." I disagree! Are you familiar with Semco in Brazil? They have many elements of this model, and more. Ricardo Semler was way ahead of his time and continues, today, to be ridiculed for his approach. Yet he has transformed that organisation and achieved consistent success and growth for nearly 20 years in one of the worlds most challenged and corrupt economies.
Technology is an enabler for sure, but attitudes are the barrier. Glad i found you and look forward to more of your posts.
Posted by: Garelaos | May 12, 2011 at 04:01 AM
Great post - has got me thinking about how some of these ideas can translate into the public and not for profit sectors where we really need to get social to overcome the many historic bureaucratic hurdles we face to do our job.
In that context one thing I'm not so sure about is project review committees. While some mechanism to vet projects is needed, creating new committees is always risky in the public sector in that it can introduce new forms to fill and hoops to jump through, and often the decisions are more political (in the office rather than party sense) that they are based on true priorities.
I really like the idea of "customers" or in our case "beneficiaries" being project team members though - we really need to find good ways to do more of this.
Posted by: Kmonadollaraday.wordpress.com | May 12, 2011 at 06:00 AM