Category Archives: Collaboration

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.

“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.