The Do’s and Don’ts of Measuring Employee Productivity in the Knowledge Economy

Unraveling the complexities of gauging employee productivity in the knowledge economy can be a daunting task. This guide will illuminate the do's and don'ts, offering a fresh perspective on how to effectively measure and enhance productivity in today's dynamic work environment.

Innovative solutions for measuring what seems immeasurable

Since the early 1900s our economy has undergone a profound shift from industry to the so-called “knowledge economy.”

• Manufacturing-based employment has fallen from 33% of total U.S. employment to 10.7%.
• Knowledge workers make up nearly half of the overall workforce.
• How can leaders measure and improve productivity in a knowledge-based workplace?

Embrace employee autonomy

Knowledge workers should have the opportunity to shape their workdays in ways that they know make them more successful and productive

• On an individual level, consider what parts of your job require your skills and knowledge, and what parts amount to chores
• At a team level, managers can work with team members to make sure they’re working on tasks that align with their strengths
• Consider creating a standardized yet flexible system of goal-setting
• Employees themselves are empowered to define what success looks like

How do you measure and improve team culture?

The “Keystone Habit” is a habit that can start a chain reaction of organizational change

• Think about measureable outcomes that reinforce a positive, collaborative team culture
• For example, if your keystone habit is incredible customer service, you might set a goal that measures customer satisfaction
• If it’s team-wide learning, set a team goal for the number of books read or courses taken

The People Puzzle

It’s less about standardizing human behavior to measure output and efficiency and more about empowering individuals and your team

• Your team’s desire to work more efficiently comes from factors like whether you demonstrate “positive and virtuous” leadership practices and whether they feel like they’re doing valued work that matches their skill-set
• Promote the idea that increased efficiency is, as Taylor said, for “mutual benefit.”

Accounting for the human element

If employees don’t want to work for you, no amount of productivity measurement and optimization will solve that core problem.

• In the knowledge economy, workers are the means of production and the output is the series of creative decisions they make in a day.

Where the Classic Productivity Tracking Model Fails Us

Traditional ways of measuring productivity fail us in a few key ways

• What is being “produced” in a knowledge job? What is that output worth? Does time even matter? If so, when?
• When it comes to knowledge work, productivity is really hard to measure

Can Team Productivity Be Measured?

The old “productivity = output divided by input” model fails us on many fronts

• No one has discovered a silver-bullet metric showing managers and company leaders how to measure the true productivity of knowledge workers
• Successful companies find innovative ways to measure and improve productivity

Remember the human element

Creating the best team has less to do with combining individually optimized rockstars and more with how members listen to one another and show sensitivity to feelings and needs

• When companies try to optimize everything, it’s easy to forget that success is often built on experiences that cannot be optimized
• There may be non-traditional ways to measure and improve cultural elements

Quality is as important as quantity

Our inability to consistently measure output quality makes it hard to find an equation that makes sense for measuring knowledge worker productivity

• Developers are problem-solvers, not code machines
• They spend hours thinking through problems and testing solutions – hours where they’re not producing a single line of code output

“What is the task?”

Input is complicated. e.g. In manual work, the task is always obvious. In knowledge work, that’s rarely the case.

• Not all tasks create the same amount of value for a company. For example, responding to an email could build a relationship with a contact who could be a critical investor down the road.

Source