To balance vision and feasibility in product development, bring engineers in during wireframing to check what can be built and what it will take, before stakeholders see the product. This post is for product leaders and founders who have to show stakeholders a new software product. It covers product vision and feasibility: what a product vision is, what feasibility means, and who checks it. It also shows what each phase produced on two Gnar projects. It matters because a product shown to stakeholders has to be one the team can build.
Elizabeth Holmes learned it with Theranos. Billy McFarland learned it with the Fyre Festival.
You can't put toothpaste back into the tube.
Once you've gotten people excited about the next big thing, you better be able to deliver.
Now, imagine being Holmes' scientists or the organizing team for McFarland's Fyre Festival: "You told them we could do what?!" It's an impossible spot to be in.
A process that accounts for expectation setting, and brings the right team into the planning process at the right time, can be the difference between a successful product launch or a flop (or jailtime!).
What are the two extremes of product development?#
The two extremes are a visionary model, where a few people design the whole product with almost no outside input, and a bureaucracy model, where everyone's opinion is heard from the start.
There are two extremes to product development.
On one end, you have the Theranos/Fyre Festival model where product visionaries design the entire output with almost zero outside input. Then they hand off their plans to the team and expect perfect delivery.
On the other end, you have the bureaucracy model. Everyone's priority and opinion is heard from the beginning so you end up with…(checks notes)...nothing fast.
If you want realistic and impactful product development, you need to take a blended approach. Here's how we see it.

There are four connected phases that require varying degrees of technical involvement.
Discovery:
Discovery is about defining scope and should be led by the product and design teams. This phase is about understanding user needs and what is being solutioned for. The focus here shouldn't be on what will be built, but on the key user flows that need to be accounted for. Engineers involved should be prepared to play a passive role at this point, only gathering context to benefit future stages where they have greater involvement, while understanding that decisions here are being written in pencil, not pen.
Wireframe:
The wireframe phase is where the "how" starts to take shape. This is still led by product and design in the form of low-fidelity wireframes. It's also where technical involvement begins to increase. Product is still setting direction, but engineers should be looped in to assess technical feasibility and effort. That's especially important before stakeholder meetings. It's key that product, design, and engineering are aligned before stakeholders see what's being created. The limited involvement here isn't about gatekeeping. It's about being conscious of everyone's time and focus.
Design & Prototype:
This is where engineers and developers should be at peak collaboration. The design team should be trying to excite users and the technical team should be making sure a first look is setting the right expectations for both stakeholders and end-users. You don't want to show them a Rolls Royce when you know you can only build a Toyota given their time and budget. This is essentially the "application blueprint" that the development team will use to estimate the time and resources needed to build the solution.
Development:
Here's where the engineering team takes over. In an ideal situation, all parties (product, design, development, and stakeholders) have a shared vision and expectation for the output. That allows for optimal heads down work and progress. That doesn't mean collaboration ends, however. You still need regular check-ins and demos with stakeholders to ensure progress is meeting expectations.
What does the Scrum Guide say a Sprint Review and the Product Owner are for?#
The Scrum Guide (November 2020 version) says the purpose of the Sprint Review "is to inspect the outcome of the Sprint and determine future adaptations". It says the Product Owner "is accountable for maximizing the value of the product resulting from the work of the Scrum Team".
At the Sprint Review, the Scrum Team "presents the results of their work to key stakeholders and progress toward the Product Goal is discussed". That is the check-in and demo step from the Development phase above. Gnar's custom software development page says: "We build in fixed-price milestones, hard parts first. You see working software at every step".
The Guide also says what happens in the session:
- What the team and stakeholders do: "During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next".
- What kind of session it is: "The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation".
- What progress is measured against: "The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against".
The Guide also says part of the Product Owner's Product Backlog management is "Developing and explicitly communicating the Product Goal".
What did each phase produce on two Gnar projects?#
On two Gnar projects, discovery worked on user flows, wireframing produced screen wireframes, and design produced a design system or final design comps. One is the Abuser Registry built for the Massachusetts Disabled Persons Protection Commission (DPPC). The other is a Shopify app for Candlebuilders, a print on demand, drop ship candle manufacturer. Discovery comes first in both, and the Gnar post What a Software Discovery Phase Should Include covers that phase.
| Phase | DPPC Abuser Registry case study | Candlebuilders case study |
|---|---|---|
| Discovery | "meeting with the DPPC team to learn more about their users personas, user flows". | "define the user flows to enable merchants to design custom candles". |
| Wireframe | "wireframes were created to further define the content hierarchy on each screen on a weekly design sprint basis". | "designing app wireframes". |
| Design | "In parallel to wireframing, we created a unified design system and component library". | "final design comps for the web application". |
| Development | "build the next generation of the DPPC Abuser Registry". | "It was built with Ruby on Rails and integrated with Stripe for payments and OrderDesk for orders". |
The DPPC case study lists its product team as "a product manager, product designer, three software engineers, and an AWS infrastructure engineer".
Gnar calls the design and prototype "essentially the 'application blueprint' that the development team will use to estimate the time and resources needed to build the solution". The Candlebuilders case study says its design comps "facilitated a detailed estimate for the development effort".
On the Gnar Discovery and Design page, the prototype is described this way: "Clickable models of your key workflows that your team and stakeholders can experience firsthand".
How do a product vision, strategy, mission and roadmap differ?#
The vision is the product's overarching goal, the strategy is the path to it, the mission states why the company exists, and the roadmap is a plan for how the product is likely to change over the coming months. Roman Pichler calls the vision "the overarching goal" and the strategy "the path chosen to attain the vision". Marty Cagan says the mission statement tries to make clear "the purpose of the company". In The GO Product Roadmap (first published 25 November 2013, updated 11 November 2026), Pichler defines a product roadmap as "a strategic product plan that describes how the product is likely to evolve over the coming months". The two authors use the word slogan differently. Pichler's board says to "use a brief statement or slogan" for the vision, while Cagan writes that people who show him a vision are often "confusing a slogan about their purpose, with a product vision".
| Term | What the source says | Source |
|---|---|---|
| Product vision | "acts as the overarching goal guiding everyone involved in the development effort". | Pichler, The Product Vision Board |
| Product strategy | "the path chosen to attain the vision". | Pichler, The Product Vision Board |
| Mission statement | "The mission statement tries to make clear to anyone that might not know the purpose of the company, what that purpose is." | Cagan, Product Vision vs. Mission |
| Product roadmap | "A product roadmap is a strategic product plan that describes how the product is likely to evolve over the coming months". | Pichler, The GO Product Roadmap |
Pichler's page, The Product Vision Board, was first published on 10 May 2011 and last updated on 13 October 2025. He calls the board "a tool that helps you capture the vision and product strategy". Its Vision section, in his words:
- Vision: "Vision states your overarching goal, the ultimate reason for creating the product, and the positive change you want to bring about. Make your vision big and inspiring; use a brief statement or slogan; and ensure that the stakeholders and development team(s) support it, that it is shared".
In his Product Vision FAQs (first published on 17 August 2021 and last updated on 25 April 2022), Pichler writes: "If your vision describes the ultimate purpose for creating the product, you will have to complement it with a product strategy." On testing a strategy, his post 10 Tips for Creating a Product Strategy with the Product Vision Board, published 16 July 2014, says: "Carry out the test, analyse the feedback or data collected, and change your Vision Board with the newly gained knowledge".
In his post Product Vision vs. Mission, dated August 4, 2020, Marty Cagan writes: "The product vision, combined with the annual company objectives, drives the product strategy." He also writes: "A good product vision keeps us focused on the customer." He adds: "A good product vision provides the engineering organization with enough clarity about what’s coming in the next several years so they can ensure they have in place an architecture that can serve the need."
Pichler calls the roadmap "an important product management tool" that "sets expectations and aligns the stakeholders and development teams".
Pichler also writes: "Without a shared vision and an effective strategy, people are likely to pull in different directions, and the chances of creating a successful product are slim". At The Gnar Company, Discovery ends with a phased plan. The Gnar Discovery and Design page says: "Every Discovery engagement ends with a Milestone Project Plan that breaks your build into clear phases, each with a fixed price."
What makes an inspiring product vision statement?#
An inspiring product vision gives the people building the product a purpose, and it still has to be one the team can build. In his post 8 Tips for Creating A Compelling Product Vision, Roman Pichler says the product vision is "the reason for creating the product" and should "inspire" people. He also says it should be "short and sweet" and "easy to memorise and recite".
Pichler's Product Vision FAQs say: "A good, effective product vision fulfils the following six criteria:" One of them is "Inspiring: The product vision creates a purpose for the people working on the product. It provides motivation and guidance even if the going gets tough".
They also say: "The company vision should describe the purpose of the entire organisation, the reason why the business exists." Pichler adds: "The product vision, however, should communicate the ultimate reason for developing and offering a specific product".
In the 8 Tips post, published 8 October 2014, Pichler writes: "One of my favourite vision statements comes from Toys R Us". The company’s vision, he writes, is to "put joy in kids’ hearts and a smile on parents’ faces". He says what you need is "a vision that guides everyone involved in making the product a success: product management, development, marketing, sales, and support".
The TechFAR Hub, a US government guide site at techfarhub.usds.gov, publishes a field guide titled Create an Inspiring Product Vision. It says that, "to have an inspiring product vision, project teams must be clear on the problem that they want to solve!"
Its step 4 is titled "Get buy-in from stakeholders". It says: "Without that support, the most inspiring and beautiful vision will likely fail." The guide also says: "Visions that focus on adding value to the lives of others are often the best at inspiring stakeholders to hold fast to the true north that it establishes!"
The Gnar Company checks that a vision can be built in Discovery, a paid engagement. The Discovery and Design page says: "You have a vision." It also says Discovery "gives your team the research, design, and technical architecture to build the right thing before a dollar is spent on development." Every Discovery tier includes "a full Technical Architecture Blueprint", and the page adds: "This isn’t a surface-level feasibility check." This paid Discovery covers more than the discovery phase described earlier in this post, where engineers only gather context.
What does feasibility mean in product development, and who checks it?#
Marty Cagan of Silicon Valley Product Group defines feasibility risk as "whether our engineers can build what we need with the time, skills and technology we have". In his December 4, 2017 post he writes: "The Product Lead Engineer is responsible for the feasibility risk, and overall accountable for the product’s delivery".
| Risk | Cagan’s definition | Who Cagan makes responsible |
|---|---|---|
| Value risk | "whether customers will buy it or users will choose to use it". | "The Product Manager is responsible for the value and viability risks". |
| Usability risk | "whether users can figure out how to use it". | "The Product Designer is responsible for the usability risk". |
| Feasibility risk | "whether our engineers can build what we need with the time, skills and technology we have". | "The Product Lead Engineer is responsible for the feasibility risk". |
| Business viability risk | "whether this solution also works for the various aspects of our business". | "The Product Manager is responsible for the value and viability risks". |
Cagan says business viability risk "includes whether the product fits with the go-to-market or sales channel".
The 2017 post begins with the first edition of his book INSPIRED, which described successful products as "valuable", "usable" and "feasible". Cagan then writes: "While it’s easy to remember these three attributes, over the years I’ve come to believe that it was obscuring some pretty serious risks and challenges". He says it was also "making it too easy for product managers to focus on customer value and overlook business value". He adds that "in my new edition, I now explicitly call out the four types of risk".
IDEO's design thinking page (undated, as of November 2026) says: "Design thinking is a human-centered approach to solving complex problems. It integrates the needs of people, the possibilities of technology, and the requirements for business success". The page says design thinking "brings together three things": "What’s desirable for people", "What’s viable for organizations" and "What’s feasible with technology".
Gnar puts it this way: "Product is still setting direction, but engineers should be looped in to assess technical feasibility and effort". The Gnar Discovery and Design page says: "Our team includes both designers and engineers, so your prototype will be built with technical feasibility in mind".
How do teams build the trust this process needs?#
Teams build that trust with strong processes, such as great retros, and a shared vision that includes the stakeholder.
Culture Plays a Key Role
Trusting your team to make decisions that are going to impact your work can be challenging. But having strong processes in place, like great retros, helps to build that rapport and trust.
There's no one size fits all process for design and development collaboration. That depends on your organization. The one thing that is almost always true, however, is to make sure your team, including the stakeholder, has a shared vision. It's the upfront work of communicating, prioritizing, and making the right technical choices that create the best end products. Also, if you liked this article please subscribe to our newsletter


