Archive for the ‘Uncategorized’ Category

Joe Ruck

Team, Task and Time – Capturing Fluidity in Leadership Communication

Monday, August 1st, 2011

Adapting leadership team communication for the digital age brings with it both challenges and opportunities. One such challenge is confidentiality. Although it is generally understood that communication between members of a leadership team requires confidentiality, it’s not always clear what that entails. It is not that every subject is top-secret, but there are plenty of sensitive topics, and even the most mundane subjects can be misinterpreted or taken out of context, sometimes deliberately. So an effective leadership team communication platform must serve as a secure environment, not just to protect against external breaches but to allow leadership to concentrate on the substance of their discussions, rather than to agonize over the precise meaning of a word or phrase.

The added challenge to capturing those communications is that their trajectory doesn’t follow a rigid, or even predictable, path. They are often evolving, adding participants or reshaping themselves around a changing objective or environment. This fluidity dictates a platform with the flexibility to accommodate those changes. At BoardVantage we use a model internally referred to as “Team, Task and Time” to assure that our NextGen platform maps to evolving requirements.

Teams are eclectic.

Leadership communication is not necessarily confined within hierarchical or structural boundaries. While members of leadership form the core of the team, outside auditors or advisors may participate to fulfill a process requirement. In other instances, individual contributors are added to provide a particular expertise. It’s this eclectic team composition that precludes uniform access and dictates a layered set of access privileges where permissions are granted in accordance with organizational position or other criteria.

Tasks vary broadly.

The fluidity of communication is also driven by the variations in the underlying process. NextGen supports three distinct but related process sets: Staging vs. Screening, Co-authoring vs. Presenting, Broadcasting vs. Interacting

Staging vs. Screening – Although related, these processes are sufficiently different to impact functionality. Screening implies a permanent exclusion of a group of users, whereas staging implies a communication process where a group is initially excluded but subsequently included, typically after certain milestones have been met. It is essential that the platform can swiftly reset from a state of exclusiveness to inclusiveness.

Co-authoring vs. Presenting – Collaboration can mean little more than sharing final work product with a peer group. In this simple case, the platform needs to support a simple dynamic of granting the authorized users access, but without the right to change the underlying content. At other times, collaboration means a form of co-authoring where two or more professionals create or edit content. This of course implies more stringent access control. Another use case would be document mark-up done through annotation or highlighting where the underlying document is not altered. Regardless, the permission model must be sophisticated enough to understand how to correlate changes, notes and highlights with the associated user.

Broadcasting vs. Interacting – In the not-so-distant past, communication to a large group often took the form of a one-way update with no feedback desired or expected. In today’s business world, some form of interactivity is generally encouraged. The platform needs to support both cases and include the granular control to constrain communication streams where necessary.

Structure evolves over Time.

Process-driven environments tend to be stable over an extended period of time. Most board communication falls into this category. Board meeting schedules are defined well in advance, sometimes years, and most board members will stay on a board for several years at a time. But this level of stability is not necessarily present at the leadership team level. Team members may be added or removed more frequently, and movement is often correlated with milestone achievement or member expertise. M&A environments are created around a particular deal and only for a limited period of time. Temporary work spaces may be formed for external auditors and finance to collaborate around an audit. These changes in team composition are frequently the case in events-driven environments. An effective leadership team communication platform needs to support both common use cases.

It was this high degree of confidentiality and fluidity that led BoardVantage to build two essential elements into our NextGen platform architecture:

Granular Controls – A platform for leadership team communication requires access and process controls that are granular enough to capture a broad and evolving set of use cases.

Self-Sufficiency – Leadership team environments change at a lightening clip. Any delays in capturing changes will make the environment irrelevant and will alienate users. This means a premium should be placed on self-sufficiency – the ability to manage all aspects of the platform. Whether creating the team experience (e.g. TeamSpace formation), administering users (e.g. provisioning), managing content (e.g. remote purge) or delivering service (e.g. password reset), third-party reliance should be avoided.

The NextGen platform delivers a broad set of user-friendly administrative controls, and by allowing the permission model to exercise control over all communication streams, effectively places security in the service of collaboration.

Joe Ruck

The User Experience Barbell

Monday, July 25th, 2011

Software vendors often talk of a “typical user”. The premise is that once you tune your design to meet that user’s needs you enter a promised land where a small amount of development produces outsized results. That is a seductive notion. What developer would not sign up for that?

Unfortunately, it does not square with reality. We learned that lesson early in the board portal market – where the ideal experience for a director, and that of a member of the CS Office, are virtually opposites. Yet both experiences should be tailored to expectations or the system will be frustrating to one or both of these key constituencies. This split model is also evident in leadership team communication where an executive and an administrator will also expect different experiences. Beyond a minimal amount of training – say 20 minutes – a typical executive is simply not open to spending time learning new tools.

That is why BoardVantage has abandoned the pursuit of that mythical typical user.

Rather than designing to a single user experience cluster based on a common use pattern, we develop our software to cover a spectrum of user experiences with the end points representing radically different requirements.  On one end of that spectrum lies “the consumer”, on the other end “the contributor”.


The Consumer

The consumer category includes members of the leadership team, typically executives and directors. They access the system on a periodic basis, but when they do, it is critical that they locate what they need promptly. Understandably, they value simplicity over all else. It’s for that reason the iPad has been an important new influence for this group. But whether they prefer a browser or the iPad doesn’t matter. The design principles to meet their needs transcend the device. They can be summarized as follows:

•       Configurability – Highlighting essential functionality while stripping out what’s redundant

•       Presentation – Enrichment through graphics, branding and, in the case of the iPad, animation

Observing these principles allows us to provide a compelling experience while leveraging the unique strengths of the underlying device.  But addressing only this user experience cluster is inadequate. That’s because the needs of the second constituency are diametrically opposite to the first.

The Contributor

In contrast to consumers, contributors “live in” the system. They rely on process functionality for hours at a time, often in high-pressure situations. While consumers are adverse to tools, contributors embrace their tools, particularly the Office suite. For them, high personal productivity in the system is a non-negotiable requirement. What they seek is:

•       Continuity – User experience paradigms that are modeled after the familiar desktop environment such as drag-and-drop, right-click, a folder tree structure etc. In effect what they require is an extension of their current environment.

•       Integration -  Tight coupling with existing desktop tools such as edit-in-native, calendar syncing, email alerts and  others

It is important to note that these experiences are diametric opposites, a barbell distribution. That is also the reason they present such a challenge. Nevertheless, both implementations need to be executed flawlessly if the product is to be accepted by the customer base. This involves a large investment in design. Today that means not just the browser, but also tablets – notably the iPad – and Android devices as they mature.

Meeting Rising Expectations

Simultaneously, driven by the superior esthetics and usability of consumer devices, customer expectations about user experience are rising. Business users routinely encounter first-rate UI design in their consumer apps only to be disappointed when they return to the office to use business apps. It’s no stretch to forecast that this discrepancy cannot last. Whether it’s a branded experience, desktop environment or the iPad, the bar is being raised. And this has ramifications for business software vendors.

Given the compounding effect caused by divergent user requirements, a multiplying number of platforms and rising customer expectations, successful designs must go well beyond touching up the look-and-feel to deliver a good user experience.

Sensitized by the user experience demands in the board portal space, we believe that staying ahead of these trends requires a modern architecture. This was a key factor in our decision to develop NextGen as an RIA (Rich Internet Architecture). Only modern frameworks are rich enough to accommodate the evolving needs of today’s customers. For BoardVantage, this meant a seven-figure engineering investment, but the pay-off is significant. Now, regardless of which end of the barbell a user represents, we are in a position to meet the ever-rising expectations for,  a more compelling user experience.

Joe Ruck

BoardVantage NextGen Architecture — a model for the normal social functioning in the modern workplace

Wednesday, February 23rd, 2011

No doubt the most exciting Internet strategies today rely on leveraging the trust relationships that exist within groups of people, be it for social, commercial or educational purposes. The concept jumped on the scene only a few years ago but has quickly gone mainstream, shape-shifting to suit ever more purposes and expanding far beyond what was originally thought possible. The technologies underneath go by the umbrella term of social networking and Facebook is considered the standard bearer.

Corporate America has been quick to embrace this trend externally, primarily for marketing purposes, but has been noticeably slower in their adoption internally. That dichotomy is understandable. The security of these networks is broadly regarded as weak and the potential for leaks of confidential information is great.

But what hasn’t been talked about to the same extent, and what is an equally grave impediment to broad adoption, is the simplistic relationship model embedded in those networks. Without a richer model to address role complexity of the typical professional in the modern workplace the value of social networks as a collaboration tool is dubious at best.

It is this latter aspect that was foremost on our mind when we set out to reach beyond our traditional board market and build a collaboration platform for leadership teams. Reconciling the needs for security and simplicity is a technical challenge for many engineering teams but, for BoardVantage, with our extensive experience in the board portal market, it is a core competency. The greater difficulty lies in the proper capture of multiple roles which are needed to support the normal social functioning of the workplace, and which are routinely combined in a single person (e.g. direct report, peer, manager, etc.).

We viewed enriching the model as the central architectural challenge, one that could only be addressed with a reinterpretation of established concepts. However, if successful, it would be the keystone to fulfilling the requirement of capturing multiple roles. Below I will delineate the five key elements of the architecture we developed.

1. TeamSpace-Driven Content and Communication
In our model TeamSpaces are shared environments that function as the focal points for confidential collaboration. They form the backbone of our architecture, permeating every aspect of our design. Individual spaces are configurable with a rich functionality to support a range of knowledge worker roles and workplace process. Since knowledge work commonly relies upon a combination of content, process and communication, TeamSpaces are equipped as such.

2. User-Driven Content and Communication
The architecture also designates a class of content as being user-driven. This class represents any content under the exclusive control of the user. Among others this class includes such items as an alert inbox, a document ‘briefcase’ and status information.

This distinction allows a user to maintain exclusive control over private information even while working in a shared-content space. User-driven content is portable so it’s at the individual’s disposal at all times, irrespective in what TeamSpace the user resides at any given time.

3. TeamSpace Arrays
TeamSpaces are often networked. They can be snapped into a collection of spaces, creating a TeamSpace Array. This permits segregation of the roles which users play across the various groups in which they collaborate. Because spaces are ring-fenced, the role played in one TeamSpace does not spill over to the role played in an adjacent one.

4. TeamSpace Backplane
A TeamSpace Array can serve as proxy for the multiple roles a professional plays in the modern workplace. But this concept only works if a user can navigate between multiple spaces — swiftly. That’s why the architecture deploys a secure backplane. Controlled by permissions, this model lets individual users jump back and forth between spaces quickly and securely.

5. Permission Model
TeamSpaces are access-controlled, but that does not mean that should be one-size-fits- all access, once inside. Consider the example of a calendar schedule. Even if a schedule isn’t confidential, it is generally considered to be privileged to the individual. While every TeamSpace is ring-fenced against intrusion by outsiders, within the space any asset, whether a document, event or otherwise is access-controlled under a permission model. The model is flexible enough to support real-world cross-hierarchical use cases.

Using this framework the NextGen architecture has proven to function in a range of collaboration initiatives by different types of knowledge workers. The model balances the concerns of confidentiality with the real needs to share. Equally important it addresses the need for multiple roles in the modern workplace in an effective and elegant manner.
(more…)