In a recent interview with one of our analysts, a Fortune 500 company’s HR director said (not verbatim) “It’s not HR’s job to define our culture. It’s the CEO’s job. It’s our job to communicate that culture.”
While I understand the position I have to say it doesn’t sit fully well with me. What do you say? Should HR have more of a voice in defining a company’s culture?
I’ve been involved with employee portals in at least 4 Fortune 25 firms in the past decade. I can say with some assurance that when it comes to their portals, what passes for long-term strategy in many large enterprises comes up decidedly short.
Strategy seems to be a bad word with a lot of enterprise middle management. There’s an artificially high value on short-term deliverables, getting easy wins and picking low hanging fruit. They believe they’re being agile and quick on their feet. They think it’s wasteful to be overly analytic. Quarterly goals are set at the expense of long-term vision, and the sad truth is that these managers are often in a revolving door; an ambitious manager achieves some carefully managed-down objectives, gets his or her gold star and is promoted in 24 months or so leaving a successor to clean up.
IMHO the baby has been thrown out with the bathwater.
I’ve known developers who have literally built, dismantled, and rebuilt the same system 3 times in a decade as the cycle of ‘new thinking’ turns endlessly. People with experience and long vision are often pigeonholed as being old-school, unable to think out of the box and have doubt cast on their often pragmatic stances. I was one of them. The outside experts were trusted to know more. I became one of those. Suddenly I knew more and am respected. Magical!
If I could advise these companies on anything, it would be train managers to be patient, to demonstrate why it really does take time to achieve world-class results and to let the first quarter of a project be spent developing a thoughtful and robust strategy that provides real vision and line of sight. They might finally stop churning and achieve the results that their mission statements so optimistically project.
When I sit down with a CIO or CFO I’m direct about the need for and value of a business-aligned strategy and honest about the time and effort it takes to achieve the goals they envision. Typically I get back honest appreciation and sometimes, relief. It’s not a cakewalk – these are sharp, brilliant people who cut to the chase with brutal efficiency. You will be mightily challenged, you must know your facts and truths and be prepared to turn on a dime from your prepared delivery. But one thing they universally recognize and appreciate is honesty. Don’t sugar-coat, misrepresent or adulterate the facts for your most senior management. They will respect you for it. You’ll suddenly be smarter, too.
At the company I was with 2 years ago the CEO had been holding town halls around the world. Corporate Communications had put together an intranet site to support the message, including a section that was positioned as being the CEO’s commentary.
One day I was chatting with the head of communications, and he asked me if I’d read the latest installment. Of course I had, personally I always found this section to be too scripted. I said that I thought it would help employees establish a sense of connection with the CEO if he were to keep a simple blog, and take a few minutes to type (or dictate) his own, honest impressions after the events, like “What a great reception I got when I arrived” or “A young man in a yellow shirt asked a really great question”, or anything that honestly sounded like his own thoughts.
My colleague’s eyes went wide. He said (I paraphrase) “Blogs? Blogs are diarrhea. I despise blogs. That’s not an appropriate vehicle for our CEO to communicate.” I understood his position – his career was built by carefully crafting and polishing words and paying great attention to nuance. Yet I could see that he wasn’t seeing the potential so I held firm, suggesting that people were more likely to react positively to a more personal voice. Eventually we agreed to disagree.
A year later the CEO’s Gen-Y son had convinced him that he should be using a blog to effectively communicate with his employees, and he wanted to start right away. I’d hate to be a senior corporate communications professional whose executives were getting direction from their kids before they got it from me.
If, in your professional capacity you may be impacted in any way by social media, don’t be dismissive. Pay attention to the changing landscape before it passes you by.
Best practice #5 – Remain neutral! Social media in the enterprise elicits emotional responses in some. Don’t let personal biases impair your ability to perceive the opportunity related to social media, even if you can’t fathom why people would use IM, blogs, wikis, Twitter…or whatever comes next. Something will and it deserves your objective attention.
Citigroup has seen it’s stock drop some 30% in the last month due to ‘exposure’ related to subprime mortgage debt issues. Last weekend, the CEO, Chuck Prince stepped down as a direct result of the losses. Prince Alwaleed bin Talal bin Abdul Aziz al Saud owns about three and a half percent of Citigroup. In an interview for Fortune, Prince Alwaleed comments:
“It is a pity what is happening, but I hope that a big lesson is learned in the board of directors and the management of Citibank.
Q: What is that lesson specifically?
A: The lesson is that, No. 1, this management has to be at the highest class possible. No. 2, they have to have a succession plan. You can’t have a company that size without a [successor] ready. And No. 3, you need a professional who has run a bank.”
Fascinating to see succession planning highlighted as a take-away for the board in light of write-offs approaching US $15 billion, yet I wonder how realistic it is for a company like Citigroup (or Merril Lynch, who are in the same position and presumably courting some of the same candidates) to have someone- internal or external – primed and ready to step up when the going gets weird. Jockeying for the top can be such a socio-political struggle that I personally can’t imagine modeling a plan to contain it.
So anyway, the job is apparently still open if anyone’s interested. Didn’t see it listed on careers.citigroup.com, though.
I had planned on a different subject today but Steve Mann’s bit on innovation in Able Brains touched something off. Read it, and then spend some time with his other writings, it’s been too long since I shilled his blog which is one of my regular reads.
There is a considerable gap between many company’s stated dedication to innovation as a competitive and growth lever and the eventual execution and product offerings. What passes for innovation in many places is too diluted to recognize. Steve offers some yellow flags:
“…if you work at an organization that doesn’t have a culture that (1) values innovation and (2) places governance, budget and resources around innovation – not that it never will but it may be a cold day in hell before Innovation becomes mainstream. Further, many top managers agree that corporate policy actually tends to offer limited incentives to innovation or limits it by placing an innovation team in a risk averse organization or business unit or having no plan to deal with failure other than to junk the team and start over. Some say this is a talent issue, other execs say its a cultural issue. The answer is “yes.””
Couldn’t agree more. I worked in e-business organizations which were walled gardens. We were kept at arms length so as not to infect the general population and once a product was deemed to be sufficiently cootie-free it was sliced out and transplanted into the business. Today, increasingly regulated and scrutinized operating environments makes innovation look more like a risk to be managed. I’ve seen the talent issues run both ways. We may have leaders and managers who have been conditioned to drive risk out, but at the same time we experience few skillful innovators and far too many who claim to be visionary but end up being undisciplined or ineffectual at matching innovation to business benefits.
The aversion to innovate affects more than competitive advantage and growth. I often work with clients whose IT has sufficient control over how apps are deployed to push them into vanilla deployments because they’re managing risk in terms of not wanting to manage code bases or introduce customizations that add complexity to upgrades. The result is business heads who don’t get what they need out of systems, with functional professionals who are relegated to awkwardly aligned processes, managers and employees who need to perform basic tasks and are presented with systems that require hours of training to use. The aversion to innovate at even this simple level – let’s make our systems easier to use by our own – is a direct cause of this pain. Risk needs to have a 360 review process so a fuller measure of is made before a decision that leans towards benefiting a single area is taken.
Many of the portals I’ve worked on have had a complete lack of attention to the HR practitioner. The generic scenario is an enterprise intranet, often driven by an underlying portal technology, with a static and outdated HR presence oriented towards policy and benefit information and links. These organizations are motivated to improve their HR offering and there’s no lack of energy around ESS and MSS integration, and plenty of thinking around how to balance centralized vs. decentralized employee programs.
When I recommend optimizing the experience for the HR professionals I find this has been given little to no thought, and that’s reflected in the environments I have seen for HRs, typically a password-protected sub-site with some stale documents and an unused discussion forum purported to be an exciting ‘collaboration’ space to share a handful of sensitive documents, with little thought to making it easier for HRs to work together (“Test Message” and “Hello World” seem to be the common subjects).
A couple of things – first, it’s generally acknowledged that the ERP user experience is sufficiently difficult to require supplemental front end work at a portal interface layer, yet the expectation is that HR professionals ought to be able to deal with it. Why is that? Frequent/’power’ users of an application stand to gain a lot from optimization, and I frequently interview folks who demonstrate tasks that require high numbers of clicks, screen changes, data fetching from other sources, etc. Training doesn’t make awkward processes efficient.
Second, the value proposition of leveraging collaborative technology in the HR space hasn’t been connected to the ongoing transformation programs in place at most large enterprises. I commonly hear from professionals out in the businesses and regions that don’t have a good sense of what’s going on in Corporate, and they often feel that their local dynamics are either unknown of ignored. Corporate people often expresses that they feel disconnected from the field and have little visibility into who does what, where. Often HR operations is under pressure to reduce operating costs, making it appear counter-indicative to provide practitioners additional IT effort on top of the ERP systems that are already in place.
Contrast this with sales. Here’s a function with similar needs: to rely on ERP but in this case a recognition that there is also a supporting data, historical information and a need for awareness of ongoing work efforts among their teams. Sales has always had a tacit social knowledge network supporting a set of individual practitioners performing against personal and group goals.
The big difference is that sales generates revenue and HR is an expense, and as such it’s managed quite differently.
The HR Professional portal should provide a functional workspace with information and tools that can be managed by a distributed workforce, centered around the areas that align to the business and corporate HR strategies and moves the value proposition away from the administrative formula. I’ve yet to see an organization that doesn’t get an ‘ah-ha’ moment when we talk about it but I have seen those that just can’t get it either funded of adequately staffed and developed. Where we are building them, they are in their infancy but I feel they will have high value as HR emerges as a strategic business partner over the next decade.
Let it be!
In best practice #3 I say that without governance, social media risks failure. Now I’m going to speak out of the other side of my mouth and say that too much governance will also lead to failure.
Like raising a child, there’s a responsibility to set a foundation that supports positive and healthy growth but one must step back and not interfere – most of the time. Groups will ultimately define their own priorities and tone, and to be valuable to itself and ultimately to the enterprise they shouldn’t be meddled with.
Overly visible ‘management’ will almost certainly stifle open discourse, and that is the opposite of the exact value proposition that social media holds. With all the thought, care and consideration given to establishing an appropriate medium for collaboration and discourse it will be hard to step back and let this nascent environment develop according to it’s own needs. The fact that the intranet environment is by definition controlled by a relative (and often somewhat disconnected) few within the organization makes this even harder.
Find the balance and resist the urge to steer conversations. Let people bump into things and make mistakes, just keep an eye out so things stay civil. In time, the community will be on it’s own feet and in the best case will become self-maintaining.
Best practice #4: Don’t interfere with the community-building process.
Yesterday I was speaking with a client about collaboration opportunities for a certain community. They described a common scenario – employees had been given broad access to Sharepoint. Folks rushed out and set up their own spaces, and now nobody collaborates across them. As a result information and knowledge is more hidden than it was before ‘collaboration’ became broadly available.
As true with collaboration than many other areas, lack of governance is a sure way to failure. There’s a common perception in the general public that a site like Wikipedia is a wild west, with anyone and everyone invited to say whatever the heck they want about anything under the sun. While a bit of that may be so, there is in fact a shadow army working within a rules set that generally rights egregious wrongs, often in near real time. Rules are indeed in place and they’re both explicit and tacit.
A rules set, structure and governance is necessary to ensure the context and health of of a collaboration platform. Volumes have been written about supporting a community, and the subject can run quite deep. For a pragmatic approach to the common problem described above I recommend reading what James Robertson of Step Two Designs posted today, a tidy summary of four stages that move the adoption of collaborative tools from fragmentation to coherence.
Best practice #3: Collaboration requires a balance of freedom and governance to thrive.
One of the first issues that comes up in the business community when discussing social computing behind the firewall is control. It’s a valid issue – companies can and are held liable for the actions, words and postings of individuals. The expressed concern is that given unfettered ability to post to a blog, wiki, discussion thread or more traditional intranet page, employees will behave badly at worst or incorrectly at best. Most often this point of view comes from the communications disciplines, who sometimes hold a conceptual model of the intranet as analogous to the newsletter or house publication, which of course is the domain of the Editor.
Publication models are still valid, but they’re no longer primary and are rapidly being replaced by transactional and collaborative models that place the value proposition more directly in the hands of the knowledge worker. It’s good to remind our communications colleagues that we’re not publishing when we send emails, we’re using technology to collaborate and share knowledge. It’s easy to see from there that what some social media represents is moving those activities out of the inbox and into the browser. Organizations with sufficient size and maturity have existing communication policies that should adequately cover the forms of communications afforded by social computing.
Sometime in that last century, the intranet I managed featured a threaded discussion forum which was greatly underutilized. An interesting ‘feature’ was that we relied on the honor system for registrations. We required an email address to use the forums and presumed that folks would identify themselves honestly. A group of employees in a service center proved us wrong. These employees were not given email as a policy so to use the forums they simply made up names or even used their personal email addresses (in retrospect, a Bad Idea). At first the group dynamic was light and friendly although they used it conversations about everything except work. Within a few weeks the crowd got larger and the conversations veered towards the street corner. We rang an alarm and pulled the service. Within a few weeks we had tightened governance and included an address verification process which drove anonymity out of the system.
Best practice #1: Trust, but verify. People behave better when they know the rules and are identifiable.
JP Rangaswami speaks of what people really do in the enterprise and how technology can and should assist those human needs. Some sound bites:
“…it is only a matter of time before enterprise software consists of only four types of application: publishing, search, fulfillment and conversation.”
“In an enterprise these relationships are usually to do with the department the person belongs to, and the reporting line. What utter tosh. Those are not relationships. They are irritants. Irritants apparently required in order for people to allocate costs and profits accurately….I am prepared to change my mind on this, the day I meet a customer who cares about what department I work in or whom I report to.”
“…people appear to ‘work’ by doing four things:
They look proactively for information. They search for things.
They receive information because they said they were interested in receiving that information. They subscribe to things.
They talk to each other using various forms of communication: letter, e-mail, audio, video, text, IM, blog, wiki, twitter, whatever. They are even known occasionally to talk to each other face to face without use of technology.
And they transact business as a result. Within the enterprise. In the extended enterprise and partners and supply chain. With customers.People do all this now. But we do not have the tools to do the job well.”
Thank you, JP for addressing what’s been missing in much the Enterprise 2.o talk of late, that being the question of “why?”. For a long time it seemed like there were two vectors driving the conversation:
a) Pro: “Look at all this AJAX-y goodness! We must bolt this on to our ERP so it doesn’t appear to be so hard to use!”
b) Con: “People are cats, they are unloyal and must be herded. Do not give them freedom to go outside the box (pun intended) or we shall introduce Risk.”
JP highlights the reason social computing has taken off – people are social and desire community. In the enterprise that means we want to work together in a fluid, on-demand manner. Nothing provided in of standard office productivity tool suite does that. They’re fine for turning concepts into artifacts, like insects in amber, but interchange is asynchronous and awkward at best. We fought for IM behind the firewall ten years ago and it’s still unusual to find widespread use.
In my workplace people form virtual teams around projects. Organizationally we’re pretty flat except for natural team groupings around core competencies like graphics, usability, technology, etc. A natural pattern has emerged where folks on a project tend to take over an available space – usually conference rooms – and cluster together so they have proximity to share ideas while their heads are stuck in their laptops creating the artifacts that emerge from their interaction. The fellow whose office is next to mine hasn’t been in it in 6 weeks. They sometimes bring graphics, products and designs into the room that reflect the project that end up being the cave paintings representing their new environment and their recent hunts as they share stories around the virtual fire.
OK – maybe that’s kind of stretching it to the poetic, the point is people require freedom to congregate and bounce off each other if they are going to produce excellence. Malcolm Gladwell holds that modern genius emerges more from collaboration than from the lone insightful person (video here).
I’ve know of an organization whose 3-year plan includes a key feature – Employee Development. Yet they have no training and development resources at the corporate level, and precious few in the businesses. This disconnect is where we find the enterprise; they truly want employees to collaborate. Yet the best tools: audio, video, text, IM, blog, wiki, twitter…are often unavailable or even banned for fear that the cats will be distracted into mere chit-chat.
As I write I see that Michael has asked for thoughts about how social computing tools can play inside the firewall. Consider this a start. I’ll say that the first critical aspect for social computing success in the enterprise would be to ‘trust…but verify’.
More later.