Learn What the Best Products
Got Wrong — And How to Fix It in B2B Software
Opinionated, specific critiques of how great products could be better — the UX improvements, architectural refactors, and product decisions we'd make differently.
Tailored for B2B software products: complex buying cycles and multi-stakeholder adoption.
Read CritiquesB2B Software Context
B2B Software
complex buying cycles and multi-stakeholder adoption
Breakdown Focus
Opinionated critiques of real products by the people who build them
Applied to B2B software products specifically.
Why B2B software teams get what we'd do differently wrong
B2B software products face unique constraints — complex buying cycles and multi-stakeholder adoption. These are the most common failure modes.
Learning only from success stories without understanding why good products still have flaws
No framework for structured product critique that produces actionable improvements
Cargo-culting decisions from successful products without understanding their limitations
No way to develop product taste without seeing both what works and what doesn't
What We'd Do Differently built for B2B software products
We give honest, specific critiques — not generic praise or vague suggestions
We explain exactly what we'd change and why — with the product thinking behind each decision
We use real products to develop the product taste that separates good from great
We show how the same problem was solved better elsewhere
Why B2B software teams study what we'd do differentlys
Sharper Product Taste
Learning to see flaws in great products develops the taste that makes your own decisions better.
Constructive Critique Framework
A structured way to evaluate any product — your own or a competitor's.
Avoid Repeated Mistakes
Learn from documented errors before you build the same anti-patterns.
Better Design Vocabulary
Specific critiques build the vocabulary for describing design decisions precisely.
How we do what we'd do differently for B2B software products
Define what the product is trying to do
Every critique starts with understanding the intended goal — before judging the execution.
Identify where it falls short
Find the specific moments where the product makes the user work harder than it should.
Propose the alternative
Describe the specific change — not just 'make it simpler' but exactly what simpler looks like.
Evaluate the trade-off
Acknowledge why the current design might have been chosen — and why the alternative is better.
What We'd Do Differently for B2B Software: what changes
B2B software products have specific constraints — complex buying cycles and multi-stakeholder adoption. A what we'd do differently in this context focuses on patterns relevant to those constraints.
Generic approach
- ×Learning only from success stories without understanding why good products still have flaws
- ×No framework for structured product critique that produces actionable improvements
- ×Cargo-culting decisions from successful products without understanding their limitations
Greta's B2B Software-specific approach
- ✓We give honest, specific critiques — not generic praise or vague suggestions
- ✓We explain exactly what we'd change and why — with the product thinking behind each decision
- ✓We use real products to develop the product taste that separates good from great
What We'd Do Differentlys to read now
Apply these patterns to your
B2B software product.
Kanban boards, real-time editors, AI integrations, payment systems — shipped in days, not months.