Lean Love Advice: Part 2 of 4

by Mike Lopez on June 27, 2007 · 2 comments

By Mike Lopez

I’ve written about the four rules of Lean before. I have been thinking about how they apply to marriage. To refresh those of you who have not read the Harvard Business Review article by Steve Spear and H. Kent Bowen, I will restate the rules here and share how I see them apply to relationships. This is the second in a four part series to apply each of the four rules.

Other posts in the Series:

  1. Lean Love Advice: Part 1
  2. Lean Love Advice: Part 2 – This Post
  3. Lean Love Advice: Part 3
  4. Lean Love Advice: Part 4

Welcome now to Lean Love Advice: Part 2

Rule 2: Every customer-supplier connection must be direct, and there must be an unambiguous yes-or-no way to send request and receive responses.

To me, this is the most important rule of all. Communication has to be the biggest problem in a relationship. Isn’t it the premise of several marriage books that communication is the cause of most major marital problems? I believe it. Rule 2 tells me that relationships have a better chance of success when both parties create unambiguous communication paths. Rule 2 applies to Rule 1 in a very important way. If I have taken the lead on finances, there must be a way for me to ask for help when needed. Rule 2 gives us the insight to create an effective communication plan. If I need help, I need to specifically request for help preferably using SMART requests:

  • Specific
  • Measurable
  • Acceptable
  • Realistic
  • Time-bound

What is a good SMART request? “Honey, after you throw that raw meat into the trash, would you take the bag of trash out and throw it into the garbage can right away? I don’t want it to smell up the house.” This is specific (throw trash out), measurable (it is done or not), acceptable (she is not asking me to eat the raw meat), realistic (taking trash out is easy), and time-bound (right after I throw away the raw meat.) A malformed request would be, “The trash needs to go out.”

This may seem excessively formal, but I love this type of request because it makes it so easy to please my wife. I know exactly what she wants and can give it to her exactly how she wants it.

Next: Rule 3 – Flow

Mark Graban 2011 Smaller Lean Love Advice: Part 2 of 4 leanAbout LeanBlog.org: Mark Graban is a consultant, author, and speaker in the “lean healthcare” methodology, focused on improving quality and patient safety, improving access, reducing costs, and fully engaging healthcare professionals. He is also the Chief Improvement Officer for KaiNexus.


pixel Lean Love Advice: Part 2 of 4 lean
Share, Print, or Be Social:
  • printfriendly Lean Love Advice: Part 2 of 4 lean
  • twitter Lean Love Advice: Part 2 of 4 lean
  • facebook Lean Love Advice: Part 2 of 4 lean
  • googlebookmark Lean Love Advice: Part 2 of 4 lean
  • linkedin Lean Love Advice: Part 2 of 4 lean
  • digg Lean Love Advice: Part 2 of 4 lean
  • stumbleupon Lean Love Advice: Part 2 of 4 lean
  • delicious Lean Love Advice: Part 2 of 4 lean
  • posterous Lean Love Advice: Part 2 of 4 lean

{ 1 trackback }

Lean Love Advice: Part 4 of 4 — Lean Blog
July 27, 2011 at 11:38 pm

{ 1 comment… read it below or add one }

1 Tom June 30, 2007 at 6:59 pm

I’ve always found SMART goals to be somewhat lacking. There’s definitely some value to the approach, but it seems to lead to a “you got what you asked for” mentality, rather than a “deliver what the customer wants” mentality. I find that conveying the intent of the request is far more important than the specifics of the individual request.

You stated the intent this in your example–the intent was to avoid stinking up the house–but the actual SMART request does not need to include it. I find that most miscommunication, both at work and in my marriage, happens not because requests are not SMART, but because they are lacking in intent.

Like or Dislike: Thumb up 0 Thumb down 0

Reply

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

CommentLuv badge

Previous post:

Next post: