Skip to main content

(Almost) Never Say Never

The words "always" and "never" are so popular in daily conversation, despite few situations being truly deserving of the adverbs. 

When getting passed over for a promotion: "My work is always overlooked"

When arguing with your spouse: "You never do the dishes"

Always means at all times. Never means at no time ever. Even if rare, I'm sure there was a time you got a pat on the back and your spouse cleaned up after eating. 

We exaggerate to emphasize. To drive home a point. We don't mean to be dishonest, but to exaggerate is to say something false. A poor foundation for communication. 

If a co-worker's late for a meeting, it's unproductive to accuse them of "never being on time", even if tardiness is common. This breeds defensiveness. It's untrue and they can (rightfully) accuse you of lying. 

Exaggerated accusations breeds exaggerated responses. "You're always complaining about me" they'll fire backAt this point, no one is telling the truth and nothing gets resolved.

Start and end with the truth, be specific with your statement. "You were 10 minutes late for this meeting and yesterday's meeting". 

Point to the exact problem. Create focus and keep things clear. Simple, honest conversation. Less dramatic, more productive. 


Comments

Popular posts from this blog

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark.  Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

Starting Really Really Small

On your desk is one of the most intimidating sights known to man. A blank page. The prospect of filling it up with anything resembling decent seems insurmountable. Staring at the long road ahead fills you with anxiety and dread.  The first step is the most difficult. So we procrastinate. We " research ", we " prep ", we " plan ". We do everything except tackling the problem. We avoid the pain for as long as we can.  To make a blank page less intimidating. Tear it in half. There, half as scary, twice as easy. Still too much? Do it again. And again. Keep doing it until the task is so small that it's too easy not to do.  Getting starting is the hardest part. So make the hardest part as easy as possible. This doesn't guarantee amazing results, but it gets you in the game. You can't win if you don't play.  

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown .  Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks.  Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...