Website improvement, start thinking from "not doing"!

Website functions are becoming more and more powerful, team ideas are emerging one after another, and new technologies are exciting, but how to weigh various ideas to avoid wasted resources and damage to user experience?

Project prioritization is crucial. An effective strategy is: Before deciding to add new features, ask yourself (or the team): What happens if I don't do this now?

When adding new features, we tend to get caught up in detailed discussions:

• Key Performance Indicators (KPI)/Objectives and Key Results (OKR): What is the return rate for this feature?
• Performance: Will this new code improve or reduce performance metrics?
• Accessibility: Can all users use this new feature?
• Maintenance: Do we have the resources to maintain this new component?
• User Experience: How will this affect visitors?

These discussions are necessary, but sometimes overwhelming. Before delving into these aspects, asking "what will happen if you don't do it" can help us prioritize and necessity in tasks.

For example, we envision three ways to improve modal boxes:

Example 1: Delay loading modal box content

What happens if we don't remove the initial page load of the modal box now? Visitors will download content they may never request, and may even block other key content. We should prioritize this and explore the path forward.

Example 2: Add animation when modal box is closed

What happens if we don't add this animation now? Without animation, the closing experience may be a bit stiff, but it may not? Will this change the conversion rate? Will readers stop visiting our website? Probably not. Let's keep the priority, move it to the non-emergency/non-important section, and rethink it if there is bandwidth in the future.

Example 3: The close button is missing aria-labels and the keyboard focus cannot be retained in the modal box.

What would happen if we don't solve this problem now? Stop reading this article, hurry up and do it!

There are many ways to improve the website, and it’s just a question asked in advance and helps drive discussions around priorities and priorities.

Extra tip: Review your website and ask: What happens if we don't keep this component? Can this SVG animation really bring happiness? (This is a trap…of course, it can!)

This is by no means saying no to every request. If we don't iterate and try new things, our website will become stale, slow and outdated. But it's another way to communicate with your team (or your inner monologue) and explore the impact of new code on your beautiful, fast, accessible website.

The above is the detailed content of Maybe Nothing. For more information, please follow other related articles on the PHP Chinese website!