StudioPass — Focusing Assumptions Before Testing

My previous article gave context to what I describe as StudioPass’s ‘Critical Incident’ — or in other words, how the idea came to be. In following on with the story, it’s important to narrow down on the assumptions we are making before we begin testing. The overall problem StudioPass is addressing and the value propositions for each user are two I’m going to define now and will form the basis of user testing when we begin interviews next stage.

OUR PROBLEM STATEMENT (assumption):

Strength and Conditioning coaches want more work and gyms have the opportunity to rent excess inventory.

Three users that must be satisfied to help address problem statement above.

  1. Gyms
  2. Strength and Conditioning coaches
  3. StudioPass

USERS & VALUE STATEMENTS (assumptions): At the end of each ‘value statement’ sentence, I’ve included a couple of points that could falsify our value assumption. It’s important to consider “how might we be wrong?” in each case. This will also become useful when asking follow up questions during interviews.

1. Gyms can increase revenue by renting their excess inventory to Strength and Conditioning Coaches at particular times throughout the day.

If true, what is their level of motivation to do this? How much ‘opportunity cost’ would warrant action?

2. Strength and Conditioning coaches can acquire more work and additional income through StudioPass.

If true, do they have clients to coach (through gym or network? Do rent times align with S&C coaches and clients?

3. StudioPass can create a successful business by building a product that satisfies both sides of this marketplace.

If true, what level of users (critical mass) defines success? Is it sustainable over time?

Now we’ve defined our problem statement and three user value statements with ‘how might we be wrong?’, it’s time to begin the testing process. We will start be interviewing Joe Agresta, Coach and Co-Owner of ‘Science of Fitness’ gym. Oh also.. he’s a Lululemon Ambassador… Until then.

DevShed..