Presenting Design Work

When designers don’t think they need to share their work, don’t want to ask for feedback, and don’t want to make changes as a result of feedback, it shows that there is a problem in the design process.

The most important time to get this right is during your first presentation to a group or the first time a new stakeholder is involved. This is the crucial moment to teach people that they have a specific role and that you want them to contribute their expertise, not their opinions.

The clients are much happier overall. They know that they contributed and that their contributions were considered, and they’re able to understand the reasons behind the project team’s decisions, which gives them confidence in the team.

What you definitely shouldn’t present is an already-built design. Not only is it harder to make changes to something that has been built, but it also communicates to your audience that you are not listening to feedback.

The first job you might consider delegating is to have someone else manage the technology—not just setting it up, but also clicking through the presentation or navigating screens in the prototype as you take on the role of narrator. It’s easier to tell a convincing, clear story if you can focus on the people you’re talking to.

Note-taking is another

When I’ve seen designers ask for sign-off for this type of work without something visual to support it, they always end up frustrated when the client changes their mind after seeing the ideas represented in a more tangible form.

I suggest you never present things like this as standalone design work—only present how they affect a person doing a thing

CONCLUSION

IF I HAD TO SUMMARIZE my key points in a single presentation slide—well, I wouldn’t. I’d make five slides, each containing one strong point:

If you plan for your audience and give everyone a job, they’ll contribute their expertise, not their opinion.

If you show the end result, not your progress or process, your audience will understand wha

Rehearse out loud, even if it feels ridiculous. It’s an important presenting trick for your brain: when you’ve already heard yourself say something, it’s easier to do it again later on and sound more confident.

Some teams make the mistake of having only a few presentations, with the first being after work has been underway for some time. Don’t do this—people will feel like they aren’t being allowed to contribute, and their feedback can undo a lot of work.