Less leadership, more technocracy

Getting good at leadership is always good, but make sure to mind the technocracy as well – someone’s actually gotta do the work! Also: plan for needing gadgets for your gadgets.

Topics

  1. Less leadership, more technocracy.
    • Go beyond high-level “why,” seeking out the “why of how.”:
      • >“I think some of my best conversations came through finding ways to respectfully ask those whys and trying to learn more about the process and why we were doing certain things, and really just diving into some of those uncomfortable situations,” said Liberty Mutual’s LeBlanc about her Pivotal Labs engagement. “But respectfully pushing back and sharing my perspectives, as well, ended up helping us learn so much more because we weren’t just taking it all in. We were really trying to understand the whole process.”
    • E.g., Seek out “patterns.”
    • Tanzu whitepapers, e.g., on ROBO, chargebacks, and TEI for business case modeling.
    • Haven’t read this one yet: Radically Collaborative Patterns for Software Makers.
    • And, of course: my two books on transformation!
  2. Now you have two problems
    • I don’t dislike my dog, I dislike the work and responsiblty that comes with her. I often confuse this.
    • Pets for your pets, work for your hobbies.
    • When the process becomes the product.
    • Be aware of this distinction in your thinking.

Mentioned

Chapters

00:00 – The agenda.
02:14 – Less leadership, more technocracy.
20:38 – kube.academy.
21:54 – tanzu.vmware.com/developer
23:01 – Pets for your pets.
28:34 – Geting started with your transformation strategy.
30:35 – Bye, bye!

CTA

Three things for more Tanzu

Colophon

The drunk under a lamppost app modernization anti-pattern – Tanzu Talk Daily 20201021

If you’re starting your app modernization plans with the biggest, most critical app you can find, you’re probably stumbling through the drunk under the lamppost app modernization anti-pattern. Chances are, you’ll also encounter a lot of resistance and excuses to avoid changing. Also, I discuss saying “no” more as a way to think about prioritization. Bonus topic: deep-fried bread in The Netherlands.

Chapters

00:00 – Agenda.
01:49 – The drunk under the lamppost anti-pattern.
15:09 – Start planning your app modernization journey.
18:07 – Saying “no.”
25:12 – “Too many salads.”
30:23 – Learn kubernetes, free!
32:07 – Gartner on IT strategy “turns.”
35:51 – Free developer education & bye, bye!

Topics

“With in-house development and acquisitions, FedEx would bolt on technologies resulting in an ‘accidental architecture,'”” Carter said. Through its renewal program, FedEx began to “build out the core services and microservices that represent the less complex, more flexible, faster-to-market capabilities that we have today.” From “How FedEx’s CIO led a decade of modernization.”

  1. Don’t get obsessed with the lamppost of pain: focusing on the difficult, critical things and concluding you can’t transform. Use a type of Disruption: work on lesser, cheaper things to creep up to the critical. Mobile apps, store finder, etc.
  2. Saying “no” as prioritization. All these execs saying no to things to focus on other customer and prospect engagement.
  3. Follow-up on strategy: check out Gartner’s “Winning in the Turns: A CIO Action Guide,” July, 2019. Good list of types of “turns” and advice on how to change the way you do strategy. In particular, as TD Ameritrade went over at s1p 2020, change “ROI” to “payoff.”

Mentioned

CTA

Three things for more Tanzu

Colophon

Shift right to improve corporate strategy – Tanzu Talk Daily 20201020

Corporate strategy could be improved by shifting right, moving closer to the week-to-week software cycle to get more familiar with customers and changes in the market. See more on corporate strategy in The Business Bottleneck.

Plus, I discuss bottleneck removal and thinking about policy and governance as human system, not static “laws.”

Mentioned

Chapters

0:00 – The agenda.

02:51 – kube.academy.

4:00 – Remove bottlenecks to get better at software, always.

22:06 – Amsterdam art nouveau.

24:06 – Shift right to improve corporate strategy.

35:45 – Discovery workshops.

38:07 – Policy is made by humans.

43:33 – Bye, bye!

CTA

Three things for more Tanzu

Colophon

Doing something works better than doing nothing – Tanzu Talk Daily 20201019

Summary

Doing something works better than doing nothing

When you put a new process, like agile, in place, you often realize there was very little process in the first place. Also, kubernetes at the edge, T-Mobile, and as architecture.

Mentioned:

Also

Programming notes

Chapters

00:00 – Staycation.
01:32 – Doing something works better than doing nothing
04:36 – BMC case study
09:03 – ending zombie process
11:21 – lack of management tools
13:59 – example of a management tool
15:09 – three small things on kubernetes
28:31 – Your CTA!

CTA

Three things for more Tanzu

Colophon

The right mindset for starting application modernization – Tanzu Talk 20201009

Marc Zottner talks with Coté about large scale application modernization. Also, they discuss the value of starting small and constraining yourself to short time lines. Also: what does the American-speaking French accent sound like?

Colophon

De-risking software – Tanzu Talk Daily 20201008

IT, let alone software development has a poor track record for success in large organizations. And yet: we’ll told software is not critical for enterprise survival. We’ve got to figure out how to de-risk software, then. That’s the topic today.

Topics, mentions, etc.

CTA

Three things for more Tanzu

Colophon

Enterprise Burgers – Tanzu Talk Daily 20201007

Summary

Platforms are often represented in enterprise architectures, “marchitectures,” or as I like to call them, “burgers.” Today, I walk through some past, great burgers, from CORBA, to J2EE, to Cloud Foundry, and more. In doing so, I over some advice about how to find and care for your burger, especially when it comes to keeping your burger fresh.

Planned on topics

CTA

Three things for more Tanzu

Colophon

The thrilling world of chargebacks, or, the dangers thereof – Tanzu Talk Daily 20201006

Summary

Chargebacks! People love asking about chargebacks – “recouping” costs, metering usage. How should you think about these in cloud native land? There’s plenty of unintended side effects that can harm your overall strategy and business, so make sure to put a lot of thought into how you’re doing it, if at all! That’s today’s topic.


Planned on topics

Chargeback

  • What goals do you have? This will determine what, when, and by how much you charge.
  • The idea of “recouping” cost can be crude. What if costs are high for one thing, but that brings down overall cost/raises overall value and price-premium, competative advantage.
  • I know this all naive and wishful thinking…
  • Like pretty much all of my work, it’s like flossing: we all smile and knod that we should do it, and then get on with managing the slow rot of our teeth instead of changing out mindset and behavior.
  • Onto the slow rot strategies!
  • Often, early on, you don’t charge. You want to drive adoption to deliver value (ironically). You might be doing your whole formula wrong. Should you measure per BU, per app, or per overall company revenue? See TDAmeritrade case of tracking ROI.
  • Also, consider the benefits – retire tech debt to get more agility; removing wait time/waste; being secure and compliant (how do you chargeback for “airgaped”).
  • Finding the unit to charge for.
  • Metering it.
  • These are all fun, technical details of curl’ing APIs, using fancier tools (like VMware CloudHealth and others)…
  • But you need to figure out what your goals are.

More material

  • Pivotal Cloud Foundry whitepaper:
  • “The value of PCF is much higher than passing along the cost of power, compute, storage, networking, and operational overhead. How do you put a price on the value of increasing speed to market? On optimizing the value stream? On improving application resiliency? These benefits are meaningful to the business. This value is baked into the cost of the PCF product. But until application teams—and platform operators—fully experience these benefits, it’s counterproductive to assign a value to the platform.”
  • Plenty of APIs you can curl (see also VMware CloudHeath, etc.)
  • Decide on goals – adoption, “recouping,” etc.
  • Find the unit to meter, paper recommends memory, but your unit price can vary. Networking can be a huge part of costs, but difficult to measure.
  • The unit to meter can get sliced by org/cluster, pod/namespace, node/container…but also service…etc.
  • Beware of scaring people off and killing adoption, e.g., THD, MasterCard, many others.
  • MasterCard case, 2018.
  • The Home Depot didn’t do chargebacks at first, 2015 talk. Also, see 2016 update.
  • Wikipedia, “The purpose of chargeback includes: (1)Making departments responsible in their usage, e.g., refrain from asking for resources they are not going to use; (2) Providing visibility to the head of IT and to senior management on the reasons behind the costs of IT; (3) Allowing the IT department to respond to unexpected customer demand by saying “yes, we can do it, but you will have to pay for it” instead of saying “no, we cannot do this because it’s not in the budget.”
  • Listen, I know all of this is “that’s fine for a FANG,” but a least aspire to not be lame and work towards this kind of thinking.
  • Rohit, 2017: “First and foremost remember PCF is a PRODUCT and when you’re launching a new product whether it’s ice cream cones or a PaaS, if you don’t price it right based upon the market conditions, then no customers will come and you’ll be left with a bunch of melted ice cream or an empty PaaS. If the market is undefined i.e. the platform engineers are not already doing chargeback for other infrastructure, any attempt to price PCF now would be a shot in the dark and more likely to over/under estimate the value of the product than to be hit the mark. And over/under pricing it both come with big risks in the both the short and long term. Put in place all the facility you need to understand consumption, do market research on what people are willing to pay. Customers don’t even know the value yet until they start using it!”
  • VMware CloudHealth
  • Purser kubernetes chargeback, VMware open source.
  • Kubecost, video. Also from Google.

CTA

Three things for more Tanzu

Colophon

What does “digital transformation” mean? – Tanzu Talk Daily 20201005

Summary

Coté discusses three ways he thinks about what “digital transformation” means, and then focuses on the software related one. That whole “BE LIKE A TECH COMPANY” thing people are always PowerPointing about. Also: technology actually is hard, and pre-dread.

Planned on topics

  • What exactly does “digital transformation mean.”
  • The Orange small shop owner example (from this talk, I think).
  • Blockchain in shipping?
  • Technology is hard, and so is “culture.”
  • Avoiding pre-dread …?

CTA

Three things for more Tanzu

Colophon

Digital transformation as fried rice, and the better software standard talk – Tanzu Talk Daily 20201002

Planned on topics

  • Revision of my standard speech: gettting better at software. To include new stuff from SpringOne and whatnot.
  • Fried Rice Transformation – cooked flat, with a ton of garlic. This is sort of a (pained, forced) metaphor for mind-shift. I was taught to make it in a wok. Look, even cracking the egg on-top is new. I’d never thing to make it in a flat pan, with that much garlic!
  • Programming note: Tanzu Talk archives now in YouTube. Soon I’ll figure out show notes.

CTA

Three things for more Tanzu

In general, just go to cote.pizza for more stuff, my free books, newsletter, whatever.

Colophon