Product engineers solve user problems, but why are there so few of them?
As recently as 1999, The Inmates are Running the Asylum told the tech industry that engineers were the reason websites and products were bad. Engineers were not trusted with knowing about users and their problems and yet, they are blamed for poor solutions to solving them.
The way we organize engineering doesn’t help. As companies grow, engineers specialize and are closely managed by project managers and product managers. It’s difficult to build anything significant that requires action across teams and departments.
Altogether that means we lack the trust in engineers to understand users and the experience pool to cultivate a strong product engineering discipline. Status quo preserving behavior will continue to keep engineering as they are, which doesn’t bode well for users.
See also:
- Most companies treat engineering as delivery.
- Startups have a much better shot at building capable product engineers because startups value generalists early
- Automating cooperation might help larger companies resist these tendencies
Links to this note
-
Having ‘good taste’ is difficult to define. Taste is subjective, it is only confirmed by assent from others (from Immanual Kant) a kind of determinate negation.
-
Why Product Engineering Always Feels Kind of Wrong
Something I’ve noticed about building products over the years is that it always feels like I’m doing it wrong. At the same time, it’s a clue about what’s really going on and what to do about it.
-
I Was a Non-Technical Product Manager Once
A common question in product management that always seems to come up is some flavor of: should product managers be technical?