A Business Technology Place

Employee Growth Chart

Childhood memories.

Did your mom mark your height on the door frame as a child? Let’s admit it. Those pen marks on the door-frame each year were exciting. It was even more fun if siblings, or other relatives, were marked on the door as well. What was it about the marks that made it so fun? Was it that we could see how much we were growing each year? Was it that we could see how close we were to a height goal? Or was it that mom would see our progress? Whatever the reason, one aspect that jumps out to me is the childhood growth chart was a visual control. We didn’t think about that at the time, but using visual controls play an important part of business life.

 

Employee growth.

A few years ago I wrote about a key concept for employee development, “employee development is better executed as an ongoing part of a business rather than an event.” As I map and transform many of my business activities to TPS and Lean principles, I think about how this relates to Principles 9 and 10.

 

Principle #9 – “Grow leaders who thoroughly understand the work, live the philosophy, and teach it to others.”

Principle #10 – “Develop exceptional people and teams who follow your company’s philosophy.”

 

The verbs ‘grow’ and ‘develop’ describe an ongoing process. To measure progress of the growth journey, we’ll need visual tools and controls.

 

Make a chart.

One tool I started using a few months ago is a flow and performance board for visual management. This is a good spot to track employee growth metrics. I’m doing this with an eye towards professional skills enhancement and team cross-training.

 

Step 1: Create a skills matrix of the staff to document the current state

Step 2: Create an individual training plan for employees that addresses their personal growth as well as overall coverage the team provides to the business.

Step 3: Make it visible just like mom did. J

 

Here’s a very simple chart framework.

(Ratings 1-5)

Skill A Skill B Skill C
Employee A 2 4
Employee B 3
Employee C 2 3

Here’s a simple action plan (employee development plan).

Task Due Date Notes
Employee A increase skill A to level 3. December 31
Employee B learn skill A to a level 2. October 31 Currently employee A has no backup for skill A
Employee C increase skill C to a level 4. November 15

Onward and upward!

 

Photo Credit: Rochelle Hartman via Flickr Creative Commons

 

Conquer the antagonist

Yardwork reflections.

I often use yard work as a time for self-reflection because what else is there to do while drawing shapes with a lawn mower? Sometimes I reflect on personal interactions and plans, but I also use the time to consider business activities. As I edged the lawn this week, I wondered how was it possible that some business leaders are able to leave behind a successful blueprint for the philosophy and culture that drive and define an organization. This isn’t a new question, but it’s a thought many business leaders go through on their professional journeys. Jim Collins spent an entire book on the subject in Built to Last. He discusses how companies find enduring success. More on that in a minute.

The antagonist.

As if by fate, I read a story tonight on NPR.com about implicit egotism that links to a study published by the Harvard Business School (HBS) called the Ikea Effect. The Ikea Effect suggests we have a preference for and place greater value on things we personally create. The HBS paper adds, “labor leads to increased valuation only when labor results in successful completion of tasks.” Meaning, when we are successful in a task, we tend to place a greater value on our creation than something someone else created.

I quickly realized the Ikea Effect told me something I’ve already observed and participated in during my professional career. Typically, new leaders and managers bring their way of doing things to a company. They want to establish a change in the company by doing what worked for them in the past. Maybe they were hired for the purpose of bringing change to the organization. On the flip-side, I bet you could think of some successful companies that started failing after a change in executive management. Considering the Ikea Effect and the thought of enduring greatness and consistency, the antagonist may very well be me!

Grow leaders from within.

One of the principles of the Toyota Production System is to “Grow leaders who thoroughly understand the work, live the philosophy, and teach it to others.” We read this same finding in Jim Collins’ books Built to Last and Good to Great. A key observation from Collins, is companies that found success spanning multiple leaders most often promoted insiders to the CEO position. Constancy of purpose, culture, and philosophy is a key ingredient to enduring success.

Know thyself.

My take-away from tonight’s mental exercise is to look and reflect on the Ikea Effect in my own decision making. Am I prone to shut-out other ideas because I didn’t create them? Am I over-valuing methods, procedures, and systems I created? Can I create sustainable systems that will be maintained by those who succeed my position in the company? The Toyota Production Systems uses the phrase “the right process produces the right results.” So success is not about what I create or what you create. But it’s more about results that are right for the company or organization.

 

Onward and upward!

Photo credit : http://maxpixel.freegreatpicture.com/photo-1207142

 

 

Do more with what you have!

We need more people. We don’t have enough resources.

Every week I hear about the conflict between the number of employees in the organization and the amount of work to do.  The underlying presumption is the organization can accomplish more by adding more people. The problem with this rationale is it takes the focus of solution delivery off the processes used to deliver solutions. Adding more people to a team is complicated:

  • It adds more strain on inter-team communication. Whatever inefficiencies exist in the current team environment will become more apparent with more people.
  • It creates the need to train and develop new people in the culture, business, and process flows of your company.
  • It moves the process bottleneck to another departmental team. For example, if you add more developers then you need more business analysts for requirements documentation.
  • It values urgent things over important things.

The right process will give the right results.

There are times when staff should be expanded. But it can’t be arbitrary and because the existing staff feels stressed about the existing workload. A better approach is to first examine the current environment for ways to work smarter and more focused. Process focused leaders look for ways to work smarter knowing that in the long run it will deliver greater capacity and more value added results. I don’t consider this doing more with less. I like to think of these actions as doing more with what you already have. Consider these approaches:

  • Write less code – If our first solution to solving a problem is writing code, then we’ve missed the opportunity to solve the problem by simplifying the process. The ultimate solution may require less code. Keep it simple!
  • Align value streams to your mission. – The activities we do that should be more important to us are the ones that align to our mission. The mission is a guide-post when deciding between what’s urgent and what’s important.
  • Develop existing employees before adding more. – The existing staff can provide more capacity if they work on the right things with more efficient processes. To do more with less we have to believe that getting existing people to understand the power of process efficiency, focus, and alignment adds more capacity. Get employees to work harder, but not before you help them work smarter.

Onward and upward!

Photo Credit: Jim1102 via creative commons.

 

Mapping software development to Lean IT.

The right process will produce the right results.

A core concept of the Toyota Production System is the right process will produce the right results. The “right process”. What exactly is that? Software development practitioners spend entire careers in search of it. Everyone has ideas and rationale to support various methods including Waterfall, Agile, and Hybrids.

But there is more here than a methodology match. As I consider how to adopt and grow Lean business principles in IT, I face a classic dilemma; how do I influence standardized tasks and visual controls into a software development process? Software developers are a different breed of office worker. Many of them have personality traits which make consistent processes quite a challenge.

Are software developers rule followers?

Here’s what I know about guys and gals that write code for a living:

  1. They are puzzle solvers
  2. They are inspired by writing code not documenting progress
  3. They don’t enjoy estimating because they don’t want to time box their craft
  4. They are artists who care more about how code is written than the process used to govern the project

So here’s my dilemma. A software developer is a person who is a creative problem solver that needs space to be an artist and really just wants to write code. How I put that person in a system that seeks to define standard processes and visual controls as a means to provide customer value?

Software developers are rule followers. They write code against a predefined language syntax. They crave requirements up-front before they start writing code. But software developers are also artists. They want freedom to express their talents through what they create, not a set rules defined by someone else.

Lean IT. Finding common ground.

When faced with opposing viewpoints, I believe the best approach is to focus on common ground. What do Lean IT and the attributes of a software developer have in common? Everyone wants these things:

  • Eliminate waste – Businesses like the effect on the bottom line. Developers don’t like spending their time on busy work.
  • Increase customer value  – Businesses like the effect on sales and repeat sales. Developers like having jobs and customers giving them new problems to solve.
  • Standardized work – Businesses like repeatable tasks that can be improved. Developers like a clear definition of what is expected of them.

Starting with these concepts, I think it’s possible to get developers on board with Lean IT.  With a little flexibility, compromise, and focus on the core business principles of Lean, a team can move down the path of increasing customer value. Let’s start there.
Onward and upward!

Photo credit: https://flic.kr/p/6U71RM – Jeff Sandquist via Creative Commons

IBM reverses course on work-from-home

We can improve business results with this change!

IBM recently announced the end of work-from-home for the Marketing department as it moves towards regional offices for co-locating the Big Blue workforce. They aren’t the first to do this. Yahoo reversed course in 2013 by banning work-from-home and Best Buy followed their lead. Could this be another business cycle forming? Companies have been centralizing and decentralizing organizational layout for years as they switch between shared service cost-savings and greater focus on customer needs. Now it appears working-from-home, telecommuting, and flexible work arrangements may start going through similar cycles.

The debatable points.

Working-from-home has many characteristics and touch-points to create debate:

  • Team collaboration vs private think-time
  • Consistent schedules vs flexible schedules
  • Meetings together vs conference calls
  • Productivity of the group vs productivity of the individual
  • Commercial office cost vs home office cost
  • Relationships and culture
  • Employee retention
  • Commute time

The irresistible force to change something.

It’s easy to see how business leaders are drawn towards this policy as a means to improve efficiency and productivity of their workforce. The debatable items can all impact workforce productivity. But change is initially disruptive and must be executed properly to yield the desired results.

Obviously there is no single right answer. Organizations must weigh options and make decisions based on their business environment, their workforce, and their culture. Workers have preferences based on their life-stage, distance from the office, position in the organization, and personality.

Regardless of personal preferences, it does not change the mission of the organization or the commitment required of the workforce to produce great work. Ultimately, managers make a decision and move forward with it to create the culture and environment they want to achieve the mission of the organization. The work-from-home policy attracts or repels would-be workers. But the workforce needs to understand the interests of the company must survive to provide services customers will buy and to provide long-lasting security for employees.

Onward and upward!

photo credit: Debra Roby via creative commons.