The Critical Difference Between How & Why

by Step on August 22, 2011

If you’re installing vinyl siding you mustn’t drive your nails tight. Otherwise the siding will buckle in warm weather. When you’re pulling wood on the green chain, rotate with the other guy every hour to preserve your stamina. In a quick-service restaurant, time your first batch of chicken to finish cooking ten minutes before the lunch rush. As laborers, most of our how questions get answered within the first day or two on the job.

Managers and business owners, on the other hand, are always looking for a better how.
“How do I hang on to my best workers?”
“How do I find good people in the first place?”
“How can we improve our customer service?”
“How can we make our marketing more effective?”

Regardless of whether our how questions have been answered, all of us need a good answer to the question “why does this matter?”. Without it our work becomes dissatisfying. If there’s ever been a time when you dreaded Monday mornings, you know what it feels like to need a better why.

Interestingly, there is a single method for answering both how and why. Tomorrow I am hosting a short event to outline that method. It’s not a sales pitch for something more, there’s nothing else to buy or do afterwards. You’ll leave the event with the method in hand.

If you’re looking for answers to how questions for your business, buy a ticket to tomorrow’s event. You’ll see a tenfold return on the money you invest.

If you need a better why, please allow me to make this my gift to you. At this point the cost of the event is covered and there is still space left. I’d be happy to have you come as my guest. At the end of the event a lunch will be provided. If you don’t mind skipping lunch or bringing your own, use the discount code “why-lunchless” and your ticket will be free. To join in the lunch, use the discount code “why-withlunch” and your ticket will only cost $10.

Whether you’re looking for how, why or both; claim your seat now. Registration closes today at 7:00 p.m.

{ 0 comments… add one now }

Leave a Comment

Previous post:

Next post: