Wednesday, July 14, 2010

Kill the hourly wage

In a previous post, I discussed why CEO compensation should be in the millions. However, the article did not address the disparity between executive and worker pay. Well, here's how to bridge and narrow the gap: kill the hourly wage.

Hourly wages worked well for a manufacturing economy. They allowed organizations to break productivity into easily measurable units. To measure productivity in a manufacturing economy, organizations simple divide input into output to get a quantitative figure. When wages can be broken into hours, hourly input dollars could be divided into hourly output product values to get hourly productivity per worker.

The measure of success in a mentisfacturing economy distorts this formula. You see, when service-centered economies and organizations take a look at input, the speed of the flow of ideas doesn't require hours to bring about multi-million dollar results. Some of the most cost saving measures an organization can take can be conceived in minutes.

For example, a client was in the process of shuttering its business thanks to the 2007 mortgage defaults. During a conversation about how best to fold the company, I asked the leadership to stop the process. They had invested millions in developing technology, systems, processes, and people to deliver their organization's services. They did not have to close their doors, no matter what analysts said. With a bit of creative thinking, I suggested, they could re-purpose those investments and assets to launch new services and recover their losses.

That two-minute bit of advice combined with a four-hour strategy session led to a business plan revamp and relaunch -- and more than $50 million in investment.

What would advice like that be worth to your organization?

Charging by the hour for ideas that are backed by years of experience, personal knowledge, problem solving skills, and collaboration is ridiculous in a mentisfacturing economy. When more organizations are making things with their minds instead of their hands, the time to put together products and services is exponentially reduced. Service industries continue to grow while contributions of goods-based industries to our national GDP are falling. So how do you compensate an employee, vendor, or consultant who takes 3 minutes to explain an idea that brings your organization $50 million in investment and $100 million in revenue over the next two years?

I recommend killing the hourly fee/wage and replacing it with a base salary or flat fee for services. For internal compensation, handsomely reward your employees with a variable value-based compensation model that shares a percentage of the savings or revenue based on the contributions they make to the organization. For example, if your receptionist answers the phone from 9am to 5pm, provide him with a base salary to cover the basic skills and time needed to greet customers and direct calls to the appropriate extension. But if that receptionist happens to handle a customer complaint and prevents a $400,000 per year customer from taking their business elsewhere, provide that person with a 5% customer value bonus ($20,000).

I know it might sound outrageous  at first glance -- receptionists don't receive $20,000 bonuses! But the only way to fill the wage gap is to shift compensation models from time-based to value-based. That process will take time for some organizations. For others, their enterprises are small enough to make compensation changes more quickly. The mentisfacturing economy requires that we reward people for the value they bring to organizations, not the time they put in at their desks.

For another example, one small business could not figure out why its bookkeeper wasn't producing results. The bookkeeper was on site for eight hours, two days a week. When the owner asked to see financial reports, the reports were little changed, if any, from week to week. After some discreet observation, the owner discovered that the bookkeeper often ran into difficult bookkeeping questions. Instead of actively pursuing answers, the bookkeeper sat quietly or sent text messages friends and family until time was up, filled out her timesheet, then left. Legally, the owner was obligated to pay the $55 hourly rate for the time spent on site though no results were produced. The hourly wage model rewarded an incompetent hire and sapped valuable financial resources from other areas of the organization. If the fee for service were value-based, the bookkeeper would have been compelled to produce results or would not have been compensated for the time wasted by both the company and the consultant.

You, too, can shift your compensation model from manufacturing to mentisfacturing. However, our public policies and labor laws need a lesson in intellectual value in the mentisfacturing economy. But your organization can make incremental changes that comply with current labor laws. Implement meaningful performance reward programs that provide compensation for goals reached, savings realized, and revenue generated. These rewards can be based on individuals, teams, departments -- or all of the above.

Base rewards on instant bottom line results for each employee's personal concerns. Cash bonuses mean more money for Junior's college fund and to pay outstanding bills. Additional vacation time means more time with the family and to spend time pursuing personal interests. Do not use "vapor pay" like stock options, futures, and programs that require being vested or could go away if they lose their jobs or the economy tanks. Long-term compensation models defeat the purpose of rewarding every day performance results.

In a mentisfacturing economy, the people, their ideas, and the results they bring override the importance of butts in seats. Just like executives.

Wednesday, July 7, 2010

Product failures are communications failures

When the customer is the last one to be consulted, product development is doomed to fail. Just ask Microsoft. I'm not 100% tapped into their market research process when they design new products, but it seems like the 48-day market lifespan of the mis-aligned Kin device forgot product development 101: Respond to the needs of your customers.

Nancy Xiao did a great job weighing the pros and cons of the Kin in her TechFlash report. As a representative of the product's key demographic, she states some rather obvious points in her breakdown. Why were such obvious smart phone features overlooked -- like a calendar, instant messaging, and an easy to use phone?

Successful product development results from successful communication. Products and services are ways that organizations say to its target audiences, "We speak your language, and our offerings directly translate your priorities and concerns into a response that you can understand." When products flop, it's because of a miscommunication. Either the priorities and concerns of the customer were missed, or the response to those priorities and concerns are translated into the wrong language.

When communications go awry, it's because one or more of the participants in the discussion are hyper-focused on their own priorities and concerns while neglecting those of their audience. This is true in flopped presentations, workplace conflicts, parent-child confrontations, lost sales opportunities, and disrupted friendships. I see this all the time during coaching sessions, assessments, marketing and sales planning, and even product development.  Good communication requires taking the time to really get to know the audience and their motivations.

It is the responsibility of the leading entity (the organization, the manager, the parent, each of the friends, each spouse) to take the time to go below the surface and really understand what is going on. When a teenager inevitably screams, "I hate you!" to a parent, the statement is rarely true. That's surface speak for "You don't understand me, haven't taken the time to understand me, and are constantly dismissing my priorities and concerns, so I no longer trust you and refuse to open up to you unless you start regaining my trust in your ability to be an open, honest, and fair parent." It's just that most teens don't yet have the sophistication to express exactly what they want to say [the same could be said for many adults].

Organizations, like parents, must employ patience and take the time to get to know the priorities and concerns of all stakeholders, not just customers. That means spending more time reading between the lines instead of just responding to the results of focus groups and surveys. It means getting out of the lab environment and into the places where your stakeholders live, work, and play every day.

By focusing product development on the REAL priorities and concerns of your customers, you can avoid costly go-to-market demises that rip holes into the financial fabric of a growing organization. Not all organizations can afford to spend billions to develop a product, test it in the marketplace, then pull product product support and production like some enterprises.  By treating product development like a conversation, you can avoid marketplace missteps and develop thoughtful offerings that respond in a way that is loud and clear.

FOR YOUR CONSIDERATION
Is your organization leading responsive conversations? Are your actions meeting the needs of your customers, employees, and other stakeholders? If it seems that you and key stakeholders are speaking different languages, call me to help you translate and prepare a clear response: 206-782-4040 x104.