Steve Neiderhauser

Time 2021-08-30 20:19:34

Web Name: Steve Neiderhauser

WebSite: http://sneiderhauser.typepad.com

ID:189857

Keywords:

Steve,Neiderhauser,

Description:

Teresa Torres provides a wealth of Hypothesis Testing information on her website.This one tip will save you tons of time. Design and run experiments before you write one line of code. Teams may also want to slightly change the feedback loop from Build - Measure - Learn to Learn - Build - Measure. This Scrum Inc. article explains how Doctors in the United Kingdom responded to volatile conditions produced by COVID 19.There was no major announcement they were moving to Scrum, instead they simply started practicing things like daily stand ups and self-organizing teams. They also made work visible (tools like Trello helped) and had a clear vision.The senior leaders reduced bureaucracy and made decisions in hours that normally would have taken weeks. Ann Handley shares nine qualities of good writing.She brings awareness to the qualities of good writing. Without awareness, your writing cannot improve.Fact is, I’ve never really thought of good writing like good teaching. Good writing strives to make things a little clearer.In her article, Ann refers to this quote from Anne Lamott in Bird by Bird.“A writer always tries… to be part of the solution, to understand a little about life and to pass this on."Read the rest of her article and insights.  Gary Hamel explains that bureaucracy is basically a massive multi-player game.“If you’re an advanced player, you know how to deflect blame, defend turf, manage up, hoard resources, trade favors, and avoid scrutiny."This game creates a ton of waste.Wise leaders are saying, The concept of the CEO as captain of the ship, is bankrupt.And Haier’s CEO Zhang Ruimin set this goal: Let everyone become their own CEO. The Truth Curve, by Giff Constable, is an elegant diagram that shows how to use Lean Startup and rapid experiments to stage your investments for a new business or product.Key Lesson?Need to look at actions with a certain amount of skepticism even as we drive forward with a action. Is this experiment worth running? Is this feature worth building? Is this startup idea worth years of my life? Steve Blank provides the keys to getting started with Customer Discovery.Don’t talk about the process of Customer Discover or try to sell it.Customer Discovery is about gathering validated learning, not selling a methodology.Stop chatting to others about Lean Startup. Do the work and focus on reducing risk. Teresa Torres pens an article on the role of user research in continuous discovery.A couple key points stood out:1. Embed user researchers with your product trio during discovery. You want to avoid handoffs and provide firsthand exposure to the customer.2. Product teams work on a faster cadence. We don’t have time for perfect research… We want to mitigate risk, not seek truth. Teresa Torres explains why the Business Model Canvas became popular.The business model canvas (BMC) makes visible the nine building blocks of business and shows how they are connected.The article goes on to explain the benefits of maps and how sketching helps us think.I’ve always liked the BMC for its simple design compared to the traditional 60 page business plan. The simplicity allows us to rapidly model business ideas and iteratively design new businesses. This post describes Business Design and its benefits.Here’s a simple definition:Business design applies design thinking to business problems with the objective of bringing innovation to life.Here’s one of the key design principles:Making ideas tangible always facilitates communication and allows designer to treat prototypes as communication media. This is Atlassian’s take on the book Team Topologies and how they view the four types of teams. They look at the four team types and the benefits of classifying your teams into one of the follow types:Stream-aligned teamPlatform teamComplicated-subsytem teamEnabling team Team Topologies teaches you how to create fast flow systems. This article describes how to get started in eight steps.Start by identifying what kind of teams exist within the software organization. There are four fundamental team types.The third step is rather interesting: Limit the cognitive load for each team by limiting the size of the subsystem the team works on. Also, break apart monoliths using natural fracture planes.The remaining five steps are well worth the read. Funny how AI and No-Code solutions were in a deep winter. Looks like both have broken through the permafrost and are enjoying the rays of spring to flower their potential.I’ve taken a closer look into No-Code solutions. They could provide a major benefit especially for startups. Bubble.io looks rather good and they list several startups that achieved business results with their solution.Apps can be built in a fraction of the time and the feedback loop is dramatically accelerated. Thus, the runway is extended for startups. Rapid dev fits nicely with Design Thinking (in studies, DT correlates with revenue). When No-Code solutions reach their full potential there will be a major shakeup in software development. Bottom line: At the very least, companies should do Build vs. No-Code analysis. There’s a strong case for using No-Code to create MVPs.Why is rapid dev so compelling? Because customers need to see it to understand it. And to see it, there needs to be a shared space. In Strategyzer’s latest book, The Invincible Company, they look at four main performance indicators.Risk and UncertaintyExpected ProfitabilityCost to test ideaLearning Velocity and Time SpentLearning velocity feels like the one number that matters. Because it measures how much you’ve learned during a time period. Jeff Gothelf gives a wonderful description of Objectives and Key Results.Here’s a couple things I learned.A good objective is qualitative and focuses on the change the team desires to see. Objectives are aspirational and challenges the team to stretch further.I don’t recalling seeing in other articles that the objective should be timeboxed. Yet, timeboxes are a powerful concept and I’m glad Jeff included timeboxes in his writeup.So for an objective, set a deadline for achieving the goal.

TAGS:Steve Neiderhauser 

<<< Thank you for your visit >>>

Musings about Agile, Lean, and Product Management

Hot Websites