Replying to @BattlefieldComm
@BattlefieldComm hi, I really enjoy this game and noticed some issues, maybe you would like to look into it:
- when shooting from prone position and you have some grass in front, the bullets ricochet
- when crates drop, the items show for a second then they disappear;
1
21
In the recent years a lot of negative things have been brought to light about China, but the way it innovates and pushes products, bravo!
24
24 of march and noticed that so many courses on @udemy are being removed from my learning paths. What is going on? Does anyone know?
27
The way we communicate in the workplace affects how our ideas are received. Many common phrases—like “Sorry to interrupt” or “This might be a stupid idea”—may seem harmless but can weaken our message, and make us appear less assertive.
linkedin.com/pulse/breaking-…
21
Sergiu Naslau retweeted
Looking to kickstart or advance your UX career? This interactive course is designed for you!
Sergiu Naslau retweeted
Simplify your #productmanagement process with @davidavpereira’s Product Roadmap Miroverse template, designed for product managers and #agile teams. mirohq.click/m
I need help! UX/UI
Does anyone know any pattern libraries where I could see behaviours (android/ios) for drop-down, calendar, and other details?
4
38
Sergiu Naslau retweeted
"You don't hire for skills, you hire for attitude. You can always teach skills."
—Herb Kelleher
Sergiu Naslau retweeted
Design is not a formula, it’s an odyssey: replacing the Double Diamond buff.ly/3OGm3Ky
Sergiu Naslau retweeted
Excellent UX Research Cheat Sheet! 🚀🔖
User research can be done at any point in the design cycle. This list of methods and activities can help you decide which to use when.
Overview:
User-experience research methods are great at producing data and insights, while ongoing activities help get the right things done.
Alongside R&D, ongoing UX activities can make everyone’s efforts more effective and valuable. At every stage in the design process, different UX methods can keep product-development efforts on the right track, in agreement with true user needs and not imaginary ones.
The chart below describes UX methods and activities available in various project stages.
UX ACTIVITIES IN THE PRODUCT & SERVICE DESIGN CYCLE
DISCOVER
METHODS:
- Field studies/user interviews
- Diary studies
- Stakeholder interviews
- Requirements & constraints
- Sales & support interviews
- Support call monitoring
- Competitive testing
ACTIVITIES:
- Find allies
- Talk with experts
- Follow ethical guidelines
- Involve stakeholders
- Hunt for data sources
- Determine UX metrics
EXPLORE
METHODS:
- Competitive analysis
- Design review
- Persona building
- Task analysis
- Journey mapping
- Human-centered design
- Design diversity exploration
- Pluralistic walkthrough
- Prototype feedback & testing
- Write user stories
- Card sorting
ACTIVITIES:
- Follow Tog's principles of IXD
- Use evidence-based guidelines
- Design for universal access
- Give users control
- Prevent errors
- Improve error messages
- Provide helpful defaults
- Check for inconsistencies
- Map features to needs
- Make software updating easy
- Plan for repair and recycling
- Avoid waste
- Consider diverse contexts
- Look for perverse incentives
- Consider social implications
TEST
METHODS:
- Qualitative usability testing
- Training research
- User group outreach
- Social media monitoring
- Forum post analysis
- Benchmark testing
- Accessibility evaluation
- Test instructions & help
ACTIVITIES:
- Protect personal information
- Keep data safe
- Deliver both good and bad news
- Track usability over time
- Include diverse users
- Track usability bugs
- Make training information
LISTEN
METHODS:
- Surveys
- Analytics review
- Search-log analysis
- Usability bug review
- Feedback review
- FAQ review
- Conference outreach
- Q&A at talks and demos
ACTIVITIES
- Pay attention to user sentiment
- Reduce the need for training
- Communicate future directions
- Recruit people for future research
View the full details: nngroup.com/articles/ux-rese…
By @NNgroup
#ux #uxdesign #ui #uidesign #productdesign #userexperience #webdesign #psychology #research #uxresearch #usertesting #usability #uxmethods #prototype #designresearch #webdesign #mobile #users #uxstrategy #productmanagement #business #startup #agile #mvp
Sergiu Naslau retweeted
The PRD is not a static document.
It's a living, breathing reflection of the team's progress.
The goal of the Product Requirements Document (PRD) is clarity. So at each and every step, aim to increase the resolution of the image.
𝗦𝘁𝗮𝗴𝗲 𝟭 - 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴
For big rocks for your next planning cycle, I recommend you write the initial speclet that will become the PRD during the planning cycle itself.
The planning cycle is a time really expand the aperture of the problem space your product team considers.
For a whole quarter or half, you’ve been focused on a narrow set of features. So planning is the time to widen your problem space aperture once again.
𝗦𝘁𝗮𝗴𝗲 𝟮 - 𝗞𝗶𝗰𝗸𝗼𝗳𝗳
Once a problem has made its way through the planning phase and you feel confident in the problem to solve, it’s time to move on to the solution phase.
This where the PRD gets detailed. The PM should put their napkin drawing together, but then the design team should be willing to blow the whole thing up.
Many PRDs end their evolution here. But I say: there's actually three stages to go.
𝗦𝘁𝗮𝗴𝗲 𝟯 - 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗥𝗲𝘃𝗶𝗲𝘄
If the design team ends up just building a UI for the sketch the PM had, then the resulting PRD needs very little change.
But, ideally, the team should feel empowered to totally change the product solution. In those cases, then you need to update the PRD.
That's why I think it's so important to approach the PRD as living: it helps you 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 explore the solution space, instead of just go with what leadership or the PM said in the second draft.
𝗦𝘁𝗮𝗴𝗲 𝟰 - 𝗟𝗮𝘂𝗻𝗰𝗵 𝗥𝗲𝗮𝗱𝗶𝗻𝗲𝘀𝘀
So after you’ve written the final steps of the PRD about risks and mitigation, the product should go through a final evolution.
Engineering should also get their hand on the PRD and comment the heck out of it.
Usually, this will bring up several areas that team has to re-imagine.
𝗦𝘁𝗮𝗴𝗲 𝟱 - 𝗜𝗺𝗽𝗮𝗰𝘁 𝗥𝗲𝘃𝗶𝗲𝘄
The final step is after you launch. Add a link at the top to your results review document.
If you actually built a big rock feature, then it will have moved the metrics and transformed the user experience. Many times in the future, someone in the company will be explaining the feature or looking into it.
For all those folks, it really helps to go back and understand why the feature was built. They’ll go to the PRD for that. So it’s great to also have a link to the results later.
𝗧𝗵𝗮𝘁'𝘀 𝘄𝗵𝘆 𝘁𝗵𝗲 𝗣𝗥𝗗 𝗰𝗮𝗻'𝘁 𝗯𝗲 𝗼𝗻𝗲-𝗮𝗻𝗱-𝗱𝗼𝗻𝗲.
Sergiu Naslau retweeted
Google just released 10 free courses on AI.
No payment needed.
Here are 10 FREE Google courses to master AI in 2023.
[ Thread ] 🧵
When @DisneyPlus is trying to be smart and subtle, but the only thing that it manages to do is to be annoying
29
Sergiu Naslau retweeted
Mindfulness is the perfect awareness technique to employ when a conflict arises and wreaks havoc on our brains. hbr.org/2015/12/calming-your…






















