Designing Is Only Half The Job

Good ideas only create value when other people understand them.

Software designers regularly explain their work to:

• teammates,
• managers,
• community partners,
• users,
• developers,
• funders.

Your ability to communicate your thinking is often just as important as your technical ability.

Explaining Your Thinking

When presenting a design, avoid simply describing what it does.

Instead, explain why you designed it that way.

For every important decision, ask yourself:

• What problem does this solve?
• What alternatives did we consider?
• Why did we choose this approach?

People are usually more interested in your reasoning than your diagrams.

Trade-Offs

Every design involves compromise.

For example:

“We simplified the interface because our users were often overwhelmed.”

“We delayed this feature because another requirement was more important.”

Good designers acknowledge trade-offs rather than pretending perfect solutions exist.

Defending Decisions

Sometimes people disagree with your recommendations.

That is healthy.

Respond with evidence rather than emotion.

Good evidence might include:

• user feedback,
• accessibility considerations,
• project goals,
• technical limitations,
• community partner input.

Presenting To Community Partners

Remember your audience.

Avoid unnecessary technical language.

Explain ideas clearly.

Connect every recommendation back to the challenge the organization is trying to solve.

People rarely remember every detail of a presentation.

They remember whether it made sense.

Communicating Uncertainty

Sometimes the honest answer is

“We don’t know yet.”

That is acceptable.

Good designers identify assumptions, acknowledge uncertainty, and explain how they would reduce that uncertainty in future work.

A Final Thought

A thoughtful explanation often matters more than a complicated diagram.

People trust designers who communicate clearly.