Academy is open. New beginner lessons every week, free.
Lesson 2 of 6 · beginner

Brainstorming the redesign with the team

Product, design and engineering talk through six early variants, and how to prompt your way out of stuck.

Prefer to listen? This video is also an episode of the CodeYam podcast: Brainstorming on a Personal Website Redesign with the CodeYam Team.

In this lesson8 chapters
  1. 0:00Six variants and where I am stuck
  2. 1:25Fonts that feel like AI defaults
  3. 2:05Make a Frankenstein of what you like
  4. 4:02Decide the hierarchy before the layout
  5. 5:13Rate every mock, then ask for crazy
  6. 7:55Communicate the feeling, not the detail
  7. 8:37Does taste still matter with AI?
  8. 13:05Pretend you work at Pixar
TranscriptClick any timestamp to jump the video there.
0:00

Six variants and where I am stuck

I am redesigning my personal website with CodeYam. The current live site is pretty simple and straightforward, and I previously built it using v0. I have generated design mocks that I am not super happy with yet, so I want Dani's feedback from a design perspective and Jared's on how I can get better at prompting for the changes I want. There are six different variants, all with different layouts, designs and copy.

1:25

Fonts that feel like AI defaults

One thing I noticed while riffing is that certain fonts feel very commonly used by AI, and I went back and forth with Claude a little because there are certain defaults. I was trying to get something that felt more custom and original. One variant feels straight up professional but very dry, another feels a little more fun, and having something that feels beautifully designed is exciting to me.

2:05

Make a Frankenstein of what you like

Dani's advice is to create a Frankenstein of all the things you like from each one. On a personal website she likes seeing a picture of the person. Which one to choose really depends on who you want this to be for. Do you want to present yourself as a CEO and founder first, or as someone who works remotely and can work from anywhere?

4:02

Decide the hierarchy before the layout

Figure out the hierarchy of what you want people to see. Is the site about CodeYam, which is your current project, or is it a CV of the work you have done before, or is it more about you? Think about who you want to see the website first, whether that is customers or VCs, and lay out the sections based on that.

5:13

Rate every mock, then ask for crazy

Jared's approach is to go through each one and rate it, and say what you like or don't like about it. You don't have to be specific, and saying you hate all of it is information too. Then ask the AI to be crazy for a few and explore ideas that have nothing to do with what you proposed. If eight mocks are generated at a time, take two or three to follow feedback, two or three as variations of your favourite, and two or three to be wacky so you discover something new.

7:55

Communicate the feeling, not the detail

Communicate your emotions, because at the end of the day it is going to feel right or not. Your attention gravitates towards something and that something is either good or bad, so describe that as best you can. As soon as I saw this I saw the photo and did not like the photo, or the font, or the colours, or the layout. Capture the first impression rather than trying to be technical about it.

8:37

Does taste still matter with AI?

In the era of AI, most of what it delivers is well designed by default, so taste is more subtle than whether something is well designed. Dani's answer is to follow your intuition and trust that what you like will work, and to gather a lot of references rather than starting from a blank page. Jared's is that calling it taste is a little off, because it is really about having more ideas about how to achieve something you like, and that is something AI can help you explore.

13:05

Pretend you work at Pixar

One thing I have done in this vein is a little silly. Rather than pointing at specific websites, I ask it to pretend it works at Pixar, or to be a designer in the Steve Jobs heyday at Apple, and approach my personal website that way. It gives a bit of direction while leaving it open enough to get genuinely different outcomes. Dani adds another version of the same trick, which is to put the AI in the designer's shoes and ask what questions it would ask you before building the site.