4 ms·
> Building the wrong feature or product A bit of background: a company I worked at had one primary product with a web interface for the customers, businesses w
by cratermoon 5y ago
> Building the wrong feature or product
A bit of background: a company I worked at had one primary product with a web interface for the customers, businesses who used the product, to do all their functions. Think AWS console but not so massive.
There was another, minor product brought in via acquisition, which had its own web interface.
A third group came into existence when my employer got acquired, which created a new web interface for its product, which did mostly the same things as the primary web interface but for a different set of customers.
These all had separate logins, so customers had to know multiple credentials. There were also several large customers of the primary product who had multiple logins for reasons which defy my full understanding to this day.
The project I was on was to bring in a system that would eliminate separate logins and provide a single sign-on system for them all. Good goal. very doable.
The VP in charge of the new group and a product manager got into their heads that what we really needed was a single landing page portal, a piece of software that didn't exist and wasn't necessary for the sign on. The team wasted at least three if not six months chasing that landing page goal before the VP decided her product needed to go live and oh by the way we didn't have time to do the single sign-on any more before her product was to go to production.
Ultimately the distraction killed any chance for the company to actually implement the desired sign-on that the customers were clamoring for, and to my knowledge they are still limping along with a every customer having at least three different logins, one for each system.