feedback
-
🪑 The missing leg of reliability
After a conversation with Tim Bird about Space-Grade Linux, an idea about reliability emerged. The obvious legs of reliable systems are design and testing. What is less obvious is the third leg: active users. Use, coupled with the ability t…
-
🛩️ Why did the Wright Brothers succeed?
While Samuel Langley had $100,000 (equivalent to $3.5 million today) in funding, a team of engineers, and Washington connections, the Wrights were bicycle mechanics from Dayton, Ohio with a fraction of those resources. Langley’s approach wa…
-
📦 What is a release used for?
A release needs to happen before a product is shipped to customers for sale. Across the spectrum of the product development lifecycle, releases are used for: Generate feedback (so we know where we stand) Provide something others can build …
-
❓ What is the difference between "releasing" and "shipping"?
Someone asked: “What is the difference between releasing and shipping?” Are they the same thing? In one sense they are. However, drawing a distinction here—though somewhat arbitrary—is helpful in this context. Release: Make something availa…
-
🚨 Problems with not Releasing First
What is the downside of not Releasing First? Integration problems Manufacturing issues Last minute bugs appearing Lack of product fit (does not solve customer’s problem) The common theme is unforeseen problems that typically surface late …
-
🌅 Why optimizing the user release experience early is so important
With Release First, the goal is to optimize the Big Blue Button (make it easy for users to use a release) early. Why is this important? There are many reasons, but the most important is so that users actually use the release and provide nee…
-
🔵 The Big Blue Button
In the past days, we’ve been focusing on the Big Green Button, but there is another side of this - what happens after the release? Does the release get used? If not, why not? If a release does not get used, there is little point in releasin…
-
🟢 The Big Green Button
The word “release” can be a noun (what gets released) or a verb (the process of producing a release). “What” and “How”. Many teams produce complete high-quality releases that allow them to produce or deploy something at some point in time. …
-
🛠️ Do things that don't scale
From Paul Graham’s popular essay Do Things That Don’t Scale: Over-engaging with early users is not just a permissible technique for getting growth rolling. For most successful startups it’s a necessary part of the feedback loop that makes …
-
🔮 Can we predict product development schedules?
Estimating or predicting product development is difficult. Teams often end up adding a 2-3x padding to any estimate, because bitter experience has taught them not to depend on their own estimates. There will always be a high degree of varia…
-
📖 When should you write the user manual?
Most of the time, teams write the user manual at the end of a product development cycle right before the Big 1.0 Release. It is one of those things that is not much fun, and teams subconsciously put it off while fighting bigger fires. But w…
-
🎬 Is a Demo the same as a Release?
Some development teams have a weekly demo where they might show what they are working on to others in the company or the customer, which is a great idea as it encourages hitting milestones and early feedback. However, is the “demo” just ano…
-
🔍 It is often more work to review something than to do it
As an experienced person, I am sometimes called on to review something. This can be a frustrating, seemingly hopeless task. With one developer, I commented that he could write code faster than I could review it. While there are some issues …
-
🤔 Isn't this just agile?
A reader responded to the last post with a comment: Isn’t “agile” a part of product thinking too? That doesn’t seem linear? This is a good question. Agile covers a lot of ground. The Agile Manifesto states: We are uncovering better ways …
-
🔄 Closed-loop engineering
What are some ways we can close the loop in engineering efforts? Systematic testing User feedback These ensure whatever we build works and is useful.
-
🔄 Closed-loop humans
What are some ways we as humans can close the loop? Listen Reflect Write Without these, we operate in a largely open-loop mode without the feedback we need to improve or correct our course. Action bias is good, but it helps to know we are…
-
🔄 Look for closed loops
Closed loop systems are stable. Why? Because they learn and self-correct. In any system, process, person, or organization, look for closed loops. If something is not working, chances are there is an open loop.
-
🔄 Close the loop with AI
There is a fascinating statement in a recent MIT study that claims 95% of organizations are getting zero return from GenAI investments. The core barrier to scaling is not infrastructure, regulation, or talent. It is learning. Most GenAI sy…
-
🎉 200 posts
This marks the 201st post I’ve sent – 2/3’s of the way through the 300 bad posts. How is it going? I still enjoy the process and the thinking it brings. However, it is getting a little bit more difficult recently to keep the discipline, esp…
-
🔄 Open loops -> technical debt
If something is corrected, it needs to be fed back and incorporated, so you don’t keep redoing the same stuff over and over and eventually bury yourself in technical debt. Effective organizations close the loop.