Why Your Project Needs a Concept

Last week at work, we were planning a new episode (aka a quarter). This involves setting our objectives, key results, and brainstorming initiatives to reach those goals.

Often, we want to improve something. A metric, a part of the customer journey, or something about how the app works.

And often, we’ll pick a few initiatives to address some known customer pain points. We make some iterative changes, and then move on to other projects.

For parts of the product that persist—sign up flows, or core functionality—we tend to do this quite often. Each quarter we make several changes based on customer feedback or user testing.

The discussion we had last week was about at what point we need to step back and think about where we’re going, instead of continuing to iterate on smaller pieces.

For long-term projects, you need a concept.

What is a Concept Car?

For those who aren’t familiar with the car world, a concept car is a prototype of what a manufacturer envisions for their cars of the future. 

It’s unlikely to ever make it to production, but often it will feature the early versions of new parts and systems that the manufacturer is working on, or some tech they’ve adopted from their racing teams or other technology industries.

Source: https://www.mercedes-benz.com/en/vehicles/passenger-cars/concept-cars/

The Mercedes concept car shown here is one such example (video here).

The Tesla roadster is another example

Source: https://www.caranddriver.com/tesla/roadster

Tesla is a bit of an exception, as their concepts have historically been much closer to the production version of the car than traditional manufacturers, but the purpose of the concept is the same.

What’s The Purpose of a Concept Car?

A concept car is a means of communicating the future of a project, or even a company.

The concept car serves to give a vision of what future cars from that manufacturer may look like.

Why is that important? 

Consumers want to be excited by what’s coming from a brand. It helps drive loyalty, and create brand awareness and buzz, and gets people excited about continuing to be part of that brand’s journey.

It also helps employees. Those working on the project get to explore new areas, think differently about how they build cars, and work on an exciting project. 

Employees who aren’t working directly on the project can also get excited about where the company is going, and what they will be producing. They can show their friends and family, and be proud of where they work.

A concept car is a means of communicating internally and externally, but it also has other applications.

A Concept Car is a List of Assumptions

Forcing engineers to put things into a physical form also forces people to clarify what they envision, and test their assumptions.

If a company claims that “this concept is a vision of where we’re going with our self-driving car”, it forces engineers and managers to confront the question: “what’s left before this car can be self-driving?”

More trivial things become clearer too: design cues that were broad in sketches become defined. Details like interior materials, seating layout, lighting design—these all become clear.

The process of building the concept becomes a process of clarification amongst all those involved, something that is critical in reaching a final product.

This process also brings to light a list of assumptions. 

  • “We’ve chosen a four-seat layout for our luxury concept, because most of our customers in this segment don’t need five.” How do we know that? What can we do to find out?
  • “We believe this styling choice is the future of our cars, and our customers will love it.” Do they? Can we get feedback from customers now?

Why Does This Matter Outside of Cars?

A concept car is easy to imagine, because most of us have seen one at some point or another.

But the same idea applies to your idea, your project, or your company.

You need a concept to communicate what your vision is. It becomes the focal point of discussions around details, assumptions, and experiments.

You can only debate details when you have a picture. 

You can only state assumptions when you’ve agreed upon a decision and the rationale.

And you can only run tests and experiments once you have the list of assumptions.

Iterative improvements are a great way to continue making progress. But at some point, you need to have a concept.

To Summarize

Concepts are a useful tool for:

  • Clarifying details and assumptions, and building experiments to test those assumptions
  • Getting customers excited about the direction of the company, and building brand awareness and loyalty
  • Getting employees excited about what they are working on, and being part of the company

For all your major projects, you should have a vision of what you believe the future looks like: your concept car.

Want to get my latest book notes? Subscribe to my newsletter to get one email a week with new book notes, blog posts, and favorite articles.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.