{"id":22609,"date":"2021-02-08T11:13:12","date_gmt":"2021-02-08T11:13:12","guid":{"rendered":"https:\/\/www.experfy.com\/blog\/why-blind-spots-terrible-remote-workers\/"},"modified":"2023-09-05T10:11:02","modified_gmt":"2023-09-05T10:11:02","slug":"why-blind-spots-terrible-remote-workers","status":"publish","type":"post","link":"https:\/\/www.experfy.com\/blog\/future-of-work\/why-blind-spots-terrible-remote-workers\/","title":{"rendered":"Why Your Blind Spots Are Terrible For Remote Workers"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

I firmly believe no one goes to work to do a lousy job, but sometimes projects deliver terrible results. So despite peoples best intentions, ‘shoddy’ work happens.<\/p>\n

I am not suggesting that there is one ‘nice and easy’ reason why projects go wrong or deliver bad outcomes; there are so many potential pitfalls. Maybe the project was a bad idea to start with, maybe the project suffered from poor project management and was rushed, or perhaps a great product was compromised by poor implementation and change management, it goes on.<\/p>\n

I am suggesting that if we don’t know or value the users’ needs, then the chances of success are compromised.<\/p>\n

So this is the nub of it, how do we know, I mean, really know what the users need?<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Finding out what customers need<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Top Tip 1<\/strong> – If you want to know what someone is thinking, needs or requires, ask them.<\/p>\n

But, its more complicated than that, and Steve Jobs <\/a>summarised the problem very well:<\/p>\n

“Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!'” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.”<\/em><\/p>\n

As problem solvers, our job is to engage with users, stakeholders, assess their needs and wants, then based on their inputs and using our skills and experience create an elegant solution.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

There is a but<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

And then there is noise, distinguishing between, fact, opinion, belief and prejudice. It’s useful to be aware of this dynamic, and apply these simple definitions:<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t