A nicely laid out story of how we got where we are in software product design.

↬ ∙ Tagged in Product Development.

Lea Verou:

Treat user effort as a currency. To create a product users love, design the tradeoff curve of use case complexity to user effort with the same care you design your pricing scheme.

…

Incremental user effort cost should be proportional to incremental value gained.

↬ ∙ Tagged in Product Development.

Catherine Wu (via Sachin Rekhi):

Step 1: Idea → Prototype Got a feature idea? Skip the spec. Build a working prototype using Claude Code instead.

Step 2: Internal Launch Ship that prototype to all Anthropic engineers immediately. No polish required—just functionality.

Step 3: Watch & Listen Track usage religiously. Collect feedback actively. Let real behavior, not opinions, guide decisions.

Step 4: Data-Driven Prioritization

• High usage + positive feedback → roadmap priority
• Low engagement or complaints → back to iteration

I’m increasingly of the opinion that focusing on prototypes first cuts through a lot of what ails many product development processes.

↬ ∙ Tagged in Product Development.

Ben Khun:

In a company like Anthropic, excellent project management is an extremely high-leverage skill, and not just during crises: our work has tons of moving parts with complex, non-obvious interdependencies and hard schedule constraints, which means organizing them is a huge job, and can save weeks of delays if done right. Although a lot of the examples here come from crisis projects, most of the principles here are also the way I try to run any project, just more-so.

↬ ∙ Tagged in Product Development.

Folks often want to know the cost of implementing an idea.

Estimating that cost is work too and we need to surface that cost.

↬ ∙ Tagged in Product Development.

Ryan Singer:

The counterintuitive thing is, we often feel like our task is to get to a “yes.” But what we actually need is a way to say “no.” It’s the ability to eliminate many, many things that aligns us on the one thing. It’s the “no, no, no, … YES!” that gives us the power to move forward and to stick with a project.

To help us to eliminate (not forever, but for the purpose of making a decision now) I’ve found one technique very helpful. The trick is to flip things around. Instead of describing the good that will happen by doing an idea, we look at what goes wrong when we don’t do it. To make that flip, we can ask two simple questions:

1. Knowing the customer can’t do what’s in the idea today, What are they doing instead?
2. What’s bad about that?

↬ ∙ Tagged in Product Development.

Tara Seshan:

For years, communicating tradeoffs to senior leaders was one of my biggest challenges. While presenting the pros and cons between two priorities, I’d somehow always end up committing to doing both, and in less time than I had planned. As you’d expect, this usually went … badly. I’d burn myself out or, worse, burn out my team.

But when I started managing, I finally understood why I had been so ineffective at it. Sitting on the other side of the table, I watched others make the same mistakes I had. I realized I hadn’t been framing tradeoffs correctly.

↬ ∙ Tagged in Leadership, Product Development.

Johanna Rothman:

But instead of placating the managers and trying to estimate, consider starting with this question:

How do you plan to use this information?

That might offer you ways to answer the question that does not require any prediction.

Also read part one and part three.

↬ ∙ Tagged in Product Development, Teamwork.

Naomi Nix:

Initially, the team carried just two product managers and one or two designers alongside dozens of engineers — a flatter and more coder-dominated group than most Meta product teams, Mosseri said. (At launch, it had grown to three product managers, three designers and 50 coders.) Instead of 30-minute presentations on a single design decision, typical at Facebook and Instagram, “It would be like, ‘Here are six things we need to go through this week.’”

Meta went for an engineer-heavy team composition and light weight process to build Threads.

↬ ∙ Tagged in Business, Product Development.

Dan North:

tl;dr

• Model and visualise your value chain.
• Structure the people around the value chain.
• Make all the demand visible, so there is no hidden work. This is key.
• Identify work that will reduce drag and give you more discretionary capacity.
• Decide what you want to invest in, and structure the people around that.
• Repeat every quarter, which is long enough to get work done, and short enough to iterate.

↬ ∙ Tagged in Product Development.

Jason Fried:

Innovation should almost never happen. It’s incredibly rare. It mostly happens by accident, not by intention. It’s wonderful when it does, but you merely fluctuate in and out of it, it’s not steady state.

Work is mostly mundane. It’s mostly maintenance. It’s mostly local improvement and iteration. Work is mostly… Work. Any innovation is an outlier, nearly a rounding error.

↬ ∙ Tagged in Product Development.

James Stanier:

When you’re staring a huge, challenging project in the face, don’t align your team around just getting it done. Instead, align your team around continually reducing uncertainty.

You reduce uncertainty until the software exists. You reduce uncertainty by doing: prototyping, designing, writing code, and shipping. Each of these actions serve to reduce the uncertainty about what is left to build.

↬ ∙ Tagged in Product Development.

Jason Yip:

Organizational effectiveness in market development is efficiently running a lot of experiments to find promising opportunities.

Organizational effectiveness in growth and maturity is efficiently building, scaling, iterating, and exploiting capabilities in order to maximize business value.

Organizational effectiveness in decline or commodity / hygiene capabilities is reducing total cost of ownership.

↬ ∙ Tagged in Business, Product Development.

Anthony Murphy:

Having overlap is deliberate and a good thing. It helps create shared accountability and remove any bottlenecks or single-points of dependencies.

↬ ∙ Tagged in Product Development.

A snapshot of the planning process at Netflix, Mailchimp, Asana, LaunchDarkly, and more.

↬ ∙ Tagged in Product Development.