Fudge Sunday - Once in a Pipeline

#56・
1.24K

subscribers

64

issues

Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that Start the week more informed 🤔💡🤯🤓 will receive your email address.

Start the week more informed 🤔💡🤯🤓
This week we take a look at FinOps via Fuller, Franklin, Talking Heads, and Cunningham.

Talking Heads - Once in a Lifetime
Talking Heads - Once in a Lifetime
Getting Informed
~300 years earlier in our jargon filled shift-left world, Thomas Fuller and Benjamin Franklin offered the proverbial phrases about one timely stitch and one ounce of prevention. Indeed, we know we must approach challenges with financial operational excellence perspective to avoid more expensive stitches and to avoid an expensive pound of cure.
~42 years ago, Talking Heads released their album Remain in Light which was produced by Brian Eno. One track, “Once in a Lifetime”, gained notoriety due in large part to a new and innovative approach that creatively combined video and music to create a brand new genre (now commonly known as a music video) that aired on the newly formed cable entertainment channel Music Television (MTV).
~30 years ago, Ward Cunningham coined the term “Technical Debt”. In effect, Cunningham captured the essence of deleterious deferral of diligence, decisions, and debugging by developers in dollars.
~10 years ago, the focus on value management in IT by companies was often referred to as Technology Business Management aka TBM. Today, combined with modern cloud economics, the discipline of TBM has a wider audience of increasingly DevOps and DevSecOps culture oriented communities embracing FinOps.
To understand FinOps, let’s explore how the lyrics and music video innovation of Talking Heads can unify what Cunningham saw in micro with what Franklin and Fuller saw in macro. So, we begin by looking lyrically at FinOps in general.
🎶 Once in a pipeline, revenue flowing underground 🎶
"Well, how did I get here?"
FinOps is a direct response to the broadly exuberant embrace of whim based on-demand cloud technology stacks, ungoverned adoption rates, and morning after regret when that unexpectedly higher party bill arrives. In fact, one 2021 survey canvased 800+ attendees of the $30B party.
So, understanding why FinOps exists might be as simple as realizing complexity grows until it collapses in our pursuit to simplify and control costs. As such, focusing on value early and often instead of costs after the fact is an evolved (shift-left) posture that embraces Gall’s Law.
"How do I work this?"
Again, getting started with FinOps might begin with a big bill surprise followed by a sudden interest in FinOps. Or, to borrow the iconic commercial phrases…
For example, consider policies as a progression towards value realization.
Showback = Crawl
  • Show what was consumed
  • Show who consumed what
Chargeback = Walk
  • Show who consumed what
  • Draw against the appropriate budget
Shameback = Run
  • Show who consumed what
  • Draw against the appropriate budget
  • Report on value return (revenue) per investment (consumption costs)
"Am I right, am I wrong?"
Applying FinOps is, in practice, a combination of people, processes, and tools. Holistically, the progression of policy above is only possible if you plan to take initiative (sit) and operationalize (fly).
Telemetry = Sit
  • Gather all cost sources
  • Gather all mapping of cost sources to organizational groupings
Showback = Crawl
Chargeback = Walk
Shameback = Run
Automation = Fly
In other words, progress will come from iterations upon innovative combinations and convergence of cultural disciplines that value an operator mindset. The cultural disciplines will be DevOps, DevSecOps, GitOps, DevCommsOps, FinOps, DataOps, MLOps, ModelOps, AIOps, RevOps, and the future .NextOps to-be-named operational culture mindsets that push service provider ethos deeper into even the largest enterprise matrix organizational chart.
Recommended Read and Repo
Newsletter section experiment: One thought provoking read and repository
Good = FinOps and Great = RevOps
Good = Reported and Great = Estimated
Work Plug!
As a reminder, I work at Faction. What’s Faction you ask?🤔🤔🤔🤔
Faction provides clientele with cloud data services across hyperscale providers to maximize innovation and multicloud outcomes.🤓☁️📊🚀
We’re hiring at Faction!🎉🤓☁️🚀
To see our current openings click here.⬅️🤓☁️🚀
Or, bookmark unicornjockey.com 🦄🤓☁️🚀
Disclosure
I am linking to my disclosure.
Did you enjoy this issue? Yes No
Jay Cuthrell
Jay Cuthrell @JayCuthrell

Sometimes a song, always a topic (or two), a read, and a repo -- every Sunday!

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.
1903 Live Oak St #92 Beaufort, NC 28516-0092