Skip to main content

A Tale of Tails

Every weekday morning, my family goes through the same routine:  I get up first and head downstairs for coffee; then our 4 year old wakes up and kicks my wife out of bed; at 8 am, I let the dog out back to relieve himself and get his morning meal ready while he is doing so; etc.

This morning, I observed something rather fascinating about our dog's behavior.  Due to the layout of our house and the orientation of the back deck, when I let him back in he takes off like a rocket.  Because we have hardwood floors, he can't turn at that speed and has to take a very circuitous route to get to the kitchen where his breakfast awaits.  I found this amusing because this is not an uncommon behavior in the professional world either.

Over the years, people often question what is more important:  design or execution.  I first encountered this seemingly philosophical (using that term very loosely) subject in college, where my professor in VLSI design stated unequivocally that a good design could be fatally hampered by poor execution.  My dog would seem to confirm this as well because even though his thought of going straight to the kitchen for breakfast is a good one, his inability to execute properly (i.e. slow down) forces him to take the most inefficient route to get to his food.

Balance is necessary
That's not to say that the act of focusing on goals should be relegated to the back burner completely.  Contrast the behavior of our canine pal with that of the Canadian rock band, Rush.  For over 30 years they have focused on one thing only:  making what they feel is the best music possible without regard to airtime on the radio or awards that they could possibly be given.  In spite of the fact that they have a rabid fan base, it is only now that they are finally nominated for induction into the Rock and Roll Hall of Fame.

Could they have arrived at this point sooner?  Yes, if they were willing to sacrifice the design of their band and focus instead on what the media expected (more radio friendly vocalist and songs to match).  But they didn't change their design even though it meant that they could possibly have never been nominated.

Careful planning to avoid unnecessary risk by developing contingency plans is a necessity to allow you to avoid making whimsical decisions on the fly that could eventually unravel your bigger plans.  But too much planning can yield an inability to execute due to a fear of never being ready.  The point here is that a healthy balance of design and execution is the ying and yang of business whether this applies to a product you are creating; your career; your ability to make a sale; etc.

Popular posts from this blog

Finding Clarity in the Chaos of a Job Search

Job searches are humbling. They test your confidence, your patience, and your ability to stay motivated when things don’t move as quickly as you’d like. But they also teach you things about yourself that you might not have learned any other way. For me, the past few months have been a crash course in rediscovering what really matters: not just in a résumé, but in relationships, self-perception, and how we use technology to help tell our stories. Here are three lessons that stood out. Reach Out to Your Network (Long Before You Need It) Your network is a living thing. It requires upkeep, time, and attention, just like a flower garden. You can’t ignore it for years and expect it to bloom the moment you need it. Start planting early. Stay in touch with people whose paths you’ve crossed - colleagues, mentors, partners, even those you only worked with briefly. Drop a note once in a while. Comment on their posts. Share something that made you think of them. These small gestures are the sunl...

Time to Level Up!

With the recent news out of Salesforce and Oracle, it’s easy to understand why folks affected by layoffs might feel discouraged. Not only are they leaving companies they may have called home for years, but they’re also facing the daunting prospect of job hunting while headlines scream about “AI taking over human jobs.” Not long ago, another company I follow - let’s call it Acme  - went through a similar round of layoffs. Two employees in particular (we’ll call them Jim and John) showed how mindset can make all the difference. Jim had been at Acme for over 20 years. He was reliable, steady, and well-liked, but not exactly the standout type. When he was laid off, he decided to take some time off before even thinking about his next move. After all, he had a severance package. Didn’t he deserve a break after two decades of hard work? John’s story was different. Though he hadn’t been at Acme as long, he’d built a strong reputation and had both technical and leadership skills. Instead of...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...