Product vision vs. company mission: What are the differences, and how to align them

As a fairly recent discipline, product management adopts and adapts concepts from other disciplines such as marketing, design, the sciences, and engineering. This isn’t necessarily a problem, as the intention is always to bring clarity to the context we are operating in, and we should be in constant exploration and experimentation as we find best practices to support our role.

But borrowing expressions and concepts from other disciplines can sometimes lead to confusion. For example, “product vision” is an adaptation of “company vision,” but they represent two distinct concepts that should not be confused, but are important to keep aligned.

Today, I’ll explore the concept of product vision and how it works within the company context, with perspectives from some of the industry’s leading voices in product management.

What is a vision in business, and how to put one together

What is a vision?

To put it simply, a vision is the communication of a future that drives and inspires people. It should:

• Be aspirational, yet believable

• Give people a purpose and make them excited about seeing that vision become a reality

• Answer questions such as “Why does it matter?” or “Why should I fight for this cause?”

A good vision statement is a compelling narrative that inspires everyone towards the ultimate transformation you want to see in the world. Saying this, a good vision doesn’t have to be a statement at all. If you want to be really effective in communicating this vision, you can use a video, a mood board, a storyboard, or a combination of all three, depending on your audience.

Finally, let’s not forget that a good vision will also be memorable. People might not remember the whole story, but the underlying principles should remain in their minds as something to look up to.

How to put any type of vision together

When I think of a truly compelling vision, I think of Martin Luther King Jr.’s words: “I have a dream.” I certainly don’t think, “Please fill out this template.”

That said, inspiration rarely strikes like lightning, and frameworks can give you a helpful starting point (more on templates later). But before you reach for one, here are three ways to get into the right visionary mindset:

1. Be clear

You want your audience to visualize what the future will be like, and they want to see and feel the change you will be introducing into their lives. To clarify your vision, ask yourself:

1. Why does this change need to happen?

2. Who will be the people most impacted by the change, and how will the world be different for them?

Clarity also gives people confidence in your ability to lead the delivery of that vision and in their own ability to deliver it with you.

2. Do your research

The vision is meant to set the tone for the next five to 10 years.

While no one is expecting you to become a “future guru,” you should look at understanding:

• Who your market segment is and what they struggle with today

• What the external signals are telling you: How is the world around you behaving and responding (politically, economically, etc.)? What have other people been saying?

• Which trends are emerging, and what is the predicted impact they will have

• Why: why now, why you?

This research provides the groundwork and context you need to put a vision together, and it should also be part of your storytelling. A vision without context is meaningless.

3. Know what you stand for, genuinely

One thing most inspiring people have in common is clear values. The theory of basic individual values is a revised framework that allows for self-reflection on the values you hold, your underlying motivations, and your goals. These are meant to be values recognized across all societies, as they’re based on basic human needs: individual, societal, and survival. The image below illustrates the dynamic relationships between these values. 

If you could highlight what you value from the wheel, what are the underlying motivations? Do you see conflicting underlying motivations, such as “Conservation” and “Openness to Change”? What does that mean? Is it a matter of context? Is this contrast part of your story, and what makes you human? How will you use this information to build and communicate the vision?

4. Read & listen to what others have written and said

Don’t limit yourself to reading companies' vision statements; many inspirational leaders have used the power of their words to “shake things up.”

After each speech or statement, think about what the speaker said, how they said it, and how it made you feel: Did it move you, did it revolt you, did it make you feel passionate about what they said? Why?

Focus on the power that the words held and how someone who you’ve never met (and you’ll probably never meet) briefly held control of your emotions. How did they do that?

Now that you know about vision as a concept, let’s see how that relates to a company and to a product.

What are a company vision and company mission?

Companies have missions. Mission and/or purpose will be the terms used within the “about us” pages across most company websites.

Most of the articles you read about mission, vision, and purpose statements can contradict each other. Because the differences between them are so subtle, I understand that people get confused about this topic. At the end of the day, you should choose what works for you and your organization, but do avoid contradictions.

Having a product vision and a company vision is contradictory in the sense that if the vision’s “job” is to align an organization, you might create repetition, thereby wasting effort, or create a contradiction by sending the product team one way and the rest of the organization the other.

Now, you might be wondering whether “mission” is less meaningful or important than vision. Rather, the mission provides much of the context needed to carry out the product vision.

The mission statement defines the company’s purpose and should help every department make decisions by answering the question: “Are we staying true to our mission?”

One of my favorite company mission statements, for example, is HubSpot’s:

“There's this notion that to grow a business, you have to be ruthless. But we know there's a better way to grow. One where what's good for the bottom line is also good for customers. We believe businesses can grow with a conscience, and succeed with a soul—and that they can do it with inbound. That's why we've created an ecosystem uniting software, education, and community to help businesses grow better every day.”

Not only do they clearly state their mission, but they also help other organizations succeed at theirs in a sustainable manner. It’s almost like you automatically become a better business just because you hire HubSpot as your CRM platform.

How does a company mission impact the business day to day?

The impact of a company mission on strategy

Earlier, we mentioned the importance of clarity and context in setting a vision. Well, the mission is what makes Microsoft different from Apple, and how they both differ from Google for example.

Microsoft’s mission (2022): “Our mission is to empower every person and every organization on the planet to achieve more.”

Apple’s mission (2025): “Apple’s mission is to create technology that empowers people and enriches their lives.”

Google’s mission (2022): “Our mission is to organize the world’s information and make it universally accessible and useful.”

Even though all three companies produce similar physical and digital products that solve similar problems, we know they differ in the emphasis they give to each product area, how they’re known for different benefits and downsides, how they prioritize, and their overall style and approach to business. All these strategic differences stem from their missions.

For example, in considering their mobile strategies, we know the three companies have chosen very different approaches. Apple values consistency across customers, Google prioritizes making information accessible to everyone, and Microsoft focused on "A computer on every desk and in every home" until 2013—coming a little late to the mobile party.

The impact of a company mission on staffing

It is also worth noting that having a strong mission, supported by strong company values, serves as a good test of employee-organization cultural fit.

For example, more and more software companies identify themselves as mission-led or mission-driven. Traditionally, these have been organizations that seek to make a meaningful, positive impact on social and environmental causes, such as FreeFrom.

More recently, the definition has broadened to encompass companies that commit to serving their customers and their needs while playing a broader role in society.

Companies with strong, clear, and meaningful mission statements have also been able to hire and retain high-quality staff. Even if larger organizations may offer higher salaries, some people are motivated to join an organization that is actively making a positive difference in the world and refuses to grow at the expense of people and the planet.

Do you know what your company’s mission is? Did it play a part in your choice to work for them?

Who owns the company mission?

Normally, the CEO, or founding team, owns the company mission. They will not be alone in crafting a powerful mission statement; the marketing lead and/or team will support the CEO throughout the process, as the mission sets the pace both internally and externally.

Internally, the mission will provide context for the actions carried out by all teams and departments. Externally, however, the mission is what your customers will use to confirm that you are here to stay and that they can trust you. The marketing team will be best placed to help craft the statement and create holistic, consistent campaigns around it.

Product vision

For many tech companies, the products are the business.

These companies grow by expanding their customer base. The underlying business model depends on how the product is “consumed.” Their customer acquisition strategy lies in understanding who their customers are and what their customers need, so the product meets them and adds value.

Having a clear, well-contextualized, and inspiring product vision can be one of the most powerful mechanisms for uniting, motivating, and aligning an entire organization.

As the authors of the book “Product Leadership” put it, “The best product visions are timeless and disconnected from the technology they are built on.”

I have even seen this happen with early-stage businesses I have worked with. The underlying solution and strategy might change, and the business might iterate, but if the product vision stays the same, it means it is doing its job: providing product direction, regardless of its underlying technology.

What a strong product business does for your business and your customers

Aside from the vision fundamentals already considered, a strong product vision:

• Shows the transformation your product will bring to your customers and users: what the future looks like for them, not the details of how you get there

• Helps the organization  hire and retain talent, as people align themselves with that ultimate goal and want to be part of that change engine

• Guides the different strategy angles, from product discovery to go-to-market strategies

In SVPG, you can find great examples of what a strong product vision can look like.

You can also see how they don’t necessarily mention the underlying technology, but rather how the visuals complement the narration, alluding to how they propose to solve everyday issues and common friction points.

Who owns the product vision?

The product leader in the organization should own the product vision, but it will be far more effective to invite other organizational leaders to contribute to it, especially the CEO or the founding team.

You might be wondering how that affects the product managers, who might also own one or more product lines. They need to be actively contributing to and realizing the overall product vision, and it’s the product leader's responsibility to ensure this happens.

Based on the product vision examples provided above, you can identify that creating an efficient product vision that will influence the whole organization towards change is more than a “box-ticking” exercise. It is a decision that will define the work for the next five to 10 years (depending on the size of the organization), and so it should take time and consideration. Therefore, asking every single product person to elaborate on their own vision is an extraneous and expensive task.

How to build the ultimate product vision

As Marty Cagan puts it, the biggest inspiration for your vision comes from a deep understanding of your customers, your business, your products, and your data.

Then the product leader will need to conduct extensive outward-looking research—from understanding what is happening with the competition and adjacent businesses in the market, to looking out to the overall industry.

Once the product leader has gathered enough internal and external context, they should meet with the design team or design leads, who are the experts in storytelling.

The team can choose to share a video or a storyboard (depending on the time and skills available in the team), but the idea should be to clearly communicate:

1. Who

Who will be the main person or group of people affected by the transformation your product will bring?

• This is especially important to inform business models, pricing, and go-to-market strategies. Marketing a product to a student will be very different from marketing that product to a corporate business. .

2. How

How will the product add value to this person or group of people?

• You will need to be clear about how the product delivers value (i.e., its value proposition).

• Remember that this is meant to set a future vision, so technology will play a supporting, not a leading role. The technology used to support the product vision always communicates an idea and explains how the product, or combination of products, will add value.

3. The “wow” factor

The “wow” factor, introduced by Paavan Buddev in one of his talks at ProductTank London, explores the Hills and Storytelling framework to highlight the “special factor” only your organization can bring to the table.

4. Make it credible

Bear in mind that a lack of credibility is one of the biggest reasons people in the company set aside the product vision, either because people don’t believe it aligns with the company’s values, or because they lack the talent and skills, not just from a delivery perspective, but also from a strategic one.

I saw this happening once. I was working for a company that had released its product vision eight months before I started. The video should’ve been shown as part of my onboarding process, but it was shown only once and met with a lot of resistance from the employees. No one believed in the futuristic product vision because the business was known for its traditionalist views and approach to product. The vision was put away because it caused more problems than it solved.

Lucid's Product Vision Board, originally created by product management expert Roman Pichler, helps you describe your product vision and strategy. Capture key details about your target group, user needs, product features, and business goals all in one place.

Do all companies need a product vision? 

In most young software companies, the solution they offer is the main reason why they started a business in the first place, so the company mission and product vision will tend to be one and the same.

It is also worth considering that many of these young organizations’ focus will be on surviving a busy market space—spending a lot of time crafting the most eloquent company mission and product vision statements won’t be a top priority. It is important to know where the business is going so the small team can focus on what matters most, but there are very few alignment issues.

As the organization grows, a clear product vision plays a more significant role because there are more people and systems to align.

A lot of the product leaders I spoke with (including myself) confessed that they weren’t fully sold on the idea of a product vision until they needed something to rally their team(s) around a higher, more ambitious objective.

Most of us will be working in a company where the role of product isn’t well understood, and we will do our best to adapt certain product concepts as well as we can.

Overall, our goals will be to ensure that everyone involved in the product work feels as empowered as possible. Crafting a product vision can be an effective way to achieve this, especially for organizations undergoing transformation.

For example, if a team is tasked with some “uninspiring” work, such as integrations or internal tools, it might be useful to have a product vision for the team. Aside from providing this team with a higher goal and greater alignment with the company mission, having a vision will also help us negotiate higher budgets and prioritize this work.

It is worth noting that this can be a consequence of an organization that doesn’t clearly understand how all teams play a crucial role in delivering the ultimate vision, so there might be a need to revisit the team topology. However, this can be a lengthy and expensive process. While I believe there should be only one product vision for the company, I also know that some product people are sometimes tasked with playing difficult roles, and that we should use all available tools to help a team succeed.

How many product visions should a company have?

The biggest misunderstanding I see regarding product vision is when each product team is mandated to have a different one. From an organizational perspective, you can create a lot of confusion when there are multiple product visions, as other stakeholders struggle to see how everything fits together. It might also generate needless competition between teams. 

The biggest issue, though, is in what it does to the product manager (or product owner), as it adds unnecessary pressure to create and evangelize this product vision. Once again, this issue might be a consequence of a company that isn’t able to find alignment across its initiatives, and the pressure falls onto the product people in each team to find answers for themselves.

We know, however, that some organizations are larger than small countries, and so you need to find strategies to give control to the teams managing different product areas.

The product leader, in this case, would need to stay very close to the other product leaders to avoid misalignment in the product vision while ensuring their participation is considered, as they will have a better understanding of their product area and customers.

Great leaders should recognize when the product structure needs to be adjusted or optimized for business clarity, as it may be affecting the value it delivers to customers.

The answer to many product management questions is “It depends,” but having a single product vision per company (or brand) is ideal.

It is especially important to remember that the product vision isn’t solely for the product organization; it will also inform strategy, which is dependent on other parts of the business. Having more than one product vision is confusing and will lead to misalignment, causing prioritization problems later on.

Why company mission and product vision drift, and how to align them

Earlier, we mentioned that one of the biggest anchors for the product vision is the company mission, so you’d assume that it would be unlikely for misalignment to happen, but it does.

In this section, we will identify the biggest causes of misalignment and how to get teams back on the same page.

Mergers & acquisitions (M&A)

The company might decide that the most effective way to carry out its mission is to acquire other products and/or companies that excel at solving a specific problem.

Depending on the speed of the acquisition program, the size of the company acquired (or merged), or the number of companies acquired, we might find “a disturbance in the force.”

You can quickly identify how this can cause misalignment: Each acquired product will have its own vision, and each acquired company will have its own mission.

Experiment opportunity

It is important to state that mergers and acquisitions are potentially among the most delicate situations you will find. It is natural for people to feel threatened, and for every meeting and conversation to be met with some anxiety.

The product leader(s) and teams shouldn’t face this on their own, but it doesn’t mean they cannot play a big part in finding this alignment.

After the new company mission is confirmed and agreed upon (it might need to be adjusted or clarified, it is important that the product leader(s) confirm and agree on the product vision.

The product vision can be improved with the acquisition of better and improved technology, perhaps. It can also be an interesting opportunity to pursue an adjacent target customer, enabling the rest of the product team to grow as well.

It is important to reintroduce the product vision and the company mission during these times, as there may be many changes within the organization. People will look for direction, and these tools are the best for revisiting it.

Product discovery “gone too far”

Given a problem to solve, an empowered team will look for the most valuable and efficient solutions based on the provided context and constraints.

One of the best examples of this situation is the story of how AWS became what it is today. As the team saw itself unprepared to tackle scale, they found a solution to a problem many others in the tech industry faced: Setting up a new project from scratch every time, including adding a database component, was lengthy and expensive. The rest is history, but as many of you might know, this is very far from Amazon’s original mission.

I wonder if, when Jeff Bezos set out in 1994 with the mission of being “the everything store,” he also meant “cloud computing services”?

Alignment opportunity

The great thing about experiments is that they are experiments, i.e., they might not yield the results companies expect. But an experiment that yields further market opportunities can positively disrupt a business.

Experimentation is a great opportunity to assess both the product vision and the company mission. Normally, the question depends on the return on investment of pursuing something completely different from what the business initially set out to pursue. If the opportunity can be profitable, and there is trust in the business.

The product vision will grow as the company grows. Logically speaking, the larger the company, the greater its impact on the world.

Digital transformation

Digital transformation can be one of the longest processes for an organization, taking many shapes and forms. The angle I want to bring up is in the context of a product team leading a company transformation.

In this case, the product vision will be the main inspiration for the organization, and it can easily and quickly shift the mission statement, as the business might decide to serve different customers or markets.

Think of all the businesses that have gone through successful digital transformations, mainly around turning “paper-based” businesses into digital businesses.

Alignment opportunity

Product leaders can work closely with the commercial and financial teams and the CEO to ensure this new mission resonates with their customers and stakeholders. 

This exercise is a line to tread with caution, as this business might have to make some very difficult choices, such as prioritizing some customers over others and closing down product lines.

Gaining the confidence of the leadership team will be essential, while also conquering the rest of the business that might be wary of the changes. Having a well-designed product vision will definitely help with clarifying where the business is headed and how each product line will play a crucial part in carrying out the vision, supported by the renewed mission.

Final thoughts

Frankly, I haven’t been much of a fan of the concept of product vision.

Aside from not having seen it done properly, it is a theme that quickly descends into arguing around semantics, and I simply didn’t find it useful.

Nevertheless, staying true to a product-thinking mindset, I approached the theme with curiosity and humility, especially given how much content has already been published about it!

I went deeper, did the research, and took it to the experts, aka, the people in the product community.

I have learned so much, so I hope you stay open to learning and asking questions, no matter how dumb it might make you feel.