Initial Design Artifacts and Market Research Validation Criteria

First iteration of design and how we’re using defined criteria to help identify markets

The first big thing to talk about for this week is how we’re looking to identify markets to pursue using a set of criteria that, if met, indicate that that market has a potential fit for Zensors. To develop these criteria, we took a look at the basics of what is needed for any market fit (eg money to purchase, people to use it) and things we know will be better if the market possesses like an appetite for actionable data that maps to Zensors core functionality.

Below is the matrix (or Pugh chart) we developed along with weights we’ve assigned to each criterion. While we developed the criteria based on our own research, we worked with our client to assign the weighting.

Note the star ratings that indicate overall weights.

Designing on Assumptions

This is a risky endeavor, but based on our knowledge of the Zensors product, where it would be going, and the strengths of its functionality, we felt pretty confident that the following areas would be ones we could start designing, validating, and iterating on while we continued our market research:

• Setup
• Query creation
• Insight gathering

With the setup, we knew that there would be certain steps that users would need to take and that the system would need to accommodate, even if there would also need to be different levels of permissions. Making sure cameras are calibrated and connected, setting permissions, setting payment, etc. would all need to be thought through at some point and, regardless of the specific vertical, we could start putting some scaffolding for these things in place.

Task flow for setting up a system with multiple cameras.

Like setup, query creation, or the formation and validation of a question or set of questions is a core part of the Zensors offering. While the experience may evolve into one in which Zensors handles the bulk of the lifting, there will need to a phased approach to these features with the initial design mapping more closely to existing functionality and processing. Eventually, once more data is collected from users and successful applications, features that integrate more intelligence and assistance for users to leverage could provide an even better experience.

Task flow draft for question or query creation.

Finally, the feature set that is built on the most assumptions, insight gathering. With this set, we know that users will need to do this, but who the user is, how they relate to Zensors in terms of access to the platform directly or indirectly remains to be seen. What we do know is that while Zensors enables the collection of data, the transformation of that data in an actionable finding or insight is one that must happen somehow, regardless of where it happens.

The riskiest task flow in terms of research backing, this illustrates how a user might interact with Zensors to access information they can use to take action.

After reviewing our task flows with the client, we looked at potential places for refinement and look forward to integrating this feedback into our initial design work, to be validated early next week.