Quick note from me

In recent years, conceptual projects gained a bad reputation. They were seen as fake, not real work, and lacking business context. Designers were often told to find freelance clients or design for NGOs instead, to simulate “real” constraints.

That narrative is quietly dying. With AI, no-code tools, and fast prototyping, the line between concept and real work has blurred. Designers are already shipping tiny AI apps to the App Store. And honestly, you don’t even need to ship. You don’t need permission, a brief, or approval to show strong thinking.

Conceptual projects will matter more than ever in an AI-driven industry. But the main question for your job search is this: How do you create conceptual projects that give you an advantage, instead of just filling space in your portfolio?

Story outline

  • Level 01: Why conceptual projects are becoming normal

  • Level 02: Think like a founder, not only a designer

  • Level 03: Look for real problems, not a brief

  • Level 04: Create innovative solutions

  • Level 05: Start building and using AI

  • Level 06: Make it stand out visually

Level 01

Why conceptual projects are becoming normal

Conceptual projects used to be about showing that you could follow a design process as someone just starting out. Designers learned the Double Diamond in bootcamps, used brief generators, and presented everything as a long report style case study on Medium.

That time is over. Today, conceptual projects are for any designer. They’re about showing innovation, problem thinking, building skills, and business mindset.

What matters more now is:

  • Can you spot real problems?

  • Can you design and build?

  • Can you use AI intentionally?

  • Can you think about the product, not just the design?

  • Can you move without waiting for perfect conditions?

A simple, built app that a hiring manager can actually use beats a polished case study with zero ownership every time.

Level 02

Think like a founder, not only a designer

Most designers start conceptual projects from screens or random ideas. They either build for fun, which is fine, or jump into solving problems that aren’t important or well defined.

Think about starting from business and strategy. Founders don’t ask “what should this look like?”. They ask what problem is worth solving and why.

Good starting points:

  • A real problem you experience yourself

  • A business friction you’ve noticed in a product you use

  • A gap between what a product promises and how it actually works

If you want to target a specific company, lean into strategic constraints, not visuals. Examples:

  • A product works well in one market. What breaks in another?

  • A feature serves power users. What about beginners?

  • A strong Western product. How would it need to change for Asia?

This is exactly what Yutong and Yunan did. They didn’t redesign Airbnb for fun. They localized it for the Chinese travel context, adapting flows, expectations, and behavior. That’s not just design thinking, but a founder mindset. Even though this example is older, this strategy is still relevant in today’s market.

Level 03

Look for real problems, not a brief

Brief generators are fine for practice. But if you want to show real passion and mirror how products are actually built, think like a scientist, not a student.

Look for real problems that genuinely resonate with you:

  • Look outward: follow the news, read research papers, dive deep into one industry, study statistics, notice where things consistently break or feel outdated.

  • Look inward: pay attention to your own friction. What annoys you repeatedly? What do you keep hacking around?

Then go deeper than surface symptoms and ask:

  • What exactly is the problem?

  • Why does it happen?

  • What does it block or prevent?

  • What triggers it?

  • Who feels it most?

If you’re redesigning an existing product:

  • Read Reddit threads

  • Scan App Store reviews

  • Look at complaints and support conversations

  • Identify patterns, not opinions

Don’t focus on the UI, like a cluttered checkout. That’s not the problem, it’s a trigger. The real problem is that users can’t complete a payment and, as a result, abandon their shopping carts.

Level 04

Create innovative solutions

Creating products by copying existing patterns is easy, and with AI it will only get easier. That’s exactly why companies will care more about innovation. When everything looks the same, businesses compete on price. Innovation is how they stand out.

Conceptual projects give you something rare: freedom
No legacy systems, roadmap, internal politics. Unless you define constraints yourself, you can explore anything. And yet, most conceptual projects still show obvious solutions we’ve seen many times: Spotify redesigns. These projects don’t prove that you can handle ambiguity or lead a complex problem.

As the VP of Design at Perplexity put it: Doing homework is easy. Doing something on your own is rare. That’s why, when hiring juniors or interns, he looks specifically for conceptual projects that show original thinking.

“If there were no constraints involved, hiring managers expect the designs to be as innovative as possible, and will be frustrated if they are not.”

How to approach innovation:

Once you understand the problem space:

Then go one step further. Strong conceptual projects feel slightly uncomfortable:

  • They challenge defaults

  • They question assumptions

  • They use AI in ways teams are still hesitant about

  • They explore how to bring more value

Level 05

Start building and using AI

Your goal is not a perfect case study story. We’re past portfolios that describe every step from research to delivery. Businesses care about speed, value, and leverage. With AI available to everyone, the bar is higher.

Companies don’t just look for designers who can design. They look for designers who can build, prototype real experiences, and use new tools to create value for users and the business.

For conceptual projects, don’t be afraid to build:

  • Use tools like Cursor, Claude, Figma Make, Lovable

  • Prototype real interactions and flows

  • Focus on moving from state A to state B

  • Design the experience, not just screens

Prioritise momentum over perfect process:

  • Bounce between problem, build, test

  • Share early work on LinkedIn or Twitter

  • Ask for feedback publicly

  • Ship imperfect versions

  • Show learning in motion

Conceptual projects feel real when people can actually use them.

Level 06

Make it stand out visually

With AI, the limits are smaller and the time to build is shorter. Anyone can now create a basic mockup or prototype. PMs, developers, founders. Give them a decent prompt and an AI tool and they’ll ship something usable.

So where is the designer’s edge?

Visual judgment, craft, contextual taste

If anyone can build something, designers need to build something better. That’s where outstanding visuals still matter:

  • Clear hierarchy and focus

  • Strong interaction decisions

  • Cohesive visual language

  • Craft that fits the product and audience

A well-designed conceptual project is easier to notice in a quick portfolio review. Hiring managers skim first. Long paragraphs come later, if at all. Visuals create the first hook. It’s aesthetic bias so use it intentionally.

🫶 Together with Framer

Betting on Framer

I’ve been thinking a lot about where web design tools are heading.

  • Less handoff

  • Less friction

  • More ownership for designers

Framer sits right in the middle of that shift.

You design, write, iterate, add motion, and publish from one place. No exporting, no rebuilding, no waiting for someone else to make it real.

That’s why I keep coming back to Framer. It aligns with how designers actually work today.

Explore Framer here

Want help with your UX portfolio? 🎁

  1. Build your UX Portfolio with this course

  2. Book a portfolio strategy call with me

Questions? Reply directly.

Keep designing
Aneta

Keep Reading

No posts found