Author Archives: Dave Arella

Work Management Software 2013 – toward a richer understanding of this emerging new category

A new business software category is emerging called “work management”.  We are eager to make 2013 the year where this new category really gains a foothold. We are concerned with closing the execution gap between goals, tasks, and results.  This article is intended to help develop a richer understanding of this new software category.  How we get more done is suddenly sexy and all kinds of functionality and vendors are eager to be included in the new buzz around “work management” software.  Unfortunately, this has tended to cloud the new field with a wide-ranging set of features and capabilities to the point where there is no succinct definition of what constitutes “work management” software.

The following is a primer on some of the distinctions across various work management software offerings.  Vendors will begin to stake out their differentiating features along the following dimensions:

—  Function-specific tools vs. general tools.  Some tools are designed to support managing the work of specific users.  For example, call centers or IT support desk users might use a support ticket system that integrates inquiries created via email, phone and web-based forms in order to manage, organize and archive support requests and responses.  Professional project managers could also be considered functional specialists who use project management software as a “work management” tool.  These function-specific tools are built around a specific set of features tailored to the activity of that function.

By contrast, generalized tools are designed for a broad user population. These “tools for the rest of us” (e.g. calendar apps) can be used to manage work in virtually any function or environment, small groups or large.

—  Individual vs. Group ware.  Some “work management” tools are designed primarily for single users; others for groups.  Most task management systems, for example, are fundamentally single user applications.  I make lists of “to do’s” for myself and then I work down the list.  Similarly, many project management tools are also designed primarily for input by an individual user.  Yes, tasks can be shared with others in the group, but interactivity between members is limited.

The term “group ware” was popularized in the 1990’s.  In contrast to “standalone” applications, “group ware” referred to messaging and workflow solutions designed to improve coordination across many users.  The new breed of “social” tools have many of the same attributes – sharing information with others to get work done.  See further comments on “social media” below.

—  Goal and Task management.  Managing work certainly involves setting goals and accomplishing tasks.  Goals are typically “bigger” and have no specific deadline, but, other than that, there is significant functional and practical overlap between managing goals and tasks.  Perhaps to oversimplify a bit, the distinction can be reduced to the size of the outcome (e.g. what’s the difference between a weekly goal and a task that’s due next week?).  Task management tools, of which there are dozens, can help manage an individual’s work, and they are generalized, but how are they to be included in the new “work management” category?  I can create Goals and Tasks for myself with or without conversation with others.  What is new is sharing (i.e. broadcasting) my Goals and Tasks with others in the group along with progress updates.  Tracking delivery commitments I have made to others and that others have made to me are essential for effective coordination of group work and resource allocation.  So goal and task management have shifted from being individual-ware to being group-ware; this is a significant shift in a familiar tool.

—  Collaboration vs. document sharing, videoconferencing, chat groups.  Unfortunately, the term “collaboration” is no longer a very helpful descriptor.  In the beginning, the term was hi-jacked into meaning shared documents (along with content management and searching).  A recent white paper by Info Tech Research Group, for example, gave high marks to one vendor’s “team collaboration portal” which boasted permission controls, voting by group members, and micro-blogging in addition to sharing content. Co-laboring clearly involves much more than managing shared content.

More recently the term collaboration has come to include an expanding range of features.  A recent Forrester study of “Collaboration Software Vendors” included eight companies with very different capabilities that ranged from file sharing and synch (e.g. Box) to video conferencing and instant messaging (e.g.Cisco/Webex, Citrix/GoToMeeting) to online chat groups (e.g. Salesforce Chatter and IBM’s SmartCloud Social Business Toolkit and Yammer).  Given this wide variety of features, the term “collaboration” no longer contributes much precision to the discourse.  I suggest we drop the term collaboration and use the actual features (document sharing, videoconferencing, chat groups, etc.) instead.

For a further discussion of the distinctions between document sharing and collaboration see my blog “Collaboration 2.0 – More Than Sharing Documents”.

—  Social media.  The word “social” has crept in everywhere.  We have: social media, social enterprise, social strategy, social collaboration tools, social work management, social workflow, social performance management, and social goals among others.  Let’s be clear that the term “social” has now been pretty much defined to mean a one-to-many communication pattern.  While it is possible to have one-on-one conversations, the “social” tools are designed primarily to enable an individual user to broadcast a question or a “posting” to the larger forum.  The term “social” has come to mean “shared with the group”.  The “group” can be a predefined group of limited members or a public, undefined group.  Familiar examples include Facebook, LinkedIn, Twitter, Chatter, Yammer. These are generalized tools without a functional focus.  Facebook and Salesforce.com have begun promoting the value of individuals posting entries and updates to help groups get work done.  See blog post about Facebook’s new group features (http://blog.chegg.com/2012/05/29/get-work-done-using-facebook/).

At the Salesforce.com “Dreamforce” convention last fall “social performance management” was the rage.  A number of sessions promoted “new ways to work”, “working together better”, “rebooting work”, “fixing work”, “new management practices”, “openness”, “transparency”.  As represented by Rypple/Work.com, “social performance management” emphasizes broadcasting individual goals, awarding badges in a public forum, and then cobbling together the badges and coaching notes for individuals into a performance review.  Interaction is primarily only one-way – one person awards a badge to another and your manager writes your review.  Social media adds value and can set the background context, for example, by aligning shared goals. Recognition and rewards add positive energy to the workplace.  Feedback, recognition, coaching, and rewards are motivating, but it remains to be seen whether changing how we write performance reviews, and how often we write them, will actually have any real effect on productivity.  Even Salesforce execs at the convention reported that “70% of all sales reps leave because of poor relationships with their boss”.  This problem cannot be fixed with purely social media tools.

—  Messaging/dialog.  In contrast to the new “social” tools, stand the old personal messaging tools, i.e. that support two-way dialog.  Email, IM and SMS are still the dominant ways two people communicate about getting work done (i.e. one-to-one communication pattern).  Emails can be shared with the group with cc’s to others, but the primary function is one-on-one conversation. This is the most personal, the most urgent, and still the most effective means for actually getting work done.  Just because these tools lack a modern marketing spin does not mean they are any less effective than they were 10 years ago.  The buzz around “work management” should not delude us into thinking that the new “social” tools come anywhere close to the power and effectiveness of such interactive media.  One can, of course, communicate one-to-one in Facebook, and emails can be shared more broadly using CC’s and blasts, but the dominant distinctions hold – Facebook is mostly a social media, email is primarily a personal messaging tool.  Read more about the distinctions between the one-to-many vs. one-to-one tools in my blog post “Bringing The Social Model to Human Capital Management“.

—  Metrics.  There is no question that measurement and feedback drive behaviors and, in turn, productivity.  Let’s be clear, however, that there are important distinctions regarding the metrics that can be obtained from social vs. interactive tools.  Tuning in to the social buzz around what has been called the ‘enterprise social water cooler’ can certainly provide a more real-time picture of employee concerns than a survey.  Employees can share comments and suggestions in an open forum that can result in improved operations.  Badges awarded to colleagues can be accumulated (even counted) at review time.  However, while creating a “social enterprise” can render new information and even insights, meaningful metrics require something more.  Social media has very limited data potential for actually informing/improving how work gets done.  Meaningful metrics rely on facts that are documented and comparable.  The system for collecting data must be structured and consistent across the entire enterprise.  These are not typically the qualities of a purely social, one-to-many network. The inherent diffusion of a large social group, coupled with its anonymity and randomness of participation severely limit meaningful metrics.  On the other hand, messaging media has the potential to be a rich source of data for tracking who is speaking to whom, how long it took to get what done, and when was it delivered.  A new era of work management and productivity metrics is emerging which will include such measures as an individual’s (or department’s) on-time delivery record, average amount to time to complete a certain standard task, or total resources expended in completing a goal to name a few.

Summary Discussion

So how does each category of tools mentioned above relate to actually improving how we “get work done”?  Which features and capabilities will actually improve execution?  In my view, the best “work management” tools will be a blend of the capabilities discussed above.  They will be generalized tools that capture and expose individual goals and tasks, that enable sharing of documents, that incorporate both social media and one-to-one dialog in real-time, and that provide a new class of productivity and performance metrics (See my blog “Nine Part System for Effective Business Execution“).

Beyond the features, the new tools will affect behaviors and practices and ultimately the culture of the organization.  New visibility into work activity will drive new approaches to accountability.  New ways of relating person-to-person will emerge that can increase trust.  The new tools will effect who speaks to whom, how they speak to each other, and even the words they use.  Organizational hierarchies will become less relevant as information sharing increases across departmental boundaries.  Personal networks with an ever-expanding number of respondents will need to be tempered with tools that clarify individual delivery commitments.  Network management will eclipse matrix management, and working in an egalitarian workplace will take on new meaning.  In the end, we expect new “work management” tools will dramatically improve productivity in the years ahead.

Electronic Office Born 25 Years Ago This Month – A Retrospective

The first use of desktop computers to process electronic forms occurred at Apple Computer 25 years ago this month.  It was an enterprise-wide, HR application that enabled every manager in the company to fill out and approve salary changes, department transfers, and performance reviews for 5,000 employees.  800 managers signed-on to access personalised data from a mainframe computer, routed forms through an approval chain, and automatically updated the host database.  This was the beginning of what soon became called “manager-self-service”.  The system was called “HyperGOLD”.  The year before, Apple launched the first “employee self-service” solution which enabled all employees to access and update their benefit elections using a personal computer.

These applications broke new ground in two areas – one technical and one behavioural.  The technical breakthrough had to do with managing user permissions and routing rules.  The system needed to accommodate “personalised” access and permissions by hundreds of users at different departments and levels of the company.  Line managers initiated various actions that had to be approved by others along the line before updating the database.  The other breakthrough had to do with the vast increase in the number of users.  Previously, computer systems, even those accessed from personal computers, required extensive training for use by a limited number of specialists.  It was untenable to consider training hundreds of new users.  The Apple systems were the first-ever to require no training!

The result was truly transformational.  Over the next three years Apple totally revamped how HR services were conceived and delivered, and the ratio of HR staff to line staff went from 1/30 to 1/300.  Getting stuff done was not only more efficient, but new policies, better practices, and improved behaviours were initiated that enhanced the Apple culture.

It was no coincidence this breakthrough occurred at Apple.  There were three enabling factors.  First, Apple was the only company in the world at that time that had a personal computer on every employee’s desk.  This accessibility meant that paper forms (and the associated double-data entry by administrative staff) could, indeed, be completely eliminated.  Second, Apple had pioneered the graphic user interface (especially valuable was HyperCard) that would support the “no-user-training-required” standard.  Third, then as now, Apple had an appetite for innovation.  These applications were not available in the market place, and Apple had to build them from scratch.  These pioneering applications took investments of millions of dollars over several years.

The team was co-led by David Arella (this author), who was Apple’s first Manager of the HR Systems Technology & Innovation Group, and Steve Austin, Information Systems & Technology Manager.  Their team included Lynne Hoppe, Dawn Black, Suzanne Summers, Aaron Hyde, Tim Hayes, Ted Ives, Ann Altman, Bill Lee, Paul Foraker, Wayne Robertson, and David Donaldson.

It turned out that Apple was way ahead of the crowd.  Many years passed before other companies implemented similar solutions.  Quantum and Adobe did their first employee benefit enrollment systems in 1992 and 1993 respectively.  Cisco did their first manager-self-service HR application in 1995, a full 7 years after Apple.  Dell Computer’s first enterprise-wide solution for line managers was not implemented until 1997 on their brand new intranet.  Other leading companies like Schering-Plough, Southwestern Bell, Colgate Palmolive, Marriott, AMD, MasterCard, Reuters, NY Times, and CNA Insurance came along in the late 1990’s.

Of course, these solutions are commonplace today, and we take all of this pioneering work for granted.  Companies that don’t have similar solutions in place are now in the minority.  New social media technologies have opened up possibilities for new advances.  So here’s an alert:  stay tuned because some of the same people who contributed this seminal work 25 years ago have been busy working on the next breakthrough solutions.

4Spires Welcomes New Customer – Fleet One

4Spires is happy to kick off the New Year by welcoming our newest customer – Fleet One.

Fleet One® provides fuel cards and fleet-related payment solutions to businesses and government agencies with vehicles. The firm offers fuel and maintenance purchasing controls, detailed reporting, online account management, and other cost-saving services.  Our CommitKeeper solution was acquired for use by Fleet One’s marketing department.

Business Situation

As with most marketing departments, Fleet One needed to handle many projects simultaneously, and each one demanded close coordination of many participants (e.g. art, copy, procurement, production, etc.) against tight deadlines.  Multiple people and groups are often involved in each project.  It was not uncommon for the department to be working on 150 tasks, but only 50 projects.  In addition, Fleet One’s Vice President, Marketing, Stacey Bright, identified two specific challenges; they needed a solution that could easily link main projects to supporting tasks and one which provided an easy-to-read, understand, and manage project summary that showed the status of any individual task at any time.  Prior to CommitKeeper, Fleet One had used Microsoft Outlook’s task system, but this product does not permit supporting tasks, making it hard to effectively manage and review the status of each project, every deliverable, and each employee’s status.  Without a proper work management solution, managing all 150 tasks in Outlook was untenable.   Stacey had been looking for a solution for a long time.  Work and project management solutions were too cumbersome and task tools were not robust enough.

Solution

Once the marketing group began using Salesforce, Stacey was delighted to find 4Spires‘ Salesforce version of our CommitKeeper product on the AppExchange.  Marketing now has the ability to assign secondary tasks within a commitment.  They have completed 200 plus commitments in less than three months across 59 active projects.  Stacey can tell at a glance where each project stands – negotiation, in progress, delivered, accepted, canceled or declined –  along with a complete audit trail.  The department now has the ability to understand where its time and efforts are being utilized.  The group-individual making the request is identified and the associated budgeted hours are captured.

By using CommitKeeper’s Observer feature, the Marketing VP is able to provide executive management with a simple summary dashboard to review and update every project.  Requests for new projects from other departments are entered in CommitKeeper so the marketing department can negotiate clear delivery agreements.  The Marketing VP is now managing down, up, and across the organisation with one integrated tool.  CommitKeeper has improved oversight, coordination, and business processes within Stacey’s team and across the company.

Stacey summed it up this way: “CommitKeeper is a fantastic solution.  It is very easy to use which equates to getting people to accept the solution; the team has already ‘committed’ to the program 100%.  The 4Spires team is top notch and really made the decision to use the solution an easy proposition.  They have been extremely supportive from day 1 and continue to work with my team. This is a great company and Fleet One looks forward to their long-term success.”

Thanks, Stacey, welcome to the group.

 

4Spires Brands New Image

 

4Spires (www.4spires.com), the leader in business execution SaaS solutions, has developed a new and exciting image that embodies and brands the spirit of our company, business philosophy, and products.

The essence revolves around the firm’s belief that all actions, all executions, all commerce is achieved in some fashion through a ‘conversation’ between a requester-customer and a performer-provider.  At an elemental-core level, all organizations can be seen as simply an interrelated, fluid network of person-to-person conversations and interactions.

To be most effective as well as for the organization and individuals to receive the greatest benefit, each of these interactions needs to involve a simple four-stage pattern.

  • The cycle begins with a solid foundation (Blue).  One person begins the conversation with a clear description of their needs and expectations; they make a request.  They INSPIRE the conversation.
  • In the second stage, the other person (i.e. the performer-provider) responds with their abilities  and constraints and the two parties make an explicit agreement to deliver (Green).  They CONSPIRE.
  • In the third stage, the performer does the work and delivers what has been promised (Silver).  Figuratively, the performer PERSPIRES.
  • The fourth stage is completed when the requester receives and assesses the deliverable; they ‘crown’ the whole interaction with a close-out comment of satisfaction and appreciation (Gold).  Both parties ASPIRE to have satisfied the original needs.

The pattern is repeated over and over, request – agree – deliver – assess.

Completion of one task-related cycle spawns the next.  Requests become more precise.  Accountability within the organization, for the individual and resultant deliverable is clear.  Results are acknowledged with increased organizational and team cohesiveness.  Feedback is provided on each delivery which fosters heightened business process efficiencies and personal recognition.

This is a virtuous cycle for improving performance in any organization.  It improves execution; it also boosts trust and builds better relationships between individuals, within departments, across the organization and even with customers.

This logo will be associated with our line of “CommitKeeper” products, each one of which is designed to facilitate the creation and support for this beneficial four-stage cycle.  We think the application of this simple idea can dramatically improve personal and organization performance.

4Spires Welcomes New Customer – National Golf Outing

 4Spires is pleased to welcome National Golf Outing as our newest customer to CommitKeeper on Salesforce.  Headquartered in Coldwater, Michigan, National Golf Outing (NGO) sets up and runs golf tournaments throughout the Michigan and Indiana area, with plans to go nationwide.  Each golf tournament is sponsored by a different public or private organization.  NGO was developed by the same team that created, owned and operated the world’s largest grass roots golf tournament, The Oldsmobile Scramble, which for almost 20 years averaged over 2,000 events with100,000 participants.

Each golfing event that NGO runs requires the smooth operation of hundreds of tasks.  Managing and coordinating all of these overlapping activities is the key challenge faced by the company.  NGO evaluated several task and project management solutions, and in the end they chose 4 Spires’ CommitKeeper on the Salesforce platform.

NGO’s Senior Partner, Dick Garn, has been managing people for over 30 years.  Over time he has noticed a simple way to describe why breakdowns occur in execution.  As he says “Employees oftentimes live in the fog – being not quite clear on what they are being held accountable.  On the other hand, managers like to have selective memory – forgetting the risks their team alerted them to and the changes in priority they directed along the way.”  One of the features Dick especially likes is CommitKeeper’s audit trail that captures the dialog thread from agreement-through-delivery for each task.

CommitKeeper enables the entire NGO team to coordinate their overlapping and interdependent tasks in one integrated tool.  Responsibility and ownership for each task is clear, accountability is visible.  Dashboards enable everyone to see the status of each other’s deliveries across all the upcoming events.  It is a powerful system that is quick-to-learn and easy-to-use.

Working with NGO has provided the 4Spires team with great feedback.  Thanks to the flexibility of the Salesforce SaaS platform, important new features and product enhancements recommended by NGO are already available in the enhanced Salesforce version of CommitKeeper.

We thank NGO for their trust in us and look forward to building a strong relationship going forward.


4Spires launches CommitKeeper on Salesforce

4Spires is pleased to announce the launch of the newest version of our CommitKeeper product on the Salesforce platform.  This application offers a ground-breaking approach for improving coordination, visibility, engagement, and accountability across all types of team initiatives.  It closes the execution gap between strategy, tasks and results, and it takes collaboration to the next level.

Notable features in this version include the following:

    • New Request.  A simple form is used to make a request for a specific delivery from a performer/provider.  The request can be tagged in multiple contexts for later search and reporting.  This begins a dialog thread that documents the whole delivery cycle.  Socialize the task with the broader community by selecting multiple observers.
    • New Offer.  In addition to using the request form, a commitment to deliver an outcome/result/task by a certain date can also be initiated by the performer/provider making an Offer to a customer/manager/colleague.
    • New To Do.  Create a task for yourself within the same tags so that you have a truly comprehensive list of all the work items on your plate.
    • Supporting Requests.  Execution often involves a hierarchy of dependent tasks.  Delivering on a “parent” request depends on the successful completion of several “supporting requests” which may, in turn, depend on other “supporting requests”.  Visualize up-to-the minute status on the entire network of dependencies.
    • Suppress emails.  To minimize and control email “clutter”, system administrators can suppress email notices without affecting the Chatter stream.
    • Attach files.  Attach files to requests/tasks that seamlessly integrate with the Salesforce document library and version control features.
    • Integrates with CRM objects.  Requests and responses made in CommitKeeper automatically appear in the activity history of the related Salesforce objects (e.g. leads, opportunities, projects, campaigns, etc.).
    • Native and Aloha too.  Built with code native to the Salesforce.com platform, the application fits right in to the user experience with no training required and feels like a “standard” platform utility.  Aloha status means the application does not count against limits imposed by which edition of Salesforce (i.e. Group, Professional, Enterprise, Unlimited) the customer is running.
  • Easy installation.  Just a few clicks and it’s done.

Find it on the AppExchange here.  Sign up for the free 30-day trial.  Please forward to your colleagues who may have interest.

Thanks for your ongoing interest and support.  More soon.

Bringing the Social Model to Human Capital Management

John Wookey, Executive Vice President, Social Applications at Salesforce.com , published “Why Human Capital Management Really Needs a Social Model” on TLNT (www.tlnt.com) in the May 2, 2012 issue.

http://www.tlnt.com/2012/05/02/why-human-capital-management-really-needs-a-social-model/

Without diminishing what John has written, I want to elaborate upon and recommend counterpoints and further enhancements to the general themes he espouses.  I will elaborate on five quotes from the article:

1.     “People-centric systems should promote connection, communication, and collaboration.  That is the core of the social enterprise”. 

At face value, this statement is true.  There are, however, various ‘flavors’ of connection, communication, and collaboration that offer and support alternate objectives.

As commonly practiced, the social enterprise advocates promote a one-to-many communication paradigm in which each individual broadcasts information out to everyone in the group.  Examples include:

  • Project team members share their personal goals with the whole team.
  • Individuals send out queries company-wide seeking help.
  • Shared document edits are seen by everyone.
  • Coworkers award badges to each other in an open feedback forum.

The benefits can be readily appreciated, but there are also limitations to these practices:

  • Participation can be spotty; some people participate a lot (sometimes too much), others not at all.
  • Kudos are happily awarded, while critiques are rarely entered.
  • Broadcasting needs and gathering input from a larger and larger social group has value, but social networks do a poor job coordinating work and actually taking action.
  • Groups tend to diffuse responsibility; information sharing is very different from accountability.
  • Too much sharing can challenge a healthy respect for privacy and appropriate confidentiality.

Lastly, due to its more random nature, a one-to-many forum produces little hard data from which to develop meaningful performance metrics.

Moving forward the most effective social enterprises will blend the one-to-many social paradigm with its newer counter-part, the one-to-one paradigm: two specific people having a focused interaction.  It is still about connection, communication, and collaboration, but at a granular level taking action involves a performer delivering some outcome to someone else who can assess the completeness and express specific satisfaction.

This dialog can be either private (visible only to the two parties) or open (visible to a broader group of interested parties).  The key principle is the authenticity and personal integrity of the two parties.  This emphasis is less freewheeling than the one-to-many paradigm, but this more disciplined communication drives greater intimacy and personal accountability by making commitments explicit and tracking each deliverable.  Accountability and engagement are made palpable, and tracking deliveries against commitments yields a wealth of actionable metrics.

2.     “Lack of meaningful information is the hallmark and curse of every legacy HR system.”

This comment is perhaps a bit overstated; though the point has merit.  I would urge, however, that while creating a social enterprise will render new information, the data’s meaningfulness has limits.  Tuning in to the social buzz around what has been called the ‘enterprise social water cooler’ can certainly provide a more real-time picture of employee concerns than a survey.  Employees can share comments and suggestions that may result in improved operations.  Badges awarded to colleagues can be accumulated at review time.

I submit, however, the inherent diffusion of a large social group, coupled with its anonymity and randomness of participation severely limits real meaningful metrics.

3.     “Making the [performance management] process collaborative – and allowing people to commit – creates and fosters a real dialogue across an organization.” 

I have spent years studying, and understanding the process and practices associated with making commitments.  Commitments are, indeed, what really drive actions.   But just making performance management ‘collaborative’ does not get stuff done.  Commitments can and, to be most effective, should be publicly shared, but the actual formation of a commitment is a person-to-person endeavor.  Some enterprises are certainly moving away from command-and-control practices and toward more bottom-up participation and engagement.  On the other hand, the actual process of making and tracking commitments, plus the feedback and metrics associated with delivering on those commitments, requires more discipline and rigor than is typically offered in purely social one-to-many dialogues.

4.     “Feedback should be open and collaborative…which results in transparency, trust, and alignment”. 

This observation is certainly overstated.  Sure, some feedback can be more open and it is fine to get kudos from colleagues in other departments, but other client-customer or manager-employee/performer feedback (one could even argue the most important feedback) should certainly not be done in an open forum.  And it is oversimplified to make the leap that open and collaborative communication automatically yields more transparency and trust.

5.     “A social HCM system still supports the creation of formal reviews and metrics-based assessments.” 

Yes, sharing goals with the group and accumulating badges and feedback from colleagues across the enterprise is a step beyond the old 360review process, but providing metrics-based assessment, not so much.

Meaningful metrics rely on facts that are documented and comparable.  The system for collecting data must be structured and consistent across the entire enterprise.  These are not typically the qualities of a purely social, one-to-many network.  The evolving complementary one-to-one social systems will add an important adjunct that can provide meaningful metrics.

 

The social enterprise is coming and with it comes a wealth of new opportunities. But, let’s include in our enthusiasm an appropriate understanding of the deeper practices and behaviors we all seek to transform, as well as the new communication structures that will actually support performance improvement.

Four Principles for a New Model of Accountability

Accountability, everyone wants more of it, from our political leaders and institutions, businesses, schools, work colleagues, and even our children. Our general understanding of the word, however, and how to acquire more is imprecise and shallow. This is particularly disappointing in the work place context because increasing accountability can indeed improve performance. This post explores the term and proposes a new perspective, based on four principles that can increase accountability.

Let’s begin with definitions and the current perspective. The Merriam-Webster dictionary defines accountability as “an obligation or willingness to accept responsibility or to account for one’s actions.” The Random House dictionary offers a different perspective defining accountability as “the state of being answerable: obliged to report, explain, or justify something.” It is noteworthy that in its common usage, both definitions emphasize a backward-looking perspective; i.e. holding someone accountable for something he or she did. Often there is also a punitive overtone. It comes down to tracking deliveries and due dates with the question:  “Did you do it, and if so, what are you going to do about it?” Going further, the term is associated with the notion of “accounting” as in checking the score and determining who’s going to pay.

These commonly held notions are actually counter-productive to building more accountability in the workplace. The underlying enforcement and punitive notions about accountability do not create the optimum mood with a prospective collaborator. We need to develop a new perspective about accountability based on four principles:

1)     Accountability is forward-looking.  Accountability should be agreed upfront and not assigned at the end. As a task or initiative is being planned, the parties involved should be talking about who is going to be accountable for each outcome or deliverable. The performer consciously and explicitly commits and accepts responsibility. 

The critical portion of the conversation is at the beginning where the commitment is formed.

2)     Accountability is based on willingness.  There is a critical distinction between being willing to accept responsibility and being obliged to perform a function or produce a deliverable. In an organization characterized by a command-and-control culture, the performer is “obliged” to accept responsibility for delivering an outcome. Accountability is foisted on the performer simply by virtue of their position relative to the requester (e.g. the boss gives the orders).  In effect, the senior person ends up saying “I’m holding you accountable…” This is not the optimum means to boost accountability. Real accountability comes from “the performer’s mouth”.

A performer willing to accept responsibility explicitly declares their commitment and says in effect “You can count on me.”

3)     Accountability is about the quality of the dialog.  Building on the dictionary definition: “the state of being answerable”, what is important is the “answer” from the performer. Instead of the more usual presumption of accountability, the dialog begins with an explicit request that needs to be met with an explicit response. A conversation ensues and a specific agreement about expected results and due date is crafted. Having responded directly to the request and committed to the outcome, the performer has, in fact, taken on the accountability for delivery.

The quality of the dialog between the parties is much more important than recording the assigned due date.

4)     Accountability involves negotiation.  The requester must acknowledge their dependency on the performer by providing an opportunity for an honest response. The performer answers by sharing their capabilities and concerns regarding the request. Commitments that evidence real accountability involve a level of disclosure and dialog that is typically not present when tasks are assigned. Most managers assign tasks and expect accountability to follow along as part and parcel of the assignment. In effect, they are saying “I am assigning you this task and holding you accountable for getting it done on time”. This is not a dialog, only a one-way statement. The performer has not actually “answered”. The performer has not made any personal or public ownership of the task. While we are all familiar with position-power simply “assigning” accountability, a superior approach is to afford the performer a genuine opportunity to negotiate a response to the request.

Negotiation strengthens commitment. 

 

Focusing on accountability can be an effective lever for improving organization performance.  Accountability drives execution. To be most effective, however, we need to replace the current enforcement and punitive notions about the word with a new perspective that keys on upfront dialog and making clear agreements.

“Collaboration 2.0” – More Than Sharing Documents

Recently, I read “Collaboration 2.0: Technology and Best Practices for Successful Collaboration in a Web 2.0 World” by co-authors David Coleman and Stewart Levine.

First and foremost I appreciate that the authors have expanded our view of  what co-laboring is all about.  The commonly held understanding of the word “collaboration” has for too long been hijacked to simply connote document sharing.  For example, a software product review written as recently as October 2011 contained the following line:

“The two most important aspects of cloud computing for small businesses are mobility (reading and editing documents on mobile devices) and collaboration (sharing and co-editing documents).” [My emphasis added]

Collaboration is so much more.  As the authors vividly point out, effective collaboration requires attention to people, process and technology.  They advise their readers “collaboration solutions that only focus on technology will fail if they do not also address the ‘soft stuff’ – relationships, trust, behavior and attitudes.”  Additionally, they suggest “what has been missing and what is a key ingredient for successful 2.0 collaboration are some. . .protocols around the basics of interpersonal communication”.  How to communicate in a virtual environment has the same, and even more, challenges as communications in the physical world.  Technology designs need to be mindful of “creating a context in which people communicate more effectively”.  Coleman and Levine rightly assert the number one communication roadblock is “Lack of Clear Agreements”.

The book’s latter section presents an insightful discourse on what the authors refer to as “Law and Principles of Agreement”, i.e. “Every collaboration is established in language by making implicit and explicit agreements. . . Collaboration and agreement for results is simple, but it is not easy.  It requires thoughtfulness and clear thinking on the front end before you move into action, and then a commitment to get through the rough spots after you begin.”

I could not agree more.  New software solutions are being developed and introduced that go well beyond document sharing to address the “soft stuff”.

To facilitate effective collaboration, technology can:

  • Create a context – a “space” in the virtual world where two or more parties can come together to carry on a dialog about achieving a shared outcome.  Different from email, new technologies enable each party to independently work in the shared space without waiting for the other to respond.
  • Guide behaviors – users make requests and offers to begin a dialog/conversation between collaborators.  Effective and efficient collaboration is spawned and carried through in a well-crafted conversation in which the two participants interact with each other, declaring specific things, in a structured sequence.  The requestor initiates the dialog/conversation by making a clear request of the output or result that would satisfy their concerns, the performer responds by making an explicit agreement to produce a specific outcome at an agreed upon delivery date, the performer presents their output, and the requestor explicitly acknowledges whether they are satisfied thus closing the structured sequence loop.
  • Make agreements explicit – who will do what by when is “on record”.  Document a clear request and the agreement by the performer to deliver by a certain date.  To emulate actual conversations, the software controls require an appropriate response from the performer (e.g., the performer must select one button option: “Agree”, “Decline”, or “Counter-offer”).
  • Provide protocols to guide the conversation flow – the conversation thread is “managed” by the software to include mutually beneficial actions and comments that progress the conversation and close the loop.  These “rules of engagement” must strike a delicate balance and not be overly restrictive; the technology must have sufficient flexibility to support human interactions in ways “natural” business conversations are handled in the physical world, but may include prompts to move the conversation along, to reach mutual resolution, and to complete the delivery.  Both parties in the conversation move forward along an explicit path.
  • Keep and maintain records – track project status, changes, modifications, updates, deliveries and outcome assessment.  Records archive all data and dialog threads associated with completed collaboration agreements for future analysis and learning.
  • Reveal execution in progress – graphically display the real-time status of the whole network of interdependent collaboration conversations associated with specific goals, projects, accounts, etc.
  • Provide metrics – measurement adds management insight and supports interventions to improve collaboration.  Technology can, at a glance, highlight initiatives: still being negotiated, ones on track, those that have been delivered, which are late, etc.  These can be presented on an organization-wide basis as well as on a person-by-person basis.  On time delivery percentages and satisfaction ratings can be quantified to build reputations.
  • Build trust – technology plays the role of a third party to the conversation, monitoring and helping facilitate the development of a successful relationship.  The software is intended to introduce and support best practices and more efficient behaviors while enhancing ways of working.  Beyond capturing data and managing workflow, the software represents a significant organization development intervention that leads to improved performance and results.

Collaboration technology is so much more than document sharing.

One Simple Behavior to Elevate Employee Engagement

There is a growing recognition of the close relationship between an organization’s performance and its employee engagement.  Many observers share a concern that employee engagement is in decline; which is directly affecting how an organization internally and externally meets its obligations.  There is particular concern regarding Millennials.  (For an overview of this age group read The Millennials.)

This article describes one specific management behavior that can elevate engagement.

In a recent article Arthur Lerner, Principal at Arthur Lerner Associates, has done a nice job of describing a hierarchy of the levels of engagement.  He writes:

“This isn’t precisely what Senge et al wrote in The Fifth Discipline, but close and slightly expanded. (The original had four types of compliance – grudging, formal, ‘regular’, and genuine, and require comment to differentiate.  I’ve substituted the words below, which includes adding in coercion as the lowest level, probably needing a line above it because it connotes no willingness.)

It was written well before the current passion for engagement, and has served well in my experience to differentiate some of what others have pointed to in this discussion already.  It presumes leader-follower/hierarchical relationship. Read the following from bottom up:

Enrolled
Committed
__________
Volunteering
Supportive
Cooperative
Compliant
Obedient
Coerced

From the bottom, each higher stage indicates a greater degree in the willingness to subordinate to do what a leader (organization) wants, in particular via greater ‘buy-in’ to the vision and perhaps the goals that underlay what is asked. . .  As it stands, with no explanation, it does not include ways to attain the stages in terms of intrinsic or extrinsic rewards, etc.  The line between volunteering and being committed indicates an internal shift from doing – even enthusiastically – what the ‘other wants’ to taking on internal ownership for the behavior or result desired.  Enrolled connotes going beyond commitment in that someone who is enrolled so fully cares about and wants to see the success that s/he will carry forth even in the absence of a prior leader of the effort.  One could collapse some of the stages as shown, but the drift is definite, and the line is a distinctive qualitative divider.  I won’t go into connections between the stages and progression between them and issues of motivation, enthusiasm, engagement etc. but they are many.”

I like this hierarchy; we can all recognize the levels.  But how do we make changes that move engagement up the hierarchy?  What are the work practices and manager behaviors that can move the needle?

One dimension that is both practical and observable is the character of the dialog that’s going on between the parties.  For the bottom five levels (Coerced through Supportive) the conversation is top-down.  In fact, there is no real dialog at all.  The manager-leader simply tells the team members what they must do.  This ranges from a direct order, with consequences, to a stated need.  The ‘demand’ or assignment changes in style (i.e. harsh direct order to kindly assignment) but not in character.  “I need this done by you by this date”.  It’s a statement.

At the Volunteering level there is a fundamentally different type of conversation.  At this level and for the first time, an actual two-way person-to-person or manager-to-employee dialog occurs.  The difference is the manager asks a question rather than making a statement (e.g. “I need this done, which one of you can get it done?”)  The performer, aware of the need, responds with an explicit agreement to fill the need.  Even though the dialog is still a bit ‘tilted’ in favor of what the manager wants, there is at least an opening for a response to express willingness by the performer.

Something very different happens when moving up to the Committed level.  To get to this level, there must be a genuine dialog between two individuals, more or less on equal footing, where the performer is making an explicit agreement to deliver.  The key change is that this conversation starts with a request (e.g. “Can you complete this project or task by Friday?”) versus beginning with a statement.

What follows is equally important.  The performer has the ability to respond by saying yes, no or by proposing an alternate completion date.  They are able to negotiate what they are able to successfully complete by a specific deadline or make a counter-offer to the request.  Most importantly, with the real opportunity to negotiate, they make a commitment (e.g. “I will get this done for you by next Monday.”).  This statement expressing “ownership” by the performer is the hallmark of the jump to the Committed level in the hierarchy of engagement.

The top level in the hierarchy is Enrolled.  At this stage, the engagement is spontaneous, even anticipatory.  As with the other levels, this one is also characterized by a certain type of dialog.  This level is characterized not by requests from the manager, but by offers from the performers; e.g. “I understand what needs to be done, have the time, resources, and enthusiasm to get it done, and therefore I am making an offer to do it.”).  Again, the performer is engaged in a negotiation with the manager-customer that results in a clear commitment for delivery.

While I readily grant the substantial over-simplification of a complex issue, managers who want to increase engagement can begin by changing one thing – the character of the dialog with the performer(s).  Changing statements to requests is a good first start.  This simple step releases the power of the performer to respond at a higher level of engagement.