Whatever "customer experience" means is specific to an industry/company, not a universally agreed upon term. For Amazon, which is largely B2C, UX is critical. For other industries, delivery time may be more important. There are such things as tradeoffs, and in some cases, it makes sense to prioritize things other than an awesome UX.
As I see it, it's as simple as taking the time to think as the customer.
I wonder how many universities make their engineers or developers actually build something for an outside or even internal customer.
Strangely, vocational folks deal with customers quite a bit in learning and learn to think in those terms. Nothing like having to redo the doors on a cabinet or rerun some plumping to make you think first.
Why would a university do any such thing?
University is the place and time to learn things that no business has the time or skills to teach you. Serving customers is exactly what you should learn at work.
For my final year full-year Software Engineering project with 16 team members we built and delivered a software product for an external customer - a big name Software company you've heard of.
It was an awesome project, working so closely and directly with the external end customer.
As a bonus, the Bach. of Software Engineering is accredited by the Australian Institute of Engineers.
I'm pretty sure they made it a full on elective class next semester.
Don't most?
At my alma mater, students in either Telecommunications or Comp Sci majors were required to do a capstone project their final semester for an outside client/customer. They made a big deal about the demo day for it and it was always a cool event. Considering my school was a large public school that isn't known specifically for its computer science/IT, it seems strange that more schools don't do this. It seems like most CS friends from other schools had the same experience as well.
It's really too bad if some people don't get a chance to do this. There are countless things during that project that were good learning experiences, but they would have been awful if it had happened when I actually had a real job. I can definitely say that project determined a lot of my future plans.
It doesn't seem like it, and I would bet it has something to do with local population size and budget.
(No idea what they do now, but I would guess they would have shifted further in that direction)
...or, does the typical engineer's needs and tastes differ so much from the typical customer's that most engineers simple cannot not see the latter? For example, many of my friends in tech could not and still cannot see why so many consumers prefer iOS to Android given how much more customizable or "tinker-able" the latter is. The ones that get it the best are the ones that play tech support to many non-techie family members.
Engineers brains just work and see the world differently than most people.
Right.
As I've related on HN before, I believe a pivotal point very early on in my career was seeing technology through the lens of my aging mother.
It completely opened up my perspective about tech in service of people.
I take your observation and my experience as evidence that this empathy and understanding can certainly be learned - it's a question of how to teach students and convince them that it matters.
>"Engineers brains just work and see the world differently than most people."
Sure, I get what you're saying, but I wonder how much of the negative side of that is self-fulfilling in teaching and ultimately being an engineer.
I'd like to think we can be excellent hammers without treating everything as a nail.
>"He paused another moment and then said, “I know that’s not your plan because it can’t be done. What is your real plan?”
He told us he wanted to see a new version the very next day. The request didn’t seem to make much sense. In fact, to this day I’m not sure what the product will be used for—but we dropped everything else we were working on and scrambled to get the demo done in time."
So the author worked (presumably quite hard) on something, received dismissive feedback that didn't make any sense, didn't question any of it, scrambled to re-implement on an uninformed guess for the next day then (surprise) got slapped around again.
That honestly sounds more like a loyalty/submissiveness test of some sort than anything else.
Ideally, that meeting was a great opportunity to challenge the man and earn some respect from him or possibly lose some for him depending on how it plays out.
>"He wasn’t thinking about the feature; he was thinking about the customer experience."
What is wrong in the culture / education of engineering that people have to be taught this after they start working?