Your app should know more than your user.
Design · 4 min read
I was working on an app where the user needed to set up an event. The first instinct, from both the client and from standard UX patterns, was to give people a blank form. Pick your type. Enter your date. Set a budget. Add your tasks. Build it from scratch.
We tried it. It felt like homework. The user opens the app, sees an empty screen, and has to figure out what goes where. For someone who's never planned this kind of thing before, a blank canvas isn't freedom. It's paralysis.
So we flipped it. Instead of asking the user to build, we asked them three questions up front. What kind of event. When. How many people. Then the app did the rest.
The wizard that does 80% of the work
From those three answers, the app generated a full plan. Timeline, task list, budget breakdown, suggested categories. All pre-populated. All based on real data the client had spent years compiling. The user's job wasn't to create anything. It was to review, adjust, and delete whatever didn't apply.
That's a completely different experience. Instead of staring at nothing and wondering where to start, you're looking at a structured plan that's already 80% right. You tweak it. You remove what you don't need. You add what's specific to you. But you're editing, not building.
The difference in how it felt was immediate. The blank canvas version made testers hesitate. The pre-populated version made them feel like the app understood what they were trying to do.
Your domain knowledge is the product
This only works if the data behind it is real. You can't pre-populate a plan with generic nonsense. The client I worked with had years of experience in this space. She knew what people needed, when they needed it, and how much it typically cost. That knowledge became the backbone of the setup wizard. Without it, the feature would have been useless.
If you're a subject matter expert building an app, this is your biggest advantage. You know things your users don't. You've seen every mistake, every shortcut, every thing people forget. An app that front-loads that knowledge into the first 30 seconds of use isn't just smarter. It's the reason people will pick yours over the generic alternative.
Editing is easier than creating
This applies beyond event planning. If your app involves any kind of setup, onboarding, or configuration, ask yourself: can the app do most of this work for the user? Can you ask two or three smart questions and then generate something useful from the answers?
People are much better at saying "that's wrong, change it" than they are at saying "I need to build this from nothing." Give them something to react to. Something to edit. Something that shows you already understand their situation. The best apps don't ask users to think. They think on the user's behalf, and let the user correct the parts that don't apply.
If your app opens with a blank screen, you're making your user do work that you already know the answer to. That's a missed opportunity.
Building an app where you know more than your users?
Book a free 20 minute call. Tell me about your idea. I'll be honest about whether this is the right fit. And if it is, we can start within the week.
Book a free 20 minute call