​​I use this canvas at the initial stage of thinking through an initiative or feature. For example, does it need permissions or design work? Would I need to include our data protection officer during solution finding?

Once the problem space is defined with a large code base, a new feature will likely have functionality that touches areas or components that should be considered in building out the scope for the development effort.

I created this artifact to aid in scope framing, but where it really shines is in highlighting the less glamorous requirements involved in scoping a well-rounded solution. This framework's objective is to help ask you questions about what you need to consider and take the load off keeping it in your head with a place to document it.

This artifact is useful in that others can get a glimpse into how multi-faceted a feature can be, how feature work should be considered, and the ripple effect that even smaller feature work can have. It helps you to think holistically about problems spaces because it can be used at different altitudes. From initial prototypes, a product bundle improvement, MVFs to MVPs, it can help you in considering (or just plain remembering) the various areas that could be impacted or that require additional thinking.

Permissions and data protection, for example, can be missed in the fervor of a nifty interface. Analytics are not considered when seeking a new API endpoint, etc.

Your customers will certainly appreciate the great UI, but those data admins will love that you understood the need to permission lock it to a smaller set of their users.

As an individual contributor, it can help bring a well rounded approach in considering the different areas your work will touch. As part of a team, it can help build pattern thinking around execution.

In hiring, new PMs can get an idea of feature reach and the areas at play.

You can tailor each section here to match your internal requirements. This artifact is meant to be sculpted to streamline your considerations. For example, imagine that you’re making changes to a certain area, and this process requires both a security review and confirmation from other stakeholders. These considerations could be broken down into their own section. Or if you’re working at a PLG org, you might want to add sections to clarify how the MVF would be made available across tiers, as well as if it would be part of a free trial or not.

Dan Szymczak

I use this canvas at the initial stage of thinking through an initiative or feature. It helps scope framing and emphasizes the less obvious requirements involved. 

The SaaSy Product Execution Canvas at Engaging Networks

Sign up to see more