Demo: Drafting Problem Scenarios, Alternatives, and Value Propositions

In this demo, we’re going to look at how to setup these trios of problem scenarios, alternatives, and value propositions. So we have a nice testable formulation of what’s valuable to the customer that we can use to drive forward to user stories and testable implementations. I’m going to go into this table that you’ll see right after your persona. And we’ll draft our first problem scenario. This is about reference documentation on the job. Trent, the technician, being able to find the references that he needs with the documentation. Finding the right documentation references for HVAC equipment on the job site is difficult. The material on hand is inconsistent and hard to search and index.

The current alternatives is, we think that they print out the documentation they need before going on the job.

And they use a kind of dated and limited documentation system on a handheld device they have. And our value proposition, we believe, is that we will have all the documentation they need in a portable format consistently indexed and searchable. Okay, why don’t we do one more just to make sure that you’re comfortable with this. We know that getting parts on site is kind of hard so we’ll write that one up. Getting parts on jobs is difficult.

The visibility on when they can get a part and even identifying the part often takes a lot of calls and waiting. The current alternatives are, they call the office and sometimes they’re using text messages which is a little better.

We will make part pricing and availability accessible online with highly usable searching. Okay, the other think I mentioned is that we may want to add bookmarks to some of these. To do that, so we can refer back to them for instance in our agile user stories. To do that, you just go here to Insert Bookmark and you’ll see this bookmark here that you can now link back to in the rest of your document.