Complexity: Different Ways, Same Output, or is It?

There are outputs and the processes that produce those outputs.  In a business, if there are many processes that produce the same output — that can be a silent killer for a business.

Consider an inventory management system, where associates on the factory floor are to use a scanner-based tool to adjust physical inventory in the cycle counting process.  Ideally, there ought to be a tool that guides and helps the cycle counter do his or her job correctly.  But, some, if not all, warehouse management systems aren’t built to actually help the associate on the factory floor.  The result: variation in processes, leading to potentially the same output, but ridden with errors. 

I once led a project that looked at how cycle counters adjusted inventory for a middle-market consumer packaged goods company.  Our team conducted a Task-Based Usability Test, where we chose a random sample of associates, chose common tasks that Cycle Counters encounter everyday, and see what tools and steps they would take to accomplish that task.  The result: A Qualitative and very revealing view of the variation in the approaches of the associates.  Below is an example of what that test might look like (because of confidentiality, the image below is not the real output of that study, but an example for this article):

On the left, we see the various common tasks that Cycle Counters see everyday in their jobs.  On the top column, we see the areas of responsibilities, followed by the associate ID, since this was a scrubbed, or anonymous test.  The content is their answers based on the tasks. 

Notice that the tools used qualitatively vary — in other words, there is clearly variation in the tools used and in how people adjust inventory for this consumer packaged goods client.  What does this mean?

For one, variation in any process can lead — no, — it does lead to defects, errors, and customer dissatisfaction.  For another, this firm introduced complexity into their system by providing so many tools that seemingly all do the same thing.  Later, we found out that there was wide overlap in the tools — their functions and goals.  The wide selection of tools for the associates to choose from creates confusion, variation, and is unnecessary complexity.  The culprit: The firm allowed complexity to be introduced to the system.

Lesson Learned

Complexity is a silent killer for a business.  Prior to our study, little did this firm know, but this complexity problem alone — which was introduced by the firm itself — was causing the firm several million dollars in inventory write-off’s per year.   The root cause was a proliferation of internal tools that was too complex and encouraged variation in how Cycle Counters adjusted inventory. 

Is there uncontrolled proliferation of products, features, and processes in your business?

+++++

For articles on queueing theory, time-traps, operations, lean and six sigma, please visit the links below:


Short URL: http://bit.ly/mJdB

Share This Post:



  • Digg
  • Facebook
  • del.icio.us
  • Suggest to Techmeme via Twitter
  • StumbleUpon
  • LinkedIn
  • email

2-pizza teams (10)
3 C's (3)
5S (38)
A3 Report (9)
adoption (7)
agile/software (59)
ajax (4)
amazon (53)
apple (3)
apple iphone (7)
axiom (3)
Aza Raskin (9)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (394)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
change management (5)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (7)
customer experience (10)
customer obsession (52)
customer recovery function (1)
customer segmentation (8)
customer service (17)
design thinking (14)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (4)
ethnography (29)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (67)
genchi genbutsu (68)
general (135)
germany (1)
google (15)
heijunka (65)
holidays (1)
hoshin kanri (1)
how to be a human (1)
IDEO (2)
image uploading (1)
iphone (5)
ishikawa (69)
IT at Toyota (67)
just-in-time (4)
kaizen (4)
kanban (46)
law of instinct (1)
Leadership (43)
lean (165)
Lean Consumption Maps (98)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (68)
nba fines (1)
net promoter score (nps) (1)
obeya (39)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (39)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (6)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (6)
product development (20)
productivity (4)
quality (41)
quasimodal design (1)
queueing theory (41)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (6)
root cause analysis (60)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (128)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (46)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (104)
the beer distribution game (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (11)
toyota (75)
travel (1)
trump bankruptcy (1)
turnaround (5)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (11)
waste (59)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (12)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

No comments yet.

Leave a comment

(required)

(required)


Additional comments powered by BackType