Product Principles for Development Teams

Jason Doherty
The Startup
Published in
10 min readJan 9, 2020

--

When bringing a product to market, you need a clear and compelling product strategy, a solid understanding of your market, a deep understanding of your customer problems, and a great team.

Ideally you have an Outcome Based Roadmap such that your vision, goals and outcomes (which are measurable changes in customer behavior) are clearly understood by the teams that are building your product.

Aligning your company’s mission, vision, principles, goals and outcomes to achieve the desired impacts in the market.

Your teams work iteratively, shipping a version of the product every 1 or 2 weeks to gather continuous feedback from customers and the market, and most importantly you measure progress towards your desired outcomes and your goals with every feature you ship. Did what we shipped work? Did it have the impact we wanted?

Daily Decisions

Photo by Jens Lelie on Unsplash

Once you start work on your shiny new product, you need to trust your team to make good decisions as they go. The team iterates on the product until the desired outcomes are achieved, or you learn that your ideas aren’t the right ones and you adjust and adapt based on feedback.

As Steven Bungay comments in The Art of Action: a strategy is not a plan. A product strategy is the

--

--

Jason Doherty
The Startup

Technologist and Product Leader who likes to build stuff