Good FDE / Bad FDE

July 9, 2026

Good FDEs know the customer, the market, the edges of the product’s surface and where it’s headed next, the partners and tools that support expansion, and the competition — intimately. They navigate that terrain with fluency and systematically expand the addressable market. Bad FDEs arrive context-poor and pattern-rich — force-fitting the last customer’s solution onto this one.

Good FDEs build pontoon bridges: quick extensions of the product’s surface that carry real weight until the permanent structure arrives. Bad FDEs build bridges to nowhere — dislocated from the product’s surface and its strategy, destined for orphanhood.

Good FDEs read the room: the power structures, and the incentives that shape them. They are voracious acquirers of data and context, and they translate it into solutions with the product at the core and their own ingenuity at the periphery — solutions that keep improving as the core evolves. At their best, these are portals to a future product state.

Good FDEs listen hard — to needs, wants, desires — but don’t defer. They challenge assumptions. There is a difference between a solution that makes the customer happy and a solution that makes the customer. FDEs are remembered for the second.

Bad FDEs are excuse factories: missing endpoints, slow stakeholders, features that don’t exist yet. Good FDEs will not be denied. A solution deployed, embraced, and in daily use is a foothold — trust, credibility, future revenue. Everything else is a demo.

Bad FDEs blame the zeitgeist when things break. “The model let me down.” “The context was lacking.” “The harness is the saboteur.” That is the solace of unearned judgment.

Good FDEs know action is information. Every step into a customer’s problem is a step toward something people want — toward a product surface that compounds. At minimum, they document what they see and feed it back to product, design, and engineering. At best, they prototype the future surface alongside them. At worst, they’ve made the next FDE — human or agent — better.

Bad FDEs optimize prematurely or not at all. They automate on the first repeat, forgetting that customers solve the same problem in remarkably diverse ways — or they build from scratch every time, which even in the age of AI signals no thought of reuse, efficiency, or how customer needs overlap.

Good FDEs run on built intuition. They know when a process is sub-optimal because regulation or org gravity keeps it that way, and they are uncanny at sensing when the signal across implementations says steps x, y, and z are now repeatable. Then they refactor, instrument, and compress.

Bad FDEs take the product at face value, let customers discover the rough edges, oversell unreleased features to spare themselves effort, and scapegoat the product when convenient. Good FDEs are ambassadors. They let the product shine when it’s earned, protect it when it falls short, and know when a new or neglected feature needs evolutionary pressure — and when it doesn’t.

An homage to Ben Horowitz’s Good Product Manager/Bad Product Manager.