The average project management tool has 47 configuration options before you create your first task. Notification preferences, workflow automations, field customizations, permission matrices, integration settings. The product hasn't done anything for you yet, but it's already asked you to make 47 decisions.
We think that number should be zero.
Configuration is a tax on users
Every configuration option exists because the product team couldn't decide what the right default should be. That indecision gets passed to the user as a “feature.” Custom fields? The product doesn't know what data you need. Workflow automations? The product doesn't know your process. Permission matrices? The product doesn't know your org structure.
This is backward. The user chose your product to solve a problem, not to configure a system. Every minute spent in settings is a minute not spent on actual work.
The Jira problem
Jira is the canonical example. It's powerful, configurable, and universally hated. Not because it can't do what teams need — it can do almost anything. The problem is that it can do almost anything ifyou configure it correctly. And configuring it correctly requires a dedicated administrator who understands both the tool and your team's workflow.
Most teams don't have that person. So they use Jira with the default configuration, which fits nobody's workflow, and everyone complains. The tool that can do anything ends up doing nothing well.
What zero-config actually means
Zero-config doesn't mean no customization. It means the product works immediately without any setup, and customization happens through use rather than through settings.
In Lova, this plays out in three ways:
- Board structure comes from conversation.You don't pick a template or configure columns. You describe your project and the AI creates a board that matches. If the structure is wrong, you say so and it adjusts. The “configuration” is just talking.
- Roles are inferred, not assigned.The person who creates the project is the Lead. Everyone they invite is a Member. That's it. No permission matrices, no role hierarchies, no access control lists. Two roles cover 95% of real-world team structures.
- Notifications are contextual, not configurable.You get notified about things that affect your work: tasks assigned to you, blockers on your tasks, comments on things you own. There's no notification settings page because the defaults are the right defaults.
The settings page is a code smell
In software engineering, a “code smell” is a pattern that suggests a deeper problem. We think settings pages are a product smell. Every toggle, dropdown, and checkbox on a settings page represents a decision the product team deferred to the user.
Some of those decisions genuinely need user input (language preference, timezone). Most don't. Most are the product team hedging: “We're not sure if users want email digests weekly or daily, so we'll let them choose.” The AI-native answer is simpler: send the digest when there's something worth reporting, and let the user tell you if it's too much or too little.
Adaptive defaults beat configurable options
The best configuration is the one the user never sees. Instead of asking users how they want the product to behave, watch how they use it and adapt.
- A Lead who checks the board every morning doesn't need a daily email digest. A Lead who hasn't opened the app in three days does.
- A project where tasks move quickly doesn't need stale-task alerts at three days. A project where work happens in weekly cycles might need a longer threshold.
- A team of three doesn't need the same notification density as a team of thirty.
None of these require configuration. They require the product to pay attention.
The competitive moat
Here's why this matters strategically: configuration is a switching cost for the vendor, not the user. When someone has spent 40 hours configuring Jira, they're not locked into Jira because it's the best tool. They're locked in because they can't face doing that setup again somewhere else.
Zero-config products compete on value, not sunk cost. Users stay because the product is good, not because leaving is painful. That's a harder position to defend, but a more honest one. And it means every improvement to the product makes it stickier, rather than every hour of configuration.
The products that win the next decade won't be the most configurable. They'll be the ones that just work.