3 LEAPS retweeted
Remembering that Excellence Wins
Here's a plug for a book that reminds me that customer satisfaction and (fanatical) loyalty come from a firm's absolute devotion to operational excellence, empathy, kindness, and the incredible power of being nice.
Ever have a book come to mind when writing? Only a fistful of business books stick with me. Today I was working on a Smooth Development Maxims post for our 3 LEAPS page and one came to mind. The subtitle for this post is "Measure, Monitor, Manage" - a core maxim taught to me by a gifted boss and mentor back in the late 80s and early 90s.
Check out the book, Excellence Wins (horstschulze.com/) by @horstschulze . Mr. Schulze was a co-founder and longtime president of Ritz-Carlton and the architect of their legendary management systems. This book will remind you of how to build lasting customer loyalty. I offer that it might inspire you to be passionate about building a better organization, being a better leader, and being a better person. Without spoilers, I will simply say that his idea of "becoming the best in a world of compromise" is something I strive to follow.
Ritz-Carlton was legendary for their service in the 90s. Their employees were (and may be still) famously empowered to spend - without management approval - a fairly large sum "per incident" in order to delight a guest. What brought me into researching them was their process discipline. As my mentor taught me, "You have to measure something in order to monitor it. You have to monitor something in order to manage it. You have to manage something if you want it to work all the time." Does it seem strange that I learned a core principle of enterprise-scale operations from the business processes of a hotelier?
The funny thing about this (important-but-dry) topic is that I learned in the context of how a hotel chain became literally world-class in service delivery. Those of a certain age may remember that Ritz-Carlton was (and still is) the only hotel company to have won the Malcolm Baldridge National Quality Award - twice (in 1992 and 1999). Here's a link to a story about win #2: nist.gov/baldrige/ritz-carlt….
If you deliver solutions with software, I humbly note that "people buy solutions from people." Those feature charts we make help us stand out in the early sale. Winning and keeping clients comes from delivery excellence. In the end, I've come to appreciate the brilliance of my former boss and mentor, teaching me that software folks could learn quite a lot from the hospitality industry. I try now to seek out examples of firms delivering excellence in any area or walk of life. People reward firms that deliver good and reliable experiences with more business. People become lifelong fans of firms that deliver excellence and have genuine empathy and initiative for their needs and for those around them.
Don't compromise on principles - deliver excellence!
#opsuccess #smoothingsolutiondelivery #3leaps
3 LEAPS retweeted
Beware the attention bandwidth trap: keep the Owner Zone sparse
Builders and operators of complex enterprise systems face many challenges. At the product level we often ask "Buy or Build?". It is better to ask "Integrate or Build?". Is there a component or service available that is a pretty good fit? Works elsewhere? Updated frequently? Then "integrate"!
I see too often a tendency to "build" to perfect edge cases. I see single-sourcing decisions made when the benefits are not weighted against substitution risk. These decisions may not even be visible in a large organization. Projects expand because of unknown "ownership" decisions!
Where must you "own" a component? For most, it would be an absurdity to say "let's WRITE our own database". Really it is no longer a good idea to even RUN your own database (use DBaaS instead). The concept extends to operations - does you team "vertically own" a process? Or do you coordinate data and work with other firms? Areas where you have trade secrets and true "secret sauce" may belong here. Most of what makes up a large solution does NOT. There are a LOT of costs in this zone. You own the documentation, the architecture, the maintenance, the roadmap, the deployments - all of it. Time spent maintaining custom pieces is time you can't spend adding features or extending your solution.
Attention bandwidth is an overlooked facet of operational success and product continuity. Think about your solution or process. Which parts "just work" and which ones require constant managing? Where are you one blip away from an outage? We use what we call an "Attention Matrix" to help us align our sourcing decisions.
Sometimes there are significant benefits to single-sourcing a component. This is fine SO LONG as you accept the responsibility to monitor (constantly). Some components are really hard to replace. Even if there are ready substitutes, we need to devote time to designing and practicing replacement actions.
We divide our component sourcing attention matrix into four zones:
1. Owner (Build, Maintain and Own): Requires most time and money - limit what goes here!
2. Mission-critical Sourcing: Single-source (presumably for a good reason) - watch like a hawk!
3. Customized Sourcing: Complex actions required to replace - design and test migration exercises regularly!
4. Catalog Sourcing: Relatively easy to replace if you take time to spec and automate - prove these are easy by changing in test!
Putting too many things in the Owner Zone will sap your teams' productivity and rob you of contingency bandwidth at the worst possible times. Having too many partners in the Mission-Critical Sourcing Zone may create failures from a few unrelated issues hitting at once.
If you aren't getting the velocity you want or expect, take a look at your processes and BOMs. Be data-driven and push back on the status quo. Lowering the ownership / single-sourcing burden will raise velocity and reliability in your solution!
#saas #productcontinuity
3 LEAPS retweeted
Want passionate users? Get them proficient first. Lessons from my (good) experience with @raycastapp.
Most of us would agree that user feedback is important to health of any application, whether B2B or B2C, horizontal or vertical. How can our product and service architecture make user feedback and support frictionless? For larger subscriber bases, we often think "customer support process". Perhaps we focus on effective chat experiences, webinars, or email handling automation (all good). What can we do in the product itself? How do we help users become experts in our solutions?
I've been playing around with Raycast on my Mac desktop. This clever productivity application (my words) acts as kind of instant search and task panel. You can bring up a little panel with a hotkey and quickly search, access data or run commands quickly. These applications grow when there is a (passionate) user community to make suggestions and to build extensions. To become a passionate user (presuming interest in the subject), one first needs to be a proficient user. How do we achieve this?
I like the way Raycast takes time to remind new users how easy it is to give feedback, using the app. This not only creates a low friction interaction point for users, but also helps to build a sense of community. Building from easy feedback, we must help users become proficient.
Like any keyboard-driven app, you get the most out of it only when the shortcuts make it into muscle memory. This takes time. I forgot the hot key to bring up the app a bunch of times and found myself needing to consult the help to remember that little automation action I wanted to do. The team has done a good job of making the basic information available, including the always available "Open Walkthrough" shortcut to bring up the tutorial.
This attention to user training often gets lost in specialized vertical applications. How many of us work with SaaS apps or specialized analytics dashboards that are important but not used 8-10 hours per day every day? We forget the little things first ("what was that hot key again?"). How often do we strand users who are simply challenged to remember how to do "important task XYZ" that is only run once or twice a month? A good UX with intuitive controls and crisp layout is the foundation of good usability. The steps Raycast takes with unobtrusive user training and low-friction feedback remind me that the product itself must drive and support user enthusiasm and product mastery.
Showing my age, I use vi as a keyboard-based editor without a cheat sheet (Emacs users, please don't hate on me :)) It took me a few years (long ago) to do without thinking. We all want our users to be proficient and passionate. We probably we don't have a few years for our users to gain mastery.
Raycast gets this right. My experience reminds me of the crucial role the product itself must play in supporting users on a journey to proficiency and mastery.
#smoothingsolutiondelivery #passionateusers
3 LEAPS retweeted
There’s an awesome skill you can hone over the years that I’d call “data instinct”.
It’s the immediate intuition about whether a metric or measurement you’re looking at is accurate or not.
It applies both to business and engineering. – at San Francisco, CA
3 LEAPS retweeted
Last month, the ESF (Enduring Security Framework) released a new report with recommendations for managing SBOMs and dealing with open source software-related risks. Here are some of the highlights.
fossa.com/blog/takeaways-esf…
3 LEAPS retweeted
Here's my pitch for a rebranding of Data Monetization to Information Trading.
As enterprises everywhere look more for first party data, I think the term "Data Monetization" is creating some obstacles to progress. The overly abstract term puts in my head pictures of data records flowing across a scanner at checkout. This concept is ages old! How might I as a purchaser of goods or services for delivery in my business get some credit or favorable terms in exchange for sharing more about how those goods and services are viewed and delivered?
Who in the business of large-scale distribution of goods and services not sought ways to learn more about how to improve the efficiency and profitability of those activities? I think we should use the term "Information Trading" here, because it drives home the benefits for both parties. We trade information for favorable pricing, incentives, access to special products - whatever. Who doesn't want to improve results?
Here are two Zig Ziglar quotes that I like a lot:
1. You don't have to be great to start, but you have to start to be great.
2. There's no elevator to success. You have to take the stairs.
I was talking with a client the other day about some challenges in a large-scale information trading project. After making some decisions on next steps, later in the day it made me think about discussions I have had with others who are thinking about these initiatives and having problems getting started with that next (or first) phase.
Our experience shows that the projects themselves usually pay for themselves quickly. A big impediment, however, is starting too big.
If your enterprise is direct-to-customer/audience, it is likely that your suppliers and partners could benefit from a better understanding of how their products are reviewed, sold or - let's be honest - not sold. Trading information is another way to improve results for both parties.
I see three stages of maturity in an information trading program:
Level 1 - Bespoke Trading
Level 2 - Information Packages and Service Tiers
Level 3 - Automated Data Marketplace
Are you just getting started? Level 1 is for you. Get with your suppliers and see what information they need in order to improve their businesses. What can you get them (mindful of data usage rights)? Make a handshake deal with a well-documented trade for rebate, lower pricing, longer terms, etc. Hustle to get them the (accurate) information. Agree to meet and review again in a month or two. Results will drive progress and scale.
Looking at those Ziglar quotes, I'd submit that sometimes we want to go straight to Level 3 with that beautiful web portal, warehouse and e-signature templates. Without hard evidence that the information trading benefits both your enterprise and that of your suppliers, the project will probably not get funded.
Start as small as you need to get results quickly, but ramp up Information Trading today!
#informationtrading #firstpartydata #datamonetization
3 LEAPS retweeted
The TXB team has expanded our Private Label offerings. Check out this recent article from C-Store News: csnews.com/texas-born-grows-…
3 LEAPS retweeted
Google’s Gen-AI Search Is Powering 84% of Queries, Study Finds adweek.it/48BbTn3 via @Adweek.
Nice piece by @trishlaostwal including interviews with leaders at @brightedge and @brainlabs. Check out the article for some interesting notes on differences in search results using SGE, and for trends in SEO spend diversification.
@Google's initial post on SGE is here: blog.google/products/search/…
You can try it out here: labs.google/sge/
A current post from BrightEdge on the topic is here: brightedge.com/blog/preparin…
3 LEAPS retweeted
Here's a quick pitch to the builders and leaders in development, IT and product management for SaaS and PaaS solutions: time for a January License Review. This might sound a bit like changing the batteries in your smoke detectors at home - important but not a lot of fun. At least this is not another reference to Dry January :)
In business terms, a semi-annual license review serves some of the same purposes as climbing that ladder with a battery in hand (to prevent disasters). Most software-based solutions are built on scores or even hundreds of different components, some of which are "nested" in other components. Even for those whose solutions leverage closed-source technologies exclusively, it is likely that some of your infrastructure and ops tools are using open-source components. Whether your licenses from closed-source providers adequately protect you is a topic for review with your IP counsel.
Over the last year, a number of solution providers switched to a Business Source License, bringing different conditions and terms-of-use. @HashiCorp did this in August (check out nitter.gq/HashiCorp/status/16897… from last August, as one notable example that had broad impact in devops circles particularly - Terraform, Consul, Vault, etc). Acknowledging the controversy sometimes associated with these licenses, the reality is providers of open-source packages often face a "freeloading" problem where large enterprises use their packages in (possibly competing) offerings without contributing to the platform. For today's message, though, the focus is on our solutions rather than platform licensing strategies. We must understand the terms-of-use for these components to be sure each is consistent with our own usage.
Over the last few years, we've seen the term SBOM (Software Bill of Materials) come into broader use (see below for some follow up links). Knowing what components make up your solution (including the operating tools and infrastructure elements you manage) is crucial to what I call product continuity planning. @3LEAPS are taking up a series on the topic later in the quarter, covering not only licensing but also other business continuity elements such as source integrity, source continuity and disaster recovery.
For now, here's a suggestion. Ask your devops team to share that SBOM and make sure the licenses match for your use cases. If your firm has to build an SBOM manually, I'd suggest using a solution like @getfossa that can help you automate in a way that scales cost-wise for both small and large projects. Even if you have automation, review the SBOM and check on the licenses at least twice yearly to help maintain your product continuity! And, don't forget to discuss findings with your IP counsel as matters of license suitability may warrant legal review and possible changes in your approach.
Intro links on SBOM:
1. This @CircleCI post at circleci.com/blog/what-is-a-…
2. This @CrowdStrike post at crowdstrike.com/cybersecurit…. Both are good starting points.
On BSLs:
1. Survey from @getfossa at fossa.com/blog/business-sour…
2. From perspective of an implementer, see this excellent @mariadb post at mariadb.com/bsl-faq-adopting…. Most acknowledge them as the first to implement the license at scale.
#productcontinuity #sbom #opensourcelicensing #softwarelicensing
Future releases of HashiCorp's core products will adopt the Business Source License. We know our community will have questions, so please read our blog post to understand why, and see our FAQs to understand the changes:
hashi.co/bsl-blog
hashi.co/license-faq
3 LEAPS retweeted
A historic view of the practice to delay releasing Open Source software: OSI’s report blog.opensource.org/a-histor… #dosp #legal #research #OpenSource
3 LEAPS retweeted
Ikea isn’t a brand usually synonymous with luxury, so creative agency Mother aimed to show off the design and quality of its kitchen furnishings by inventing a fictional premium brand with its own commercial and influencer event. adweek.it/3RZEQls











