Design and “Gamification At Work”

June 24, 2013

gamification_at_work

The Interaction Design Foundation is publishing Gamification At Work by Jankaki Kumar and Mario Herger for the public tomorrow. I just finished reading the book and taking notes thinking I might review it. However, rather than do a simple review of the book’s content, I decided to situate the major points from the book into a post on the general topic of gamification in the workplace.

I appreciate the opportunity to read the book’s early release and, if you haven’t yet seen it just click on the link to it above and you can access it as well. Hopefully you will also consider reading my own thoughts on how the points in the book fit into what is most aptly considered gameful design.

Gamification At Work is an interesting read for several reasons. Kumar and Herger not only cover the essential components of a well-thought approach to why playing games is not antithetical to getting work done. They add to that contribution by outlining a design strategy, which they refer to as Player Centered Design, and providing case-study insights from the SAP Community Network that add essential details to each part of their overall discussion.

Read the rest of this entry »


Siloed Social Conversations Impede Shared Experience

June 19, 2013

screenshot-altimetersocialbusiness-2013

The Altimeter Group’s report from earlier this year, The Evolution of Social Business: Six Stages of Social Business Transformation, offers the above graphic to exemplify the way social networking develops as the social activities of businesses mature. I tend to feel skeptical about many developmental models in social business simply because markets differ, sometimes in fundamental ways, and businesses organize accordingly. However, since a previous post here summarized the currently dominant Hub and Spoke approach as falling short as a way to organize collaboration in relation to customer experience, I feel elaborating on that point is in order.

Shared experience, not just shared information, is fundamental to the social networks underlying collaboration and innovation. Many, if not most, employees don’t only need to get to know one another through reputation systems, like who people tag as possessing expertise. As Thomas Vander Wal continues to point out, comfort with one another is needed to develop a shared experience that encourages the open sharing of information.

Collaboration means getting to know that other employees possess expertise on this or that topic, but also developing comfort with one another by sharing significant symbols relating to self, family, friends, and social activities, thereby understanding one another as people. Shared experience with co-workers and customers is a key factor in innovative business practices. It is especially important to multichannel collaboration.

Shared experience is so important because, as Karl Weick so deftly noted almost twenty years ago, it provides the basis for mutual understanding or, to put it bluntly, how we understand one another when we do things together. Nancy Dixon recently offered a concise summary of this point which I recommend reading.

I’ve noted the importance of shared experience to collaboration in several posts. Michael Sampson summarized the points I’ve tried to make as aptly as anyone in his post Get to Know Your Virtual Colleagues as People – and Good Things Happen (to Important Things Like Productivity) and his perspective is much appreciated by me. He noted:

Trust between collaborators is an important factor related to collaboration effectiveness. Spending time talking to and learning about the people you work with provides the mechanism for trust to flourish – if they are trustworthy – or diminish – if they are not worthy of your trust…It makes sense that when people experience the same thing together – creating shared history and shared memories – it binds the group together in a much deeper way than merely having the same information.

So, you might say, what does this have to do with organizational silos?

The best way to begin answering the question is to look at an interesting insight offered by Mark Fidelman and Dion Hinchliffe regarding the cross-currents enterprises face in attempts to use social software to increase collaboration. In Rethinking the Customer Journey in a Social World they noted:

…it’s the mindset of the social world, where everyone knows what everyone else is doing, and perhaps even thinking, that may very well be the hardest to adapt to and instill in our corporate culture. It’s a world where those who know how to tap into global knowledge flows in social networks on the “edge” of our businesses will succeed. Thus, we need a new vocabulary for understanding not only our businesses, but how it will deeply affect the entire experience of our customers, from beginning to end. This transformation of thinking and working is required in order to access the significant benefits of truly remaking how we engage with the market.

Their thinking seems torn between insight into where the changes for business are headed and what they think likely to happen in the short-term. Dion in particular recognizes the fact that social business requires organizational transformation when, for instance, he asserts, ” social business is first and foremost a transformation involving people and the organizations they work with.” Yet, if you consider where he thinks the in-roads for social software (including social media) are for business over the next year or so, the contrast in perspective is pretty distinct. Dion says in another post that it is in the vertical space of enterprises where most of the innovation is set to occur for social software.

While general purpose social software platforms can certainly be used in all of these areas, high impact application of social media to the way we work often requires application-specific constraints on conversations and the resultant community activity (my emphasis). This means social customer care benefits from conversations organized around support, social supply chain focused on ERP transactions, and so on, along with software that supports these applied uses.

Yammer spread out over Sharepoint sites is a good example. The enterprise use-cases of social business implementation offered by Ray Wang support Dion’s assertion. Indeed, one of the recent findings by The Community Roundtable offered in their 2013 State of Community Management report is indicative. The report observes that community managers are most often “hubs” and, further, that:

Key factors, such as the amount of cross-functional interactions and size of community teams [with external or internal focus — my point], are putting a resource strain on community managers, particularly in large organizations.

A key organizational point is worth making here because it relates directly to the burdens the hub-and-spoke model, whether  cross-functional or dandelion, places on collaboration between employees, customers, partners, and other stakeholders. Indeed, the “Tip” offered by Jeremiah Owyang of Altimeter regarding the “dandelion” hub-and spoke model is telling. He noted that,

the lines connecting the multiple hubs may be severed.  Tip: provide way for spokes to connect to each other, not just be funneled through a central group.

Just like social networks do not respect organizational boundaries, edge cases do not respect vertical (read, silo-oriented) organizational constraints on conversation. This is an important point when you consider that most of the time spent by employees involves dealing with edge cases, i.e. exceptions to core processes. I suggest that at least part of this outcome results from the fact that not enough employees in the enterprise develop shared experiences. If you agree with me, I guess we just need to think about how to make this happen. If not, then you probably need a bit more detail which, hopefully, you can spare the time for.

Read the rest of this entry »


Podular Organization and Edge Businesses

May 9, 2013
Podulation -- From Dave Gray's Connected Company

Podular Design — From Dave Gray’s Connected Company

In Institutional Innovation and Podular Design I noted a number of insights from the Aspen Institute’s report, Institutional Innovation: Oxymoron or Imperative?, especially that “the most important innovation challenges are now in fact institutional in nature.” As an aside, let me just note that institutions typically change in dramatic ways only over long periods of time. Think of institutions such as religion, government, the economy, and then consider the various organizational forms in which these institutions took shape across cultures over time.

One insight I have not discussed in previous posts is relevant to understanding the changing way teams work together in organizations and, by implication, in a Connected Company — as outlined by Dave Gray. Richard Adler the Rapporteur for the Aspen sessions, noted that,

“New findings about the power of collective intelligence and about the most effective ways of organizing teams are providing practical insights about how to accelerate innovation.”

To start, let’s consider many companies organize teams and then turn to the “power of collective intelligence” mentioned by Adler to see how the two relate to podular organization. Several research projects in recent years noted the fuzzy boundaries of teams in large organizations. Skilful Minds first noted this phenomena in Who’s on Your Team? Enterprise 2.0 and Team Boundaries , and then a couple of years later in Social Learning, Collaboration, and Team Identity.

In fact, the phenomena of transitory team membership is so pervasive that some people propose we analyze “teaming” rather than teams when talking about how groups organize for cross-functional purposes within, or between, companies. Consider, for example the way, Mark Mortensen summarizes this trend in team dynamics,

First, organizations increasingly require collaborations to be fluid in their organization and composition, able to adapt to the rapid changes of the external environment. Second, collaborations increasingly overlap with one another, sharing resources — including people — as those resources become more limited due to increased competition. Third, collaborations must increasingly take into consideration the different contexts within which collaborators are embedded, including locations, time zones, cultures, and languages, structures, or organizations.

The liminality of such transitory teams results from several institutional challenges including the high degree of misunderstandings that initially occur due to team members rarely having the time to translate the different ways of thinking that people bring from their professional specializations into a mutual understanding of their shared business purpose. Developing mutual understanding requires shared experiences, getting to know who you are collaborating with, not just what they do or their skills profile. In addition, conflicting functional priorities, and often a lack of clear accountability, make it difficult for such teams to remain focused on the business purpose of their collaboration.

Teams were not always organized this way. As Mortensen notes, teams in multi-divisional companies were, at one time, defined by bounded and stable team membership and common goals that interdependent work was required to meet. Cross-functional teams in such companies today are not typically defined by bounded and stable membership, and common goals are still too often related to divisional performance driven by scalable efficiency rather than a connection to the purpose of the business the team is serving.

As Brown and Hagel recently observed:

Over the last 40 years, the emergence of new digital infrastructures and a global liberalization of economic policy have increased the pace of change exponentially. Many companies that were extremely successful in earlier times of relative stability are now finding that their relationship architectures are fundamentally misaligned with the needs of their business today. As the pace of change increases, many executives focus on product and service innovations to stay afloat. However, there is a deeper and more fundamental opportunity for institutional innovation—redefining the rationale for institutions and developing new relationship architectures within and across institutions to break existing performance trade-offs and expand the realm of what is possible.

Institutional innovation requires embracing a new rationale of “scalable learning” with the goal of creating smarter institutions that can thrive in a world of exponential change.

The challenge then remains how to enable organizations to adapt to their ecosystems by enhancing access to flows of knowledge that are likely to result in learning. Leinwand and Mainardi recently observed that permanent cross-functional teams tend to fare better than transitory teams in engaging organizational ecosystems. As they note:

We’ve recently seen a more robust cross-functional construct emerge, one  with an overarching organizational structure, based on building and maintaining a distinctive capability. Members of these capabilities teams are assigned permanently to them, reporting there rather than through a functional hierarchy.

Permanent cross-functional teams provide an institutional basis for what Hagel and Brown refer to as edge businesses that develop within large-scale enterprises, noting that such companies “should resist the temptation to confront the core, and instead  focus on opportunities on the periphery or at the ‘edge’ of their businesses that can scale rapidly.” I suggest below that Dave Gray’s conception of podular organization affords an important insight regarding how the institutional innovation of edge case businesses can develop and organize. Read the rest of this entry »



Social Flow and the Paradox of Exception Handling in ACM

September 28, 2011
Compliments of Dave Gray’s photostream

There is nothing like an exception to the way things are done to highlight the need to increase knowledge sharing, especially if the exception is one instance of a pattern that results in bad experiences for customers. As Jay Cross recently noted, people learning at work rely on social, or informal learning, around 80% of the time. Interestingly, I noted in a former post, Social Learning and Exception Handling, that John Hagel and John Seeley Brown contend that “as much as two-thirds of headcount time in major enterprise functions like marketing, manufacturing and supply chain management is spent on exception handling.” It is not coincidence that the two numbers are aligned.

Social Learning and Exception Handling, discussed the organizational challenges involved in dealing with exceptions to business process and their relationship to the shared experience of people working together saying,

The most basic point to remember is that exceptions to formal business processes require efforts to design a scalable learning architecture that supports content co-creation needed to adapt to emergent challenges and manage the flow of that adaptation through an enterprise’s ecosystem. Whether judging an adaptation successful requires it to result in new formal learning content, i.e. content co-creation, or a new business process, i.e. organizational innovation, or both, remains an open question.

Informal, social learning is key to exception handling since both make up most of what people do in organizing work in enterprises. We know people face difficulty when drawing from shared experience, especially in distributed teams because fewer points of common reference exist. Leadership and management consultants often contend a common organizational culture pulls teams together, even though distributed teams frequently span national, regional, and global locations. However, the mere challenge of everyone on a team knowing who else is a member can prove daunting as enterprises grow.

One of the promises of social business is the capability to embed social networks into human relationships to organize business enterprise in a way that people can act together without centralized command and control. The discussions linking the capability involved with its organizational implications for group performance are far fewer. Dave Gray’s discussion of pods in The Connected Company is one notable effort in that direction. In my conception of it, the key challenge is one of organizing businesses for social flow.

Read the rest of this entry »




Social Learning, Collaboration, and Team Identity

March 4, 2010

Harold Jarche recently offered a framework for social learning in the enterprise in which he draws from a range of colleagues (Jay Cross, Jane Hart, George Siemens, Charles Jennings, and Jon Husband, all members of the Internet Time Alliance) to outline how the concept of social learning relates to the large-scale changes facing organizations as they struggle to manage how people share and use knowledge.

Harold’s overall framework comes down to the following insight,

Individual learning in organizations is basically irrelevant because work is almost never done by one person. All organizational value is created by teams and networks. Furthermore, learning may be generated in teams but even this type of knowledge comes and goes. Learning really spreads through social networks. Social networks are the primary conduit for effective organizational performance…Social learning is how groups work and share knowledge to become better practitioners. Organizations should focus on enabling practitioners to produce results by supporting learning through social networks.

Indeed, Jay Cross suggests that the whole discussion needs framing in terms of collaboration, and I tend to agree. Yet, saying social learning occurs largely through collaboration means delving into the subtleties of how social networks relate to the organizing work of project teams as well as to their performance. After all, much of the work done in Enterprises involves multidisciplinary teams, often spread across departments, operating units, and locations.

One of my earlier posts posed the question Who’s on Your Team? to highlight the importance of social networking to establishing team identity and enhancing knowledge sharing across distributed, multidisciplinary teams. Its focus was on the importance of social software applications in the Enterprise to the ability of distributed project team members to recognize who is on their team at any point in time, and who isn’t. Organizational analysts refer to the challenge of establishing team identity as a boundary definition problem for teams, when members are spread across large distances whether geographic or cultural in nature.

Read the rest of this entry »


Empathy and Collaboration in Social Business Design

August 27, 2009
dachis_eco

Source: David Armano "Social Business by Design"

My first corporate position carried the title Methods Analyst, working for a large billing center serving a telephone company. One of my main tasks in that role involved learning how other employees performed their work and documenting it. On each project I typically spent several hours observing people work (what some today call rapid ethnography or guerilla ethnography) and then did in-depth interviews of the people I observed. Usually, at the end of my observation, I took responsibility for doing the work for a brief time under their watchful eye. In some sense you could say my work required me to continuously cross train in other people’s work, analyze the process, and write it up in a technical document.  The main insight I took away from that experience was an appreciation for the importance played by empathy in effective collaboration.

First off, collaboration isn’t just about people sharing information to achieve common goals. Collaboration is about people working with other people to achieve common goals and create value. Advocates of Enterprise 2.0 sometimes make the fundamental mistake of arguing that collaboration is really only about achieving business goals, leaving the implication that incorporating social software into the work flow of organizations is sufficient. Even though goal-orientation is a big part of collaborating, collaboration requires more to achieve goals effectively. It requires shared experience. As Dev Patnaik and Evan Rosen recently noted, empathy and collaboration go hand in hand.

Read the rest of this entry »


Scalable Learning and Learnscapes in Social Business Design

August 10, 2009

 learnscapeAbout a month ago I read What Would Andrew Do?, an unbook by Jay Cross and friends. I’ve mentioned Jay’s work in previous posts dealing with elearning 2.0 and collaboration in informal learning. In particular, its important to remember that focusing on informal learning doesn’t mean we must disregard the relevance of formal learning because learning is never 100% formal or informal.

However, the term scalable learning probably does require a bit of clarification. After all, isn’t elearning supposed to scale to the size of the learning group and remain available when they need it, where they need it, as long as they are connected to the Web? Well, yes–and it does pretty much. Nevertheless, instructional designers too often fail to incorporate emergent learning requirements of the organization, the enterprise, into  their learning architecture largely because the approaches used to evaluate learning content (whether elearning, blended, or instructor-led) do not incorporate assumptions about the larger ecosystem’s need for the co-creation of knowledge.

The concern for whether the learner is exposed to every thread of content in every course, and assessed for mastery of the information, tends to predominate design thinking about learning, and for compliance training sometimes this is required.  However, too often, instructional design fails to focus on whether the learning scales to support the learner’s ability on-the-job to recognize a problem as a particular kind of problem, much less provide the ability to find the learning content that provides a solution.

I don’t intend to delve here into the minutiae of distinction possible between types of learning. Suffice it to say that when a learning architecture supports all types of learning along the range of formal, non-formal, and informal experience, it must design formal learning in small enough chunks to serve as resources for non-formal and informal learning activities. It also means that the knowledge created using non-formal learning (whether mentored or accomplished in collaboration with peers), or informal learning taken on its own, needs to become a performance resource in developing new formal learning content.

Jay contends that the performance challenges facing organizations are most aptly conceptualized as a learnscape, a concept initially articulated by John Seely Brown and Paul Duguid. In the August 2009 issue of Chief Learning Officer magazine, Jay offers the following synopsis.

Learnscapes are the factory floor of knowledge organizations. The “scape” part underscores the need to deal at the level of the learning environment or ecology…The “learn” part highlights the importance of baking the principles of sound learning into that environment rather than leaving it to chance.

 John Hagel sees learnscapes as part of a global transformation of industrial society that he, John Seely Brown, and Lang Davison call the Big Shift: the move from institutions designed for scalable efficiency to institutions designed for scalable learning. Hagel’s thinking is relevant since, as I explain below, Jay uses the Push/Pull distinction to demarcate formal and informal learning. The basic insight is conveyed by Hagel, Brown, and Davison in their thoughts on Measuring the Big Shift:

Companies must move beyond their fixation on getting bigger and more cost-effective to make the institutional innovations necessary to accelerate performance improvement as they add participants to their ecosystems, expanding learning and innovation in collaboration curves and creation spaces. Companies must move, in other words, from scalable efficiency to scalable learning and performance. Only then will they make the most of our new era’s fast-moving digital infrastructure.

The participants that Hagel, Brown, and Davison refer to consist of consumers, customers, partners, and employees using social media to talk about, talk to, and engage the products and services, i.e. brands, that an enterprise markets. Don’t misunderstand the focus on performance in the discussion of scalable learning. It isn’t about the traditional focus on efficiency, pursuing ever leaner processes for the sake of officially recognized best practices. Rather, the focus is on creating the knowledge needed to adapt to emergent challenges and manage the flow of that adaptation through the enterprise’s ecosystem. For learning architecture it begins with understanding the importance of keeping the focus on distinctions between push and pull learning.

Read the rest of this entry »


Social Business Design: Insights from HP’s WaterCooler

July 15, 2009
snakes_handling

Social Media Snake Oil?

Does your organization approach using social media in its business as something to fear or as something to evangelize? Several recent observers note that incorporating social media into business involves changing the culture underlying communication patterns and decision-making in many large organizations.

Amber Naslund, for instance, tells us that adopting social media means changing the mindset on how to do business. In particular, she says using social media in business means “giving your customers a visible, valuable say in how you do things, and having the faith that doing that is just good business.” On the other hand, Caroline Dangson, of IDC contends enterprises aren’t yet sold on social media and that “there are executives still fearful of the transparency that comes with the social media spotlight.” Specifically, Caroline says that,

Corporate culture has everything to do with adoption of social media. I believe the number one factor preventing full adoption of social media is the lack of executive trust in employees. This culture is about control and creates a workplace of silos. This type of workplace is not set up to be social and the silos are barriers to worker productivity.

So, here social media sits, between fear and faith. Needless to say, the truth about social media’s implications for business design lies somewhere in the middle. The fact of the matter, as Todd Defren tells us, is that we need to begin seriously discussing “how Social Media Thinking will impact the greater whole of the company.”

As noted in an earlier post, keeping in mind the distinctions between formal, process-oriented organization and informal, practice-based organization is crucial in thinking through the collaborative challenges posed by social software for enterprises and designing for the experiences supported. We can learn a bit about the complexity of the challenges involved by considering a recent framework offered on social business design by the Dachis Corporation team and discussing the way it relates to a recent report on an experiment in enterprise social media at the Social Computing Lab of HP Laboratories.


Read the rest of this entry »


Social Business Design and Multichannel Team Collaboration

July 7, 2009

hub

David Armano recently asked the question, Is the Hub and Spoke Model Adaptable? Anyone who ever worked on a project team in a large organization, especially corporate enterprises, probably recognizes the hub and spoke team design depicted in the graphic above. In this post I take a closer look at the hub and spoke design’s purpose in hierarchical, bureaucratic, organizations–the kind associated with industrial society. Our next post discusses how David answered his question and what an adaptable hub and spoke model implies for social business design.

Project management, typically consisting of one or more team leads clustered in the hub, considers the failure of any spoke’s functional work practices to align with approved best practices as evidence of process ignorance, a failure of competence in following the detailed process requirements in the team’s project plan, not a failure of the organization’s adaptive capability. The hub and spoke model’s basic idea is that a matrix-organization, consisting of cross-functional project teams, optimizes the traditional hierarchical organization by adding increased flexibility in responding to market demands for innovation in products and services, and maintaining adherence to a standard management process. However, as Rob Cross and Robert Thomas observe in their recent book, Driving Results Through Social Networks,

…most projects and processes are enabled by productive networks that form among some (but not all) team members in combination with relationships that bridge to key resources and expertise outside of the team.

In other words, much of the collaborative effort going into innovation projects also involves social networks that aren’t part of project teams. Instead, these networks emerge from relationships with others in the enterprise, or from outside friends and associates. Perhaps this is one of the reasons that some research into geographically distributed teams shows that on average, only 75% of the employees on any given distributed team agree about who is, and who is not, on their team. The challenge increases in importance as project teams form and disband more rapidly to manage risk and opportunity, thereby increasing the already fuzzy distinctions of formal organization, i.e. official teams, and informal organization, i.e. social teams.

Ross Mayfield summarized the point well in the following observation:

Process is “how work should be done.” And Practice is “how work is actually done.” When process fails (exceptions), people use practice to fix things. When process doesn’t exist, practice fills the void. While people don’t realize it when they engage in practice, they actually are tapping into community — an informal social network within or beyond the enterprise to discover expertise and get things done. The problem is that we haven’t had the tools to support good practice. The problem is that we haven’t developed the group memory around practice that creates institutional leverage. In fact, we still design organizations to prevent practice and cultures that hoard knowledge and communities. 

I suggest that the real value of social business design comes from the promise it holds for enabling management practices to develop to deal with the following fact:  Social networks do not respect organizational walls, they never did.

Shared experience, not just shared information, is fundamental to the social networks underlying collaboration and innovation. Many, if not most, employees don’t only need to get to know one another through reputation systems, like who people tag as possessing expertise. As Thomas Vander Wal continues to point out, comfort with one another is needed to develop a shared experience that encourages the open sharing of information.  

Collaboration means getting to know that other employees possess expertise on this or that topic, but also developing comfort with one another by sharing significant symbols relating to self, family, friends, and social activities, thereby understanding one another as people. Shared experience with co-workers and customers is a key factor in innovative business practices. It is especially important to multichannel collaboration.

Read the rest of this entry »


Social Business, the Golden Rule, and Open Empathy Organization

May 20, 2009

empathyI first took real notice of the term “social business” in a post early this year over at Peter Kim‘s blog. The concept of social business is not limited to those enterprises seeking to “generate social improvements and serve a broader human development purpose,” though these are certainly admirable goals. Rather, social business is increasingly discussed as a frame of analysis for considering the business implications of  large numbers of people using web 2.0 technologies, especially social media, within corporate enterprises as employees, or outside them as customers.

Channels, policies, processes, touch points and transactions are increasingly viewed as parts of the social experience organizations use to engage employees in collaboration, and customers in conversation. The common goal of the discussion involves transforming business practices to incorporate social relationships into the value proposition to customers and other stakeholders.

My recent reading of Wired to Care by Dev Patnaik (with Peter Mortensen) provided some basic insights for me in thinking about the development of social business practices. I highly recommend it to anyone with an interest in the intersection of experience design and organization. The book explores the concept of empathy in a manner that speaks to the social business discussion by pointing out that the result of a transformation is more than adoption of new technologies such as social media.

Wired to Care offers an approach to organizing business as well as creating design insights on how to engage customers to improve products and services. One of my earliest posts on Skilful Minds, Break the Golden Rule with Customer Dialogue Support, offered the following observation,

Many “customer care” approaches call for treating customers the way you’d like to be treated—the so-called Golden Rule. Treating customers the way we, as service providers want to be treated implies that we inherently know what’s best for them. A customer dialogue approach alternatively assumes that customers know, or can quickly learn, what’s best for them as individual customers. We need to treat customers the way their actions indicate they want, not the way we would want to be treated as a customer.

Reading Wired to Care persuaded me that my previous point only moved the discussion a part of the way to an understanding of the nuances of the Golden Rule for business. Wired to Care offers an interesting point of view on the limitations inherent in the traditional understanding of the Golden Rule, while contending that a full appreciation of it reveals truths about us as individuals, and our relationship to organizations, whether as employees or customers. It outlines three levels of the Golden Rule:

  1. “Do unto others as you would have them do unto you” — the most basic level with limited efficacy unless people share the same view of the world
  2. “Do unto others as they would have done to them” — requires increased empathy to distinguish the wants and needs of individuals
  3. “Do unto each other as we would have done unto us” — provides for empathy by focusing on “how we’d all like to be treated, inside the company and out,” yet also recognizes that good business practice might additionally require treating people “better than they expect to be treated”

Dev contends that the third level of the Golden Rule provides a basis for integrating empathy into the everyday practices of organizations. Though he does not use the term social business, Dev’s analysis offers a foundational strategy for implementing social business through the concept of an Open Empathy Organization.

Read the rest of this entry »


Brand Experiences are for Employees and Customers

April 6, 2009

cem_puzzleThe topics discussed at Skilful Minds fall in a range of challenges involved in translating strategic business goals, and the complex needs of people, into exceptional experiences, for employees who provide products and services and those who consume them, whether the latter are customers, users, learners, or just plain people. Commentators and practitioners of experience design tend to focus on the latter while largely ignoring the former. A few recent posts by influentials speak directly to these concerns and merit specific attention for their insights into experience design and brands.

The underlying theme is that brands are not simply about the way customers view products and services. The way employees engage customers in the design, development, and delivery of those products and services is also crucial to brands. However, exhorting employees to live the brand and talk customer-centricity is a prescription for failure when isolated from transformational changes to a company’s engagement with customers.

Read the rest of this entry »


Onboarding, Social Capital, and Wikis

April 16, 2008

All organizations face a similar challenge when new employees come onboard. The new employee needs to learn the ins and outs of the organization. HR typically provides them an orientation packet and a point of contact for information. Their team, or department, management gives them an overview of their job and, if they are lucky, walks them around to introduce them to their co-workers and provides any virtual introductions, i.e. email announcements, needed to other members of the organization. However, providing new employees with access to the information needed to understand how to do their work is always a daunting challenge. Referring them to policies and procedures, whether manuals or online, remains the most common first step. Sometimes the new employee even receives on-the-job-training for a few days.

Making the first few days of a new employee’s orientation smoother and making the curve of their time to performance steeper are challenges requiring ongoing innovation in the management of human capital, but also social capital. Read the rest of this entry »