1. Mapping Our Assumptions
We organized our assumptions into a Product Assumption Risk Map, using two dimensions that represent our product’s core value propositions:
- Team Alignment & Visibility: Shared context, clear ownership, and aligned priorities.
- PM Efficiency & Coordination Automation: Less manual coordination, more time for strategic work.
We then categorized assumptions by risk, prioritizing those that could most fundamentally undermine our product’s value (image in Canvas Submission). These issues have less potential evidence, but the experiments carried out in the test cards would generate the evidence for us.
Our highest-risk assumptions are:
- Teams will adopt another centralized workflow. Even if our product provides value, whole teams must be willing to incorporate another tool into their existing processes. (Viability assumption)
- Teams are willing to consistently document and track requirements, scope, and feedback. Our product depends on teams maintaining structured information, but this requires an upfront and ongoing behavioral commitment. (Desirability assumption)
- Visibility improves team alignment without creating surveillance. We assume that centralizing project information will help teams develop a shared understanding of priorities, ownership, and progress that is unobtrusive to individual members’ workflows. ()
2. Test Cards
We designed three experiments to validate the underlying behaviors and value propositions.
Test Card #1: Project Visibility Improves Team Alignment
We believe centralized project visibility improves team alignment by helping team members develop a shared understanding of project priorities, responsibilities, and progress.
To verify, we will divide participants into teams and give each team a simulated project scenario with distributed information, competing priorities, and overlapping responsibilities.
We will measure the time required to reach agreement, the number of conflicting assumptions or duplicated responsibilities, the accuracy of team members’ understanding of project status and ownership, and the frequency of proactive information-sharing and clarification between team members.
We are right if teams using the centralized dashboard reach decisions faster, demonstrate fewer conflicting assumptions, and achieve greater consistency in their understanding of project status and ownership than the control group, without a meaningful decrease in proactive communication or increase in perceived surveillance.
Test Card #2: Teams Will Consistently Document Project Information
We believe teams are willing to and will consistently document and track requirements, scope, and feedback.
To verify, we will interview PMs and team members about their current documentation practices and conduct a diary study in which they record how they manage requirements, scope changes, and incoming feedback over one week.
We will measure the frequency of documentation, the percentage of feedback captured, and the perceived effort required to maintain records.
We are right if teams already demonstrate a consistent need to document these activities, capture most relevant feedback, and express willingness to maintain a centralized record.
Test Card #3: Teams Will Adopt Another Tool into Their Workflow
We believe teams are willing to incorporate another tool into their existing workflows if it provides sufficient value in coordinating project work.
To verify, we will invite teams to use our v0 prototype to manage a simulated or active project over a defined testing period. We will provide an initial introduction but allow participants to independently explore and incorporate the product into their workflows.
We will measure the percentage of invited users who activate the product and complete core workflows, the frequency of repeat usage, the proportion of team members who contribute project information, and whether teams independently return to the product to manage ongoing project activities.
We are right if at least 70% of invited users complete a core workflow, a majority independently return to the prototype during the testing period, and multiple team members actively contribute to shared project activities. Additionally, teams should demonstrate willingness to incorporate the product into their existing workflows rather than using it solely for the purposes of the experiment.
3. Connection to Reading
Jill Lepore’s The Disruption Machine offers a useful lens for evaluating our project, challenging the assumption that technological innovation necessarily constitutes progress. While AI may accelerate workflows such as documentation, ideation, and task coordination, efficiency alone does not establish that it makes product teams more effective. For example, our product relies on teams developing the behavioral habit of consistently documenting, revisiting, and reflecting on their decisions rather than simply moving faster through existing workflows.
