Archive

Posts Tagged ‘service design’

Waterfall Design (QFD): Looks Good but Watch Your Step

February 24th, 2013 4 comments

Pretty but Watch Your Step

Waterfall design looks so good on paper.  You start by defining customer requirements and then each step naturally leads to the next until the service is offered, product produced or new process is launched.  A QFD is a waterfall design process and it expresses this natural progression as linked matrices.  Anyone who has ever seen a presentation for QFD sees and accepts the logic of the waterfall concept.  Why then is it that what seems like a smooth running machine usually ends up a painful and burdensome process?

The problem is that elements of a product or service are usually put through in phases to keep the whole work flow running.  If that weren’t done, the Company would have the vast majority of the people in the process idle having either finished, or still waiting for their turn, to contribute to the final work.  Such massive underutilization is no way to run a company.  So we avoid the poor utilization by breaking things down into pieces and sending them through the process in components.  The pressure to maintain utilization and the resulting flow of components creates a tremendous problem in waterfall design processes.

The problem is the series of rework loops caused by gaining buy-in and responding to feedback from internal customers. As each segment flows through the maze of work, each functional area has valuable feedback and expects to be heard.    Once again, using the QFD process as an example, as the output of each matrix becomes an input to the next matrix, the new parties have comments.  And as such, the input to a particular matrix gets kicked back along with the new functional area’s thoughts and comments. The water is now flowing up the waterfall!

Now the problem starts to compound when you have more than two matrices in the process.  When its just two, the rework and new work cross and loop until their joint work product meets exit criteria.  They are just handing off to each other like two people having a catch with two balls.  Every now and then one player may have both hands full but the waste of his compatriots empty hands is short lived.

Download WP “Design Basics – QFD Overview”

But once past two players, problems arise quickly.  As a simple example, let’s imagine three matrices starting with product definition.  Product definition provides input to design which, in turn, provides input to Service Operation or Manufacturing, as the case may be.   Now imagine, just like when there were two matrices, that the output of the first matrix (i.e. product or service requirements) goes to a design team which provides feedback.  They remain in equilibrium until the design team’s output goes to a production or delivery team which has its input.  As Player 2 passes reworked Cycle 1 to Player 3, they are also receiving reworked Cycle 2 from Player 1.  It isn’t long before a ball hits the ground.

Irrespective of how fast everyone can be, if you add enough matrices or steps, the process breaks down.    What usually happens is that Player 1 ends up with a stack of balls on the ground around him.  The system was designed for one set of requirements to flow smoothly.  When multiple rework loops occur, the perfectly designed machine collapses under its own weight.

There is no easy and universal problem for this breakdown.  Some possible solutions are for fully integrated teams representing all functional areas to work on components together through all phases.  A design “cell” if you will.  Another solution might be to design from the back to the front.  And yet another might be to simply accept underutilization as a cost.  But whatever the case, you should be aware and step outside the box before you drown in the waterfall.  If you have comments, please contact me.

Productivity – The Coming Golden Age of Continuous Improvement

February 10th, 2013 Comments off

A Drive for Productivity

Last week I wrote a post entitled Value Creation for Private Investors that went largely ignored as it was one of my lowest viewed posts of the new year for a Monday when most of you tune in.  The idea about which I wrote was a revelation to me but it was still nascent at the time and thus very undeveloped and weakly presented. But it gnawed at me and so it kept turning in my head.  And now it pops out again this week hopefully a bit more developed.  The idea is the transition we are making from creating the illusion of wealth with financial engineering to needing to truly drive wealth with productivity gains which will make for a golden age in Operations and Operational Excellence.

As a nation, we will flourish based upon our ability to drive productivity.  You see wealth, as measured by GDP, during the majority of our lifetimes has been driven by population growth.  But as our population growth slows, wealth will only be created by increased productivity.  This transition has been hidden from us for some time by the illusion of wealth creation brought about by high capital liquidity and inappropriately priced risk which eventually lead to the bursting of a financial bubble.  But with risk being more appropriately priced, the illusion is gone and we are now faced with long term slow growth and the only way to stoke it is with increased productivity.

To drive the growth in productivity, I wish to cite a recent blog post by GE’s Jeffrey Immelt a portion of which read as follows;

There are four new drivers of productivity, and success in each depends on the technology and talent we develop. The first is how the sheer volume and increased access to shale gas in regions around the globe is changing the energy debate and the balance of energy power. It would require real infrastructure and pipeline integration between Canada, Mexico and the U.S., but North America could achieve energy independence within 10 years. The second driver for dramatically increased productivity is applying the lessons of social media to the industrial world and building what we call the Industrial Internet. By owning and connecting the analytical layers around industrial products – and using real time data to extract real timeknowledge – we can improve asset performance and drive efficiency. The third driver is speed and simplification because the only way to serve our customers better and compete in a complex world is by working faster and smarter. The last productivity driver, and related to the other three, is the evolution of advanced manufacturing. Manufacturing excellence, forgotten for too long, is once again a competitive advantage.

Drive Value with OpEx

Now when you look at this argument about from where we will get the productivity growth, a problem jumps out.  Namely, we have to generate non-population related productivity gains with a population that isn’t geared to Immelt’s productivity drivers.  Our younger citizens certainly are better aligned and skilled but as population growth slows, they will be the minority.

So guess what — the knowledge of how to improve services, products and processes is really valuable.  Now I’m not talking about how to write a project charter or write up a SIPOC.  I’m talking about revolutionizing energy with process innovation in the extraction of natural gas, the development of the cloud so we can jettison underutilized servers from expensive IT budgets and citizen publishing of information so knowledge flows freely and into every nook and cranny of the population instantaneously.  Imagine – those have all happened in the last five years.  Those are the types of improvements that transform an economy.  But there is plenty of room between a project to save an AP process two days and reinventing the extraction of fossil fuels.  And every time a new industry is targeted, all the operating processes below the top level change will also be looking to improve.

Can you imagine where these big seismic changes will happen next?  How about redesigning education so everyone has access to knowledge inexpensively?  Or health care where we can all see an insanely low level of simple IT tools that if applied would eliminate gobs of waste.  Or all levels of government where we have constantly rising costs with little measureable gains in services.  These trends will continue.  They must continue or we, as a nation, will slowly lose our global relative wealth.  And I just don’t think Americans are ready for that.  But the changes will be disruptive.

In the race to drive wealth through productivity gains, we will see the greatest impact in processes and services simply because they are the largest percentages of the economy.  I’ve already named drilling services, the cloud, newspapers & magazine publishing, health care and education as service companies which either have gone through or are poised to go through significant redesign. What of the process side?

Systematically Driving Value with OpEx

Well I think we are going to see work get reinvented.  My former colleague at Qualtec, Mitch Lawrie, is working on software to focus management on results versus activities and my recent blog on the subject drew significant attention from many of you.  We have worked with several clients in financial services, telecom and transportation which are redesigning long accepted processes to drive greater than 50% reductions in key process cycle times by making them leaner, reducing complexity and capturing information better as well as analyzing it for knowledge.

To return to my original post, my “aha” moment was that I was at a private equity conference where investors of all sizes where lamenting they could no longer make easy money.  That easy money was driven by a combination of capital liquidity, high tolerance for risk and poor quantification of that risk.  It was a recipe for a bubble.  If you bought an asset, held it and sold it before the bubble burst, you made money.  If it was levered, you made a lot of it. The funny thing is that private corporate investors weren’t the only players at the casino. We were all there with real estate and stock portfolios.

But that is gone now.  And as we look into a new environment, we realize we are facing the longer term challenge of slowing population growth and an aging population that isn’t skilled at what is needed to drive the sort of productivity gains needed to maintain historic wealth creation.  To create wealth as a country, we now have to earn it the hard way.  And since there are only so many hours available in the work force, it means we have to work smarter.

And a clearer definition of that “aha” moment brings me to the message in this post.  We figure out ways to work smarter – whether it is a fifth level sub-process or an entire industry.  The result is that we are entering a golden age for people focused and skilled at how to work smarter.   We have the opportunity to make great contributions to our economy.  I urge you all to THINK BIG.  If you’d like to discuss, feel free to contact me.

Michelangelo’s Principles of Design Thinking

January 27th, 2013 Comments off

Perfect Design?

Some time ago, I read an article about great art and artists.  The author recited a lengthy list of what constitutes great art.  As I read it, I thought about how his arguments applied to industrial design as easily as they did to the Renaissance.  Recently, I’ve been engaged on service design problems and I decided to write down as much as I could remember from the article as principles by which to work on these engagements.  Here are the principles I documented:

1. Simplicity of Design is Clarity of Purpose.  So often, I look at a product or service packed with functions or features and walk away without bothering to learn to use it.   You would think the default would be the simple version but when people try to get creative, they somehow feel packing more into an essay, a painting or a product makes it better.  It doesn’t   Often, it simply masks the work has no real purpose.

2. The Best Designs Can’t Be Improved Upon. Imagine a math proof with either a mistake or that is overly complex.  In time, it will be improved upon and erased from the text books.  Imagine doing something so well that you leave no room for improvement. Similarly, imagine designing a house or piece of equipment that is as comfortable or useful today as it was five hundred years ago.  Won’t it be as comfortable five hundred years from now?

3. Design Starts with Defining the Right Problem. Developing the right solution for the right problem are two design problems in one.  You are better off making sure you’ve properly defined the problem before working on a solution.  Imagine if Columbus had designed a ship capable of dealing with the end of the earth?  Obviously, Columbus redefined his problem.

4. Getting Design Right is Hard Even Though It Looks Easy.  This one is really important…especially when you juxtapose it with #1 above.  Sometimes you look at a product or service that has been elegantly designed and think – so simple, I could have done that.  Well, you probably couldn’t because it was really hard.  Imagine the simplicity of the light-bulb  yet it took Bell 1,000 attempts which he called “steps”.  Each failure is a step forward.  But there are many failures before there is success.  It is hard even if the final product is such a perfect answer that it appears to have been obvious.

5. Nature reflects the Greatest Designs.  Look around at nature.  It is especially well designed.  A trout is perfectly designed to thrive in a cold mountain stream feeding on a bustling colony of insects which in turn are perfectly designed to live between the rocks of the same stream.  Good designers copy nature.  And their work product is often described as “natural”.  One of nature’s more relaxing elements is symmetry and repetition.  Gardens are more peaceful when you don’t have one of everything but repeat patterns of colors and plants.  Isn’t there an amazing elegance to a DNA strand?

6. Treat All Your Designs as If They Were a Mistake…And You Knew It Would Be.  In other words, do it over because you’ll do it better.  In doing so, you’ll look for your mistakes and try to correct them.  That is the hard work part of it.  And since no one sees every iteration of your design, they think it was easy.  I think recognizing you can always do better is what is particularly scary about being a parent – there really isn’t a second chance.  And since you know you’ll make mistakes, you just hope your children will one day forgive you.

 

Download PPT on Design Basics

 

7. A Great Design Can Be Really Scary.  More than likely, a great design so redefined the problem that the new solution won’t look anything like what current solutions look like today.  We can see today’s post-secondary education model is broken.  What will it look like in 20 years?  Would anyone in the ‘60’s have believed you if you told them that to get their news and information, they’d be reading digital content written by ordinary citizens in place of listening to Walter Cronkite?

8. To Design Well, Seek Collaboration…and Competition.  Something happens beyond ourselves when we are with each other.  It happens whether we are working together or competing.  Humans drive each other to excel.  That is why cities are so creatively vibrant. They explode with both collaboration and competition.  It is why you see two rivals push each other to excellence in sports…whether they are on the same or rival teams.  To design well, commune.

I hope my engagements yield great solutions for my clients.  I hope I help them see ways of satisfying their customers and stakeholders they’d never thought.  I hope these principles help me get them there.  Feel free to send me your’s.

Innovation – Beware the Voice of the Customer

January 1st, 2013 Comments off

Beware

Malcom Gladwell, in his #1 national bestseller “Blink” (2005), recounts fascinating results from Columbia University professors Sheena Iyengar and Raymond Fisman’s speed dating studies.  The professors ran speed dating nights across the street from Columbia University for university graduate students.  The events were like other speed dating events in which attendees would meet members of the opposite sex for a short set period of time (four to six minutes) and check a yes or no box on a form listing all their “dates” for the evening.  If both the man and woman checked each other’s names, they would given the information by which to meet each other and pursue a relationship.

But on a few occasions, in the interest of psychology and economics, Professor Iyengar and Fisman’s respective fields of study, attendees were asked to fill out a short questionnaire asking them to rate what they were looking for in a potential partner on a scale of 1 to 10 on six criteria that included attractiveness, shared interests, sense of humor, sincerity, intelligence and ambition.  They were asked to do so before the event, shortly after the event, a month later and then six months later.  In addition, at the end of each “date” during an event, they were asked to rate the person they’d just met on a scale of 1 – 10 and for the aforementioned attributes.

As you can tell, by the end of an event, attendees declared what they wanted, who they’ve chosen and how they rated who they’d chosen versus what they wanted.  So what happened?  Well, Mr. Gladwell reports that Professors Iyengar and Fisman found that the people to whom their subjects were actually attracted didn’t match the attributes to which they’d said they were attracted prior to the event.  But now it gets a little trickier.  If a subject said they wanted attractive, sincere mates but chose funny, intelligent ones, when asked after the event which attributes they preferred, they answered funny and intelligent. But when asked a month later, they could switch back to their initial preferences.

When the two professors were asked to interpret the results, the psychologist said she didn’t know what it meant while the economist said “the real me is the me revealed by my actions”.  Given the stated preferences changed and there is no report of the same candidates attending a second event so their actions could truly reveal the real them, I’m with the psychologist.

Download “Service Design & Innovation – Service Blueprinting”

What does this have to do with anything about which we write on this blog?  Well, I think the title says it all — “Beware the Voice of the Customer”.  If we don’t know what we want in a partner in whom we might vest our time and emotions, imagine the challenge to clearly and consistently state our preferences for a product or service over the time necessary for a company to recoup the investment to develop and launch?

So how do we successfully develop and launch new products and services if we can’t trust what customers tell us?  Well, we do have some tools and philosophies that more readily capture our fickle nature.  Namely observation linked with rapid prototyping.  Meet enough people and you don’t need a list of likes and dislikes.  The process of evolving preferences and product or service attributes meet.  If you wish to discuss VOC and or Design Thinking deployment models, feel free to contact me.

Design Thinking in Operational Excellence

October 11th, 2012 2 comments

Design Thinking - Left Brain, Right BrainRecently, I have been very interested in design.  The interest has been born of the need to help customers grow.  It started a few years ago when working on Service Design issues with a client.  The interest eventually took me to Stanford’s d.school of design where I had a chance to examine some case studies.  Naturally, I sought to apply the lessons to my own work. So I began to think of how the ultimate left brain world of Operational Excellence would mesh with the right brain world of design.

A key point I took away from Design Thinking was the suggestion to solve problems by fast iterative prototyping irrespective of whether you felt you’d  found the true root cause of a problem.   How could the idea of prototyping be applied to Operational Excellence where we teach to gather data and analyze with the intent of finding root cause before designing a solution in the form of an improvement?  How could these two seemingly contradictory philosophies be reconciled?

What I concluded was that if we know the process and have the data, we can find root cause. But that in most cases, especially in service businesses, we don’t have that sort of data.  In those cases, prototyping can be a highly effective way to improve or design.  Some might consider this little more than another name for simulation.  But it’s not because when prototyping, you must find a way to launch and go live with the prototype which creates new customer feedback and that is not available in a simulation.

Download Service Blueprinting an overview of Service Blueprinting …

Now some might say that launching prototypes is akin to letting customers find your mistakes and will damage your relationship or brand.  Certainly, there are those cases.  There are products and markets in which launching prototypes is really not possible.  But in many cases, a co-creation process is not only possible but is preferable.  Certainly, when working with a customer where information and actions flow back and forth in a joint value stream that is part of a supply chain, co-creation of prototypes may be the only effective way to find solutions.

I’m not here to tell you we should throw out existing problem solving methodologies.  I’m simply here to say that the right and left hand sides of our brains can work together to be more flexible in how we find solutions.  Design Thinking is very applicable to Operational Excellence and we are using it in many situations to help customers get to solutions faster.  If you’d like to discuss, you can reach me at jlopezona@ssqi.com.

Service Design and Innovation – Are You Armed with the Right Tools?

October 2nd, 2012 1 comment

I recently worked with a client that had a not uncommon, but likewise complex, organizational structure –  the matrixed organization.  This is often the chosen structure in B2B service businesses that seek to recognize the different contributions and responsibilities of customer facing business development folks, service design groups and service delivery personnel with project management skills. This is especially the case in businesses that deliver large, discreet and technical projects.
essay writers needed
These organizations wish to be sensitive to customer needs and innovative with new services but are often burdened by complex human systems and competing points of view.  One way to address the disarray or sub-optimization is to establish a base set of skills for all the various groups and then pockets of knowledge that serve the needs and demands of the different groups, allow migration between groups and provide a ladder to the top of the pyramid.

For our client, we developed such a roadmap of skills.  The first level was that everyone has to know how to map customer and company processes and how they interface.  Examples of such work was to develop joint value streams or, even more valuable, a service blueprint.  In addition, the first level includes VOC, identifying waste, and economic value analysis from both the customer and enterprise viewpoints.  As previously stated, all the personnel involved had to master this knowledge.

Download Service Blueprintingthis overview of Service Blueprinting …

The second level had everyone in a service design role learning to interpret VOC, convert it to CTQ, plan for the future and price value.  Modules included Enterprise Value Stream Mapping (EVSM), Service Blueprinting, Advanced Process Analysis and the initial tables of the House of Quality.

Finally, the last level was constructed for personnel with broader account and/or service responsibilities. At this level we introduced long term planning and complex service design knowledge and skills.  Concepts included economic value analysis, multi-generational planning and TRIZ.

For those familiar with Six Sigma Black Belt type curriculums, we constructed a laddered set of tools and concepts along with design roadmaps similar to DMAIC as a body of knowledge for Service Design and Innovation professionals. Service Design and Innovation are learned processes and skills which can be assembled into a career path of knowledge.  If you’d like to discuss this further, please contact me at jlopezona@ssqi.com.

I Hear Voices! … Tips for Turning VOC into Good Design

September 13th, 2012 4 comments

voice of the customer - VOCSo often when we have product, service, process, or system failures, we find that the root cause is a lack of connection to what the customer really cares about …. Voice of the Customer (VOC).  Everyone sees the disconnect, agrees it is the problem, and now sets about obtaining VOC.  Now, things really get complicated for when you seek VOC you discover many voices struggling to be heard.  The challenge becomes to sift through all those competing voices and understand which are critical and what they are saying before trying to convert what you’re hearing into a design or redesign.

So, in an effort to help sort through all of this, there are some simple but very important concepts that can be used to put some structure around all those voices you hear when you set about gathering VOC and converting that information for use in design.

  • Direct v. Indirect – When gathering customer information within your organization, make sure you distinguish between direct and indirect voices.  A direct voice is feedback coming from the end customer.  Indirect voices are the customer facing parts of your organization that theoretically act as a proxy for the external end customer.  Indirect voices are important as they represent can provide meaning to what you hear from the external end customer.  BUT, they are not the end customer voice.  Both direct and indirect are important, and are very different.
  • Customer Requirements v. Product Requirements – Recognize when you are hearing a customer requirement or a product requirement.  A customer requirement is usually framed within the context of what the customer experiences while a product requirement is usually a key function or feature of the product.  I want a comfortable ride on my bicycle is a customer requirement.  I want a big soft seat is a product requirement – even if it’s direct feedback from the customer.  When a customer gives you a product requirement, you must ask “WHY?” before designating it as a desirable product requirement to be used in designing a solution.
  • Qualitative v. Quantitative – Qualitative feedback is rich but expensive to get so it is normally provided from a smaller customer base.  Quantitative feedback can be easily obtained from a large population at a significantly lower cost but it is far less descriptive. The answer is not to solely rely on one or the other.  Use interviews to define your survey or your survey to define your script and interview population.  Go back and forth taking advantage of the deep aspects of one and the breadth of the other.
  • Segmentation – Always segment but segment in whatever way is meaningful to your product, service, process or system.  As an example, in designing an internal software application many designers look at the functional departments that are going to use the system.  But you may find it more meaningful to segment according to the type of usage irrespective of functional area.
  • Basic v. Performance v. Excitement – Applying the concepts of the Kano model are invaluable.  You must know what are basic, performance and excitement levels and their marginal returns as they all would receive different priorities depending on your objectives.   The nature of the requirement  becomes especially useful when you sort it by demographic or customer segment.

Download VOC QFD

 a short intro to QFD and how it can be used to create linkage between customer and technical requirements.

After you have sorted, ranked and prioritized your assembled customer information, it is time to compare and rank product characteristics relative to the customer information.  This can be done in a planning matrix (see downloadable PowerPoint document).   The planning matrix can then be used to develop design alternatives. The design alternatives can be ranked and rated against both the product requirements to determine process and production feasibility and versus the customer requirements to determine impact to the customer. The two exercises can then be brought together to choose a design which factors in the value, cost, and feasibility of solutions.

It is incredibly valuable to have VOC information.  It is even more valuable if you understood how you got it and how you plan on using it.  Knowing the end game can also help you determine how you want to gather information and make it an efficient process.  The key is to gather, convert, analyze and use the information in the right way.  Otherwise, whatever you invest in getting VOC will go to waste and you’ll be right back where you started wondering how a newly launched product, service, process, or system, once again, missed the mark.  If you wish to discuss this article or any of its point, please feel free to contact me at jlopezona@ssqi.com.

Voice of the Customer for Service Design – Are you Getting It … Really?

September 6th, 2012 1 comment

We have just finished working with a large international services company which has had challenges rolling out new services.  The most difficult aspect of their business was in discovering the real customer requirements, and converting those requirements into service requirements and, ultimately, a service design.  Like many service companies, they just have an immature process for this.

rorschach_inkblotThe service design team is essentially the sales team. They get multiple voices from many parts of both their organization and the client.  It is literally a cacophony of noise which, when converted to a service, the service process map looks like a Rorschach image.  It is then “launched” for the bugs to be worked out as the service is being delivered.  The rework is expensive, taxes the company’s employees, and rarely produces a happy customer.

To help them, we built a Voice of the Customer (VOC) Maturity Model with laddered capabilities for them to climb. That model was built on some basic premises and observations after working with service companies for many, many engagements over the course of my entire career.  Let me lay these out to you so you understand our final recommendation to any service company struggling with the same problem.

Download VOC Maturity Model

 a short Powerpoint presentation that describes a 5-stage Voice of the Customer (VOC) Maturity Model

First, there are two aspects to VOC – getting it and using it. They are very different.  And there are two basic ways to Get VOC: 1) directly from the customer,  and 2) indirectly from all your company’s customer facing team members.

Our experience has been that companies are better at using what information they have than in getting good information. Further, that what they do to get the information often relies on customer facing team members as surrogates for the customer.    One thing is for sure, while only a small fraction of companies that use it well get it well, almost none of them that manage the information get good information. Why?

I think this is true because after crashing a few launches, companies suffer enough pain to cause them to start gathering information.  Then as they develop the disciplines in using it, they discover it isn’t very good and they need better information.  So until they try to use it, they don’t start improving the quality of the information gathered.  Just as an aside, along with discovering they aren’t getting good information, they often discover they aren’t getting the right information as the system focuses on product specifications rather than customer requirements. So the learning curve goes from we need information to …. we need good information to …. we need the right information.

As a company goes through this discovery process, they have to overcome some assumptions that are being taken as truths, and are really holding them back from progressing.  Why does this happen?

  1. The assumption that customers don’t really know what they need.
  2. Information is gathered once at the beginning by simply asking customers what they want.
  3. They only gather information from surrogates.
  4. They only gathering information from their best relationships (often happy customers).

These are the traps that get you stuck in bad information and more rework. To overcome these traps, information must be gathered both directly and indirectly. The information gathered must be prospective and from a broad population.  And gathering and incorporating information must be continuous, NOT a one-time event.

Needless to say, the process isn’t easy and requires a significant effort.  But the payoff is a multiple of the effort.  There is no doubt that companies that have structured processes for gathering and converting customer information outperform companies that don’t, regardless of whether they do it well or not.  Working with a plan, even if not perfect, outperforms no plan.  And needless to say, if your plan and execution are done well, then your company performs even better.

Take a look at the summary presentation of what we recommended.  If you have any experiences, comments or questions you’d like to share, let me know at jlopezona@ssqi.com.  And by the way, while this is all written based upon an experience with a B2B service organization, it is equally applicable to internal processes such as a Shared Services organization providing a service to operating units.

When Leaders Overlook Process in Service Organizations …

March 16th, 2012 Comments off

Leadership…we want to be leaders and want leadership.  When you have a leadership role you personally grow and you can help the organizations in which you work and the individuals with whom you work.  When we are group members, leadership sets a vision and inspires us.  Leadership, like great architecture that conceives of a soaring skyline, can be magical.

Process…a series of operations which bring about a result.  It is a logical, nearly mechanical algorithm devoid of emotion.  You unemotionally define the inputs, suppliers, required actions and desired outcome in terms so you can measure.  You strive for stability so you can then improve capability as measured by customers.  Defining each brick and how they are assembled might not sound so inspirational, but you’re kidding yourself if you think it’s any less important.

Leaderships’ vision of that skyline and processes’ preoccupation with laying bricks can seem far apart and disconnected.   Yet when leadership looks past process, the results are eviscerating to any vision and corrosive to the leaders themselves.

In service organizations, processes are always driven by people, and managing the people for each process is the work of a process owner.   The process is the service and the people are the process.  So the people are the service, trying to be productive each and every day within their process.  Getting processes to work as a system is about getting people to work together toward a final objective.

When leaders ignore process they ignore the people that are the service.  And that never turns out well with your customer.  A current TV show has CEO’s come down from their lofty perches to work ordinary jobs to get a feel for the people and what they do day in and day out.   In a recent episode, the CEO was stunned at the impossibility of work processes.  Workers were stressed out, fought with each other and delivered poor service to customers.  As you can well imagine, no one believed in the CEO much less the CEO’s vision, as he soon found out!

Download Service Design - Service Blueprinting

this short .ppt overview of customer-focused process design and Service Blueprinting …

A smart CEO might hand the problem over for process redesign.  He might also say with empathy that this is just the wrong way to treat these people and the customer, and do what is necessary to make it right for both.  Theoretically, the two statements lead to the same place.  But the former continues with the same disconnected state between leadership and people while the latter begins a transformation.

The point of all this is to remind ourselves that working with processes in a services organization is about working with people.  That when we see leadership disconnected from the concerns of process we probably see leadership disconnected from people.  And when we find that situation we’ll probably find dysfunctional teams and dissatisfied customers.  BUT,  when we see leadership concerned with making processes work we will see people who find their jobs fair and who are dedicated to their mission, which should lead to more satisfied and loyal customers.

So all of us as leaders and members of a team need to think about the processes upon which our vision is built because, in so doing, we think about the people in the organization and the customer of our service.  And everyone in that chain will notice the attention, how their work is made easier and thus buys into the larger vision.  If you’d like to discuss the points in this article, contact me.

Service Design vs. Product Design – 5 Key Differences

December 19th, 2011 1 comment

Designing a product and designing services have many similarities but also key differences.  Both need clean VOC, clear definition of CTQs, stakeholder input and intelligent tollgates.  But the differences in the design process for the two are far greater.  And those differences are defined by the nature of products versus the nature of services.  So here are the top ten differences in their nature.

Service Design vs. Product Design - DifferencesHow do these attributes change the design process?  Well imagine how difficult it is to know if you have the right design if you can’t easily measure different attempts since repeatability and storability are issues.  And you really aren’t sure what you can measure since quality is defined by the customer’s experience of an outcome more than measuring the attributes of output.  And imagine what happens to multi-generational planning when you have to factor in how difficult it is to maintain your moat of defensibility for a new service without the right of a patent. Time and again basic elements of a design process are scraped or reinvented in an attempt to build a proxy for what is normally taught and practiced as good design principles.

In the end, you essentially have to nearly start over n building your design process for a service.  Basics are retained but new elements must be introduced or emphasized.  In a recent blog post, I point out how the basic principle of tollgates must be retained but mapping becomes the foundation to test, validate and repeat due to the absence of data.

Download service blueprinting

a short presentation on Service Blueprinting now ……..

At Qualtec, we’ve built a new design process or roadmap and established a set of tools to support each step of the way.  We will continue to write about this subject as we find there is a real dearth of information available.  But we also welcome your input and so if you’d like to discuss the differences and how to adapt to them, we invite you to contact us.