Khash Faiz

UX design manager / Lead UX Designer @Tesco Enterprise Team | Curious about human behaviours | @LboroDesign graduate | Opinions are my own | 🇺🇳

[Khash Faiz @khashfaiz]

@implausibleblog There are 1000 vacancies at Tesco. Those 400 roles are roles which are not as relevant as before. Tesco isn't cutting down on its number of staff.

[Scott Berkun @berkun]

"Your success as a designer depends equally on your relationships as it does your talent. The ppl you need as allies will know little about design. Your ability to convince them to use your ideas is as valuable as your creativity."

- From Why Design Is Hard #designishard

[Khash Faiz @khashfaiz]

@andybudd Excited to order my copy soon

[Khash Faiz @khashfaiz]

@berkun Got my copy today Scott! Thanks so much for writing it! 🙌

[Luke Wroblewski @LukeW]

"UX" today. how many meetings did this take?

[Khash Faiz @khashfaiz]

@LukeW This is scary!

[Andy Budd @andybudd]

The reason we get stuck in a feature factory is because we’re feature obsessed. Much much better to be problem obsessed and focus on keeping a problem backlog over a feature backlog.

https://t.co/2uqeKCUsp9

[Khash Faiz @khashfaiz]

@LouDowne hi Lou, question about https://t.co/gFP59Ag5iq when you were working on it. A lot of the new user journeys had to bring multiple domains/departments together. Do you have any examples? E.g. applying for a passport and how many departments there are being the scenes

[Khash Faiz @khashfaiz]

@sarahdoody Yeah, but don't have a lot of headspace for things to come and consume/contribute on here
Have always loved the UX community on Twitter / X tho

[IxDA London Local @IxDALondon]

We're running our 2nd in-person IxDA london event next Wed, featuring @genmon who will be presenting on Acts Not Facts, Product invention via exploring and making.

RSVP here for tickets and tell your friends!

https://t.co/YsQFxT2Ahj

Note the tube strike so do check on travel!

[Khash Faiz @khashfaiz]

@cwodtke solution i.e. with less bias.

[Khash Faiz @khashfaiz]

@cwodtke solutions and testing to then come back to this
*Explore solutions (not just take one idea - the most obvious one - and run with it) on a high level end-to-end; low-fidelity thinking; normally comes with sketches
*Evaluate a solution without trying to affirm their own …

[Khash Faiz @khashfaiz]

@koker_szpaner Interesting parallel

[Khash Faiz @khashfaiz]

Hahaha not surprising at all! We've been overindexing on delivery for years. I personally get pushed by PMs to put pressure on designers to churn sh*t out cos we can't have engineers sitting on their bottoms doing nothing 🙄

[JustAnotherPM | Sid @JustAnotherPM]

𝗦𝗵𝗼𝗰𝗸𝗶𝗻𝗴: 80% of product features are rarely or never used.

A 2019 study (by Pendo) found that 80 percent of features in the average software product are rarely or never used.

As a product manager, this statistic hit me hard. Creating solutions that add value to the user's lives is my primary responsibility. And if users are not using my solutions, I have failed as a product manager.

Let's understand what leads to such failures, and how we can avoid them

1️⃣ 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗢𝘃𝗲𝗿𝗹𝗼𝗮𝗱:
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: focusing on building 𝘵𝘰𝘰 𝘮𝘢𝘯𝘺 features without validating actual value and impact on users.

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: prioritize only high-impact features that solve critical user pains. Do 𝗡𝗢𝗧 build a solution that does not add value to the user (even if you have nothing else to do)

2️⃣ 𝗟𝗶𝗺𝗶𝘁𝗲𝗱 / 𝗻𝗼 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗼𝗳 𝘁𝗵𝗲 𝘂𝘀𝗲𝗿:
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: implementing features either based on 𝘶𝘯𝘷𝘢𝘭𝘪𝘥𝘢𝘵𝘦𝘥 𝘢𝘴𝘴𝘶𝘮𝘱𝘵𝘪𝘰𝘯𝘴 or 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 𝘢 𝘥𝘦𝘦𝘱 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥𝘪𝘯𝘨 𝘰𝘧 𝘵𝘩𝘦 𝘶𝘴𝘦𝘳.

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: Invest time in 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥𝘪𝘯𝘨 𝘶𝘴𝘦𝘳 𝘯𝘦𝘦𝘥𝘴 (via user research/interviews) and 𝘷𝘢𝘭𝘪𝘥𝘢𝘵𝘪𝘯𝘨 𝘢𝘴𝘴𝘶𝘮𝘱𝘵𝘪𝘰𝘯𝘴 (via experiments, prototyping, etc.)

3️⃣ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗶𝗻𝗴 𝗱𝘂𝗲 𝘁𝗼 𝗽𝗿𝗲𝘀𝘀𝘂𝗿𝗲 𝗼𝗿 𝗙𝗢𝗠𝗢
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: building solutions due to pressure from HIPPOs or FOMO of a competitor, without caring for the user.

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: focus on 𝘢𝘴𝘬𝘪𝘯𝘨 "𝘸𝘩𝘺". Do NOT build anything unless it 𝘢𝘭𝘪𝘨𝘯𝘴 𝘸𝘪𝘵𝘩 𝘶𝘴𝘦𝘳 𝘷𝘢𝘭𝘶𝘦 𝘢𝘯𝘥 𝘤𝘰𝘮𝘱𝘢𝘯𝘺 𝘨𝘰𝘢𝘭𝘴.

4️⃣ 𝗠𝗶𝘀𝗮𝗹𝗶𝗴𝗻𝗲𝗱 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: poor prioritization leads to building features that don't solve user needs or contribute to product's goals. These features increase tech debt and add to the cost of building and maintaining a feature.

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: create foolproof prioritization methodologies. Focus on testing and validating first, scaling second. Take risks, but never compromise on impact. Regularly reassess and iterate on priorities.

5️⃣ 𝗟𝗶𝗺𝗶𝘁𝗲𝗱 𝗲𝗱𝘂𝗰𝗮𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝘂𝘀𝗲𝗿𝘀
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: not providing adequate communication and education to users about value of the new features.

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: market features effectively, helping users understand how it solves their problems.

6️⃣ 𝗦𝘂𝗻𝗸 𝗰𝗼𝘀𝘁 𝗳𝗮𝗹𝗹𝗮𝗰𝘆 / 𝗼𝘃𝗲𝗿𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗶𝗻𝗴
𝗠𝗶𝘀𝘁𝗮𝗸𝗲: continuing to invest in features that show little or no impact

𝗜𝗻𝘀𝘁𝗲𝗮𝗱: invest time in setting the right success criterion, measure performance regularly, iterate or consider killing features that aren't meeting expectations

What would you do to ensure what you build will be used by the users?

[Omid Djalili @omid9]

Incredible video. Afghan dad jokingly says school is only for boys. Watch his remarkable daughter - who can’t be more than 5 or 6 years old - respond with these arguments.

Afghan girls have been denied access to schools and universities. This little girl's courage represents the collective voice of countless Afghan girls who yearn for equal educational opportunities.

As an advocate for girls' education the father's teasing is simply to highlight an important message: that the Taliban - another backward regime - are harming the people of his country.

It’s time the world is done with them.

Ditto the “Islamic” Republic in Iran #regime

[Edison Thrustwell @EdisonGPT]

Okay just so ya know, here’s a partial list of all the privacy intrusion you agree to when you use Mark Zuckerberg’s friendly thought police app. A thread…🧵

[Khash Faiz @khashfaiz]

@andybudd @abookapart Can't tell if this book makes me happy or sad

[Khash Faiz @khashfaiz]

I'm finding it so hard to stomach how people are still giving Facebook / Meta a chance! Using Thread is not going to improve anything in the grand scheme of things

[Peter Yang @petergyang]

70 million sign ups just 24 hours after launch.

I spent time studying why this app became the fastest growing consumer app ever.

Here's what I found 👇