MIS - 6

Welcome to week six. Now that you've

defined your MVP and started building

your prototype, it's time to get clear on what you still

need to learn. This week, you'll write

a short testing plan that outlines your

riskiest assumptions and how you'll know if

your MVP is working. Every MVP is built

on assumptions, about what

users want, what they'll do, and

what they value. Your job is to identify

which assumptions matter most and figure

out how to test them. For this assignment,

you'll write a one - to two-page APA

-formatted Word document. You'll list two to

three key assumptions, describe how

you'll test each one, and define the

metrics or behaviors that will help you

measure success. Choose clear, testable

metrics that connect to real behavior,

like whether users click, complete a task,

or express interest. Avoid vanity metrics like downloads or

vague feedback. This plan will shape your validation strategy

and help you learn faster with

fewer resources.

Introduction

This assignment helps you prepare for validation by turning vague ideas into testable learning goals, grounded in metrics that matter.

Review the following video for this assignment (Transcript attached)

Instructions

Draft a one- to two-page APA-formatted Word document that outlines your plan for testing the riskiest assumptions behind your MVP. You’ll identify what you still need to learn about your product and explain how you’ll define success if your MVP performs as intended. Your paper should include the following.

1. Top Assumptions to Test - List 2–3 key assumptions you still need to validate in order to move forward with confidence.

· These could relate to customer behavior, willingness to adopt, perceived value, or usability.

· Clearly describe what each assumption is and why it's important.

2. Testing Plan - For each assumption, explain how you plan to test it using your prototype or MVP.

· What kind of interaction, observation, or feedback will help you learn?

· Will you use interviews, usability tests, surveys, “fake door” tests, etc.?

· What signal or result would count as validation (or invalidation)?

3. Success Metrics - Describe what success looks like for your MVP.

· What key metric(s) will you track (e.g., task completion, time on task, interest clicks, sign-ups)?

· How will those metrics help you determine whether the product is delivering value?

Tips for Success

· Use clear, testable language—avoid vague goals like “see if people like it”.

· Make sure each test links directly to one of your assumptions.

· Choose realistic, observable signals for success based on your prototype.

· Keep the focus on learning—not launching.