Tuesday, October 14, 2014

Content Creation and Word of Mouth

The "rule" of 90/9/1, ascribed to various sources, maintains that 90% of Internet users are passive consumers of information, 9% are active consumers of information who will pass along content from other sources, and only 1% are creators of original content.   There are various sources that cite these figures - and while none of them provides a reference to the original research, the proportions seem entirely plausible.

Consider that very few individuals maintain blogs or personal websites, and even many of those are merely collections of content that has been gathered from other sources, so it's more likely that the 1% of "originators" may well be closer to  0.1% or even 0.01% - and in all the "voice" of the Internet is merely people repeating things that other people have said.

Until the advent of social media, user-generated content was largely a niche activity and was often communicated in closed environments (the limited number of participants in a bulletin board that was behind a password gateway).  But in the present day it is quite voluminous, highly visible, and is given greater credibility that company-sponsored content on the Internet.

However, given that the vast majority of people who communicate in social media are merely commenting on, sharing, or otherwise calling attention to something that someone else said rather than contributing something of their own to the conversation, the notion that the voice of the crowd will entirely replace traditional advertising seems to be ill-conceived.  The crowd is merely repeating things it heard elsewhere - so while people might not be hearing the message directly from the advertiser, the advertiser is still the point of origin and the crowd is more of a medium through which their message is spread.

Given that people who redistribute information are picking it up from another source, the voice of the advertiser may in fact be stronger than ever before.  In literal word-of-mouth promotion, the message was likely mutated by intention or fault of memory - people can often remember an interesting or funny commercial, but not the brand.  So when they speak of it, chances are the brand identity is stripped - but when they link to it, or cut-and-paste the content, the message is redistributed intact, complete with the identity components.

A common caution relates to the "telephone game" in which each person modifies a message as they repeat it to someone else - but this too is an inaccurate reflection of the manner in which messages are passed along in social media.    People do not rewrite an advertisers content - they link to it in its original source, or create a digital copy without modification.  At worst, they may excerpt a shorter message from a longer one, but it is not a common observation that they alter the substance of the message itself.

In all, this suggest that the "voice of the crowd" is less ominous than many would imply: the crowd is merely a flock of parrots, and the advertiser is still firmly in control of the message they deliver.

Thursday, October 9, 2014

Healthy Conflict

It seems to me that I have been asked about half a dozen times over the past week, ‘How is your relationship with ______?” – in which ______ was a team member or stakeholder in a project that is altering the customer experience.   The way in which I answered these questions began to fall into a pattern, and it seems to be culminating into a general method of assessing working relationships.  So I’ve mulled over it a bit more, and here’s what I have come up with …

In general, my assessment of a working relationship seemed to be based largely on the level of conflict and the friction of negotiating toward a common goal and a strategy that was mutually acceptable.    I’ve commented before that I spend at least double the amount of time persuading others to support a design than I do crafting it, and all things considered that might be a gross understatement.

But to lurch back toward the point I was setting out to make, a good working relationship seems to be based on the manner in which the work product is negotiated, and I think I’ve arrived at a ratio of healthy conflict that defines a good working relationship:
  • 75% of the time, the other person trusts in my expertise and accepts my decisions.
  • 20% of the time, the other person questions my expertise, demands that I explain a decision, and then either accepts it or negotiates to a mutually acceptable modification.
  • 5% of the time, the other person completely ignores my expertise, digs in, and insists on having things done their way.
Here’s the reasoning I think that this ratio is about right:

75% Faith

A project team is assembled of people from certain areas – software developers, systems analysts, product managers, operations managers, marketers, and the like – each of whom is an expert in their domain of knowledge.  While they all contribute to the definition of the final solution, the negotiation between them must entail a high level of respect for the expertise of other people.

Said another way, a database programmer may have a suggestion for the way in which the product should be marketed – but should ultimately defer to the judgment of the marketer in decisions pertaining to marketing.  Just as the marketer may make a suggestion about the way in which he things the database should be schematized, but ultimately defer to the expertise of the database programmer.

Even so, I don’t think that an expert, however experienced and knowledgeable, should ever demand or expect complete faith in 100% of all instances.   If that ever happens, he has intimidated his colleagues to the point where they do not feel that they can question something they find to be  unusual, which is not by any means the sign of a healthy relationship.

20% Debate

Debate should account for about 20% of a healthy relationship.  This need not be a protracted argument to come to a decision, but may be as simple as someone asking “why do you propose to do it that way?” followed by an “oh, I see” after a brief explanation has been tendered.

A certain level of debate is healthy, in that it causes an expert to check himself from time to time, and be ready to explain any decision he has made.  Where that doesn’t happen, experts tend to become high on their own fumes and to be less diligent in their work, knowing that they will never be questioned.

There is also the possibility that a non-expert will contribute “out of the box” thinking that an expert will often fail to exercise – because expertise in an area is often based on assumptions of what will and will not work, and it sometimes takes a person who doesn’t accept that a given idea is impossible to get an expert to pause to explore whether it actually might be possible.

A lack of debate can also be a sign of a lack of engagement – a person who doesn’t care about something will not bother to ask questions or make arguments.  Or worse, it is a sign that the “expert really isn’t contributing any expertise, and is telling the rest of the group things that they already know.

5% Inflexibility

The last mode of interaction, inflexibility, is not at all healthy, but I have nonetheless decided to include it because it is entirely inevitable.   People in positions of power like to exercise their authority at times, and even the most complaisant and respectful leader still feels the need to wield his power to see his orders carried out without question.

That’s not to say that inflexibility is the sole demesne of executives and managers – as there are quite a few little tyrants in the lower echelons, people who insist on having their way as a method of feeling empowered, or who sense that if they do not interfere in the work of others they will be perceived as non-contributors.  While they are largely gnats in the grand scheme of things, their buzz can be quite the nuisance at times.

So perhaps the ideal ratio would eliminate this manner of behavior altogether, but I don’t expect it is a realistic expectation to do so, and as such I’ve included it as a “no more than” percentage rather than a desirable goal.

Possible Broader Applicability

While I have meditated on this in the context of a project team, my sense is that this notion of conflict and the ratio of types might be germane to other working relationships as ell: superior-to-subordinate, peer-to-peer, and so on.   But admittedly I haven’t thought much about that broader context, so this is merely a musing without much deliberation.

Thursday, October 2, 2014

Increasing Human Efficiency

It is interesting, and more than a bit depressing, to read some of the classical works on topics such as management and economics - as it can very often be observed that a "new" trend is merely the revival of an idea that has been around for decades or centuries. And that there are many ideas that seem confounding simple - such that you can't read them without a sense of "of course this is so" and "why would anyone think otherwise" - but have been ignored or abandoned.

Reading Walter Dill Scott's book on Increasing Human Efficiency gave me exactly that sense.  Written in 1911, it outlines a number of ideas that seem entirely reasonable, and which have largely been ignored or forgotten over the course of the past century.   My sense is that productive workplaces employ at least some of the principles he mentions, and that unproductive ones ignore some or all of them.

There are so many principles in this book that are clearly beneficial to efficiency and effectiveness of work, and which are just as clearly being violated in many workplaces, that to do it justice would require re-typing the entire book - but to keep this meditation manageable, I'll focus on five ideas that seemed to strike a nerve.


The efficiency of work can only be improved by a change in the technique or technology by which it is done.  Simply insisting that men work faster and harder is insufficient.

Scott considers the practices of "scientific management" in which a manager observes his workers, notices the practices of those who are most efficient, and then teaches those practices to the less efficient worker in order to boost productivity.

Frank Gilbreth's work with masons is an excellent example: Gilbreth noticed the average worker used eighteen motions to lay a single brick, where the productive worker used but seven, and he was able to eliminate two of them.   By teaching a five-step process to a crew, he was able to boost the productivity from 40 bricks per hour per man to 120 - tripling the speed of work.

However, this practice does not seem to exist in the modern workplace.   Managers simply set production quotas without providing any indication of how they may be achieved: if you produced 1,000 units last month, you goal for this month is 1,100 or if you completed a task in thirty days you must now do it in twenty-eight.   Ask "how may I accomplish this?" and the answer will be "figure it out for yourself."

The bosses (who are not managing anything, merely bossing people around) do not even understand what a worker does, but insists that he must somehow figure out on his own a way to do it faster and better.  This is not scientific management by any means, and yet it is all too familiar to many workers.


In order to discover more efficient ways of working, the worker must be allowed to experiment with the process and technique by which he accomplishes a task.

Scott's insistence that men must be taught a process by which to work is mitigated by the insistence that they be provided some latitude in getting their work done: so long as their product is good and the rate of production is acceptable, they should be left alone.

The value in giving workers such latitude, and even being tolerant of some temporary decreases in productivity, is that they have the freedom to innovate - to deviate from standard practices and discover more efficient ways of working, which workers have an uncanny ability for doing.  If held too rigidly to standard procedures, the workers can only become as efficient as the procedure.

To discover a new method requires deviating from the prescribed method, in a process of trial and error to discover more efficient means of accomplishing a goal - with the risk that the new method may not be more efficient, and acceptance that a new method may be less efficient at first but be modified or habituated to gain proficiency.

But again, this does not happen. In the present day, workers are given the paradoxical command to "innovate while following procedures" - which is as logical as ordering them to "sit down while standing up."   It simply cannot be done, so workers end up following procedure - to attempt to innovate is to risk punishment merely for doing something in an unauthorized manner, and since the reward for success is paltry (if any at all) and the punishment of failure grievous, most workers regard innovation as an unacceptable risk.


When a worker's task is intellectual, more dependent on thought than physical action, he can only be productive if he is protected from distractions.

Scott gives special attention to the "intellectual worker," those who are in positions where the activity of their work is more mental than physical.   It would be entirely foolish to expect the task-worker to complete his work while he is constantly being physically jostled - and it is equally foolish to expect the mental-worker to give focus to his work while being constantly distracted.

This is clearly violated in the present workplace under the banner of "collaboration," which eliminates quiet places in the office in favor of creating an environment in which employees are constantly talking to one another, in meeting rooms or on the work floor, and having no opportunity to retreat to a quiet place and attend to the work that results from the conversation.

While it cannot be disputed that information exchange is a good thing, there can be too much of it.   In a circus-like environment in which there is too much noise and motion to remain focused on a thought for more than a few minutes, the mental worker simply cannot get tasks done in an efficient manner.   And yet, "open" office spaces with constant noise and distraction have come into fashion, in direct contradiction to Scott's principle of the necessity of concentration.


Loyalty is reciprocal.  An employer wins the loyalty of his workers by showing loyalty to them.  He cannot expect them to be attentive to his welfare unless he is attentive to theirs.

During the early industrial era, the workplace became a very unpleasant environment, and unions formed to protect the basic health and safety of workers, as well as to negotiate a fair wage, reasonable hours, and continuity of employment.  The result was a hostile relationship between employee and employer, and perhaps the worst in human history outside of the institution of slavery or serfdom.

An yet, even in his age of antipathy, there were stunning examples in which union workers would abdicate the terms of their contracts to give an extra effort to help employers in time of need: to work longer hours, accept less pay, and otherwise sacrifice for the good of their employers.

Scott was very quick to point out that "loyalty begets loyalty" and through real-world examples demonstrates that in every instance that workers were loyal to an employer during a time of crisis, the employer showed great loyalty to the workers well before the crisis arose.

There are many firms even in the present day that covet that level of devotion - and worse, who expect that level of devotion as a matter of course.   It is not uncommon for salaried workers to be expected to work fifty-hour weeks for no additional pay on a long-term basis (and sometimes on an ongoing basis), for exceptional performance to go unrewarded, for the annual increase in pay to be well below the increase in the cost of living.  And all of this from firms who wonder why employees have no loyalty to them.


Work becomes efficient when the worker is able to apply his skills in a consistent manner and discover methods of efficiency.  Any change disrupts his progress to efficiency, and constant change prevent him from ever becoming efficient.

Of all the various methods of increasing the efficiency of work, Scott considers habituation to be the most powerful.   The worker gains efficiency where there are consistent practices he may follow, devoting his attention to the things that are most important by being able to ignore the many things that are unimportant.   Any change in procedures, particularly for routine and inconsequential parts of a job, require attention and discipline until they can become routinized - and it is wholly unproductive if the practices that are changed are not contributing to production.

And yet, in the modern workplace, the pace of change is relentless.  Employees must constantly be attentive to the "new way" of doing something that is different to the "new way" it was done the month before.   It is insisted, without rationale, that changes bring improvement - but it is a consequence that constant change prevents efficiency from ever developing.  The employee is prodded from one awkward and unfamiliar way of doing things to another awkward and unfamiliar way, never becoming habituated enough to gain efficiency (and to reap the full benefit of the method prescribed).

It is not that change is universally undesirable, but should be mitigated: a change should be made when it provides an improvement to a process that creates greater efficiency in the work.  But in the present day, change is seldom explained - and it is wondered if it is ever considered in any meaningful way.   And moreover, many changes are implemented to create efficiency for non-productive staff (such as accounting clerks) by placing additional burden on productive staff (those who do the work to produce and deliver the product or service of the firm).

***

In all, I have the pessimistic sense that I should perhaps simply stop reading so much to and instead focus my attention on mindless acceptance of things such as they are.   Knowledge of a better way only makes the present ways more noxious - and discovering that the "better way" has existed for decades or centuries but has simply been ignored depresses me profoundly.


Tuesday, September 30, 2014

The Joy of Discovery

I had an interesting moment sitting behind the mirror in a usability lab, watching participants experiment with a widget I thought to be rather clever.   I can't disclose particulars, as it's something that is unusual and I'd like to leave the competition stunned and stammering for a while, but the lesson learned is worth meditating upon.
Upon seeing the widget, the participant paused a moment.  "I don't know what I'm supposed to do here," he said.
I sighed, and glanced at a colleague who was already giving me the YFU smirk.
But a moment later, the participant said "Oh, I get it.  All I need to do is [action] and it [results].  That's really cool." And he spent several seconds toying with the widget and watching the screen change.
I smirked back at my colleague.  His opportunity to haze me had just evaporated.
It's worth noting that this was not a data point in which one participant found something to be delightful that everyone else didn't even notice.  I got a similar reaction from every single person who tested the interface.

So what's the point?

The point of this incident, or at least the one that I took from it, is that intuitive is good, but  discovery is much better.   Had the participant been able to figure it out at a glance (which was admittedly my original hope), he would have been able to use it with no hesitation whatsoever - and he would not have been delighted.

But there is value in that moment of hesitation, and the sense of pleasure that comes from figuring something out.   It's a small sense of accomplishment that gives a person a sense of being empowered, and having struggled a little bit before finding success makes an interaction that would have been unremarkable into something that is emotionally engaging.   That's powerful.

It's much in the same way that getting a compliment for something that took no effort at all feels hollow, while getting complimented on something that took a little effort feels good (and getting complimented on something that was difficult is really great).  A reward simply means more when it took an effort.

But Don't Overdo It

Even though I have the sense that letting people struggle a little is not a bad thing - and that learnable is more emotionally rewarding than intuitive - I would not say, by any means, that more is better.  If every single task a person does requires a moment's hesitation before they figure it out, the joy of discovery will likely be played out and what once was regarded as cool will be much less satisfying.

Another happy accident here is that the widget I was designing is on the last page of an application form, when the user is one or two clicks away from hitting the "buy" button.   I feel very optimistic that giving them that little dose of emotion, so close to the point of commitment, is going to carry over and there will be a nice bump in the conversion rate.

That may well be a good indication of how to place a discovery boost in an application flow: a few clicks before something that will be difficult or prone to trigger an anxiety reaction.   Ideally, those will be few - but you can't eliminate them all.  A "buy" button is always going to give users pause, but if they are feeling intelligent and empowered when they encounter it, that may help put them over the hurdle.

I would promise to report back with the improvement in the conversion rate after the new widget is rolled out - but again, it's something I will have to keep under my hat for obvious reasons.

Friday, September 26, 2014

Technology's Limitations

Some notes from an article I read ... I think I may have explored this issue before.

The assumption that technology eliminates human error is a fallacy: a computer system is programmed by people, and as a result it thinks like people - specifically, the people who programmed it to think in a certain way.   So a computer system is merely consistent in its logic, not merely right in its logic.   And the one quality it lacks is the ability to think differently.

Thus technology can be rigged to make consistently bad decisions just as readily as it can be rigged to make consistently good ones.   And even if its decisions are good at the time it is programmed, the world changes.  A computer system programmed ten years ago is doing what made sense ten years ago, which may be different to what makes sense today.

Technology is also limited to those elements that can be quantified and measured, and will ignore any data that seems inconsistent even if it is valid and relevant.   This is valuing reliability over validity, and results in a system that is out of touch with reality because it is rigged to ignore the factors that matter most in favor of those that are most easily measured.

The appeal of technology is often to escape the responsibility of judgment.  A person who does what a computer tells him is not to blame.  He is prevented from thinking for himself, but is merely following orders.   And as the computer was programmed according to logic dictated by others, he is not following the orders of the machine but of the person (or committee) who determined how the machine was to be programmed.

In that way, technology also caters to megalomania.   The person who programmed the system exercises great power over everyone whose daily activities are dictated by the system for as long as the system is in use.   Autocrats enjoy making rules for others to follow, and the ability to do so through the proxy of a computer, to effectively control many others over a long period of time while meanwhile escaping the blame (their bad logic will be the computer's fault) is very attractive to cowardly and manipulative people.

That said, the flaws in the motives and methods of technology should not be used to dismiss it altogether.  Technology is very good for some things, particularly when the most valid factors are, in fact, quantifiable and unlikely to change over long periods of time.  The data they provide is invaluable to optimizing a process that is repeated frequently in a situation that will not change.  The question, which is seldom raised, is whether the real-world phenomenon to which technology is applied actually meets those criteria.   Very often, technology is the wrong tool for the job - and almost as often, it is used anyway.

Where the factors that are most influential to outcomes are qualitative, or where the elements and environment are subject to change, technology is a very bad solution - which puts a firm on rails to do the wrong course consistently, and never to discover a different course that would be more successful.