The new product anxiety cycle

Am I the only one who has this? Let me know.

Phase 1: Discovery of New Product

Suddenly everybody talks about New Product. It’s said it changes everything. Articles about New Product appear on Hacker News for weeks. Then colleagues on LinkedIn even mention New Product (Warning! People you know, know New Product!). (Or they’re just linking to articles about New Product, so they look cool. Either way: they must know New Product!)

Phase 2: Anxiety

Oh man, everybody already knows New Product: Spotify, Local Retailer and even that fitness app you use. Mental images of everybody working happily with New Product – for at least a year! Some of your colleagues confirm: you are now much less cool, because you don’t know New Product. Definitely!

You ignore some stories about people who think New Product isn’t the solution. They’re probably losers that don’t adapt these new technologies and got left behind ages ago.

New thought: “I’m left behind. I have to do something”. Short, shallow breaths. “But first let’s catch up with my mail..”


Phase 3: Failed attempts to understand New Product

Okay, okay, let’s calm down. There is still time. There must be some information on this. Let’s go to the product’s website. “New Product is an enterprise solution for scalable streaming .. “. Ohhh, buzzwords. I don’t get any of this!


Phase 4: Despair

I’m a goner, aren’t I? That’s it. It’s the way of the dinosaurs for me. Well, maybe I can still keep a job somewhere, working with my outdated technology experience. That happens, right?


Phase 5: Youtube

Wait. What if there’s someone who explains New Product to me… in a Youtube video of about 10 minutes? (A conference like Dataworks Summit might also help. Just saying.)

Yes!! Yes, there is!

Sudden grasp of what New Product is. Thank you, video from Indian guy from 2015.


Phase 6: Is that all?

You thought New Product was an entirely new paradigm, but it’s just a new way to <containerize applications | manage data streams | basically a specialized file system>. You can’t imagine anymore that there ever was a time you didn’t grasp this. It’s so easy now. Of course you want to <containerize applications | manage data streams | use this new file system> this way. It’s just common sense.

By the way, other colleagues who don’t get New Product are totally uncool. Definitely!


Phase 7: Actual experience with New Product

<Your company / That site you work at> finally adopts New Product. Two years after.

This New Product is great, but nobody told me about this particular annoying bug. Plus it doesn’t do <security measure> and that won’t fly in my organization. Internal customers complain New Product doesn’t do Y.

Actual work.

Contact with support.

Bug reports.


Phase 1: A New New Product Appears

Where did New New Product come from? It totally came from left field, but Hacker News is allll over it.

About Marcel-Jan Krijgsman

Data engineer at DIKW Intelligence | Python fan | Security concerned | Stage actor | Solar system knowitall | Spaceflight enthusiast | Cycling fanatic
This entry was posted in Uncategorized and tagged , , . Bookmark the permalink.

1 Response to The new product anxiety cycle

  1. Sree says:

    me too…In fact lot of us!! nailed it Marcel.

Leave a Reply to Sree Cancel reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.