Why First Ideas Are Rarely The Best

Many students enter CIS3750 believing that good designers come up with brilliant ideas immediately.

In reality, experienced designers expect their first ideas to be incomplete.

That isn’t a weakness. It is simply how design works.

When you first begin working with a community partner, you know very little about the problem. As you ask questions, gather feedback, and develop prototypes, your understanding changes.

Good design evolves.

Your first prototype is not meant to be your final prototype.

Your first requirements document is not meant to be your final requirements document.

Your first timeline is not meant to be your final timeline.

Every version teaches you something new.

Feedback Makes Ideas Better

One of the greatest advantages of working with a community partner is feedback.

Feedback helps us discover:

• incorrect assumptions,
• missing requirements,
• unexpected user needs,
• better ideas,
• and opportunities we had not considered.

Rather than seeing feedback as criticism, try to see it as additional information. Every question someone asks about your design is an opportunity to improve it.

Designing Is Revising

Professional writers revise.

Architects revise.

Engineers revise.

Software designers revise.

Revision is not evidence that you failed.

Revision is evidence that you are learning.

Embracing Change

Sometimes change feels frustrating.

You may discover that an entire feature should be removed. You may realize an assumption was incorrect. You may need to rethink an entire workflow.

This is normal.

The goal is not to avoid change. The goal is to manage change thoughtfully.

Continuous Improvement

Every version of a design should answer one question:

How is this version better than the previous one?

Sometimes the answer is

• clearer,
• simpler,
• more accessible,
• easier to understand,
• or more aligned with user needs.

Small improvements accumulate over time.

A Final Thought

Perfection is rarely achieved in one attempt.

Good software grows through curiosity, feedback, revision, and continuous improvement.

Design is not a straight line.

It is a cycle.