AM I NEXT? NO LOVE AT SPLUNK

San Francisco, California-based Splunk, a producer of software for searching, monitoring, and analyzing machine-generated data via a Web-style interface, has announced a reduction in company headcount and outside consultants.

The cuts will impact approximately 325 employees.

Chief Executive Gary Steele noted,

"As we begin FY24, I’m writing to share an important update on how we are positioning Splunk for future success. Today, we are making the difficult decision to reduce our global workforce by approximately 4%, mostly in North America. This decision is another step in a broader set of proactive organizational and strategic changes that include optimizing our processes, cost structure, and how we operate globally to ensure Splunk continues to balance growth with profitability through these uncertain times and drive success over the long term."

"The early proactive steps we’ve taken over the past several months have minimized the scale of the changes we are making now. Unfortunately, today’s decision impacts about 325 Splunkers across the company."

"Decisions of this nature have a significant human impact, and I don’t take that lightly. Since I joined the company, I’ve often heard the phrase “once a Splunker always a Splunker.” That statement couldn’t be more true than it is today. The people leaving the company are our fellow Splunkers, our friends, and have helped drive our success. I want to express my gratitude for the important contributions they’ve made to Splunk and to our customers."

"Additionally, as you’ve heard me describe before, one of our cost-reduction efforts has been to decrease Splunk’s reliance on external resources, such as agencies or consultants, to get work done. While utilizing these providers was prudent during Splunk’s early years, moving forward we will be more judicious about what work we outsource and what we will stop doing. Each organization will communicate changes that align these activities to our new cost structure."

"Being proactive and agile has always been, and will always be, part of Splunk’s DNA. I want to assure you that I remain confident in our strategy and that these decisions, difficult as they have been, are in service of building a better, stronger Splunk. No doubt you’ll have questions about today’s news. We have posted resources on Pwny Portal to help guide us through this process."

"Looking ahead, we will continue to invest in the areas that got us to where we are today – including how we engage with customers, our innovation and our talent. This will include the select recruiting of new Splunkers in FY24, consistent with our focus on accessing global talent in lower-cost areas. At the same time, we will continually assess our organizational health, where and how we work, and how we deploy our team and resources to deliver customer and shareholder value. I believe that the changes we are implementing today will help Splunk realize its potential to deliver incredible long-term value and become the best-in-class global enterprise that our customers and investors rely upon, and an amazing employer where Splunkers can thrive and grow their careers."

"Thank you for your focus, support, and collaboration as we evolve Splunk for our shared future success."

Change is coming. There will always be a tomorrow, no matter how much you may try to ignore it. There are no guarantees in life or promises for a bright future. We see good people being laid off through no fault of their own. Just because something bad hasn't happened yet, doesn't mean it won't. It can happen to anyone, anytime, anywhere. No one is guaranteed to wake up tomorrow and still have a job by evening. Are you now wondering, Am I Next?

IS THERE A MANUAL FOR DEVICES CONTAINING ARTIFICIAL INTELLIGENCE?

Am I Next? Future of Work. Artificial Intelligence.

I have both read and written a fair number of manuals for the setup, use, maintenance, and troubleshooting of electronic devices. And unfortunately, the largest percentage of calls coming into our help desk could have been answered with a cursory glance at the manual. 

What I have learned is that there is a mathematical relationship between the thickness of the manual, even though it may contain multiple languages and pages of official government-approved disclaimers, and an individual’s propensity to toss the manual aside -- ostensibly to be read later -- after first opening the box.

And, for years I used a personalized license plate to spark discussion among my colleagues about “1sr Reading Your *** Manual.” I got laughs – but little compliance. 

Such is life. 

Therefore, designers spend an inordinate amount of time idiot-proofing the graphical user interface (screen or control panel to ordinary people) to force people to follow some semblance of a sequence and to trap the majority of errors. Along with the original design comes on-screen prompts, help keys, and referrals to particular problems through the use of error codes. My favorite being the one we used on the help desk to indicate especially problematical users. One-Dee-Ten-Tee. Or as it was coded into the system, 1D10T. 

But no amount of skill can overcome a user’s propensity to skip the manual and plunge ahead. Unless they are forced to read the manual, tested on the knowledge contained in the manual, and compelled to demonstrate some level of competence with the device. And yet, months later, the manual is nowhere to be found or buried in a dusty JIC (Just In Case) file for some future need. Another observation: the manual travels farther and farther from the device as time marches on. Unless you are smart enough to build a manual holder unobtrusively into the case design of the device. Unfortunately, most electronic devices are smaller than the manual – so no joy to be found there.

Which begs the question: how do you write a manual for devices containing artificial intelligence with self-learning capabilities? Or do you just record (or backup) the device’s state at every use? I would hate to think that years of learning and better decision-making would be lost every time you needed to replace the device or repair its memory. Think about it: genius solutions and performance in the morning and relative stupidity after the repair man leaves

So what’s the point of this blog post? Perhaps it is a plea for you to read your manuals. But, it most likely is an illustration that knowledgeable individuals who can read manuals, solve problems, and deal with cranky people will always have some position in the job market – because, as the night follows the day, most executives do not want to assume the hassle of actually speaking with customers and users after the sale.