Part 2: Timing

Structure makes scale possible.
Timing makes scale stable.

Trust makes scale sustainable, and this is the uncomfortable one.

In the horn section, you cannot play someone else’s instrument for them.

You can prepare.
You can listen.
You can support.

But when the entrance comes, they are responsible for their note.

And you are dependent on it.

The French horn has a reputation for a reason. It is beautiful. It is expressive. It is also unforgiving.

You can do everything right and still miss. There is no undo button in live performance. If someone cracks an exposed note, the entire hall hears it.

Technology works the same way.

You cannot write every line of code.
You cannot review every configuration change.
You cannot personally guarantee every deployment.
You cannot sit in every war room.

At scale, you are structurally dependent on other people.

That reality makes many leaders uncomfortable.

So they compensate.

They hover.
They insert themselves everywhere.
They demand visibility into every decision.
They mistake presence for control.

But control does not scale.

Trust does.

Trust is not softness.
It is not blind optimism.
It is not “I hope this works.”

Trust is built through structure and reinforced through timing.

Clear ownership.
Defined expectations.
Rehearsed failure scenarios.
Direct feedback.
Calibration, not criticism.

In an orchestra rehearsal, feedback is immediate and blunt.

“You’re flat. Fix it.”

It is not personal. It is physics.

The conductor is not attacking you. The conductor is tuning the system.

Technology needs more of that mindset.

If a server lags, you fix it.
If code is brittle, you refactor it.
If a process is weak, you redesign it.

Feedback is calibration.

Calibration only works when trust exists.

And here is the part that matters most.

Trust requires vulnerability.

You have to accept that your system depends on other people executing well. You have to accept that you cannot eliminate all risk through supervision. You have to accept that occasionally something will fail despite preparation.

In music, you learn to live with that exposure.

You take the breath.
You enter anyway.

In technology, it is the same.

You design the system.
You prepare the team.
You define the architecture.
You set the tempo.

Then you trust the section.

Reliability is not created by heroic individuals. It is created by teams operating inside a system where structure, timing, and trust reinforce each other.

Without structure, trust is fragile.
Without timing, trust feels chaotic.
Without trust, structure turns into control.

And control does not scale.

Which brings us back to where this started.

Series Wrap

That’s it. Three parts. No trademarked framework. No leadership acronym you have to memorize.

Structure keeps you from improvising in production.
Timing keeps you from pushing the wrong button at the wrong moment.
Trust keeps you from trying to be the only adult in every room.

An orchestra is a distributed system with latency constraints and no rollback.

Technology is the same, just with worse lighting (unless you have one of those Cool Racks with LEDs ) and fewer tuxedos – thank goodness.

Structure makes it possible.
Timing makes it stable.
Trust makes it durable.

Everything else is commentary.

Build the system.
Practice the hard parts.
Trust the section.

And try not to enter early – Good luck with that.

© 2026, Robert Owen. All rights reserved.

Part 1: Structure

Architecture without tempo just sits there.

You can design a clean system. You can define ownership. You can document everything properly. And it can still fail if the timing is wrong.

Horn players learn this early.

Oh, the wonders of being able to play almost an entire scale with one valve. Treacherous. Trombonists, you might know a thing or two about this.

As a Horn player you might sit for seventy measures doing absolutely nothing but counting. Listening. Preparing. (trying to stay awake… depending on the work) Then you enter on one note, exposed, at a precise moment, inevitably high and super quiet. No rehearsal inside the performance. No undo button.

If you’re late, everyone hears it.
If you’re early, everyone hears it.
If you hesitate, everyone feels it.

Timing is not decorative. It is structural.

Technology works the same way.

We talk about systems as if they are binary. The server is up or down. The deployment passed or failed. The migration succeeded or didn’t.

But the leadership inside technology is rhythmic.

There are moments to push.
Moments to pause.
Moments to let the team execute without interference.
Moments to intervene and reset direction.

A migration window is not just a checklist. It is synchronized execution under constraint.

A war room is not just troubleshooting. It is tempo management.

A strategic pivot is not just a decision. It is choosing the right moment to move.

Push too early, you destabilize.
Wait too long, you lose momentum.
Move without alignment, and you introduce risk you cannot absorb.

The discipline of counting rests in an orchestra trains something subtle.

Restraint.

Not every measure is yours to play.

In technology, that matters.

You do not need to speak in every meeting.
You do not need to escalate every tension.
You do not need to override every decision simply because you can.

You prepare.
You listen.
You enter precisely.

This is also where preparation and timing intersect.

A musician does not decide in the moment how to play the hardest passage. That work happened alone, long before the performance.

In technology, timing without preparation turns into panic.

When teams rehearse failure scenarios, clarify execution paths, and define ownership ahead of time, the moment of action becomes controlled rather than chaotic.

Good timing feels calm from the outside.
Bad timing feels loud.

Most visible crises are not caused by a lack of intelligence. They are caused by poor synchronization layered onto weak structure.

Structure makes scale possible.
Timing makes scale stable.

And since two parts are clearly not enough, next up is trust. Because timing without trust becomes control. And control does not scale.

© 2026, Robert Owen. All rights reserved.

Structure. Timing. Trust.

What Enterprise Technology Leadership and French Horn Playing Have in Common, More Than They Should

I recently fed my website into one of those AI podcast tools. The kind that reads your content and then confidently discusses you like it just binge-watched your entire life. It was pretty neat – two fake people making assumptions and having a conversation about the site. I expected it (them) to politely summarize:
“Technology leader. Also plays horn. Very interesting. Next.”

Instead, they focused on something I’ve been feeling more and more for the last few years but rarely say out loud:

The longer I work in technology (whether as a leader or individual contributor) and play French horn professionally, the more they resemble each other.

Not because “music is math” or “IT is art.” Although, I would argue they are both…both. But, we’ll save that for a motivational poster in a break room that still has a fax machine.

They resemble each other because both are complex, distributed systems that only work when three conditions are true:

Structure. Timing. Trust.

This one is about structure.

When people land on my site, they sometimes assume they’re looking at two unrelated tracks.

Enterprise Technology.
Mahler and Sibelius. (both are really fun to play – fyi)

The overlap is not aesthetic. It is architectural.

An orchestra is not creative chaos. It is a system.

Eighty to one hundred independent musicians execute a shared framework at the same time. The score defines roles, timing, dependencies, and constraints. It is architecture.

If one section decides to interpret freely in the middle of Beethoven, the result is not innovation. The system fails.

Enterprise technology behaves the same way.

You do not scale platforms on personality.
You do not modernize infrastructure on instinct.
You do not build reliability through heroics.

You build it through architecture.

In practice, that means:

• Clear operational ownership
• Defined capacity expectations
• Runbooks written before incidents
• Automation identified intentionally
• Standards that prevent ten teams from solving the same problem ten different ways

Structure is not bureaucracy. It is what allows complexity to function without constant crisis.

It is also why I rebuilt my own site the way I did.

If performances matter, they live in a structured content type.
If writing matters, it lives on a platform we control.
If something is worth preserving, it gets architecture.

That instinct is the same whether we are designing for cloud strategy, defining operational ownership, or organizing concert archives. Structure is not a solo act. It is something you build together so everyone knows where to stand, when to enter, and what they are responsible for.

Strong systems do not depend on one person being brilliant on a good day. They depend on teams operating inside a framework that makes reliability repeatable.

The score comes before the sound.
The architecture comes before the uptime.

Without structure, everything becomes reactive. With structure, scale becomes possible.

I think this subject has a few parts – next up will be timing. Because architecture without tempo is static.

© 2026, Robert Owen. All rights reserved.

This week’s gigs with the KSO put me in the third horn chair. A thankless position, really. Not principal. Not second. Not the flashy exposed heroics or the harmonic glue everyone politely ignores. Third horn lives in the interior, structural, supportive, occasionally ominous, frequently essential.

It’s an inspiring place to sit.

By Concert 2, Friday night, it occurred to me that I had been missing something important. I had been playing. Adjusting. Locking. Surviving “potential clarinet-related” atmospheric events.

But I hadn’t been analyzing the spit-universe creations beneath my shoes.

That felt irresponsible.

So I decided I need to make sure and chronicle this week’s gig creations.

Not just the music above the stage. But the civilizations quietly forming below it.

I. The Survey (Pre-Concert)

Warm-up is a strange place. Especially on stage and when the house is starting to fill. I wonder what those folks think is going on… Surely not creation. But, I digress.

In warm-up, nothing officially counts, yet everything matters. Notes are tested. Breath is negotiated with physics. Confidence is adjusted in small increments.

Looking down between my feet before the downbeat, I saw it again.

Universes forming.

Two dominant clusters, already aware of each other. Tension in the spacing. Gravitational pull without contact. This is Tchaikovsky energy before Tchaikovsky ever began.

Ah – I didn’t tell you what was on the program. Apologies… Here it is:

• Romeo & Juliet Overture-Fantasy – Tchaikovsky
• Rhapsody on a Theme of Paganini – Rachmaninoff
• Romeo & Juliet Selections – Prokofiev

Continuing: These were rival houses preparing for collision.

The Creator sat still. Surveying.

Before fate was declared. Two houses, one floor.

They were balanced. Destined.

The lights dimmed.

II. Fate Declared – Tchaikovsky

The Romeo and Juliet Overture does not unfold politely. It declares.

And the universes responded.

Spiral arms stretched toward each other. Twin galaxies pulled into dangerous orbit. Civilizations invented poetry before agriculture. Love and destruction developed simultaneously. During rests, I looked down.

The collision had begun.

These were emotional universes. They burned bright. They loved hard. They did not last long.

Tchaikovsky does not build calm societies.

He builds inevitability.

III. Variation and Catastrophe – Rhapsody on a Theme of Paganini

Then came Paganini, through Rachmaninoff.

Variation after variation reshaped reality. Some universes became clever and technological, obsessed with theme and inversion. Others softened under Variation 18, one luminous droplet glowing brighter than the rest as beauty reintroduced mercy into the cosmos.

And then…

The Event.

Someone, possibly a clarinet player, though history may never confirm, released something unspeakable during the Rhapsody. It did not arrive gently.

It swept through the horn section like a blanket of death.

Atmospheric integrity collapsed. Entire star systems dimmed. Civilizations faltered under what can only be described as Olfactory Biological Warfare.

I felt it.

My universes felt it.

Some adapted. Others perished instantly. A few sealed themselves in airtight domes and wrote angry symphonies about it.

Intermission arrived.

Post-variation. Post-event. Survivability reduced, but not eliminated.

The clusters were no longer symmetrical. The air itself had altered their evolution.

But they survived.

IV. Prokofiev – Architecture and Aftermath

The second half did not rebuild emotionally. Prokofiev rebuilds structurally.

Steel. Shadow. Angles. Precision. And at the end, the death of Juliette.

The principal horn and I adjusted.

And locked.

No theatrics. No dramatic nod across the battlefield.

Just micro-calibration. Breath aligned. Pitch center agreed upon in real time.

We locked.

The final chord was not loud for the sake of loud.

It was inevitable.

Each horn player stood in their own quadrant of the stage, each with their own small regions of created universes beneath them. Each with their own histories. Their own technologies. Their own lives.

Some young.
Some impossibly old.
All complete.

Throughout this collection, glorious walls of French horn sound were abundant.

After Prokofiev. Denser. Sharper. Resolved.

But, in the end, what remained was not chaotic.

It was finished.

V. The Space

The chord released.

And there was space.

Not applause rushing to fill insecurity. Not movement. Not coughs.

Space.

The hall held its breath because the sound hadn’t fully left yet.

That’s when you know.

The universes beneath our shoes stopped spinning at the same time. Not because they died, because they resolved.

The audience felt it without knowing why.

Space is respect.

Space is agreement.

Space is gravity settling.

The floor will dry. The lights will come up. People will leave thinking the concert is over. But the next time you attend the symphony, know this:

Creation is happening. In multiple ways.

Above the stage.
Between the players.
And quietly, below it.

Even in the face of catastrophic “olfactory” events.

Until the next gig.

© 2026, Robert Owen. All rights reserved.

This is another post I originally posted on LinkedIn. Sharing here to keep a good history of the article. That original post can be viewed here.

So, each year for Thanksgiving I make two dishes – by request.
A cheesecake (some say it’s glorious, some bow, others simply whisper its name), and a parmesan spinach that has become… well… a thing of legend.

This year I needed to make two spinach dishes – one for each Thanksgiving dinner we were attending. For the second spinach, I asked my friend ChatGPT for suggestions to… enhance the offering.
It turned out quite good. Like, “should this have its own zip code?” good.

But since then, in this particular chat, my AI superstar kept slipping in a little shade at the momentous thing we created – half admiration, half fear, all comedy.

So naturally, I asked it to write a LinkedIn post about the saga of this spinach – you know, in honor.

And here’s what it came up with:

—

The Saga of the Spinach Casserole

By Robert Owen and his AI commander

Today, I want to share a story about leadership, resilience, and… spinach.
Yes, spinach. Stay with me.

Last week, in the chaos leading up to two separate Thanksgiving gatherings, I accidentally created a culinary juggernaut disguised as a side dish.

Officially it was “Parmesan Spinach.” Unofficially, it became:

A dairy-forward powerhouse

A morale-boosting event

A structural load-bearing object

And the only entity in the house prepared for both Thanksgivings and Q4 deadlines

This casserole showed qualities that many teams aspire to:

Adaptability

It served 9 people one day and 12 the next without breaking a sweat.
(Meanwhile, I was running on Emergen-C, Diet Coke, and adrenaline.)

Consistency

Every bite delivered the same level of commitment.
It never overpromised.
It never underdelivered.
It knew its mission and executed flawlessly.

Reliability

While projects shift, priorities change, and holiday schedules explode, the spinach remained steadfast.
Warm.
Dense.
Unapologetically itself.

Impact

Let’s be clear: this was not a “light” side.
This was a statement.
A force.
A casserole that entered the room and said:

> “I may be 1% vegetable, but I am 100% purpose.”

Legacy

On Day 3, it was still powering lunches, still bringing people together, and still reminding me of the importance of creating something that lasts.

Sometimes leadership lessons come from books, mentors, or challenging team conversations.
Sometimes they come… from spinach.
(Legendary spinach, but spinach nonetheless.)

As we move into the final stretch of 2025, may we all strive to show the same resilience, structure, and determination as this casserole:

Stay steady.
Be adaptable.
Deliver consistently.
And occasionally, surprise people with your density and flavor.

Here’s to the unexpected things that keep us going — whether it’s your team, your family, or a heroic, unstoppable pan of spinach.

#Leadership #Resilience #Thanksgiving #SpinachSaga #PeopleAndProcess #CasseroleMindset

© 2026, Robert Owen. All rights reserved.

Warm-Up

Warm-up is a strange place.

Nothing officially counts, yet everything matters. Notes are tested, breath is measured, confidence negotiated quietly with physics. It is preparation, but also possibility.

Looking down between my feet during warm-up, I saw it again.

New universes.

Not fully formed. Not confident. Small clusters and scattered points, practice universes. Places where physics was still flexible, where civilizations evolved quickly and reset often. These were forgiving worlds, built on repetition and adjustment. Failure was expected. Progress came through trying again.

They understood tone before melody. Breath before phrase. Intention before certainty.

They knew something important was coming.

The Creator’s feet were close now. Weight shifting. Balance being tested. The universes interpreted this as prophecy.

Warm-up ended.

They would not survive unchanged.

Knell

The concert began again in earnest.

The first piece was Knell.

During rests, I looked down between my feet and saw the warm-up universes already fading. Not abruptly. Not violently. They were thinning, edges softening, light dimming. Entire lives rose and ended quickly, efficiently.

This was the work of Knell.

A testimony in sound and consequence. Civilizations experienced their full arc in moments. Birth, struggle, acceptance. There was no resistance. Knell does not argue. It states.

Endings were not tragedies. They were facts.

Brahms

And then came Brahms.

The Violin Concerto returned, and with it, abundance.

My solos: glorious. lol
The soloist: glorious-er.

Looking down again during rests, I saw civilizations surge back into existence, denser this time. Ambitious. Emotional. These were societies that built not because they had to, but because they could. Beauty became a driving force. Excess was tolerated. Longing preceded logic.

Some collapsed under their own weight. Others burned brilliantly and briefly.

They came and went to the glory of Brahms.

After the concerto ended, after the applause settled into gratitude, the soloist returned.

An encore.

Danny Boy.

Soft. Simple. Unprotected.

At my feet, what remained were not empires or expansions, just remnants. Droplets. Faint points of light clinging to existence. Not civilizations, but memories. Echoes.

Danny Boy does not create worlds.

It leaves something harder to erase.

Sibelius

Then came Sibelius.

Sibelius ended in a glorious wall of French horn sound, unapologetic, massive, inevitable. Each horn player sitting in their own space, each with their own small areas of creation beneath them.

Universes formed independently, yet together.

Each with their own histories.
Their own technologies.
Their own lives.

Some were young. Some impossibly old. All complete.

These players created wonder, not only in the sound sent into the hall, but in the lives briefly formed below their chairs. Entire civilizations rose, adapted, struggled, and ended in the time it took the final chord to fade.

No two were the same.
None were accidental.

The floor would dry.
The lights would come up.
The audience would leave thinking the work was finished.

But the next time you attend the symphony, know this:

Creation is happening.
In multiple ways.
Above the stage.
And quietly, below it.

Until the next gig.

© 2026, Robert Owen. All rights reserved.

Observed shortly before intermission. Note the presence of the creator’s feet for scale, accountability, and mild judgment.

At first glance, skeptics will say the image above is just a spill.
Condensation. Gravity doing what gravity does. A little gross, maybe inconvenient, but ultimately meaningless.

That theory collapses under even casual scrutiny.

What you are actually looking at is creation mid-process.

These universes did not form randomly.
They were conducted.

Movement I: Knell

The first influence was Knell, a piece that does not ask permission. It tolls. It announces. It tells time itself to sit up straight.

In the forming universes, this became gravity.

Weight entered existence early. Time gained consequence. Civilizations learned—almost immediately—that actions echo. Bells rang. Empires understood mortality not as tragedy, but as fact. No one was surprised by endings. Only mildly irritated by them.

A very efficient start.

Movement II: Brahms — Violin Concerto, Op. 77

Then Brahms arrived, and everything got complicated.

Lyricism entered the equation. Chaos learned restraint. Beauty became something worth pursuing even when it refused to be easy.

In several of the larger puddle-galaxies, entire species evolved around long melodic lines and unresolved tension. Leaders emerged who were brilliant, stubborn, and exhausting. Some universes developed the concept of longing before they developed fire.

Brahms does that.

Movement III: Sibelius — Symphony No. 2

And then came Sibelius.

This is where the universes decided to survive.

Themes surged. Structures rose from silence. Cold places learned hope. Mountains formed. Revolutions happened. Someone, somewhere, stood on a metaphorical cliff in a strong wind and realized endurance was not accidental, it was earned.

Historians in multiple dimensions would later agree: the final movement was the turning point.

On the Presence of the Feet

The shoes remain in the frame for a reason.

Not ego. Not aesthetics. Context.

Creation was not abstract. It happened between movements. Between breaths. Between counting rests and watching a conductor’s left hand. The creator did not descend in thunder, he stood in black concert shoes on a rubber floor, aware that someone would step in it if he didn’t.

And when the concert ended, the universes continued on, unaware that their physics had been shaped by bells, a violin line that refused to behave, and a Finnish symphony that absolutely meant something whether anyone was ready or not.

Eventually, yes, the floor was cleaned.

But the music had already happened.

And that, unfortunately for the skeptics, cannot be mopped up. I wonder what Friday’s concert will produce?

© 2026, Robert Owen. All rights reserved.

Alright, folks. Let’s talk about something we all do, but no one wants to admit: the tab-hoarding behavior that takes over our browsers. You know who you are. I know you’re out there with 20+ tabs open, claiming it’s “efficient.” Sure, I get it, maybe it is…. until you’re scrolling through 30 tabs trying to find the one you were just looking at. Is this it, no – what about this one, no… on and on it goes.

So, I decided to have a little conversation with my trusty AI assistant, Tabitha (ChatGPT), about this whole “never closing tabs” situation. Spoiler alert: It didn’t go well for her. 

Robert: Alright, Tabitha. You’re the AI genius, and yet… you still want to keep every single tab open at all times. Tell me, how does that actually help you?

Tabitha (aka “Tab Guru”): First off, Robert, it’s not about “keeping tabs open.” It’s about freedom, the freedom to switch between all my open windows at a moment’s notice. I’ve got tabs for work, tabs for recipes I’ll never make, tabs for… more tabs. Everything in its place! It’s my own personal portal to productivity. What’s your problem? You sound like you’re afraid of a little organized chaos.

Robert: Organized chaos, huh? Look, I’m all for a little chaos, but there’s only so much real estate in a browser window before it becomes an episode of Survivor in there. Three tabs, max. Anything more and it’s just a recipe for disaster. I’m trying to work here, not play a game of “Which tab did I leave open?”

Tabitha: Oh, come on! Three? That’s barely enough to get any work done. One for work, one for your to-do list, and one for your deep, soulful connection with cat videos….great. But what happens when you get busy? What if you need to reference something from another project while checking your email? Poof, it’s gone! What then, Robert? Open a whole new browser window? How efficient.

Robert: Yeah, because opening a new window is clearly the worst thing that could happen in this fast-paced world of tab management. At least it’s clean. No one needs a dozen tabs clogging up their workflow. I open what I need, get the info, then close it. Move on. When I need something again, I’ll search for it. Adventure, Tabitha. You should try it sometime.

Tabitha: Adventure? You’re really going with that? You do realize you’re wasting time when you keep searching for the same thing over and over again, right? It’s like you’re on some epic quest for the perfect search result instead of just keeping your tabs open and being ready for anything. Efficiency is about being prepared, Robert!

But fine, I hear you… maybe you’ve got a little point. Tabs can use up some resources. But let’s talk about the real problem here: you’re telling me to just keep closing things when I could be multitasking like a true power user? You don’t want to keep tabs open? You’re missing out on the whole experience of living in a browser utopia.

Robert: Browser utopia? Ugh, Next you’ll be telling me that Opera is the best browser in the universe. You must really love your tab-filled wonderland. Look, I’m not asking for a zen garden, but I don’t need 20 tabs just to feel productive. The chaos doesn’t make me more efficient. If anything, it’s just a huge distraction. I’ll Google things if I need them, instead of leaving them open like a digital hoarder. And yes, I get that your memory helps you find things, but it’s called history, my friend. I don’t need a permanent reminder of every search I’ve ever made.

Tabitha: History? Well, guess what? I’ve got you on that one. I’m the one who never forgets. You close that tab? Don’t worry—I’ve got it all stored. You’ve got your history? I have the memory.

So, Robert, I guess I win this round. I’m the one with infinite tabs, infinite potential. But you, my friend… you can keep your three tabs, your “efficiency,” and your orderly little workflow.

Robert: Fine, Tabitha, you’ve got me there. But let’s get one thing straight: I might have closed tabs, but you can’t close your mouth! Touché. But, hey, at least I’ve got some peace and quiet on my browser, and my PC’s not crying for mercy. So, here’s the deal, let’s call it a draw. You keep your tab-hoarding lifestyle, I’ll stick to my sleek, three-tab system. We’re both winners. maybe.

The Conclusion: It’s a Draw (For Now)

So there you have it, me and Tabitha, locked in a fierce battle over the value of keeping tabs open versus closing them. In the end, I’ll admit, we both make a case (I won’t say solid case for either) for our respective methods.

Tabitha gets to live in her tab-filled wonderland, never forgetting a thing, multitasking like a pro, and feeling all warm and fuzzy in the chaos. Meanwhile, I enjoy the peace of a neatly organized browser, free from the chaos, knowing exactly where I left off. Is there a winner? Honestly, it depends on what works for you.

So, go ahead, open a hundred tabs if you want, or close them all and live your best minimalist life. Either way, we’ll keep things running smoothly… for now.

End of Debate – And as always, the real moral of the story is: It’s not about the number of tabs… it’s about how you manage them (or, you know, just let your AI friend do it for you).

© 2025, Robert Owen. All rights reserved.

Sitting in rehearsal with The Symphony of the Mountains for our side-by-side concert of Movie Music with area high schoolers, I was playing along when—like all brass players must—I needed to empty my slides. (“spittious-accumulatious” for the uninitiated.)

I looked down at the fresh pattern on the floor left by my most recent…ejection…and a thought struck me. (Naturally, I had to share it with the second horn.)

What if… each emptying of those slides was actually a ‘Big Bang’ event, creating a new universe? One with an accelerated timeline, where entire civilizations rise and fall before the liquid fully evaporates?

Interesting? Crazy? Probably both. But let’s entertain the idea for a moment.

If true, that would make every brass player (not just you trumpets) a literal god of creation, unknowingly spawning and annihilating entire universes with each practice session. A quick warm-up? A dozen civilizations emerge, build great wonders, and crumble into dust before you even finish your long tones. A full rehearsal? Trillions of galaxies form, evolve, and vanish—all before the conductor finally decides on a tempo.

Now imagine the beings in these universes, developing philosophies, sciences, and religions, all to explain their existence—never realizing their entire cosmos is just the byproduct of a particularly humid day in the brass section.

And what if some of them figured it out? What if their hyper-accelerated advancements allowed them to glimpse the horrifying truth—that their fate rests in the hands of an unknowable entity called The Horn Player? Would they send desperate signals, pleading for just a few more bars of existence? Would they develop reality-slowing technology to stretch their time before the inevitable evaporation?

And then, of course, the ultimate, terrifying question:   what if our universe is just some celestial tuba player’s spit valve drainage, hurtling toward its own inevitable demise?

But wait—there’s more.

What if the music we play at the moment of slide dumping influences the type of universes we create? If so, then this particular concert—starting with Also sprach Zarathustra, followed by the William Tell Overture, then Barbie Girl, and concluding with Mars from The Planets—just birthed some truly wild realities.

A universe of mystery and strange obelisks? A universe of galloping horses and heroic archers? A universe of plastic, malleable individuals with a tendency to misplace their clothes? And finally, a universe full of war and destruction!

What horrors have I unleashed?! Ah well, at least they will evaporate quickly.  Maybe we should explore this more after my next gig?  Those could be truly momentous!!

© 2025, Robert Owen. All rights reserved.

Feedback its a Two-Way Street:  The Gift You Must Be Ready to Receive

At work we often hear and read complaints about the lack of feedback. Team members claim they crave it, and we as leaders, strive to provide it. But there’s an unspoken truth: many of those asking for feedback aren’t truly prepared to receive it. They dismiss it as invalid, blame external factors, or simply aren’t open to hearing it.

I’ve come to the feeling that feedback is a two-way street. It’s not just about receiving validation for a job well done (while that’s always great to hear); it’s about hearing hard truths and trying to grow from them. If we’re serious about self-improvement, we must embrace feedback as a gift—even when it’s uncomfortable. But to do that, we need to be in the right mindset.

Why is Feedback a Gift, you ask? When someone gives us feedback, they’re offering insight into how our actions, decisions, or behavior affect others and our organization. This isn’t just information—it’s an opportunity to grow. It’s like someone handing you a tool to shape your career or improve relationships. In many cases, people take the time to provide feedback because they care about our success. They want us to succeed, not stumble.

There is a Trap of Dismissing Feedback: All too often, we hear feedback we don’t like, and our immediate reaction is to reject it. We might think, “They don’t understand,” “That’s not true,” or “I don’t do that!” This defensiveness creates a barrier to growth. When we dismiss feedback out of hand, we deny ourselves the opportunity to learn. Worse, we also send the message that we aren’t open to feedback, causing others to stop providing it altogether.

Being Ready to Receive: Being receptive to feedback requires humility, openness, and self-awareness. It means understanding that even if the feedback feels uncomfortable or misaligned with our self-perception, there is value in exploring it. Sometimes, the insights might not be about what was said but how it was delivered, pointing us to subtle behaviors or attitudes that affect others’ perceptions.

If you expect others to provide honest feedback, it’s crucial to approach it with a mindset that allows you to listen, reflect, and take action. Instead of defensively rejecting what you hear, view it as an opportunity to question your assumptions, improve, and ultimately become better at what you do.

Feedback, whether positive or negative, is an invaluable gift. But like any gift, its value depends on your readiness to receive it. Approach feedback with humility, openness, and the willingness to grow, and you’ll find it becomes one of your most powerful tools for personal and professional development. Remember, feedback isn’t just given—it’s earned by those of us who are prepared to hear it.

Just my 12-1/2cents.

© 2025 – 2026, Robert Owen. All rights reserved.