> Generally it is quite important especially for SaaS. You see, I don't think that's true at all. If it was, certainly you'd have clients complain loudly enoug

> Generally it is quite important especially for SaaS. You see, I don't think that's true at all. If it was, certainly you'd have clients complain loudly enough for the PMs to notice. But that doesn't seem to even register a concern, both from the client and from the PM point of view. Convenience is a nice-to-have, and fixing problems that don't exist registers even lower in the priority queue. > Non-technical PMs tend to gloss over things like that (...) See, this is where I think we disagree at a very basic level. There is no such thing as a technical and non-technical Product Manager, because a product isn't technical. A product is something that meets the needs and expectations of its customers. A Product Manager's responsibility is to know their product and manage it to meet its clients' needs, and in the process help guide the development effort to maximize its returns on investment. Whether it's to paint a button red instead of blue, or to tell if they need to upgrade TLS, a PM's job is to read the room and deliver what meets the needs.