2.3 Designing for Your User

Time: ~30 minutes

What You'll Learn

• Why design matters even for internal tools
• Simple rules that make any interface easier to use
• How to describe design improvements to your AI
• How to test whether your design works

Key Concepts

Design is not about making things pretty. It is about making things obvious. A well-designed app is one where people do not need instructions to use it.

Five Rules for Non-Designers

These five principles will handle 90% of your design decisions:

1. Labels should describe what happens, not what something is.

• Bad: "Submit"
• Good: "Send My Request"

2. The most important action should be the most visible.

• If the whole point of the page is to fill out a form, the submit button should be big, colorful, and obvious. Secondary actions (cancel, reset) should be smaller and subtler.

3. Group related things together.

• Name and email go together. Payment info goes together. Do not scatter related fields across the page.

4. Show one thing at a time.

• If your form has 15 fields, break it into steps. Three fields per screen feels manageable. Fifteen fields on one page feels like paperwork.

5. Tell people what just happened.

• After they submit: "Got it. We'll be in touch within 24 hours."
• After they delete: "Deleted. You can undo this for the next 30 seconds."
• After an error: "Something went wrong. Try again, or email us at support@example.com."

Describing Design Changes to AI

Be specific about what you want changed and why:

The submit button is too small and blends in with the page.
Make it larger, use our accent color, and add the text
"Send My Request" instead of "Submit".

This is much better than "make it look better."

Testing Your Design

The simplest test: hand your phone to someone who has never seen the app and say "figure out how to [the main task]." Watch silently. If they struggle, the design needs work. If they breeze through it, you are done.

How to Start

Tell your AI:

I want to improve the design of my app. Here are the pages:
[Describe or share screenshots of your current pages]

Apply these principles:
- Clear, action-oriented labels
- Most important action most visible
- Related fields grouped together
- Show success/error messages after every action

Walk me through the changes one page at a time.

What's Next

In lesson 2.4, you will learn how to maintain your app over time -- handling bugs, adding features responsibly, and knowing when to stop.